29 November, 2011

Insert Clipart causing install loop problem for MS Office apps

On my work laptop, running Win7 Pro, all of my MS Office apps are all 2007 except for Visio 2003. When Visio was installed, for whatever reason the clipart was not installed. If I tried to use the clipart, it would start the install wizard, ask for a path to the install disk and eventually fail as I didn't have the disk. This is unfortunately is expected behavior.

But, when I go to insert clipart from my other Office apps, they run into a problem due to Visio. It goes through the same Microsoft Office Visio 2003 install wizard, and after failing, it will open the clipart that WAS installed for 2007.
I search for solutions, but never found one. This works for some install loop type problems, but not my specific case.
Enter one of the following using Run.... Substitute Excel, Visio, or PowerPoint for Word as necessary:
  • Office 2007: reg add HKCU\Software\Microsoft\Office\12.0\Word\Options /v NoReReg /t REG_DWORD /d 1
  • Office 2003: reg add HKCU\Software\Microsoft\Office\11.0\Word\Options /v NoReReg /t REG_DWORD /d 1
I eventually got a Visio 2003 disk, but then I ran into a new error message -- it wouldn't let me change the install path -- error 25091. This error is thanks to the tighter security in Windows 7.

To change an install path, you need to be running the application with Administrator privileges. Unfortunately, I wasn't able to right-click on the Shortcut and select "Run as administrator," I needed to find the source file. Right-clicking and opening the Properties dialog to get to the source didn't work either, as it was unavailable. I browsed to C:\Program Files\Microsoft Office\Office12, right-clicked on POWERPNT.EXE and clicked "Run as administrator." From here, I tried to insert clipart again, and this time I was able to provide a path to my Visio disk and the problem has been resolved.

I'm not sure what to suggest to others that do not have a Visio 2003 disk -- someone had one (or a network install) to get it on your machine originally. Likely your IT department that originally set up your computer will be able to solve this -- assuming they're accessible.

No comments: