Hope I'm posting this in correct forum. Created a new site as a sub on a site collection on Development farm using Team site template. Site contains custom lists, InfoPath forms, SharePoint designer workflow, some jquery. Saved site as template with content, uploaded as solution, activated and created the site on our QA/Test farm with no issues. Made some changes to the InfoPath forms, lists, etc. Saved as template on QA/Test farm, then uploaded to production, tried to create site and get the following;
Watson bucket parameters: Microsoft SharePoint Foundation 4, ULSException14, 269cd32d "sharepoint foundation", 0e00178d "14.0.6029.0", d2cb6259 "onetutil.dll", 0e0017e2 "14.0.6114.0", 4ec6c041"fri nov 18 15:29:53 2011", MISSING, 000d6c1b "000d6c1b", c0000005 "c0000005", 3833376c "837l" 161a1018-2431-4f73-8645-1a9b4e74f427
09/19/2014 10:18:31.73 w3wp.exe (0x0B30) 0x17A4 SharePoint Foundation General 8kh7 High <nativehr>0x80020009</nativehr><nativestack></nativestack> 161a1018-2431-4f73-8645-1a9b4e74f427
09/19/2014 10:18:31.73 w3wp.exe (0x0B30) 0x17A4 SharePoint Foundation Feature Infrastructure 889y High The element of type 'Module' for feature 'OpenSourceMgmtTemplate8Modules' (id: 8c0e129c-7498-4652-9c5e-e3529f168e80) threw an exception during activation: 161a1018-2431-4f73-8645-1a9b4e74f427
09/19/2014 10:18:31.73 w3wp.exe (0x0B30) 0x17A4 SharePoint Foundation General 72by
Have verified that the site collection features are the same. Development and QA/Test farm have had SP2 applied, but Production has not yet. Have verified that I can save other sites as template and take them to Production and create site with no errors. Have tried re-saving this particular site with content and without content, same error. Have removed the jquery and query filter web part, lightning conductor web part, re-saved and tried on production, still the same error. We have reloaded each web node and tried again - same error. Have tried creating the site under a different site collection on Production and same error. We are not able to reboot the entire farm yet. Has anyone run into this issue or have any suggestions on how to narrow down what's causing the issue?
Thanks,
Kathy








