TOPIC: Database logon failed. (emailCrystalReport)

Database logon failed. (emailCrystalReport) 21 Mar 2014 19:45 #1543

  • RonMoses
  • RonMoses's Avatar
  • Offline
We're in the process of migrating our data from SQL Server 2005 to 2008 R2. We have a login set up on both servers called "report" which we use exclusively for reporting purposes. We have verified that these logins are identical between the two servers.

All of our reports (created in XI) have been working fine in Logicity against the 2005 server. We made copies of all the reports, changed their data locations in Crystal to point to the new 2008 R2 server, verified the data, and confirmed that each report works in Crystal.

However, Logicity gives the error "Database logon failed. (emailCrystalReport)" for every report run against the 2008 R2 server.

Originally, the error was...
Failed to open the connection.
Failed to open the connection.
OpenAppointments {GUID}.rpt
(emailCrystalReport)

In the course of troubleshooting, we tried creating an ODBC connection to make sure we didn't have a problem connecting to the 2008 R2 server using the report login. That worked fine, so it didn't appear to be a general connection problem from the report server. However, after we created the ODBC connection, the error message changed to the one above. (Note, we never created an ODBC connection to the 2005 server, and never had a problem with it.) Removing the ODBC connection brings it back to the original, longer error.

We upgraded to 1.7.0018 with no effect. We even rebuilt the RRD from scratch, no go. We're purchasing Pro on Monday in hopes that the log files will help.

We looked at the server logs, and all we've been able to see so far is that it looks like the wrong password is being sent in the connection string. We've more than quadruple-checked the password, including opening the RRD in Notepad, so we know it's right.

Any suggestions?
thanks,
ron
The administrator has disabled public write access.

Database logon failed. (emailCrystalReport) 24 Mar 2014 11:46 #1544

  • RonMoses
  • RonMoses's Avatar
  • Offline
SOLVED. It requires a User DSN on the report server for some reason. A system DSN will not work.

ron
The administrator has disabled public write access.