My Tasks: When to expect the unexpected error has occurred

With the latest hotfixes and the Infrastructure Update applied the majority of causes of the "unexpected error has occurred" should now be eliminated. There may still need to be some cleaning up to finally resolve the problem - and this usually means publishing the plans again that are leading to the issue.  Occasionally this may also need to be combined with deleting the project from just the published database, and also using the ProjTool utility from the SDK to do a full publish.

There is however still one other class of error that can lead to the unexpected and that is due to a change in the way the status manager is applied in 2007 compared to 2003.  In 2003 the status manager (the person who gets the updates) related to the assignment.  In 2007 this has changed and now the status manager relates to the task - and all assignments under the task.  So in 2003 you could have multiple status managers for each task if there were multiple assignments - but for 2007 only a single status manager can exist for each task.  For projects imported from 2003, and I think also for projects created from templates that came from 2003 it was possible in 2007 to end up with different status managers for assignments of the same task.  This could lead to a number of issues - the unexpected error on My Tasks, and also it could cause problems with the update process as the "real" status manager would not necessarily get the updates and these may not be seen by the "false" status manager.  So if you have updates that are not getting applied to the plan check the status manager to see if you have this condition.  The task usage view is probably the easiest place to see the problem - and also to resolve it - by copying down the right status manager to all the assignments in the task.

Technorati Tags:

Comments (2)

  1. xo883 says:

    Hi, I found an unexpected error during installation that cannot be resolved after repeatedly restarted the server.

    Base on your experience, do you have any idea?

    One or more configuration settings failed. Completed configuration settings will not be rolled back. Resolve the problem and run this configuration wizard again. The following contains detailed information about the failure:

    Failed to create the configuration database.

    An exception of type System.Management.ManagementException was thrown. Additional exception information: Initialization failure

  2. Not familiar with this one xo883.  Looks more dep routed in SharePoint than specifically Project – as if the SharePoint config db doesn’t get created then you don;t have a farm.  Could be connectivity issues – or possibly the binaries haven’t installed correctly in the first place.  Sorry I can’t be more help.

    Best regards,


Skip to main content