Crystal Report 7 with Access 97 giving Error - 20536

[Former Member]

Our client is getting an error at his machine.

Application is in VB 6.0 with Access 97 as database and while generating reports,it gives error "Runtime Error 20536 Unable to Connect: Incorrect Log On Parameters" .Report version is Crystal Report 7.

Also client has Win XP sp3 OS.

This error was not reproducible at our machines which has the same OS.

Please if anyone could help in this regard ,that will be really great.

[Former Member · Accepted solution]

Hello,

Crystal Reports 7 is ancient, and the OCX (crystl32.ocx) component has been retired after CR8.5. I'm surprised your application would work at all. Service Pack 3 for XP was released in 2008, so there's no expectation that CR7 would work in that environment. It's possible that something changed that impacts the running of your client application. Since you have it working on a test machine at your end it's probably not OS related, but it still possible since CR7 was never tested on XP SP3.

Was the application working previously on the client machine? If yes, what changed?

If not, the error message for the OCX is usually accurate, so you'll want to focus on the database connection. "Incorrect Logon Parameters" usually means just that. You didn't say how your report connects to the database - ODBC, OLE DB, etc.. If your application uses an ODBC DSN check it to make sure it's correct - no typo in the name, system DSN (not file or user), confirm that the user's credentials actually does have access to the DB. Is the Access DB accessible from the client machine?

Sincerely,

Dan Kelleher

[Former Member · Accepted solution]

Hello Dan,

Thanks for your response.

Application also works on my machine with XP SP3 and also on our test machine so it was a surprise to know that CR7 was not tested on XP SP3.

Our application is loaded on to this client machine for the first time so there is no history of the application,if it was working or not.

Our connection type is OLE DB ,so what I can check to see ,what caused this problem?

Also ,are there any dlls with the absence of which this error might have caused ?

Thanks for your help.

Prachi

[Former Member · Accepted solution]

Hello Prachi,

Crystal Reports 7 reached End of Life for patch support in August, 2002. CR7 was released in 1998 - long before the XP operating system was released. Back then Crystal Decisions rarely went back and added OS support for the older versions of Crystal Reports. There weren't major changes to Windows until Vista/Win7, so that's probably why it's working on your machine.

The KB article links that don't work can be found with manual searching. You can go to [http://service.sap.com/support|http://service.sap.com/support], click on the Help & Support link, and then click on the SAP xSearch link. Use the "C-number" listed in the document in the Search For field and click on Go. The KBA that corresponds to that particular "C-number" will have that "C-number" in the Keyword section of the article. Other articles may reference that "C-number" so your search may return more than one result. It is unlikely that the document with the links will be updated due to its age.

You can use a utility called Modules to see if you can find any DLL differences between the working and non-working machine. You can download it from SAP at this link: [https://smpdl.sap-ag.de/_{sapidp/012002523100006252802008E/modules.zip|https://smpdl.sap-ag.de/}sapidp/012002523100006252802008E/modules.zip]. There are instruction in the ZIP archive. Run the utility on the non-working machine and the working machine. Save the two results and then compare them and address any differences.

I'm rusty on database connectivity issues so perhaps Ludek or someone else can throw in some additional suggestions related to OLE DB connectivity.

Sincerely,

Dan Kelleher

[Former Member · Accepted solution]

Hello Dan,

Thanks for such a useful response.

I used the module utility that you suggested and it runs smoothly and displays all the dependancies on my machine for the application.

I will be forwarding this to my client to check the differences.

i will let you know the result of the same.

As you stated if Ludek can help me in regard to

OLEDB that also will be helpful.

Also will go through the knowledge base articles.

Thanks again

Prachi

Edited by: Prachi_RK on Sep 30, 2011 9:13 AM

[former_member183750 · Accepted solution]

Seeing if you can connect to the datasource using UDL may also be helpful

- Ludek

[Former Member · Accepted solution]

Thanks for all your inputs.

I have sent the modules utility to my client.

I hope we will solve the issue at the earliest,will let you know regarding the solution.

[Former Member · Accepted solution]

Tried the module utility but in vain.The files missing,shown by the utility, were there at the client machine.

No solution still.

If any other solution ,please respond.

[Former Member · Accepted solution]

Hello Prachi,

If I understand your reply the modules do show a difference. Is this correct? If the modules show differences on the client machine that means they were not loaded by your application. It doesn't really matter if the "missing" files really are on the client machine. It's more important to know why the files didn't get loaded by the application.

What files showed up as "missing" or different? That might point to what is going on.

Sincerely,

Dan Kelleher

[Former Member · Accepted solution]

Sorry for the late reply.

The files missing were :

1.VBAJET32.DLL

2.MSJTES40.DLL

Let me know if there is any finding.

Thanks

Prachi

[former_member11696 · Accepted solution]

CR 7 used the native JET DB engine to connect to Access tables. I believe Windows stopped supporting that driver in current OS's.

Create a System ODBC DSN and set location using the new DSN then it should work.

It's an issue with MDAC. Go to MS's site and you can find a utility that can check the version of MDAC installed. Either youa re still using an older one or your customer is using a different version.

Modules show CR versions are the same but the Windows files are missing or outdated.

Post to MS's forums and ask MS if Access 97 supports using the Jet engine.

Don

[Former Member · Accepted solution]

I have shared your response with the client and are waiting for their answer.I will share the same when I get it.

Thanks

[former_member11696]

Moved to Legacy SDK forum

[former_member183750]

See if these articles help:

[Crystal Reports ActiveX (OCX) and Access FAQ|http://www.sdn.sap.com/irj/boc/index?rid=/library/uuid/70fbc1cc-751e-2b10-1e98-ae9b3df95c0f]

[Troubleshooting Database Errors When Using Crystal Development Tools|http://www.sdn.sap.com/irj/boc/index?rid=/library/uuid/e03402d5-651e-2b10-8892-aa7e112cd949]

Ludek

Follow us on Twitter http://twitter.com/SAPCRNetSup

Got Enhancement ideas? Try the [SAP Idea Place|https://ideas.sap.com/community/products_and_solutions/crystalreports]

[Former Member]

Thanks for your response.

The links you mentioned are good ,but the links that are pointed for 20536 are not working.

If you could let me know some active links ,that will be good.

Thanks again.