Friday, July 30, 2010

Datasheet Edit Error - Timeout

This was a frustrating problem to diagnose.  I usually find quite a bit of help on the technical forums but this particular error/issue was not listed anywhere. 

The error:  Users were reporting that when they attempted to do bulk edits on a large list, they received a timeout error and were prompted to either discard or retry their changes.  It was nearly impossible to make changes to more than one line at a time using the datasheet view and edit function.  The users were located in different buildings and had either the Office 2007 or Office 2003 client installed and were using either IE7 or IE8.  I also tested and the problem was not limited to a particular type or size of list, but it was limited to one site collection.


The error message was "A timeout occurred while communicating with the server. Changes to your data cannot be saved." 

Attempting to Retry the change would bring back the same error.  The only option was to Discard.

The end users were quite patient but they typically would make 10-15 changes at once to certain properties in this list.  The only work-around was for them to make one change at a time using the standard "Edit Properties" function. 


The solution:  After a week of researching and coming up with nothing, I began to research the "Access Web Datasheet" function and came across a few posts that led me to believe this may be a database problem and not necessarily a SharePoint application problem. After all, the error message did state that a timeout occurred while communicating with the server.  The configuration for this web application was a small farm - the database was on a separate server.  The database administrator re-organized the index for the database using SQL Server Management Studio. Voila!! After my own testing and confirmation from several users, the problem was gone.

Yes, this seems like a rather simple solution but it was not obvious, at least not to me.  The users were, to say the least, pretty happy we got this fixed.  To quote one of them, "You rock!!!"  That, of course, made my day.  :)

Thursday, July 29, 2010

Why blog?

As a SharePoint administrator/architect/developer (what do I call myself anyway?) working for a state agency, I'm often called upon to troubleshoot user issues, diagnose database problems and design and configure websites for large initiatives and small projects.  This usually involves searching the web for tips and tricks and hoping someone else has had the same trouble I've had.  And, obviously, I hope they've found an answer. 

In my internet investigations, I've run across many blogs and they are, for the most part, outstanding.  But I always find myself needing to solve a problem or design and build a solution without customizing code, buying any gadgets, or hiring a skilled coder.  Because, to put it simply, it's just not allowed - at least not at my particular agency.  So, I've had to become more of an "out-of-the-box" specialist.

And that is why I decided to start blogging.  I hope to build a repository for myself and if others can benefit, then that's an even better - and less selfish - reason to blog.