[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 696
  • Last Modified:

Getting an Error 1904.Module error when installing a VB developed application that uses Crystal Reports dll

I have an application developed in VB6 that uses Crystal Reports 10.  Everything has worked fine for a year now, but recently I started getting the following error during installation:

Error 1904.Module C:\Program Files\Common Files\Crystal Decisions\2.5\bin\ReportRenderer.dll failed to register. HRESULT -2147319780

The only difference I can think of is that the machine I am installing onto recently had Office 2000 uninstalled and Office 2003 installed in its place.  Could that be creating the problem.  Any ideas as to how to resolve it?

Thanks
0
Ron_Rea
Asked:
Ron_Rea
  • 2
1 Solution
 
frodomanCommented:
I can only see that being a potential problem if you're reporting off an Access database (or otherwise using the MS Jet DB Engine).  I don't know for sure but I suspect that the Office upgrade may change the MDAC package installed on the machine.

Have you tried to manually register the dll?
0
 
Ron_ReaAuthor Commented:
Thanks for the reply, frodoman.  You are correct, I am using an Access 2000 database.  I have included merge modules for it.  Is there something else I need to include when I create the setup.exe that will remove this problem?
0
 
frodomanCommented:
I don't really know what the solution to this might be.  I checked some Microsoft documentation and the error number is a problem referencing the OLE registry.  My guess is that when Office 2000 was uninstalled there was some registry key and / or data access component that was removed or replaced.  I do know for certain that there is a huge difference in data access between Access 2000 & 2003.

Probably you could install the latest version of MDAC on your development computer then add the necessary components to your project and recompile.  I suspect that would solve the installation problem; however, there is more security overhead and considerations with remote access of an Access 2003 database so you might have some work ahead of you to get the application working again.  I'm afraid though that this may be your only option.

What you might try is to reinstall Office 2000 and see if both versions will co-exist on the same machine and if your application will work.  I suspect that it won't work because the problem is probably in MDAC and I'm certain that two versions of that can't co-exist (also an older version cannot be made to overwrite a newer version) but I can't foresee any damage from giving it a try.  You could completely uninstall Office 2003 and then reinstall 2000, but that means you're stuck staying at 2000 with no upgrade path.
0

Featured Post

Important Lessons on Recovering from Petya

In their most recent webinar, Skyport Systems explores ways to isolate and protect critical databases to keep the core of your company safe from harm.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now