Are you a user?

The dreaded “internal error!”  What to do?  What was I trying to do?  Simple.

I was attempting to connect a Visio diagram to a SharePoint list.  I’ve done it before a million times…but not in the last year or so.  Soooo….

I fire up Visio Premium 2010 and attempt to connect to a simple list in SharePoint 2013 and am met with the error:

Visio internal error: #3400 Action 2011:  Link Data to Shape

…or some such nonsense.  An then it proceeds to tell me to restart Visio or some such nonsense.  But I try it anyway, but it doesn’t help.

So I start Google-ing (or Bing-ing) and find others with the issue.  Some dribble about needing Premium vs. Professional, required data missing in SharePoint and other babble.  Nope, not even a restart of the old tried and trusted Windows 7 would change things.  So I tried my Windows 8.1 machine with Visio 2013.  Worked the first time.

I decided to “repair” my 2010 version of Visio, since I tend to have all sorts of mixes of version of stuff on my computer and repair Microsoft Office fairly regularly.  So, off to Programs and Features to find the Visio entry.  Fired up a repair and it asked me, fairly forcefully I may say, to finish by rebooting my computer.  So I did.

Long story short…I fired up Visio, made my connection to the same list I’d been using and BAM!  It worked like it was supposed to.

Now on to bigger and better things.

Keywords:

SharePoint Foundation, Visio repair, Fix found

Every time I opened a Word document (or tried to create one) using a content type in SharePoint 2013 that had a managed metadata column and the document information panel was displayed, Word would crash.

This was happening on both my Windows 8.1 Lenovo Yoga that has Office 2010 and Office 2013 and My Windows 7 Dell D830 that has Office 2010.  Both of these machine had SharePoint Designer 2013 installed on them, in addition to SPD 2007 and SPD 2010.

I found this post from L.L that seemed to address my problem.  It appears that running an office repair fixes the issue.  Yay!

I guess the last one you repair (Office 2013 or Office 2010) is the one that gets registered as the default application.  Which is okay by me, because I am constantly annoyed by the ditching of skeuomorphism and replacement of flat design found within Office 2013.

Keywords:  Office 2010, Office 2013, SharePoint 2013, Managed metadata, Content types, Crash, MS Word 2010, MS Word 2013.