Hello,
We recently upgraded our SharePoint server and Nintex versions to 2010 from 2007. We have 2 servers, a staging server called "devsharepoint" and a live server called "sharepoint", theoretically they are the same but may have some minor differences as the dev server was migrated over a month early than the live using the same process.
On the devsharepoint server only, we are seeing an issue where all nintex workflows are failing if at any point a Reminder or Complete Task action is used (including the ones rolled into Flexitasks). While trying to resolve this issue and squeeze any kind of error information out of Nintex and Sharepoint, we turned on verbose logging on the devsharepoint server and started getting a large number of the following entries in the diagnostic logs:
07/21/2011 16:35:08.18 OWSTIMER.EXE (0x1618) 0x1594Nintex Workflow 2010 Error 0000Unexpected: Nintex.Workflow.NWException: Error getting context data for 'SiteOwners'. ---> System.NullReferenceException: Object reference not set to an instance of an object. at Nintex.Workflow.CommonDataItems.<>c__DisplayClass4.<GetSiteOwners>b__3() at Microsoft.SharePoint.SPSecurity.<>c__DisplayClass4.<RunWithElevatedPrivileges>b__2() at Microsoft.SharePoint.Utilities.SecurityContext.RunAsProcess(CodeToRunElevated secureCode) at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(WaitCallback secureCode, Object param) at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(CodeToRunElevated secureCode) at Nintex.Workflow.CommonDataItems.GetSiteOwners(ContextDataOptions options) at Nintex.Workflow.CommonDataItems.GetValue(String key, ContextDataOptions options) at Nintex.Workflow.ContextDataItems.SiteOwners.GetValueObject(NWWorkflowContext ctx) at Nintex.Workflow.NWCustomCommonContextData.get_Data() --- End of inner exception stack trace --- (Build:2201)01d4979c-579f-49f6-b464-0e386d81679a
This is a rather obscure error and I am not even sure if it is directly related to the original problem, but my research online hasn't turned up anything helpful.
Anyone have any suggestions about a possible cause or solution for this error message?
Regards,
Kain