newbie - Wise Packager .dll registration issues
I am newbie trying to repackage .exe to MSI. I haven't used any of WISE products before and this is my First attempt to repackage .exe using WISE.
I am using Wise Package Studio 7.0 SP2.
I am using Setup Capture to create a MSI file with out any issues. When I deploy the MSI file during the installation I get these error messages regading .dll registration
Error Message "Error 1904. Module C:\Program Files\NetScreen\jre\bin\NPOJI610.dll failed to register. HRESULT -2147220991. Contact your support personnel.
MSI (s) (E8:74) [10:17:20:374]: Product: NetScreen -- Error 1904. Module C:\Program Files\NetScreen\jre\bin\NPOJI610.dll failed to register. HRESULT -2147220991. Contact your support personnel."
Can you please help? I am not sure why this error message is displayed.
When the exe is executed manually on the same server there is no issues with the installation and I am logged in as Local admin while deploying the package.
I am using Wise Package Studio 7.0 SP2.
I am using Setup Capture to create a MSI file with out any issues. When I deploy the MSI file during the installation I get these error messages regading .dll registration
Error Message "Error 1904. Module C:\Program Files\NetScreen\jre\bin\NPOJI610.dll failed to register. HRESULT -2147220991. Contact your support personnel.
MSI (s) (E8:74) [10:17:20:374]: Product: NetScreen -- Error 1904. Module C:\Program Files\NetScreen\jre\bin\NPOJI610.dll failed to register. HRESULT -2147220991. Contact your support personnel."
Can you please help? I am not sure why this error message is displayed.
When the exe is executed manually on the same server there is no issues with the installation and I am logged in as Local admin while deploying the package.
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
zipsantro
15 years ago
The avobe error says the dll file needs registration. Yes it's true that the EXE will work on the server where you have taken setup capture. Basically at the time of setup capture you will install the application using .exe and all the required changes will be done to the machine.
You need to identify that you msi should have all the installation changes done by exe.
DLL registration is also one part.
I suggest you to do this manually. You can use "C:\Program Files\Altiris\Wise Package Studio\Windows Installer Editor\WiseComCapture.exe" utility to do this. Command line will be :-
-->WiseComCapture.exe C:\Program Files\NetScreen\jre\bin\NPOJI610.dll <reg file and path to create>
Now the reg file will have all the registry information required to use the DLL. Import this reg file into your MSI.
Cheers
:-) Santro
You need to identify that you msi should have all the installation changes done by exe.
DLL registration is also one part.
I suggest you to do this manually. You can use "C:\Program Files\Altiris\Wise Package Studio\Windows Installer Editor\WiseComCapture.exe" utility to do this. Command line will be :-
-->WiseComCapture.exe C:\Program Files\NetScreen\jre\bin\NPOJI610.dll <reg file and path to create>
Now the reg file will have all the registry information required to use the DLL. Import this reg file into your MSI.
Cheers
:-) Santro
Posted by:
anonymous_9363
15 years ago
Ignore the above for this file. It's good advice for other DLLs, but read on...
This file is one of the gems in the JRE which Sun insist on compiling this way. This file is one of several (6, I think) in the JRE which contain the DLLRegisterServer entry-point but which actually contain no COM information. WiseComCapture (and the equivalent InstallShield tool) see that entry-point and attempt to extract the COM information or, if you have the WRONG option set, will populate the SelfReg table (the work of the Devil).
Stop attempting to register this DLL (and its companions) because it can't be registered.
This file is one of the gems in the JRE which Sun insist on compiling this way. This file is one of several (6, I think) in the JRE which contain the DLLRegisterServer entry-point but which actually contain no COM information. WiseComCapture (and the equivalent InstallShield tool) see that entry-point and attempt to extract the COM information or, if you have the WRONG option set, will populate the SelfReg table (the work of the Devil).
Stop attempting to register this DLL (and its companions) because it can't be registered.
Posted by:
chanakya
15 years ago
Thanks mate.
Is there a way where we can identify a .dll requires registration or not before compiling the package?
You might find this as a very basic question but I would rather ask you guys now.. By using WiseComCapture.exe how can I determine the registration path of a .dll in the registry?
WiseComCapture.exe /r and /u is a rule of thumb which option to choose?
kind regards
Is there a way where we can identify a .dll requires registration or not before compiling the package?
You might find this as a very basic question but I would rather ask you guys now.. By using WiseComCapture.exe how can I determine the registration path of a .dll in the registry?
WiseComCapture.exe /r and /u is a rule of thumb which option to choose?
kind regards
Posted by:
anonymous_9363
15 years ago
I built myself a script which looks for the DLLRegisterServer function in DLLs and OCXs (and before you ask, no, I'm no longer distributing it) but, as I mentioned, that's no fail-safe guarantee. You can *sometimes* be guided by the size of the .REG file created by WiseComCapture. If it's less than 100 bytes (it will contain just a header) , try re-running WCC from the directory containing the DLL/OCX. If the size remains the same, it's probably safe to assume that there's no COM information in the file.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.