My package breaks Office 2003
I have an app that, once installed, causes Office 2003 to self repair whenever Access is opened. The only entry in the Event Log is MSIEXEC's Configuration completed sucessfully entry. No reason for the self repair is logged. Office 2003 works fine, even if the repair is canceled. Problem persists after uninstalling the bad package.
I'm having a heck of a time trying to find what's triggering this. Any suggestions?
I'm having a heck of a time trying to find what's triggering this. Any suggestions?
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
MSIPackager
18 years ago
Tricky - did u conflict check Office 2k3 against your package?
Presumably you are using a vendor MSI for the app that's breaking Office - have you tried capturing the install on a machine (with Office already installed) to see exactly what it's doing. May highlight any Office files or reg keys which are being changed or deleted as part of the install..
Cheers,
Rob.
Presumably you are using a vendor MSI for the app that's breaking Office - have you tried capturing the install on a machine (with Office already installed) to see exactly what it's doing. May highlight any Office files or reg keys which are being changed or deleted as part of the install..
Cheers,
Rob.
Posted by:
VikingLoki
18 years ago
No vendor MSI, It's a capture. Already conflict checked it too, must be something on one of Office's many CA's. I found a few overlaps with Test Expert, a few regkeys were taken out. I might have it licked... doing some testing now.
It's still quite annoying that Office 2003 will self-repair but not log the component that triggered it. (That's not a config setting somewhere, is it?)
It's still quite annoying that Office 2003 will self-repair but not log the component that triggered it. (That's not a config setting somewhere, is it?)
Posted by:
MSIPackager
18 years ago
It's still quite annoying that Office 2003 will self-repair but not log the component that triggered it. (That's not a config setting somewhere, is it?)
Not that I know of - I thought writing to the eventlog was a core part of msiexec functionality, how typical that and MS app should be non standard! Not that surprising I suppose - MS MSIs always have the most validation errors out of the box!!
Good luck,
Rob.
Posted by:
VikingLoki
18 years ago
Argh. This is driving me nuts. [:@]
It ocurred to me that the Office SP was applied to the Admin Install Point after it was imported into the Software Repository. Great, reimport it and I should find the conflict right? No. The SP included an Autorun.inf file and you know how Windows hates to copy that anywhere but root... Well, it causes the import to the SW repository to fail when it tries to copy it into \000\..
[:@] %$#@! Microsoft!!!! [:@] What's an autorun.inf doing in an MSI, anyway!
So, now I'm copying the install point and modifying the PRO11.MSI file with ORCA to rip out autorun.inf so I have something to conflict check against.
It's just not my day.
It ocurred to me that the Office SP was applied to the Admin Install Point after it was imported into the Software Repository. Great, reimport it and I should find the conflict right? No. The SP included an Autorun.inf file and you know how Windows hates to copy that anywhere but root... Well, it causes the import to the SW repository to fail when it tries to copy it into \000\..
[:@] %$#@! Microsoft!!!! [:@] What's an autorun.inf doing in an MSI, anyway!
So, now I'm copying the install point and modifying the PRO11.MSI file with ORCA to rip out autorun.inf so I have something to conflict check against.
It's just not my day.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.