SharePoint Designer 2013 (SPD) and Visio 2010 – not so good together…

Microsoft recently released SharePoint Designer 2013 (SPD is a free product – you can download it here) which allows non-code luddites like myself to create magic in SharePoint 2013. However, there’s a bit of a problem if you:

  • Have Visio 2010 installed on the machine you deploy SPD 2013 to
  • Have SP 2013 Workflows Deployed and activated (Instructions here)
  • Choose to create a 2013 Workflow

It puts you into a never-ending spiral of “Repair SPD?” then “Repair Failed; Try again?” with both Yes and No triggering the repair question again. There is no way to get out of it except for killing the thread using Task Manager… and when you open SPD again it starts the same process (essentially rendering the product useless). The actual error is:
Microsoft SharePoint Designer can’t start Microsoft Visio. An error occurred and this feature is no longer functioning properly. Would you like to repair this feature now?

MS have released a patch mid-December which addresses this issue – you can download it here: http://support.microsoft.com/kb/2752031

I’m surprised that this was not in the test plan, it seems a bit obvious… Ah well, we’ve all missed the obvious at some point in our lives.

B

Advertisements

About Brad Saide

I'm a SharePoint consultant. I'm also slowly going bald, seem to have a permanent spare tyre around my waist and enjoy socialising with friends over a beer or 10. The last 2 may possibly be related. Started working with SharePoint when the first version was in limited beta release (participated in the Technology Adoption Program while at Woolworths) and have been committed to the adoption of the technology as a business enabler ever since.
This entry was posted in Uncategorized. Bookmark the permalink.

3 Responses to SharePoint Designer 2013 (SPD) and Visio 2010 – not so good together…

  1. Andreas Bijl says:

    Thanks for this post, it really bugged me I couldn’t modify a workflow I had made before installing Visio 2010. The patch resolved this issue.

  2. Mark E says:

    Thank-you. I had this exact problem.

  3. Robson Giovanni Parisoto says:

    Thank you Brad! Works perfectly to me. Regards from Brazil.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s