Hi,
I have just discovered that my installation fails on Windows Vista RC2. The installation was written under InstallShield 10.5 professional, as an "Installscript MSI project" and works properly on Windows 2000 and XP. I have recorded a log of the failure:
Action ended 12:39:41: CostFinalize. Return value 1.
MSI (c) (84:48) [12:39:41:188]: Doing action: SetServerDir
Action 12:39:41: SetServerDir.
Action start 12:39:41: SetServerDir.
Action ended 12:39:41: SetServerDir. Return value 1.
MSI (c) (84:48) [12:39:41:188]: Doing action: MigrateFeatureStates
Action 12:39:41: MigrateFeatureStates. Migrating feature states from related applications
Action start 12:39:41: MigrateFeatureStates.
Action ended 12:39:41: MigrateFeatureStates. Return value 0.
MSI (c) (84:48) [12:39:41:188]: PROPERTY CHANGE: Adding ISSETUP_UISEQUENCE_PROCESSED property. Its value is '1'.
1: Not using skins for this installation. Could not find skin file .
MSI (c) (84:48) [12:39:41:375]: Note: 1: 2262 2: ReserveCost 3: -2147287038
MSI (c) (84:48) [12:39:41:375]: Note: 1: 2262 2: DuplicateFile 3: -2147287038
MSI (c) (84:48) [12:39:41:391]: Note: 1: 2262 2: ISRequiredFeature 3: -2147287038
MSI (c) (84:48) [12:39:41:641]: Note: 1: 2205 2: 3: ISAlias
MSI (c) (84:48) [12:39:41:641]: Note: 1: 2228 2: 3: ISAlias 4: SELECT * FROM ISAlias
1: Failed to register server into ROT with ROTFLAGS_ALLOWANYCLIENT flag, error is 0x800706be, try default flag instead.
1: Failed to get register object into ROT, error is 0x800706ba
MSI (c) (84:48) [12:39:50:110]: Destroying RemoteAPI object.
MSI (c) (84:F4) [12:39:50:188]: Custom Action Manager thread ending.
=== Verbose logging stopped: 07/11/2006 12:39:50 ===
There appears to be a problem connected to the running object table. As far as I am aware, none of the components I am installing use the running object table, so I assume this is InstallShield functionality. However I have also seen other, similar, installshield installations complete successfully. I would also guess the problem may also be connected to security changes in Vista.
Any idea of the true cause of this problem and how I can fix it
Error when installing my application under Windows Vista RC2 (running object table?)
Hot Topic
- Activity Queues in Parallel
- it seems SetThreadExecutionState does not work on Vista rc1/rc2
- How to hit test non-client buttons in Vista?
- A problem with Installing VS 2005 Extension for WWF
- One qestion about yellow text on top of a graduated fill background, using this mask to modulate the opacity.
- Vista with Samba
- RichTx32 merge module
- How to call webservices in a workflow in an asynchronous way
- sAPO sample modification problem
- ATI TV audio problem - $300 offered
Windows Vista
- Host a statemachine and have multiple client applications receive events
- WWF PERSISTENCE USING ASP.NET
- Vista built-in partitioning flawed?
- How to correct the "Unidentified Publisher" message
- Attaching to a file as it is being encoded
- Workflow Designer Rehosting and XAML Workflow
- Attaching to a file as it is being encoded
- Suggestion for Samples
- How to get Vista theme's highlight color?
- LogonUser returns ERROR_PASSWORD_MUST_CHANGE
Error when installing my application under Windows Vista RC2 (running object table?)
Galin Iliev
I've tried the InstallShield forums. So far no reply. Here is the log from the admin installation:
Action ended 09:13:00: CostFinalize. Return value 1.
MSI (c) (44:34) [09:13:00:079]: Doing action: SetServerDir
Action 09:13:00: SetServerDir.
Action start 09:13:00: SetServerDir.
Action ended 09:13:00: SetServerDir. Return value 1.
MSI (c) (44:34) [09:13:00:079]: Doing action: MigrateFeatureStates
Action 09:13:00: MigrateFeatureStates. Migrating feature states from related applications
Action start 09:13:00: MigrateFeatureStates.
Action ended 09:13:00: MigrateFeatureStates. Return value 0.
MSI (c) (44:34) [09:13:00:079]: PROPERTY CHANGE: Adding ISSETUP_UISEQUENCE_PROCESSED property. Its value is '1'.
1: Not using skins for this installation. Could not find skin file .
MSI (c) (44:34) [09:13:00:266]: Note: 1: 2262 2: ReserveCost 3: -2147287038
MSI (c) (44:34) [09:13:00:266]: Note: 1: 2262 2: DuplicateFile 3: -2147287038
MSI (c) (44:34) [09:13:00:282]: Note: 1: 2262 2: ISRequiredFeature 3: -2147287038
MSI (c) (44:34) [09:13:00:579]: Note: 1: 2205 2: 3: ISAlias
MSI (c) (44:34) [09:13:00:579]: Note: 1: 2228 2: 3: ISAlias 4: SELECT * FROM ISAlias
1: Failed to register server into ROT with ROTFLAGS_ALLOWANYCLIENT flag, error is 0x800706be, try default flag instead.
1: Failed to get register object into ROT, error is 0x800706ba
MSI (c) (44:34) [09:13:09:375]: Destroying RemoteAPI object.
MSI (c) (44:F4) [09:13:09:375]: Custom Action Manager thread ending.
=== Verbose logging stopped: 08/11/2006 09:13:09 ===
nares
Did you install as Admin with full admin rights You need to start the setup by right clicking and choose Run As Admin. Or you disable UAC while installing. Don't forget to turn it on again.
--
SvenC
George2
Hi,
1628 is invalid or unknown table specified. Strange.
To get a log again, you can start cmd.exe with "Run As Admin" and call msiexec with log params.
--
SvenC
CalinMac
Did you right click the setup and choose Run as Administrator
With UAC enabled even an Admin is not full admin.
--
SvenC
DLdfrd
SteveWiggins
Did you try to get some help in the Installshield forums if they have such thing
How different is the log - just repost, maybe someone will see something in them.
--
SvenC
Can-Ann
The working installation mentioned above used the legacy installscript support, and wasn't an MSI installation. I have also confirmed that a simple Installscript MSI installation fails using vanilla InstallShield 10.5 (without service pack 1).
I haven't seen an InstallShield 10.5 InstallScript MSI project that works on Vista.
shatl
samssb
Enix591
Ok - I've now tried right clicking and running as administrator. The installation still fails with error 1628.
No log this time as I was running from explorer rather than using the command line.
cunningdave
Bad news - IS tends to not make many SPs for old versions but to force an upgrade to the next version. Understandable from their dev perspective, but a but time consuming and costly for the users.
--
SvenC
Carl Daniel
Hi,
I searched "Failed to register server into ROT with ROTFLAGS_ALLOWANYCLIENT flag, error is 0x800706be, try default flag instead" and guess whom I found ;)
So far you seem to be alone - but hopefully not log. The IS team should know when and why it is trying to access the ROT.
--
SvenC
Ghia
I've now managed to replicate the problem on an installation that only installed one file, with no scripts, merge modules, custom actions or the like. The problem seems to occur with Installscript MSI projects but not basic MSI projects
I've also seen InstallShield 10.5 installations developed by a colleague that work ok on Vista. The most significant difference appears to be that I had installshield service pack 1 installed whilst he didn't. I will try uninstalling Installshield, and re-install without the service pack. See if that works.