This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Error 1904: registering dll, in win7/win2k8 64 bit
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 11, 2010
06:48 PM
Error 1904: registering dll, in win7/win2k8 64 bit
When we moved to Win7/Win2k8 from win xp we started seeing a problem where the dlls were not registered properly and we were missing typelib information.
To workaround the issue we make a number of dll self registering. It works for all of them except for one that uses mfc. Towards the end of the installation under ISSelfRegisterFinalize we receive this error message "Error 1904.Module failed to register. HRESULT -2147220473"
After searching with the error code it turns out to be a generic registration failure. A bit googling reveals a lot of other application sees this and the workaround is to run regsvr32 manually but why it happens is not explained properly anywhere.
If we manually run regsvr32 to register, it works and typelib information appears correctly in the registry but this inconvenient for our customer. It only fails when InstallShield tries to do it automatically.
In the log file I also noticed an error message "Error extracting ISBEW64.exe from ISRegSvr.dll" and was wondering what causes this and if it has something do with problem. Any information is appreciated.
To workaround the issue we make a number of dll self registering. It works for all of them except for one that uses mfc. Towards the end of the installation under ISSelfRegisterFinalize we receive this error message "Error 1904.Module
After searching with the error code it turns out to be a generic registration failure. A bit googling reveals a lot of other application sees this and the workaround is to run regsvr32 manually but why it happens is not explained properly anywhere.
If we manually run regsvr32 to register, it works and typelib information appears correctly in the registry but this inconvenient for our customer. It only fails when InstallShield tries to do it automatically.
In the log file I also noticed an error message "Error extracting ISBEW64.exe from ISRegSvr.dll" and was wondering what causes this and if it has something do with problem. Any information is appreciated.
(6) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 15, 2010
09:13 AM
Are you having the problem with a 64-bit executable? If so, make sure that you set the 64-bit Component setting to True for the component that installs the file in question.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 15, 2010
12:44 PM
Jazaman,
I had a similar problem when I moved to Win 7 to do my IS Builds. Had to turn on UAC (at least 1 level up from min) on my IS Build box to get TypeLibs to work.
See this post.
http://community.flexerasoftware.com/showthread.php?t=192471&highlight=typelib
I had a similar problem when I moved to Win 7 to do my IS Builds. Had to turn on UAC (at least 1 level up from min) on my IS Build box to get TypeLibs to work.
See this post.
http://community.flexerasoftware.com/showthread.php?t=192471&highlight=typelib
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 23, 2010
07:36 PM
hidenori wrote:
Are you having the problem with a 64-bit executable? If so, make sure that you set the 64-bit Component setting to True for the component that installs the file in question.
This is not a 64 bit component. This is a 32 bit dll I am trying register automatically.
I followed the example form 'rguggisberg' and enabled the UAC. Now when I am trying to build I am receiving the following error:
Extracting COM data from 8 component(s)
ISDEV : fatal error -6017: Internal build error
Any clues anyone?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 24, 2010
08:36 PM
rguggisberg wrote:
Jazaman,
I had a similar problem when I moved to Win 7 to do my IS Builds. Had to turn on UAC (at least 1 level up from min) on my IS Build box to get TypeLibs to work.
See this post.
http://community.flexerasoftware.com/showthread.php?t=192471&highlight=typelib
Changed the UAC level and now the packaging is failing with "ISDEV : fatal error -6017: Internal build error".
Any clue is appreciated.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 24, 2010
09:32 PM
rguggisberg wrote:
Jazaman,
I had a similar problem when I moved to Win 7 to do my IS Builds. Had to turn on UAC (at least 1 level up from min) on my IS Build box to get TypeLibs to work.
See this post.
http://community.flexerasoftware.com/showthread.php?t=192471&highlight=typelib
Changed UAC level as suggested but now I cannot package at all. It is giving me the following error message:
Extracting COM data from 8 component(s)
ISDEV : fatal error -6017: Internal build error
Any information is appreciated.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 25, 2010
09:26 PM
rguggisberg wrote:
Jazaman,
I had a similar problem when I moved to Win 7 to do my IS Builds. Had to turn on UAC (at least 1 level up from min) on my IS Build box to get TypeLibs to work.
See this post.
http://community.flexerasoftware.com/showthread.php?t=192471&highlight=typelib
I followed your suggestion but I could not package anymore. Whenever I try to start packaging it is giving me the following error:
"Extracting COM data from 8 component(s)
ISDEV : fatal error -6017: Internal build error"
