/build/static/layout/Breadcrumb_cap_w.png

ISScript 11 problem on Windows 7

hi all,

i have an application that i'm trying to install before creating my installation package. it's called CA Technologies Identity Manager.

the app came as an vendor msi.

under Windows 7, i can't install it. as soon as i start the installation, after the "please wait" initial screen, i got a message that the installation has failed.

ISScript is needed for the application. i run the installation as the admin account.

can someone tell me what is wrong here?

here's the relevant part of the log file i generated.

MSI (c) (E0:00) [11:24:34:688]: Doing action: ISMsiServerStartup
Action 11:24:34: ISMsiServerStartup.
Action start 11:24:34: ISMsiServerStartup.
MSI (c) (E0:00) [11:24:34:688]: Note: 1: 2235 2: 3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'ISMsiServerStartup'
Action ended 11:24:34: ISMsiServerStartup. Return value 1.
MSI (c) (E0:00) [11:24:34:757]: Doing action: ISStartup
Action 11:24:34: ISStartup.
Action start 11:24:34: ISStartup.
MSI (c) (E0:00) [11:24:34:757]: Note: 1: 2235 2: 3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'ISStartup'
MSI (c) (E0:0C) [11:24:34:817]: Invoking remote custom action. DLL: C:\Users\ADMINI~1\AppData\Local\Temp\MSIA040.tmp, Entrypoint: MsiServerStartup
MSI (c) (E0:04) [11:24:34:817]: Invoking remote custom action. DLL: C:\Users\ADMINI~1\AppData\Local\Temp\MSIA08F.tmp, Entrypoint: StartUp
MSI (c) (E0:48) [11:24:34:891]: Cloaking enabled.
MSI (c) (E0:48) [11:24:34:891]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (E0:48) [11:24:34:891]: Connected to service for CA interface.
1: The InstallScript engine version currently installed on this machine is adequate.
1: Event 'E24351' is created
MSI (c) (E0!38) [11:24:35:001]: PROPERTY CHANGE: Adding ISStartupEvent property. Its value is 'E24351'.
1: GetInstallDriver, Can not find InstallDriver in ROT table, Return Code = 0x80004005
1: {65CC05AD-6F46-45DF-BED0-E121E75067B0}
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 = 0x80010105
1: MsiServerStartup failed. Abort installation.
CustomAction ISStartup returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Action ended 11:24:35: ISStartup. Return value 3.
MSI (c) (E0:00) [11:24:35:962]: Doing action: SetupCompleteError
Action 11:24:35: SetupCompleteError.
Action start 11:24:35: SetupCompleteError.
MSI (c) (E0:00) [11:24:35:962]: Note: 1: 2235 2: 3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'SetupCompleteError'


thanks!

0 Comments   [ + ] Show comments

Answers (6)

Posted by: anonymous_9363 13 years ago
Red Belt
0
As ever, there is a ton of stuff about this in the archive. Search for 'ROT table'.

Once you've fixed your MSI, get all the IS engines and drivers included in your build. There's no harm in adding them to your packaging box, too.
Posted by: AngelD 13 years ago
Red Belt
0
Check out the section "Summary of InstallShield InstallDriver DCOM Identity problem" at http://www.appdeploy.com/messageboards/fb.asp?m=19850
Posted by: kardock 13 years ago
Second Degree Green Belt
0
yeah i know, but i forgot to mentioned that i've already made a search for this. i didn't find anything to fix my problem though.

the DCOM identity problem is not present on my test computer, the "launching user" is correctly set.

ProcMon is not helping either.

the fix about editing the msi to skip the setup.exe run does not work, i use the msi.

etc...

i've done all i could find on appdeploy search, i was hoping for more help!

i've tried this too: script

thanks!
Posted by: jmaclaurin 13 years ago
Third Degree Blue Belt
0
Sorry, but this isn't going to help much with the packaging, but I remember this app. I guess it was a good thing in the end because so many directors and vp's screwd up their passwords and were locked out so often that they gave us the go ahead for a single sign on project for LDAP integration/authentication.



Good luck...
Posted by: anonymous_9363 13 years ago
Red Belt
0
Closer scrutiny of the log shows something which I think is significant.(38) [11:24:35:001]: PROPERTY CHANGE: Adding ISStartupEvent property. Its value is 'E24351'. 1: GetInstallDriver, Can not find InstallDriver in ROT table, Return Code = 0x80004005 Error 80004005 translates to decimal '5' - Access denied. I suspect the registry branch is permissioned somehow to exclude even administrators.
Posted by: kardock 13 years ago
Second Degree Green Belt
0
do you sometimes feel like you would like to kill someone?

i'm dealing with this vendor's support and since the beginning, they ask me to use the SP6 of their product. i just received this:

Hi Daniel,

You mentioned that you are on SP6, from my research, the Credential Provider was not certified with Windows 7 until SP7.

Are you running Win7 SP1? Then you would need 12.5SP9.


2 weeks efforts thrown in the garbage.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ