CA installer restarting twice upon every reboot? [Resolved]

Discussion created by helios1974 on Nov 29, 2008
The Windows Installer begins twice at every reboot after CodeAnalyst is installed.

CodeAnalyst installs and runs fine. However, each time the PC is restarted, the following happens:

First, this window appears as the Windows desktop begins loading:
"Windows Installer - Preparing to install..."

Second, after all processes have loaded:
"CodeAnalyst Performance Analyzer - Please wait while Windows configures CodeAnalyst Performance Analyzer"

Third, after a progress bar completes:
"CodeAnalyst Performance Analyzer - You must restart your system for the configuration changes made to CodeAnalyst Performance Analyzer to take effect. Click Yes to restart now or No if you plan to manually restart later."

If "No" is clicked, the above process repeats once more. If "No" is chosen a second time, the boxes disappear and Windows operates normally (until the next reboot, at which point the process repeats.)

However if "Yes" is selected at the first prompt, Windows begins to close down running applications, but is interrupted with the following installer error message (assumedly because of the second instance running):
"CodeAnalyst Performance Analyzer - Error 1719: The Windows Installer Service could not be accessed. This can occur if you are running Windows in safe mode, or if the Windows Installer is not correctly installed."

If the first prompt is clicked "No" and the second prompt "Yes," it will restart as expected, with no error. However, upon the next restart, the process repeats from the beginning.

These "installations" never finish or otherwise resolve themselves -- so each time the PC is restarted, this process begins again. Code Analyst was uninstalled, the PC rebooted, and freshly installed again, with the same result. Anti-virus software was disabled along with firewalls, and the Windows Installer itself was reinstalled. Any help would be appreciated.

WinXP Pro x32 SP3, Athlon x64 4000+, CA v2.84.512.0356

Edit: This has been "resolved" by removing the installer data via http://support.microsoft.com/kb/290301 however, the installer should be examined to find out why this problem is happening.