cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to connect: incorrect log on parameters

Former Member
0 Kudos

I am trying to connect to a "Southware" database using a Transoft ODBC drive from a Crystal Reports Server 2008 Version 1. When I try to run the report from within CRS I get the following error: Unable to connect: incorrect log on parameters. The report will connect to the database from the report deisgner, but not from the Report Server.

The Transoft ODBC driver version is 4.30.0005. The dll is TSODBC32.dll.

Does anyone have experience with this driver in a Crystal Report Server environment and is familiar with the configuration of the driver in Crystal Report Server?

Any ideas would be appreciated.

Thanks.

Ralph

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Don:

I added the trace to the start up parameters for Crystal Reports Job Server and then restarted. I tired to view the report and then for the log, but I don't know what to look for in the log. Do you know what I should search for? It's all greek to me.

Thanks for all you guidance regarding this problem of mine.

Ralph

0 Kudos

Look at the lines where Cr tries to connect to the database, should be on the first page or possible the second page and then further down if you have subreports.

The error would show if failed to connect and why. Usually the password is empty but if it has a bunch of ***** then it's passing a password but you have to verify if it's correct.

So you are scheduling the reports correct? Did you go into the CMC and verify you entered the correct report DB logon info?

Thank you

Don

Answers (4)

Answers (4)

Former Member
0 Kudos

Don:

I tried ODBC tracing. When I started tracing and then ran the report in CRS, the log file was blank. If I started tracing and then tested the ODBC connect then I got results in the file.

Ralph

0 Kudos

Hi Ralph,

Ah, that tells us CRS can't even find the ODBC driver to know what to load.

I should ask also, in the CMC when you published the reports did you also set up the Database connection info by adding the Password? CR will not and never will keep the password.

A couple of ways to test this now. Go into the CMC and turn on tracing for the Report App Server by adding this to the command line:

"-trace - crpetrace 7"

And restart the server. Or search here and you may find a Knowledge Base article on how to enable logging without stopping the service.

Then preview the report on demand by viewing the Report instance. this will generate logs for ever report run so if you have a test server or can lock every one out for a few minutes while testing it will make things a lot easier.

For scheduled reports use the Job Server for logging.

Don't forget to remove that trace enable to the command, it will affect performance a lot.

If this doesn't help I suggest you purchase a case and work with a support rep directly.

Thank you

Don

Former Member
0 Kudos

Don:

I had unistalled CR and CRS and then reinstalled just the CRS to get back to a clean slate. I've been having this connection issue before I installed CR on the server to see if I could acutally connect to the data.

Pardon my naiveté, but I don't know how to turn on ODBC tracing. Would you mind instructing me on how to do this?

Thanks.

Ralph

0 Kudos

Hi Ralph,

Sorry but clean is not clean. MSIExec does not always uninstall everything. You may want to do it again but before reinstalling delete any registry keys and folders left over. AND the Usual WARNING about manually altering your registry.

At this point I don't think logging will help because the install may be corrupt.

It can be a pain to get tracing working some times. Click on the Tracing tab and add a file to the location. Sometimes it will create the file for you and other times it won't so you may have to create it first using notepad.

Then close the ODBC Admin down and then reopen it and click on Trace. It may work... I've never been able to get a consistent list of steps to make it work all the time....

Thanks

Don

Former Member
0 Kudos

Don:

Thanks for the reply.

I had the designer installed at one time, and was able to run the report and connect to the data without issue. I uninstalled the designer for other reasons.

The DSN is created from the system tab, and when tested will connect to the data.

I don't know how to check if the ODBC is ANSI 89 or 92 standard. I do know the database is written in COBOL and is considered a legacy database. Does this help?

Ralph

0 Kudos

Hi Ralph,

Uninstalling the designer may have broke the CRS install. Try doing a repair install for CRS. PLEASE back up everything first just in case.

If you turn on ODBC tracing the log should tell you what version of ODBC it's using.

Also from the logs run your report, it may tell you what is failing. To compare you could install CR Designer again and then run the logging while previewing in CR Designer and compare the logs for errors.

Thank you.

Don

0 Kudos

Hello,

Is CR designer installed on the server also?

Typically CR requires access to the driver from the PATH statement but I've ot heard of that driver/client before so not sure. It may simply be your DSN. How did you create the DSN, under User or System Tab? And if you test the connection does it work?

Use any third party tool to verify you can connect to the DB server from the CRS PC.

And is the ODBC driver ANSII 89 or 92 Standard? In other words is it ODBC 2 or ODBC 3?

Thank you

Don