• State Suggested Answer
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 20 subscribers
  • Views 3667 views
  • Users 0 members are here

Microsoft Office 2013 breaking MicroStation??

zrider
Offline

We are in the process of deploying Microsoft Office 2013 corprate wide.  We have noticed that the offices that have recieved the update, I am recieving calls that MicroStation is now missing part of their Tasks. 

Of course the Tasks/Workflows that are missing are the common ones:  Main Task, Drawing Task, and the Drawing Composition Workflow.

No idea how exactly things are being broken, just know they are.  It appears MicroStation is not recognizing the ustation.dgnlib (where these tasks are stored).  ustation.dgnlib still exists after the install, and the modified date doesn't change.

I have been fixing this by running a repair on MicroStation with the MicroStation.msi file.  For the remaining offices getting the deployment, I will be adding the following script to the end of the Office 2013 install (note my MicroStation install location is NOT default):

If exist "C:\Program Files (x86)\Bentley V8i\MicroStation\ustation.exe" goto RepairUStation
exit:RepairUStation
msiexec /qn /f "\\<<server>>\software\Bentley\Microstation\ms081107443\Extract\MicroStation.msi"
exit

If anyone has experienced this and has better ways of running Office 2013 and not breaking MicroStation, please let me know.  Not sure if it is Office specifically that is causing the issue, or the Windows updates that come with them...

We are running MicroStation SS2 (08.11.07.443), mostly on Windows 7 machines.

Parents
  • 0 Offline
    My company recently started deploying Office 2013 and I've been seeing this issue a lot ever since. I found out that the Office 2013 install either removes or deletes a file called "capicom.dll", which is located in the "C:\Windows\System32" folder. Running a repair of MicroStation regenerates this file, but if you want to fix it in less time, you can create a script that copies the file over (if necessary) and registers it via a "regsvr32 C:\windows\system32\capicom.dll" command. I've seen in some forums that capicom.dll is basically deprecated, so more recent versions of MicroStation probably don't require it, but I haven't tested that. We're using MicroStation V8i (SELECTseries 2) 08.11.07.443.
Reply
  • 0 Offline
    My company recently started deploying Office 2013 and I've been seeing this issue a lot ever since. I found out that the Office 2013 install either removes or deletes a file called "capicom.dll", which is located in the "C:\Windows\System32" folder. Running a repair of MicroStation regenerates this file, but if you want to fix it in less time, you can create a script that copies the file over (if necessary) and registers it via a "regsvr32 C:\windows\system32\capicom.dll" command. I've seen in some forums that capicom.dll is basically deprecated, so more recent versions of MicroStation probably don't require it, but I haven't tested that. We're using MicroStation V8i (SELECTseries 2) 08.11.07.443.
Children
No Data
Communities
Support and Services
Training and Learning
Social Media