locked
4.0 Server Rollup 14 Install Issue RRS feed

  • Question

  • Current config:

    CRM 4.0 Rollup 10

    SQL Server 2008

     

    CRMv4.0-KB2389019-i386-server-ENU.exe  (server rollup 14), dies with following error:

    Action Microsoft.Crm.Setup.Common.Update.DBUpdateAction failed.

    The INSERT statement conflicted with the FOREIGN KEY constraint

    'lk_timezonerule_timezonedefinitionid".

    The conflict occured in database "XXX_MSCRM",

    table "dbo.TimeZoneDefinitionBase", column 'TimeZoneDefinitionId".

     

    Any idea?

    Thanks in advance

    Bojan

     

     

     

     

    Tuesday, November 30, 2010 10:43 AM

Answers

  • Problem solved.

    I have been misled that this is rollup 14 problem, so my internet search was wrong.

    This is multitenant server, and there were some differences between organisation databases.

    Some rollup updates in some organisations were not correctly applied....

     

    Details and resolution  are here:

    http://blogs.msdn.com/b/emeadcrmsupport/archive/2010/06/28/crm-dbupdates-issue-installing-an-update-rollup-on-a-multiple-organization-environment.aspx

     

    Regards,

    Bojan

     

     

     

    Tuesday, November 30, 2010 9:18 PM

All replies

  • I hope you are testing this on a dev environment.   Have you tried implementing the previous rollups?

    I certainly have experienced issues trying to leap forward to a new rollup.

    Let us know if that helps because this SQL error on the timezone table may be resolved by a previous Rollup.

     


    Curtis J Spanburgh
    Tuesday, November 30, 2010 6:55 PM
    Moderator
  • Curt, thank you for your response.

    As stated here: http://blogs.msdn.com/b/crm/archive/2010/11/18/update-rollup-14-for-microsoft-dynamics-crm-4-0.aspx

    rollup 14 is cumulative since rollup 7.

    But, who knows. I will try to install all rollups one by one till rollup 14.

    Will keep you informed.

     

    Regadrs

    Bojan

    Tuesday, November 30, 2010 7:45 PM
  • Yeah, I 've been burnt by that in the past on some upgrades.

    Let us know how this works out because it will be a big help to the other forum readers. 

    Every bug figured out counts.

     

    You have any customization with C360 products?

     


    Curtis J Spanburgh
    Tuesday, November 30, 2010 8:03 PM
    Moderator
  • No, there is no C360 product.

    Just started with rollup 11, passed OK, but rollup 12 failed with same error.

    So, it's not rollup 14 issue, it started at rollup 12 for me.

     

    Hmm. What to look next?

    Tuesday, November 30, 2010 8:34 PM
  • Well, we have established that it's not rollup 14.  It seems it's the database table itself.

    In the table "dbo.TimeZoneDefinitionBase", column 'TimeZoneDefinitionId" the timezones are defined with a GUID.

    Look to see if anything regarding time is different.    Also compare the table to a working instance of CRM where the Rollup will install.

     


    Curtis J Spanburgh
    Tuesday, November 30, 2010 9:07 PM
    Moderator
  • Problem solved.

    I have been misled that this is rollup 14 problem, so my internet search was wrong.

    This is multitenant server, and there were some differences between organisation databases.

    Some rollup updates in some organisations were not correctly applied....

     

    Details and resolution  are here:

    http://blogs.msdn.com/b/emeadcrmsupport/archive/2010/06/28/crm-dbupdates-issue-installing-an-update-rollup-on-a-multiple-organization-environment.aspx

     

    Regards,

    Bojan

     

     

     

    Tuesday, November 30, 2010 9:18 PM
  • Great , Thanks for letting us know.

     


    Curtis J Spanburgh
    Tuesday, November 30, 2010 9:44 PM
    Moderator