Hello all,
we have a problem when install our msi only in windows 7 (32 or 64 bits)...
i did a lots of search, but i do not found anything that could help...
i already tried:
1) install ISScript10.msi
2) install ISScript11.msi
3) Set the DCOM identity to launching user
here we have 6 msis that have the same GUID ({0FA15315-FCA8-443A-939C-97C79BB84257}), but this msis are not registered, they just copy the files to a specific folder....
during the install, we have this scenario:
first msi - OK
second msi - ERROR
third msi - OK
fourth msi - ERROR
fifth msi - OK
sixth msi - ERROR
the log show this result:
1: Event 'E5749281' is created
1: GetInstallDriver, Can not find InstallDriver in ROT table, Return Code = 0x800401e3
1: {0FA15315-FCA8-443A-939C-97C79BB84257}
1: Extract supporting files
1: Failed to extract _IsUser.dll, Ignore it.
1: Failed to extract IGdi.dll, Ignore it.
1: ISMsiServerStartup Failure, Failed to RegisterMsiServer, Error = 0x80004005
1: MsiServerStartup failed. Abort installation.
Ação concluída 08:57:51: ISMsiServerStartup. Valor de retorno 1603.
very weird because these msis have the same GUID, and one installs ok and the other return error....
i hope that i has explained the problem...
thanks
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.

Error = 0x80004005 - windows 7
Started by
bruno_pt-br
, Feb 17 2011 19:01
5 replies to this topic
Posted 14 March 2011 - 18:00
Not sure what's going on there. First recommendation: use difefrent GUIDs for different installs. Also, make sure you wait between the installs so that any cleanup tasks are completed.
In additoin, consider using pure InstallScript if you don't use the msi functionality, or use pure "Basic MSI". Combining both technologies in "InstallScript MSI" can cause problems.
In additoin, consider using pure InstallScript if you don't use the msi functionality, or use pure "Basic MSI". Combining both technologies in "InstallScript MSI" can cause problems.
Stefan Krüger
InstallSite.org twitter facebook
Posted 14 March 2011 - 19:11
Hello Stefan,
Thanks for your help...
One time, i thought that the time between these installations could cause this problem... I will investigate this, and if I get some different result, I will tell you...
Thanks
Thanks for your help...
One time, i thought that the time between these installations could cause this problem... I will investigate this, and if I get some different result, I will tell you...
Thanks
Posted 21 September 2012 - 22:15
GetInstallDriver, Can not find InstallDriver in ROT table, Return Code = 0x800401e3
Working on an install that did the following steps:
1) Test for IDriver.exe that was installed by InstallShield 10, if it is not found then run InstallShield 10 installation.
2) Install application that needed InstallShield 10.
This was not working and would get the an error, "GetInstallDriver, Can not find InstallDriver in ROT table, Return Code = 0x800401e3".
My fix, that was recommended here.
I changed the scripted install to use a pause between the InstallShield 10 install and the execution of the application that needed to use InstallShield 10.
My working installation script now does the following:
1) Test for IDriver.exe that was installed by InstallShield 10, if it is not found then run InstallShield 10 installation.
2) Pause 50000 milliseconds (allows the InstallShield 10 installation to complete tasks I could not control with a wait command in the script)
3) Install application that needed InstallShield 10.
Maybe not a fix for all, but something to try.
Working on an install that did the following steps:
1) Test for IDriver.exe that was installed by InstallShield 10, if it is not found then run InstallShield 10 installation.
2) Install application that needed InstallShield 10.
This was not working and would get the an error, "GetInstallDriver, Can not find InstallDriver in ROT table, Return Code = 0x800401e3".
My fix, that was recommended here.
I changed the scripted install to use a pause between the InstallShield 10 install and the execution of the application that needed to use InstallShield 10.
My working installation script now does the following:
1) Test for IDriver.exe that was installed by InstallShield 10, if it is not found then run InstallShield 10 installation.
2) Pause 50000 milliseconds (allows the InstallShield 10 installation to complete tasks I could not control with a wait command in the script)
3) Install application that needed InstallShield 10.
Maybe not a fix for all, but something to try.
Posted 12 November 2012 - 11:13
Hey,
what do you mean by "run InstallShield 10" ?
Did you mean ISScript10?
Regards
Björn
what do you mean by "run InstallShield 10" ?
Did you mean ISScript10?
Regards
Björn