M
Marcel A. Bernards
This was driving me nuts and it took me a full day to figure out what was
going on here.
On a few systems I get repeating MSIEXEC User setups after starting Access
2003
I tried repairs and removes and reinstalls, it did not solve the problem.
After diggin a bit deeper by enabling MSI logging and digging trough the
log, there were traces of a problem with JET XL registrations and also with
HTML edit:
--8<---
SKUREDReg: failed to get Current property, error 80070103
FixAccessXLISAMRegistry: ....Reading Jet XL ISAM current version...
FixAccessXLISAMRegistry: ....Cannot Open Jet XL ISAM registry key...
....
WriteRegistry2: Error 0x80070103: failed to read action from custom action
data
Info 1721. There is a problem with this Windows Installer package. A program
required for this install to complete could not be run. Contact your support
personnel or package vendor. Action: MsoHtmEdLFNSelfReg, location:
"\\server\office2003$\pro\Files\Program Files\Microsoft
Office\Office11\msohtmed.exe", command: /regserverfp
Action ended 8:52:25: InstallFinalize. Return value 1.
-8<---
I checked the Jet DLL's and registry keys and the registry key was missing
most of the Jet 4.0 engine registrations. Stealing the JET key from a working
system and loading in the test computer solved the issue.
But what caused this problem with the missing JET registrations?
When I reinstall stuff, I want a clean start. Therefor I used the Office
2003 Resource kit Cleanup utility OFFCLN.EXE to cleanup everything.
Nobody else but me and our helpdesk staff uses this thing.
On some of our helpdesk staff computers this problem was also reported.
I checked with other systems in our network and there were no problems
reported
So I concluded this problem must be caused by this tool.
I checked again by testing this scenario....
Conclusion: This thing junks the JET 4.0 tree (maybe more) and cripples the
Office 2003 PRO setup, causeing the repeating MSIEXEC progress bars after
starting access.
Not sure if the HTML edit stuff is crippled too, that's next.
So be carefull with the Office Cleanup utility. it's cleans a bit too much
going on here.
On a few systems I get repeating MSIEXEC User setups after starting Access
2003
I tried repairs and removes and reinstalls, it did not solve the problem.
After diggin a bit deeper by enabling MSI logging and digging trough the
log, there were traces of a problem with JET XL registrations and also with
HTML edit:
--8<---
SKUREDReg: failed to get Current property, error 80070103
FixAccessXLISAMRegistry: ....Reading Jet XL ISAM current version...
FixAccessXLISAMRegistry: ....Cannot Open Jet XL ISAM registry key...
....
WriteRegistry2: Error 0x80070103: failed to read action from custom action
data
Info 1721. There is a problem with this Windows Installer package. A program
required for this install to complete could not be run. Contact your support
personnel or package vendor. Action: MsoHtmEdLFNSelfReg, location:
"\\server\office2003$\pro\Files\Program Files\Microsoft
Office\Office11\msohtmed.exe", command: /regserverfp
Action ended 8:52:25: InstallFinalize. Return value 1.
-8<---
I checked the Jet DLL's and registry keys and the registry key was missing
most of the Jet 4.0 engine registrations. Stealing the JET key from a working
system and loading in the test computer solved the issue.
But what caused this problem with the missing JET registrations?
When I reinstall stuff, I want a clean start. Therefor I used the Office
2003 Resource kit Cleanup utility OFFCLN.EXE to cleanup everything.
Nobody else but me and our helpdesk staff uses this thing.
On some of our helpdesk staff computers this problem was also reported.
I checked with other systems in our network and there were no problems
reported
So I concluded this problem must be caused by this tool.
I checked again by testing this scenario....
Conclusion: This thing junks the JET 4.0 tree (maybe more) and cripples the
Office 2003 PRO setup, causeing the repeating MSIEXEC progress bars after
starting access.
Not sure if the HTML edit stuff is crippled too, that's next.
So be carefull with the Office Cleanup utility. it's cleans a bit too much