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

Project Server 2007: Upgrading from a Pre October CU may fail during PSConfig step 8

Project Server 2007: Upgrading from a Pre October CU may fail during PSConfig step 8

  • Comments 15

With Project Server 2007 SP2 just around the corner many of you will hopefully be upgrading over the next few weeks.  As with any upgrade you should always test first in a non-production environment but preferably with a copy of your production data.  We are aware of an issue that can occur when upgrading from a server that has not been patched since before the October CU to any level from October up to SP2 and even the April 2009 CU (which will be available around the time SP2 ships too).  We are working on a resolution for this problem and depending when you are reading this we may already have a solution.  If you run into this issue during your testing then please log a support incident.

The details of the failure are that the SharePoint Configuration Wizard will fail at step 8 while it is updating the databases and the error logged to the upgrade and ULS log will look something like:

The DELETE statement conflicted with the REFERENCE constraint "FK_MSP_TimesheetLine_TaskNameUID". The conflict occurred in database "TaskConsistency_<instance_name>_Reporting", table "dbo.MSP_TimesheetLine", column 'TaskNameUID'.

The statement has been terminated.

   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)   at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async)   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()   at Microsoft.Office.Server.Data.SqlSession.ExecuteScript(TextReader textReader, Int32 commandTimeout)   at Microsoft.SharePoint.Upgrade.SPDatabaseAction.ExecuteSql(String sql, Int32 commandTimeout)   at Microsoft.SharePoint.Upgrade.SPDatabaseAction.ExecuteSql(String sql)at Microsoft.Office.Project.Server.Upgrade.ReportingDatabaseUpgrader_12_1_153_0.Upgrade()   at Microsoft.SharePoint.Upgrade.SPActionSequence.Upgrade()

with the key parts of the message being:

Microsoft.Office.Project.Server.Upgrade.ReportingDatabaseUpgrader_12_1_153_0.Upgrade()

You will also notice the Versions table in the reporting database will look something like this:

VersionId Version Id
00000000-0000-0000-0000-000000000000 12.0.4518.1016 2
00000000-0000-0000-0000-000000000000 12.0.6218.1000 3
00000000-0000-0000-0000-000000000000 12.0.6300.5000                                             4
00000000-0000-0000-0000-000000000000 12.0.6318.5000 5
00000000-0000-0000-0000-000000000000 12.0.6327.5000 6
A1EF27C5-A62C-44A2-BEA8-D244C622A092 12.1.152.0 1

The first few lines will depend on the various upgrades previously loaded, but the final line signifies that the last successful upgrade step was 152, and the 12_1_153 failed.

As I mentioned, we are working on a resolution for this problem but wanted to be sure you can either find this information if you have already run into the problem, or consider it as part of your planning process for your upgrade – and making sure you test upgrade your production data in a non-production environment.

From our experience we suspect this issue to only affect a very small percentage of our customers (we have only seen the problem once in the wild) but we do appreciate, that if you happen to be one of this small percentage then this is no comfort.  Log a support call and we will help you through this.

Thanks to Aik for his great work on this one!

Leave a Comment
  • Please add 4 and 2 and type the answer here:
  • Post
  • PingBack from http://www.anith.com/?p=29784

  • We ran into the same issue when applying the August 2008 CU. Reindexing all tables of the reporting database solved it.

  • Hi Brian;

    We seem to have a similar issue at of our sites upgrading from AugCU to Dec CU. Error message is below. Please let me know if you have come accross a resolution for this issue.

    Regards

    PJ

    pj@projectsolution.co.uk

    -----

    [ReportingDatabaseUpgrader_12_1_153_0] [12.1.153.0] [DEBUG] [4/6/2009

    2:25:02 PM]: Begin Initialize()

    [ReportingDatabaseUpgrader_12_1_153_0] [12.1.153.0] [DEBUG] [4/6/2009

    2:25:02 PM]: End Initialize()

    [ReportingDatabaseUpgrader_12_1_153_0] [12.1.153.0] [INFO] [4/6/2009

    2:25:02 PM]: Fix TaskUID values in MSP_EpmTimesheetLine

    [ReportingDatabaseUpgrader_12_1_153_0] [12.1.153.0] [DEBUG] [4/6/2009

    2:25:02 PM]: Begin Upgrade()

    [SPManager] [DEBUG] [4/6/2009 2:25:09 PM]: SyncUpgradeTimerJob: sleeping

    for 10 seconds

    [ReportingDatabaseSequence] [ERROR] [4/6/2009 2:25:12 PM]: Action

    12.1.153.0 of

    Microsoft.Office.Project.Server.Upgrade.ReportingDatabaseSequence failed.

    [ReportingDatabaseSequence] [ERROR] [4/6/2009 2:25:12 PM]: The DELETE

    statement conflicted with the SAME TABLE REFERENCE constraint

    "FK_MSP_TimesheetTask_LatestTaskNameUID". The conflict occurred in database

    "ProjectServer_Reporting", table "dbo.MSP_TimesheetTask", column

    'ParentTaskNameUID'.

    The statement has been terminated.

    [ReportingDatabaseSequence] [ERROR] [4/6/2009 2:25:12 PM]:    at

    System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean

    breakConnection)

      at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException

    exception, Boolean breakConnection)

      at

    System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObjec

    t stateObj)

      at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior,

    SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet

    bulkCopyHandler, TdsParserStateObject stateObj)

      at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String

    methodName, Boolean async)

      at

    System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult

    result, String methodName, Boolean sendToPipe)

      at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()

      at Microsoft.Office.Server.Data.SqlSession.ExecuteScript(TextReader

    textReader, Int32 commandTimeout)

      at Microsoft.SharePoint.Upgrade.SPDatabaseAction.ExecuteSql(String sql,

    Int32 commandTimeout)

      at Microsoft.SharePoint.Upgrade.SPDatabaseAction.ExecuteSql(String sql)

      at

    Microsoft.Office.Project.Server.Upgrade.ReportingDatabaseUpgrader_12_1_153_0

    Upgrade()

      at Microsoft.SharePoint.Upgrade.SPActionSequence.Upgrade()

    -----

  • Hi Brian

    Thanks for the update. I have Dec CU in my environment. Is there going to be any problem if I deploy SP2?

    Can I deploy April CU without SP2?

    Thanks

    Anil

  • Hi Berend,

    Thanks for the feedback. Interesting that a re-index resolved this for you.  I'll discuss with my colleagues, as my understanding of the issue I can't initially see how this would help - but great if it does.

    Best regards,

    Brian.

  • I'll keep you posted PJ - do you have an open support incident on this issue?

    Best regards,

    Brian

  • Hi Anil,

    If you have this issue you will have a problem with any CU or SP2 until we get a resolution.  I you don't have it then it will be possible to load April CU without SP2, but it is recommended that SP2 be a prerequisite for April CU.

    Best regards,

    Brian.

  • Hi Berend,

    I think you may have had a different issue unless you saw this exact error.  This error is first known to occur when upgrading to October CU (from pre October CU).

    Best regards,

    Brian.

  • Hi Brian – yes I do have an open support call (Case SRQ090409600564) with MS tech support. Shazeb Khan (shazebk@microsoft.com) said he might contact you to touch base regarding this as well.

    Do you think reindexing the reporting DB might resolve the issue? as indicated by Berend van der Zwaag.

    Thanks for the update.

    Regards

    PJ

    pj@projectsolution.co.uk

  • Hi PJ,

    No, I don't think indexing will help.  On reviewing Berend's posting I think he was seeing a different problem, as this was introduced at the Oct CU so wouldn't be seen applying the Aug CU.  You are in great hands with Shazeb and we are close to having something we can help you (and others) to get round this issue.

    Best regards,

    Brian.

  • Hi Brian,

    I have the same problem when installing SP2 on my project server 2007.

    My EPM system: Project Server 2007 + SP1 + IU + Aug 2008 CU.

    Error message is below.

    [ReportingDatabaseSequence] [ERROR] [4/30/2009 10:51:26 AM]: Action 12.1.153.0 of Microsoft.Office.Project.Server.Upgrade.ReportingDatabaseSequence failed.

    [ReportingDatabaseSequence] [ERROR] [4/30/2009 10:51:26 AM]: The DELETE statement conflicted with the REFERENCE constraint "FK_MSP_TimesheetLine_TaskNameUID". The conflict occurred in database "ProjectServer_Reporting", table "dbo.MSP_TimesheetLine", column 'TaskNameUID'.

    The statement has been terminated.

    [ReportingDatabaseSequence] [ERROR] [4/30/2009 10:51:26 AM]:    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)

      at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)

      at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)

      at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)

      at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async)

      at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)

      at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()

      at Microsoft.Office.Server.Data.SqlSession.ExecuteScript(TextReader textReader, Int32 commandTimeout)

      at Microsoft.SharePoint.Upgrade.SPDatabaseAction.ExecuteSql(String sql, Int32 commandTimeout)

      at Microsoft.SharePoint.Upgrade.SPDatabaseAction.ExecuteSql(String sql)

      at Microsoft.Office.Project.Server.Upgrade.ReportingDatabaseUpgrader_12_1_153_0.Upgrade()

      at Microsoft.SharePoint.Upgrade.SPActionSequence.Upgrade()

  • Hi Alex,

    Contact support (methods can be found at http://support,microsoft.com).  This is a bug so there will be no charge for the incident - although it may be charged then refunded depending on the method.  We can help you resolve this.

    Best regards,

    Brian.

  • Brian,

     Has any resolution been found, we tried the index and it did not fix it. We were trying to go from August to Feb CU.

    Thanks!

    Mark

  • Hi Mark,

    Our support teams can help you with this - it is a bug so any charge will be refunded so please open an incident. http://support.microsoft.com gives you the options.

    Best regards,

    Brian.

  • I finally bit the bullet and decided to upgrade our SharePoint farm yesterday. I’d been holding off for

Page 1 of 1 (15 items)