We upgrade our software via what amounts to a Major Upgrade (Product and Package Code changed with each release) and have been doing so for quite some time without problem. All of a sudden, after installing our latest upgrade, the app. repairs itself (looks for source cd, etc.) upon execution of the app.'s main executible.
What could be some possible causes of this!
It looks as though most if not all of the major components are intact/replaced properly after/during the upgrade.
Pleas help me! This one is a biggie for us!
Any help or points to info is GRRRRRRRRRRRRRREATLY APPRECIATED!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
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/Source Resiliency
Started by
Superfreak3
, Apr 03 2002 21:46
5 replies to this topic
Posted 04 April 2002 - 15:46
Note: On 2K systems, the CD is not needed for the 'repair'. It just 'fixes' itself.
Is there any way to create a log to trap the problem? I am creating a log via the Command Line parameter in setup.ini - /l*v "log path". Will this do it?
Is there any way to create a log to trap the problem? I am creating a log via the Command Line parameter in setup.ini - /l*v "log path". Will this do it?
Posted 04 April 2002 - 16:31
You can use a registry key. Copy the code section into a file "SetLog.reg". Double click the file. I find it convenience to make a file because I can easily run it on problem machines.
The log files are created in the current users temp directory (Documents and Settings\SuperFreak3\Local Settings\Temp)
Code Sample |
REGEDIT4 [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer] "Logging"="iwearucmopv" |
The log files are created in the current users temp directory (Documents and Settings\SuperFreak3\Local Settings\Temp)
Ian Blake
(Currently Unemployed)
(Currently Unemployed)
Posted 04 April 2002 - 17:47
I trapped the problem via the OS Event Viewer. I also used Help files ...
It appears that the KeyPath for a file is missing or broken. I checked the Component table via Orca and there is a value in the KeyPath for the component. This component has not been changed in anyway for quite some time. I checked back several releases when this was not a problem, and everything looks the same. What could have caused this and, more importantly, how do I fix the broken key path?
Do I change the component code? Is the component's file corrupt in some way? Should I remove the component from the project entirely and rebuild/add it?
Please help!!!
It appears that the KeyPath for a file is missing or broken. I checked the Component table via Orca and there is a value in the KeyPath for the component. This component has not been changed in anyway for quite some time. I checked back several releases when this was not a problem, and everything looks the same. What could have caused this and, more importantly, how do I fix the broken key path?
Do I change the component code? Is the component's file corrupt in some way? Should I remove the component from the project entirely and rebuild/add it?
Please help!!!
Posted 05 April 2002 - 08:49
What kind of key is it? Is it an exe, dll, com dll, com server exe, active x object. registry value.
In the case of com objects the installer 'decorates' the class, interface registration. If this decoration is damaged by registration of another object (or self registration) then this can trigger a repair.
I do not know enough about this to help. Good luck.
In the case of com objects the installer 'decorates' the class, interface registration. If this decoration is damaged by registration of another object (or self registration) then this can trigger a repair.
I do not know enough about this to help. Good luck.
Ian Blake
(Currently Unemployed)
(Currently Unemployed)
Posted 05 April 2002 - 14:52
Can anyone make anything of this? The component contains DAO350.dll. I am Using Advanced Setting as the registry parameter and the file is being installed to:
\Program Files\Common Files\Microsoft Shared\DAO.
\Program Files\Common Files\Microsoft Shared\DAO.