Error in File - Unable to connect: incorrect log on parameters.

[Former Member]

I am running a WPF app using a SQL Server 2005 backend. My reports are built into my solution and are written using Crystal Reports 2008.

A client has a machine that returns the following error when they try to run a report from within the application:

Error in File temp_da4aaac3-0a6b-49d9-ba60-9890a220645f {75EA372F-D154-43CD-8C02-E935EA03C6A4}.rpt:

Unable to connect: incorrect log on parameters. (System.Runtime.InteropServices.COMException (0x8004100F):

Error in File temp_da4aaac3-0a6b-49d9-ba60-9890a220645f {75EA372F-D154-43CD-8C02-E935EA03C6A4}.rpt:

Unable to connect: incorrect log on parameters.

at CrystalDecisions.ReportAppServer.Controllers.ReportSourceClass.GetLastPageNumber(RequestContext pRequestContext)

at CrystalDecisions.ReportSource.EromReportSourceBase.GetLastPageNumber(ReportPageRequestContext reqContext))

This report runs fine on all of the other 4 client machines.

Can someone give me a clue as to why this report runs on all of my client machines except one?

Regards,

Joe Rich

[Adam_Stone · Accepted solution]

Its a matter of figuring out what is different between the working and non-working clients. Since the error is database related, I would expect it may have something to do with the database drivers possibly missing.

You can use our modules utlilty available [here|https://smpdl.sap-ag.de/~sapidp/012002523100006252802008E/modules.zip] to get a listing of all dll's being loaded on each machine and then do a comparison.

[Former Member · Accepted solution]

Further information......

The reports are integrated into my application and use the same database connect string that my application uses. My application is able to read/write to the database with no trouble. On this one client machine, the application connects successfully, but the Crystal reports do not.

So that rules out drivers as far as I can tell.

Thanks for the tip on the Modules tool. I will run it and see what might be the difference...

[Former Member · Accepted solution]

One more problem, the url you directed me to

https://smpdl.sap-ag.de/~sapidp/012002523100006252802008E/modules.zip

will not bring up a web page. So access to the modules utility is moot.

Thanks

[Former Member]

I found the answer to this problem a couple of months ago. My reports are "pull reports". That is, they use a stored proc to provide the data. When the reports were created, I selected SQL Native Client as the provider to be used to connect to my SQL Server database. This works great, *EXCEPT WHEN THE CLIENT MACHINE DOES NOT HAVE SQL Native Client installed.* When this condition occurs, Crystal throws a "check engine light" error. Logon Failed, etc.

The solution is to redeploy the proper MDAC on that client, making sure that the SQL Native Client provider is installed.

[former_member183750]

Hello Joseph:

Many thanks for sharing the solution with the community. I think the solution is what Adam aluded to in his post on May 7, 2010.

For those reading this thread, also see the following:

[Troubleshooting Guide to Database Connectivity Issues with Crystal Reports in Visual Studio .NET Applications|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/b0225775-88c4-2c10-bd80-8298769293de]

And of course, don't forget to search the forums and KB:

https://www.sdn.sap.com/irj/scn/advancedsearch?cat=sdn_ossnotes&query=&adv=true

Ludek

[steve_norton]

Moving to the CR .net sdk forum.