Home » sharepoint designer 2010 » Use Logs to Debug Publishing Problems between SharePoint Designer 2010 and SharePoint Server 2010

Use Logs to Debug Publishing Problems between SharePoint Designer 2010 and SharePoint Server 2010

We have spent some time, recently, building the content type, and workflow demonstrated by Eric Eaton in our Project Task Tracking video tutorial. This video tutorial can be viewed by anyone with a subscription to SharePoint-Videos.com. This video is also available as part of our SharePoint 2010 Project Management videos tutorial DVD. This DVD can be purchased either for individual viewing, or for enterprise viewing.

We were neither able to associate our workflow to the Project Tasks List we created, nor to the “Project Tasks” content type we built to replicate the environmental features surrounding the points made in the video (please note: this video tutorial series does not include an explanation for each of the technical features). We successfully published our workflow and saved it. But, despite the workflow popping up in SharePoint Designer 2010 correctly in relation to the test site we built and the content type, itself, as we just mentioned, we were not able to use the SharePoint Designer 2010 ribbon prompts to associate the workflow correctly. Each attempted ended with an “Unexpected Error” message with a reference to SharePoint Foundation.

If you experience similar difficulties, you should make a point of accessing your SharePoint Server 2010 Unified Logging Service (ULS). You can trace the error by correlation ID within the activity logs, themselves. You can read a blog post on MSDN, ULS Viewer, for SharePoint 2010 Troubleshooting, authored by Jie Li. We found the instructions in this article to be entirely correct, even for our Virtual Environment (be sure to check the c: drive of your Virtual Machine, and NOT your local machine to locate the correct SharePoint ULS information).

Of course it is much simpler to remediate a known problem. At a minimum, mapping the correlation ID for the error to the matching activity noted in the SharePoint ULS will at least identify the problem for you. We will write more on remediating the problem we experienced in the next post to this blog.

Ira Michael Blonder

© Rehmani Consulting, Inc. & Ira Michael Blonder, 2013 All Rights Reserved