Welcome to CoolWriteups. If you have completed an upgrade of a Nintex Content database from MOSS 2007 to SharePoint 2010, you may see an error displayed in red on the WorkflowDesigner.aspx page. The error states: “Object reference not set to an instance of an object”, similar to the one in the image below.
- I was unable to find any pattern for this, at first I thought all workflows created in an earlier version (in 2008, 2009) were the cause;
- I then checked to see if this was only for workflow that were set to run automatically, but that wasn’t it either;
- I also checked to see if there were any actions that were broken in the workflow but they all seemed to be fine;
- The SharePoint log files did not provide any clues either;
- In the end the best way to solve this is to simply Publish the workflow. If you do not publish the workflow and try to run it, it will throw an error message: Failed on Start. Republishing the workflow fixed the issue.
Questions and Comments welcome.
Send us a quick enquiry at Certified Solutions Australia to find out how we can help you.Derek Halstead is a SharePoint consultant as well as the founder and principal of CertifiedSolutionsAustralia.com and CoolWriteups.com. He has 16 years of experience in the IT industry, with over ten years focused on Microsoft SharePoint. He can be reached by using the Contact Me link in the top menu.