This application use CTL3D32.DLL which has not been correctly installed.

[former_member601368]

Hi CR Gurus,

I am using both CR V10.0.0.533 and CR2011 on my windows 7 PC to access a RocketData D3 database via their ODBC driver. Both suffer from the same problem when running a particular(ly complex) report. Simpler reports have no issue, but his particular report with plenty of shading, formulas and sub reports poses a problem. I must say from the outset, the problem only occurred a few days ago after making some changes to one of the 2 sub reports. Prior to this it had no issues (even with the shading, formulas and sub reports). I can edit the report quite happily, but when I try to run it I get the following error message:

This application use CTL3D32.DLL which has not been correctly installed. CTL3D32.DLL must be installed in the Windows system directory.

I have searched high and low for a definitive solution to this problem but have come up empty handed. I have checked and the dll IS installed in both the System32 and the SysWow64 folders, albeit they are a slightly different version. I cannot simply copy one over the top of the other as windows won't let me. I have used SysInternals ProcMon to try and see what CR is up to when the errors occurs, but am no wiser for it. I did notice however CR tries to read the ODBC settings from 2 different locations in the registry which I find rather odd. It finds the settings in one location, but not the other. This could just be a red herring, I don't know.

I have also tried to reinstall CR10 to no avail. I have also reinstalled the D3 ODBC drivers to no avail. (This itself proved to be frustratingly difficult as it also complained of missing system files, but was sorted after many hours of painstaking trial and error.)

Trying to register the dll again using regsvr32 does not work either as it complains about not being able to find the entry point and doesn't think its a valid DLL or OCX file.

Any help/insight anyone can offer would be greatly appreciated.

Regards,

Walter

[former_member601368 · Accepted solution]

To any D3, Crystal Reports Developers:

EUREKA!!!

I have found the problem and its solution…

The problem:

Our D3 account names have a period (.) in them. This makes them inaccessible using ODBC. To get around this issue, we have created Q-pointers without the “dots”, affectionately known as “dotless” accounts. Thus PSF.TEST becomes PSFTEST. When setting up the ODBC driver we specify the “dotless” account name, i.e. PSFTEST. The ODBC driver doesn’t care what we enter and simply accepts anything (text). Only at the time of connection do we find out if the account name has been correctly entered, or exists, i.e. if no error occurs, then the account name is correct (and it exists).

In our case, the “dotless” Q-pointer was missing from the MDS. This caused the system to go through the Windows 32 bit odbcad32.exe instead of the RainingData (now RocketSoftware) ODBC Parameters Manager, and of course not able to connect to the account even if I did fill in the parameters correctly.

The solution:

Create a”dotless” Q-pointer in the MDS for the “dotted” account name.

I would not have expected any non D3 CR  Developers or Support people to know of this issue.

At least now it's in the cloud for all to see (including me, when it happens the next time).

Thanks to those who tried to help. Much appreciated.

[former_member183750]

Also, you do not mention what OS you are using, but CR 10 will not support any of the current Operating Systems (e.g.; win 7, etc.). The list of supported OS for CR 10:

Win XP, WIN 2000, WIN 2003

It would be advisable to do all your testing using CR 2011 - with the latest Service Pack installed. See:

Downloads for SAP Crystal Reports and others

- Ludek

Senior Support Engineer AGS Product Support, Global Support Center Canada

Follow me on Twitter

[former_member601368]

Hi Ludek,

I did mention in the post I'm running Win7, but failed to mention it's 64bit (sorry about that). I also mentioned I tried it in both CR10 and 2011 with the same resulting error.

Regards,

Walter

[former_member183750]

Understood.

Still, use CR 2011, not CR 10 and do apply the latest updates to your CR 2011 install...

- Ludek

[former_member292966]

Hi Walter,

Can we try a couple of things?  It sounds like something in the updated subreport is causing the error. I'd like to see if we can determine if it's one of the subreports that's causing the problem. 

Make a copy of your report so we have a backup. 

Remove one subreport and see if it runs. 

If it does, open the original report again and remove the other subreport.  Does the report still run? 

If it fails with one of the subreports, we need to look at the failing subreport.  So now you can right-click the failed subreport and save it as a new report.  I want to see if that subreport can run on it's own. 

If the newly separated subreport fails with the CTL3D32.DLL error then we can have a closer look inside the subreport. 

Try that first and we'll see where we are.  It may be the extra formatting is causing the error. 

Is Windows 7 32 or 64 bit? 

What sort of formatting did you add to the subreports?  Images, linked documents? 

Thanks,

Brian

[former_member601368]

Thanks for your suggestions Brian.

I am running Windows 7 64-bit. The formatting in the report involves conditionally changing the colour of a fields font and background. I also changed the background colour of the 1st group from white to a custom blue. (The subreport originated from another report with different selection and sort criteria, hence the suppressed headers and footers.) There are no images or other linked documents in it.

I have removed both subreports from the main report and it now runs fine (although it obviously shows no data, just a header and footer). When I added the 1st subreport (as shown above, being the last one I edited), CR fails again with the CTL3D32.DLL message. So I tried to run that subreport on its own and I get the same error. This seems to indicate the problem is with the subreport itself.

Regards,

Walter

[former_member292966]

Hi Walter,

Can you run the subreports just by themselves, outside the main report?  I'd like to see if they run on their own. 

Also, do a Verify Database on both subreports.  Grasping at straws but lets see if something from the other report may be lingering in them. 

Good luck,

Brian

[former_member601368]

Hi Brian,

As per my previous reply, I had already tried to run the sub-report on its own, i.e. separate from the main report. This also caused the error. Furthermore, verifying the database causes the same error. After dismissing the error message I'm presented with the D3 Data source Connection Parameters Dialog Box. Even if I enter valid info, it won't connect and I end up with a Login Error.

Please keep in mind this was all working fine, both as an isolated report and as a sub-report in the main report. I developed the sub report as an individual report before inserting it into the main report. I'm getting the feeling the error is related to the D3 ODBC driver more than to CR itself...As I write this reply, I just tried to access the database using WinSQL and I'm getting the same error. Looks like it's not a CR issue after all... I may have been following the wrong path in troubleshooting, but it took your post to point me in the appropriate direction. I I ever find the solution to my problem I'll post a response to this thread.