/build/static/layout/Breadcrumb_cap_w.png

Installation of Microsoft Visio 2013 triggers repair of Office 2010 while starting Microsoft Access 2010 + eventviewer error

Hi everyone,I have just deployed MS Visio 2013 in test so we can deploy it to our MS Office 2010 users.When testing on my test computers, it seems that upon opening MS Access 2010, MS Office 2010 needs to be repaired. After 1 repair, everything seems to be working fine.But on 1 computer it keeps on asking for a repair. I let it continue, but when I try to open an MDB file, MS Access 2010 crashes.In the eventviewer, I can find this error message:Do you have any idea what I can do about this error? I tried the following:

0 Comments   [ + ] Show comments

Answers (3)

Posted by: vjaneczko 10 years ago
9th Degree Black Belt
0
You seem to have been cutoff before finishing your post, but since it works on other PC's but not this one, I'd suggest the basic troubleshooting of the system; chkdsk, etc. Such a problem was encountered at a clients office and it turned out to be a bad hard drive.
Posted by: Silencer001 10 years ago
Orange Senior Belt
0
Thanks for your replies! To complete this threat, I would like to inform you about what I tried:
  • Full Repair of Office 2010 with Visio 2013 installed ==> Doesn't work
  • Full Repair of Office 2010 without Visio 2013 installed ==> MS Access 2010 works like before, but this isn't a solution since MS Visio 2013 needs to be installed.
  • SFC /scannow
  • Complete reinstall of Office 2010
  • Checkdisk (thanks to vjaneczko suggetion) ==> No issues found
  • Checked Add-ons ==> None were active
I have tried this repair with the original package sources or files in C:\MSOcache\GUID\setup.exe

Since this was an isolated issue on 1 PC, my management decided to swap this PC.. So topic may be closed.

I would like to thank you for your suggestions!!
Posted by: GAKIS 10 years ago
Fourth Degree Green Belt
0

Run a repair option on Office 2010 Suite.  Dont see the eventvwr error but it thinks something is missing so is trying to self heal the MSI file but must not be working correctly if it doesnt have administrative priveledges etc.

 

 

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ