Crystal Reports Prodn Deploymt: incorrect logon parameters

[TOraptor]

My Crystal reports are being supplied the logon credentials via a C# code class that recursively loops through all the tables present in the reports and applies the login credentials (Servername, databasename, userid and password). This setup is working fine when i have it working within my domain (office network) where the server is another box (SQL svr 2000).

The login credentials are being read from a web.config file and everthing seems to be normal.

I attempted to deploy these reports to the production box(es) where the reports are on the webserver and the database is on another box. I can see the code gathers the updated server credentials. But i am getting the error incorrect logon parameters while attempting to apply the logoninfo to report's tables. I ran the SQLProfiler to check if the server was being reached at all and found the report logon function cannot even connect at all.

The port for using SQL queries 1433 is open as other queries from the webserver to db work fine. Is there anything i am missing which i should specify along with the report logon params?
Please help.
Thanks in anticipation.

Gary

 

[lyanch]

The problem is probably that the ODBC driver isn't available to the reports. They have the right credentials, just don't have anywhere to use them.

Lisa

 

[TOraptor]

Thanks for your message Lisa.
I am, however not using ODBC drivers. I am also not specifiying them anywhere explicitly. I am unsure it will should look for ODBC drivers.
I am in fact using OLE DB drivers in the report (I assume these settings are saved due to the links in these reports to a database that i tested the reports on in my local network). The database now in production env is different and myreports have not been modified to the new database. I see no reason i should have to, since my app programmatically passes the new database machine name, database name, userid and pass to the reports at run time.

This setup is working for me during the local network testing. I apply logon parameters recursively and obtain a report instance.

However the reports on the production box arent even getting to the database server. Funny since rest of the app (asp.net) talks to the server perfectly.

Gary

 

[lyanch]

Ah, I missed that you were using ADO. You will need to strip the fully qualified name from your reports or they will continue trying to send:

DAtabase.dbo.table where database is the old database.

check this recent thread on how to do this:

thread149-725740


I would test to make sure that solved your problem before I did all of them.

Lisa