Automation problem in 2010 Premium Edition

saarum · April 04, 2012, 06:39:19 AM

I have a problem with Viso 2010 that I am not able to fix. For some strange reason which I don't know the cause for the automation part of UML and BPMN and other premium stencils are no longer working. The license is confirmed, the program re-installed and it still isn't working. As an example the UML extensions are missing and I cannot edit the objects. To me it seems that Visio store these bindings somewhere I am not able to find, and it is not cleaned during an un-install. Can anyone propose a solution except for re-installing Windows?

Paul Herber · April 04, 2012, 08:15:38 AM

So, for example if you start Visio then select UML as a new diagram type does a blank UML diagram appear, and does the UML menu appear?
Check this: File -> Options -> Advanced
(down in the General section) ensure
Enable Automation Events
is ticked.

saarum · April 04, 2012, 08:37:26 AM

Automation is checked, but the UML menu still does not appear

That was the only info I found trying to google this problem.

Paul Herber · April 04, 2012, 08:41:37 AM

Does the blank diagram with a selection of UML stencils appear?

saarum · April 04, 2012, 08:43:27 AM

It does, but navigator pane is missing and I cannot edit methods and attributes. It behaves as if the license is not valid but it is.

Paul Herber · April 04, 2012, 08:53:47 AM

No, it behaves as if the UML addon is not being recognised. If the license wasn't being recognised then many more things wouldn't work!

menu File -> Options -> Addins
Look at the list of addins and check that there are non in the inactive and disabled lists.

At the bottom of that page Manage -> Disabled items

Just noticed, Manage -> Com addins then clicking Go closes the Options window. Bug.

saarum · April 04, 2012, 08:59:10 AM

There are actually no add-ins at all. Neither active nor disabled....

saarum · April 05, 2012, 07:05:46 AM

Problem solved.
I removed Visio, cleaned out the Registry for anything smelling like Visio and after a new installation it worked. Seems like Visio left something there.