SharePoint Errors, Warnings and Problems Collection
Guest Author: Devin Walker
DLOCC, Inc.
The following is a collection of errors that have been encountered while working with MOSS and SharePoint Designer. The purpose of this article is to post solutions to the problems and benefit the SharePoint community. As well, this article will be continually updated with screenshots and is not meant to have any negative impact on SharePoint’s reputation. In fact, we love SharePoint; it’s just a little quirky at times!
Microsoft Office SharePoint Server 2007 (WSS 3.0)
Error: An unexpected error has occurred
Error: Unable to connect to database. Check database connection information and make sure the database server is running.
Solution: When receiving this error check to see if dbs are online and if fully operational resort to power
Error: The security validation for this page has timed out. Click Back in your web browser, refresh the page, and try your operation again.
Error: This Page has been modified since you opened it. You must open the page again.
Solution: If this is continually happening while editing a page using the browser the page may be detached from the page layout. Open SPD and reattach the page to its page layout.
Error: An unexpected error has occurred (v. 2)
SharePoint Designer 2007
Error: Value does not fall within the expected range.
Error: Masterpage is invalid
Disclaimer: All ’solutions’ are not endorsed by Microsoft and DLOCC does not take any responsibility for mishaps, malfunctions, losses or total failures as a result of attempting our suggestions.
Guest Author: Devin Walker
DLOCC, Inc.
About: Devin Walker is a professional web designer, SharePoint enthusiast and founder of the consulting company DLOCC, Inc.. Devin has years of experience working with companies of all sizes to successfully implement, test and launch SharePoint enterprise content management systems. He writes about his experiences on his blog: DLOCC | Articles and Tutorials
- How to remove the “title” column from a SharePoint list
- SharePoint Errors, Warnings and Problems Collection
- Link Two Lists and Display the Data Using the SharePoint Data View
- SharePoint Workflow Time Zones
- Redirect a SharePoint site by using the Content Editor Web Part
- How to Move SharePoint Calendars Fast
- Style a Page using the Content Editor Web Part and CSS
on
Is something missing at the end of the article? There are no solutions to the last two errors.
Nope, nothing that I can see. What specifically are you looking for?
Useful article. The one thing that I would like to point out in your first error is this is seen a lot if you perform some poor coding on a masterpage. I don’t know if it is entirely driven by a connection to DB. Unless, you look at it as the Master Page being customized and that is considered an issue with connecting to DB. If you really want to get a feel for this vague error you would want to adjust the webconfig file on web server to disable friendly errors.
Paul
Sorry, Mark. In my quick skimming it looked like all the errors had solutions, but now I see this is just a “collection” of errors, so not all the errors will necessarily have solutions.
What about “Object reference not set to an instance of an object” ;)
It might be helpful to mention that when you get anunexpected error (my personal favorite) – check the log – thats pretty obvious I suppose if you’ve worked with Sharepoitn for any length of time – BUT – if not – it’s vital info
look in …\Program Files\Common Files\Microsoft Shared\web server extensions\12\LOGS
(or you might have specified a different location for the logs – in your setup – in which case you can look that up in CA )
You can change the verboseness (is that a word??) of the loogs in CA -> Operations -> Diagnostic Logging
I think this article whould be much more useful if the errors were numbered – and each one had some sort of soution for each one
“The purpose of this article is to post solutions to the problems and benefit the SharePoint community.”
As paisleygo said, the article would be much more useful if all the errors had a solution. Unfortunately, some errors don’t had a solution.
Sorry, I don’t see how to paste a picture of the error, but here is the text:
Error
You must fill out all required properties before checking in this document. at Microsoft.SharePoint.ApplicationPages.Checkin.OnLoad(EventArgs e)
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
Troubleshoot issues with Windows SharePoint Services.
The only required property of the Web Part Page is the name, which is obviously completed.
Anyone have a solution for this error?
Sometimes the Title field is required but is hidden in the form. Try exposing the title field in a view, then using datasheet view to add placeholder value. — Mark
Thanks, Mark
The only field I could find was called ‘Default Title’ and there doesn’t appear to be anything that indicates it as a required field. However, I added it to the view, went to datasheet view, entered a value in the ‘Default Title’ column (it was blank), and that solved the problem. Thank you. :)