Invalid user on ODBC connection

[jdupre]

I just installed Peachtree Complete Accounting 2010, with the database on a server. I went through the steps found in the Peachtree knowledge base to create an ODBC connection. In Peachtree I enabled all users access to the database using the "Crystal" username. However, everytime I attempt to create an ODBC connection, I get the following error:

Logon Failed. Details: 28000:[Pervasive][ODBC Client Interface][LNA][Pervasive][ODBC-Engine Interface][Data record Manager]Invalid user authorization specification.

Before I deployed version 2010 for the whole company I tested it on my local machine and I was able to run my custom reports (via Crystal Reports Pro v10). Now that the database is on a server, it fails.

Peachtree support was unable to help. Can anyone here shed some light on the matter?

[Marques Ward]

Check the user settings and make sure your login has permission to use Crystal. I think you need your peachtree login to have access to Crystal It worked as single user before you addedusers? Also, did you download the crystal update? Can you run regular (canned) Crystal Reports?

[jdupre]

I set Crystal Repoorts/Data Acess to "anyone" in Peachtree, which supposedly uses the special username "Crystal" without any password.

Before I deployed v2010 on the network, I installed it on a stand-alone machine, converted the database (also local on this computer), created the ODBC connection and it worked. When I installed the datbase on the server, it does not.

The difference is that the ODBC driver used is different if you have the database on your local workstation vs on a server.

This has nothing to to with Crystal Reports per se. This is an ODBC connectivity issue. The error indicates that Pervasive is not accepting the user "Crystal" that is passed by the ODBC driver. (The test connection button in ODBC setup fails. This is why I believe it is not a Crystal Reports issue.)

[jdupre]

So, I tested a connection on the sample database and it worked fine. Thus, something was messed up with our database. A backup and restore solved the problem.

[Marques Ward]

In case you have a similar problem, Peachtree says this about the password:

Select who can access company data from Crystal Reports, OLEDB, and ODBC:
• No one: Access is denied for all users.
• Only one user: Select one user that can access the database.
• Anyone: Any user can access the database. If this option is selected and the user is prompted for login information in the ODBC/OLEDB application, the default user name is Crystal and the password is left blank.