Applied the feb CU on the weekend, tested before adjusting the timeout and could reproduce the issue, but after setting the time out the issue is gone.
Thanks! The problem described wasn't identical to my issue, but similar and the issue is now resolved. Sincere thank you to all that gave your suggestions :) Sent from Max's iPad On 21/02/2013, at 2:40 PM, Ivan Wilson <[email protected]> wrote: > Check what Windows updates have been applied to your SharePoint and SQL > servers recently. It may match up with when the problem started to occur. > > One possibility could be to do with XSL transforms timing out. If you have > the Feb 2012 CU you can increase the timeout interval: > http://blogs.msdn.com/b/joerg_sinemus/archive/2012/03/07/xslt-and-timeout-problem-when-transforming-runs-more-than-one-second.aspx > > > Ivan > > > -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf > Of Maxine Harwood > Sent: Thursday, 21 February 2013 9:21 AM > To: ozMOSS > Subject: Help with troubleshooting > > Any advice or tips would be appreciated! Getting to the end of my bag of > tricks. > > We have had Sharepoint 2010 running and stable for 18 months. Late last week, > we started having some random issues in our site collection that include > * errors showing views and dvwp. Logs indicate that the site failed to cache > the field {various GUIDs}, Refreshing the page (sometimes twice) and the view > works again. The same view might open without error next time... There is no > consistency on which views across the site will fail > * attempting to open the item menu results in a message stating that the item > has been moved or deleted, refresh the page to try again. As above, > refreshing 2-3 times and the item menu will open again. > * conditional nintex workflows running when the criteria hasn't been met > > Most significantly, there is no apparent similarities between where these > occur, different lists, library's, different sites. Across the board issues. > > There were no scheduled server or application changes before the issue > started. > > I have tried rebooting, and a Sharepoint repair. I only have the one site > collection, but the central admin isn't experiencing any issues. I suspect > it's an issue in the content database. > > As this is a production environment, that is still mostly functional (though > through a few refreshes) I am planning a course of action to run over the > weekend, I would appreciate any suggestions on what I could look at. I am > considering exporting the content database, deleting it and then creating a > new one before importing, thinking it might be an issue in the content DB. > Running out of ideas.... > > Thanks for your time.... > Maxine > > Sent from Max's iPad > _______________________________________________ > ozmoss mailing list > [email protected] > http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss > > > _______________________________________________ > ozmoss mailing list > [email protected] > http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss _______________________________________________ ozmoss mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
