InstallShield ... iKernel.exe error
I have this realy frastrating problem. Every time i try to install apps that use install shield i get an error message:
Install Shield Engine (iKernel.exe) cannot be installed. (ox10000)
This just started recently and also i just clean installed win 2k (SP 2)
Tryed searching microsoft and installshield.com knowledge bases, but none of their solutions helped.
I tryed the following without any success:
- reinstalling IE 6
- reinstalling ikernel.exe from installshield.com
- deleting installshield/engine folder
- checked the permessions in DCOM
Here's an exerpt for you:
"The InstallShield Engine (iKernel.exe) could not be installed.
The folder 'c:\program Files\Common Files\InstallShield could not be created.
Make sure that you have the appropriate privileges to create this folder. (0x5)"
Windows 2000 and XP
"Setup has detected that unInstallShield is in use. Please close unInstallShield and restart setup.
"Error installing iKernel.exe: (0x800)"
"Error installing iKernel.exe: (0xa00)"
When the error is acknowledged by clicking on OK, the InstallShield installation is closed and the user is left at the CADKEY installation introducer screen.
CAUSE AND RESOLUTION
*All of the above errors are caused by the user not having the proper privilege level in Windows 2000 or XP to install software. Software must be installed from an Administrator account or from a user account with an Administrator or Power User privilege level.
Yeh, but this doesnt help, because i always log on as an administrator and it still doesnt work.
I ran dcomcnfg.exe and checked the access privilages, but there werent any users in the list so i added myself, but again it did not help. :o
You created another Administrator account and it still failed? Man...I don't have a clue why that would happen.
Ok, i reinstalled win2k and wow installshield finally works! , thats all so weird, the only difference between now and my old intallation of windows is that i havent installed Service pack 1 and 2 yet.
Eureka! Reinstallation resolves another goofy error message! It just shows ta go ya how complex the interaction between various system sub-components is these days.
It's also enough to drive us nuts.