I have noticed what appears to be a hard to track down error. After
installing my program on several computers, many of them seem to have come
down with what I would call "RE-INSTALL-ITIS". Apparently any of the msi's
that have been previously installed (the in-common factor is that they all
have a reference to OUTLOOK) suddenly trigger off as another program with an
OUTLOOK reference is being installed. The msi for one of the previous
msi's installed on that machine is run during the install of another msi.
The result is an endless loop of the msi triggering another msi that
attempts to install from the first msi... hard to explain. Another error
came up after the installation which says a file and missing and the
computer needs to reboot. The reboot happens and the message comes back up
and says the computer needs to reboot. This is unrelated to the first
error but they both happened this morning on multiple machines all of which
have in common a successful install of my latest deployment (see repodbc.dll
missing for more on that).
I'm lost on this one. Where do I start?
Giac.
When MSI really screws I use MSIFix to delete MSI reg keys
for particular installation and then delete folders by hand, then reinstall.
Better than uninstalling.
http://www.mshelpwiki.com/index.php?page=MsiFix
Rob

Signature
Rob Chandler
MS Help MVP
http://helpware.net/FAR/
http://MSHelpWiki.com
> I have noticed what appears to be a hard to track down error. After
> installing my program on several computers, many of them seem to have come
[quoted text clipped - 15 lines]
>
> Giac.
thejamie - 23 Jul 2004 18:23 GMT
Are you suggesting I do this for all 1000 or so installations?

Signature
Regards,
Jamie
> When MSI really screws I use MSIFix to delete MSI reg keys
> for particular installation and then delete folders by hand, then reinstall.
[quoted text clipped - 27 lines]
> >
> > Giac.