Jump to content


This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
Photo

Crystal Reports 9 & Win NT4


2 replies to this topic

PaulDeveloper

PaulDeveloper
  • Members
  • 28 posts

Posted 23 January 2004 - 13:39

Hi Everyone!

When I include the CR9 merge modules (license.msm, mapping.msm & rdcruntime.msm) in my IS7.04 standard project setup, it fails on an NT4 machine. The following error occurs:

Error 1904.Module C:\Program Files\Common Files\Crystal Decisions\2.0\bin\Emfgen.dll failed to register. HRESULT -2147024769. Contact your support personnel.

The verbose log is similar:
...
SI (s) (69:79): Executing op: SetTargetFolder(Folder=C:\Program Files\Common Files\Crystal Decisions\2.0\bin\)
MSI (s) (69:79): Executing op: RegSelfReg(File=Emfgen.dll,FileID=Emfgen.dll.68FCF676_98BE_41AD_8EC9_E806EEC940CB)
SelfRegModules: File: Emfgen.dll, Folder: C:\Program Files\Common Files\Crystal Decisions\2.0\bin\
Error 1904.Module C:\Program Files\Common Files\Crystal Decisions\2.0\bin\Emfgen.dll failed to register. HRESULT -2147024714. Contact your support personnel.
MSI (s) (69:79): Invoke wait timed out
MSI © (82:7E): Invoke wait timed out
MSI (s) (69:79): Product: Flightdeck -- Error 1904.Module C:\Program Files\Common Files\Crystal Decisions\2.0\bin\Emfgen.dll failed to register. HRESULT -2147024714. Contact your support personnel.
...

When I try to register this dll manually using regsvr32, I get the following error:
LoadLibrary("C:\Program Files\Common Files\Crystal Decisions\2.0\bin\Emfgen.dll") failed. GetLastError returns 0x000000b6.

I have followed the instructions in articles Q106852 and Q108650 correctly.

It works fine on Windows 98, Me, 2000 and XP!

I have also tried using a very simple setup which just installs Notepad and these merge modules, it is still the same.

Can anyone help, please?


Balachandar

Balachandar
  • Members
  • 23 posts

Posted 23 January 2004 - 14:47

Check for the dependancies. Probably the dependant DLLs are missing in NT systems.
It could be that you miss the .NET frame work.


Glytzhkof

Glytzhkof
  • Moderators
  • 1,447 posts

Posted 25 January 2004 - 05:56

Check the file that fails to self-register with dependency walker: http://www.dependencywalker.com/
Regards
-Stein Åsmul