Failed to Initialize script support - Error = 0x80070006
I am having issues with installations which require the InstallShield Scripting Engine.
I am attempting to install Macromedia Dreamweaver 8 under SYSTEM context.
The machine is logged on as a locked down domain user, and the installation is running under SYSTEM context (its a Radia installation BTW).
The MSI bombs out straight away with this message .....
[font="Courier New"]1: The InstallScript engine version currently installed on this machine is adequate.
1: Event 'E3013736' is created
1: GetInstallDriver, Can not find InstallDriver in ROT table, Return Code = 0x80004005
1: {3C2A19BE-99CA-444A-AE3A-3B56BB55420B}
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 Initialize script support, Error = 0x80070006
1: MsiServerStartup failed. Abort installation.
Action ended 08:30:16: ISMsiServerStartup. Return value 1603.
The following scenario's have also been tested .....
a) Logged on as local admin - WORKS FINE
b) Logged on as local admin but installation runs under SYSTEM context - WORKS FINE
c) No user logged on and installation runs under SYSTEM context - WORKS FINE
d) Logged on as domain user but installation runs under SYSTEM context - DOES NOT WORK
I've found some articles which refer to changing the DCOM properties on the Installshield Driver so that it starts with the launching user rather than the interactive user but the damn thing changes back to interactive user as soon as the installation is attempted again !!!
I've even tried modifying the ISScript.msi in Wise (search the registry table for RunAs and remove the Interactive User string so it launches as launching user - also set ALLUSERS=1)
Although when the driver is installed the setting is correct, but again, the minute the installation is run, the friggin' thing is set back to interactive user. GRRRRRR !!!
To ensure that no other apps could be changing the DCOM settings I started a CMD box using a scheduled task
[font="Courier New"]AT 12:00 /interactive CMD
Changed the DCOM settings to launching user and ran the MSI manually from within the CMD (under SYSTEM context). Sure enough, it bombed out and set the DCOM settings back to the original (interactive user) settings.
I don't understand why they keep changing back.
I'm fairly sure the DCOM properties are at the root of the problem but can't get the settings to persist.
Any help much appreciated, this is doing my nut .............
Thanks in advance
Chris
I am attempting to install Macromedia Dreamweaver 8 under SYSTEM context.
The machine is logged on as a locked down domain user, and the installation is running under SYSTEM context (its a Radia installation BTW).
The MSI bombs out straight away with this message .....
1: Event 'E3013736' is created
1: GetInstallDriver, Can not find InstallDriver in ROT table, Return Code = 0x80004005
1: {3C2A19BE-99CA-444A-AE3A-3B56BB55420B}
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 Initialize script support, Error = 0x80070006
1: MsiServerStartup failed. Abort installation.
Action ended 08:30:16: ISMsiServerStartup. Return value 1603.
The following scenario's have also been tested .....
a) Logged on as local admin - WORKS FINE
b) Logged on as local admin but installation runs under SYSTEM context - WORKS FINE
c) No user logged on and installation runs under SYSTEM context - WORKS FINE
d) Logged on as domain user but installation runs under SYSTEM context - DOES NOT WORK
I've found some articles which refer to changing the DCOM properties on the Installshield Driver so that it starts with the launching user rather than the interactive user but the damn thing changes back to interactive user as soon as the installation is attempted again !!!
I've even tried modifying the ISScript.msi in Wise (search the registry table for RunAs and remove the Interactive User string so it launches as launching user - also set ALLUSERS=1)
Although when the driver is installed the setting is correct, but again, the minute the installation is run, the friggin' thing is set back to interactive user. GRRRRRR !!!
To ensure that no other apps could be changing the DCOM settings I started a CMD box using a scheduled task
Changed the DCOM settings to launching user and ran the MSI manually from within the CMD (under SYSTEM context). Sure enough, it bombed out and set the DCOM settings back to the original (interactive user) settings.
I don't understand why they keep changing back.
I'm fairly sure the DCOM properties are at the root of the problem but can't get the settings to persist.
Any help much appreciated, this is doing my nut .............
Thanks in advance
Chris
0 Comments
[ + ] Show comments
Answers (0)
Please log in to answer
Be the first to answer this question
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
