Hey guys, can anyone recommend a method to trouble shoot an unintended self-repair? We've got an install that we've installed on dozens of machines all with Visual Basic, but on this one machine, everytime VB is started our install kicks off in a self-repair. And it doesn't stop, it runs in an indefinite loop of repairing over and over and over again. Can you guys give me any idea what might be causing this? By the way, VB was installed long before our install. Thanks.
This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
Self-repair?
Started by
CGreg
, Jan 21 2002 18:57
1 reply to this topic
Kurt Schneider
-
- Members
- 98 posts
Posted 21 January 2002 - 19:45
Greetings,
The first thing you will want to do is to enable installation logging. It will give you a surplus of information on what is happening during installs, uninstalls, and repairs. Most likely files are getting overwritten or something like that. The log will show you the way!
Put the following text into a .reg file and run it on the affected machine. This will turn on the logging
REGEDIT4
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer]
"Logging"="voicewarmup"
Remove this key when your done fixing your issue. It will run for anything installed using MSI. It will slow down the install drastically but the information can be well worth it. It will dump the log into your temp directory, with a file format like MSI?????.log
Kurt Schneider