Cascade Skyline - with Microsoft Logo and Project Support header - author Brian Smith

An Unexpected Error Has Occurred, or Unknown Error in WSS 3.0

An Unexpected Error Has Occurred, or Unknown Error in WSS 3.0

  • Comments 23

With Project Server 2007 being a WSS 3.0 application you may come across either of these error messages.  The Unexpected error can appear on web part pages, and the Unknown error is more likely on pages without web parts.  The two errors are really telling you the same thing - This page (or web part) needed some data - but the data doesn't fit what I was expecting.  If you get this then you probably need to raise a support call (see for options available to you) - or search through the KBs to see if there is a fix for the specific problem you are seeing (depending when you read this there may or may not be fixes up there right now).

But for some potential immediate relief from the problem here are a few tips that may at least get that page displaying again.  The problem could occur on a number of different pages - but just to give some context lets talk about the "My Tasks" page.  This will be displaying the "My Assignments" view by default, but in fact as this web part loads the SQL stored procedure behind the scenes will be bringing in data for any of the views that a specific user has access to from the drop down of views.  So even if "My Assignments" is the default - if you also have a custom view in the list that perhaps includes some custom fields then this data will also have been retrieved (and could be the culprit!).  So identifying the bad data will help us with your support call and also hopefully get that page working again.  Thinking in rows and columns - any customization will be changing the columns - and the rows will depend on things such as date ranges, tasks and assignments.  So things you can try:-

  • If it is a web part page then go to the Web Part Maintenance and either reset the part - or remove it and then add it back again.  This will have the effect of defaulting the web page settings and if the bad data happened to be beyond the "current tasks" range or other filter specific to the part this may get things working.  This isn't a fix - just avoiding the bad stuff for now.
  • If you have customized then try removing any additional custom fields or other added fields from the view.  Again this isn't a fix, and certainly the customizations shouldn't lead to errors - but it may at least allow you to continue working.
  • Try removing some rows that could be causing the problem - so any recent assignments would be targets - or if timesheets are the problem removing some added task lines might help. 

None of these are meant as long term fixes - they are really just avoiding the issue until a fix can be found - which either the support call or KBs will help you achieve.  But hopefully it will give you an understanding of what might have led to the issue - and could get your resources back up and running while together we solve the deeper problem.

Technorati Tags: Project Server 2007

Leave a Comment
  • Please add 6 and 7 and type the answer here:
  • Post
  • Brian,

    You also may want to have a look at this. It will mean you can see more debug information and may save  a PSS call.

    Regards, Vince

  • Thanks Vince - very useful!  I'll try it out on a couple of scenarios where I can make the error appear.  

    Best regards,


  • Brian,

    I am using Virtual PC 2004 to connect to a development image with hosts Project Server 2007. I have connected the network adapter from the physical server on which it is hosted with the virtual adapter in the image. Then, I have assigned a unique static IP to the image so that it  I accessible from our network. However, once we did this, the PWA (Project Web Access" has stopped functioning. Whenever we try to open it, it gives the error "An unexpected error has occured". Even when I open IIS and try to open the site (Project Server site), it tells me that the page is not found.

    What could be the reason and how can I resolve this?


  • Hi Sharat,

    I can only give you some general thoughts here - then you may need to go to or the newsgroups.  You don't say how you are connecting, but I have seen similar issues to this when trying to use IP addresses where DNS is not configured correctly.  WSS knows its own server names and will redirect to the name - even if you initially connect via a direct IP address.  Either configuration of Alternate Access Mappings or a local hosts file will help if this is the cause of your issue.

    Best regards,


  • I tried all the above suggestions, but couldnot overcome the error. I am getting this error when I try to open mytasks page. I am the only member facing this problem in the company. All others face this error when they submit task updates using "Submit selected" button.

    Do we need to apply any patch? any clue to solve the problem would be highly appreciated.

    Thanks & Regards,


  • Brian,

    I am having the unexpected error on the MyTasks page with one particular user (!) in a fully operational system, so I cannot (not being a programmer) fiddle about in a web.config file (which one in particular ?) too much with the risc of screwing things up for the rest of the 350 users. On the other hand I have a complete copy of this system in my virtual. Can you point me to the right web.config file in this case ?

    Thanks in advance !

  • Glad you are thinking about your users Maarten.  The web.config should be the one for port 80 by default - so would normally be found in c:\inetpub\wwwroot\wss\virtualdirectories\80.

    Best regards,


  • Another addition to the discussion is this: I spoke to my colleague and he mentioned that after a resource is assigned to a task in a projectplan and reported hours on the task the projectmanager assigns a second resource to the task. The first assigned resource gets the same error message. Once the second assignment is deleted from the plan the troubled resource gets to see his MyTasks-page again. This is clearly a bug. If ss, do you know this will be solved soon by the project-group ?  

  • The latest hotfix (KB950816) contains a fix (QFE20994)that has eliminated this and other symptoms on the MyTasks page. I have tested for a customer and it works well.

  • Thanks Kermit - most if not all scenarios giving this error should now be addressed.  You may need to re-publish to completely fix the problem after applying a hotfix.

  • I have a problem with Sharepoint 2007 and Project server 2007, i get an error message when i try to view my tasks. i have about 3500 tasks   assigned to me but cant access the page.

    Please help.

  • Hi Syntax,

    With 3500 tasks it could be time-out issues, or data issues with one or more tasks.  The full error message may help identify which. We have addressed many of the data issues with hotfixes and the infrastructure update - what release level are you running?


  • Unknown Error in WSS 3.0 When i have restored a WSS 3.0 backup on WSS 3.0 SP1 with new installation.

    This is really a challange for MOSS Administrators.

    I dont know how to get out of it.

    and What will happen when i upgrade WSS 3.0 to MOSS 2007. Dose this site Really Work?

    Help for this issue strongly appriciated.

    Thanks & Regards,


  • Not sure what the error means in your case, but turning custom errors off and showing the stack trace for that web app may give a better error to troubleshoot.

    Best regards,


  • I do have such error type with PS 2007 SP2.

    When some of PS users try to open any timesheet


    they get this error. When i enabled callstack the error description is as follows:

    Specified cast is not valid.

    Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

    Exception Details: System.InvalidCastException: Specified cast is not valid.

    Source Error:

    An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below

    Stack Trace:

    [InvalidCastException: Specified cast is not valid.]

      Microsoft.Office.Project.PWA.WebParts.TimesheetPart.LoadTimesheetData(GetTSDataModeEnum LoadingMode, Guid resUID, Guid prdUID, Navigation ps) +12473

      Microsoft.Office.Project.PWA.WebParts.TimesheetPart.OnLoad(EventArgs e) +2145

      System.Web.UI.Control.LoadRecursive() +50

      System.Web.UI.Control.LoadRecursive() +141

      System.Web.UI.Control.LoadRecursive() +141

      System.Web.UI.Control.LoadRecursive() +141

      System.Web.UI.Control.LoadRecursive() +141

      System.Web.UI.Control.LoadRecursive() +141

      System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +627

Page 1 of 2 (23 items) 12