ACCPAC error cannot open sql server 1

[weingartctr]

I get an error on ACCPAC - cannot open sql server when trying to print checks. Printboss is installed correctly according to printboss support. The check is not even displayed in preview and then the error appears.

This used to work but after upgrading the server from win2k to windows 2003, we had to reinstall ACCPAC and then it stopped working. Everything else in ACCPAC works incl posting transactions.

 

[Jay Converse]

Recreate your ODBC DSNs.

 

[weingartctr]

Hi, Thanks for the reply. I already did. I deleted the system dsn's and when you start accpac it gets recreated automatically.

I would like to see how the database is setup in pervasive sql server but I dont know sa or admin password.

 

[Jay Converse]

1. Pervasive doesn't use sa.
2. You absolutely need the Accpac ADMIN password before you go any further. The answer to your problem could be what's in Accpac database setup, because you changed servers.

 

[weingartctr]

Ok, I went in and recreated the company and system databases in database setup. I still get the same error in ACCPAC.

When I verify the databases, I get 0 errors. But when I click on test in the database setup, i get the following error:

[Pervasive][ODBC Client Interface][LNA][Pervasive][ODBC Engine Interface][Data Record Manager]The Btrieve file directory is invalid(Btrieve Error 35)

 

[Jay Converse]

When you create your DSNs on the server, you have to use UNC paths.

1. Delete all DSNs from the server and the clients.
2. Create new DSNs on the server via the Pervasive control center, using a UNC path.
3. Create new DSNs on the client you'll use for the next step.
4. Run Accpac Database setup, and delete the company and system databases
5. Add the system database, then the company databases.

 

[weingartctr]

Thanks for your help. Really appreciate it. I tried creating new DSNs on the control center. I am logged in as domain admin. I got the error below:

Cannot retrieve database names. You do not have sufficient access rights for the operation.

 

[Jay Converse]

Must be an RDC session. Set HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Utilities Interface\Settings\Restricted Access On WTS client to 0

 

[weingartctr]

IT WORKED!!! After I changed the restricted access setting, I was able to setup the DSN's.

Thanks so much! You are very helpful.

 

[weingartctr]

Hi, one more thing, pls. We can not seem to be able to post a/p invoices now. The user said she usually prints the invoice to screen and then it used to enable her to change the ready to post from 'No' to 'Yes" and then the "post" button should be enabled.

One thing i've noticed is the posting sequence# has been reset to 0. I checked the A/P settings but the next posting sequence is correct at 2445.

Thanks again for your valuable help.

 

[weingartctr]

My mistake. It was an access level issue and it has been fixed. Thanks again.