Project Server 2010: What to Expect when you get the Unexpected

One of the most common error messages you will see in SharePoint 2010, and therefore Project Server2010 is “An unexpected error has occurred”, which will look something like this:

unexpected error (2)

The important thing to note here is the GUID, which in this case indicates it is the correlation ID.  This number isn’t an indication of the error, in the way an Event ID may be considered in the event logs, but indicates where in the ULS logs you can find more details of the error.  The time on the error will also give you guidance of which log to look at – as fresh ones are created every 30 minutes by default, and have a filename which indicates the server name and the time.  The only thing to work out then in a farm environment is the server that gave the error.  It will sometimes be obvious (and usually the web front end – WFE) but may be an error from the application layer and from the application server.  In 2010 these roles are a little less defined, but WFE will be the server(s) serving the web pages and the application server the server(s) where services such as the Project Application Service are running.

Just a reminder – ULS logs can be found at c:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions14Logs (12 for 2007).  Also see my previous blog from the 2007 days at – and i do need to reset the hosted version of that webcast referred to on that page as our beta SilverLight hosting went away.  I’ll try and get this sorted soon…

One of my favorite tools for reading ULS logs is still Excel, and with 2010 I’m sure I will be creating slicers and doing all sorts of new things, but also worth a look is the ULSViewer, which is available at and you can also find details for using there.  One neat feature is the ability to see alive feed of logged items, and filter for the unexpected (which only really makes sense if you are expecting it!)

Technorati Tags: