Post reply

Fatal Error encountered while applying SQL 2005 SP2

  • March 28, 2008 at 9:41 am

    #120654

    We are getting the following error while upgrading our SQL Server 2005 instance from SP1 to SP2:

    MSP Error: 29528 The setup has encountered an unexpected error while Setting Internal Properties. The error is: Fatal error during installation.

    Has anyone seen this before?

    Once encountered, we have no other recourse but to restore a LUN copy of the installation and system-db files back to their original locations. That has luckily worked for us and we have been able to revert to SP1, but the question remains: what is the cause of this error?

    __________________________________________________________________________________
    SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
    Persisting SQL Server Index-Usage Statistics with MERGE[/url]
    Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]

  • March 28, 2008 at 9:51 am

    #795299

    Microsoft has published a KB based on this error message. Refer the below link, http://support.microsoft.com/kb/925976

    [font="Verdana"]- Deepak[/font]

  • March 28, 2008 at 10:22 am

    #795322

    We followed the recommendations on that link and tried re-applying the SP, but no luck.

    __________________________________________________________________________________
    SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
    Persisting SQL Server Index-Usage Statistics with MERGE[/url]
    Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]

  • March 30, 2008 at 4:16 am

    #795683

    You can try to contact Microsoft support.



    My blog

  • March 31, 2008 at 2:16 pm

    #796159

    I think we have found the problem. The data and log files of the resource db are not in the same location:

    You cannot install SQL Server 2005 Service Pack 2 when the database file of the Resource database is not in the same folder as the log file of the Resource database:

    http://support.microsoft.com/kb/947989

    __________________________________________________________________________________
    SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
    Persisting SQL Server Index-Usage Statistics with MERGE[/url]
    Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]

  • March 31, 2008 at 2:18 pm

    #796160

    Thanks for sharing the information



    My blog

  • March 31, 2008 at 2:25 pm

    #796166

    No problem! 🙂

    MS really should add this info to their README file for the SP2 install. Having data and log files in the same location is against their best practices, so they should explicitly make this distinction in their PREREQUISITES section.

    __________________________________________________________________________________
    SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
    Persisting SQL Server Index-Usage Statistics with MERGE[/url]
    Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]

  • March 31, 2008 at 2:43 pm

    #796175

    I agree with you.



    My blog

  • March 31, 2008 at 2:58 pm

    #796180

    I've run into all sorts of issues when deviating from the default installation location of SQL Server and now splitting the data and log files of a system db into different drives.

    It seems it is not worth the effort trying to tweak default SQL Server settings too much, especially those that have to do with system entities. It's asking for trouble...

    __________________________________________________________________________________
    SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
    Persisting SQL Server Index-Usage Statistics with MERGE[/url]
    Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]

  • March 31, 2008 at 3:08 pm

    #796186

    I am planning to upgrade my cluster soon. I am glad you post this before I upgrade it. 🙂



    My blog

  • March 31, 2008 at 3:25 pm

    #796187

    I would suggest that you:

    - Read the sp2-install readme file carefully. Incomplete though it may be, it is still a must.

    - Install in the default installation location

    - Prior to the upgrade, stop your instance and copy your system db data and log files to a location in the C: drive.

    - Take a LUN copy of the C: drive

    In case of installation failure, all you'll have to do is restore your LUN copy of C: and copy your system db files to their original location overwriting the corrupted versions that resulted from the botched install.

    These precautions of course are not necessary if you are only doing a clean install from the base version.

    In that case you have nothing to lose if the install fails.

    __________________________________________________________________________________
    SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
    Persisting SQL Server Index-Usage Statistics with MERGE[/url]
    Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]

  • March 31, 2008 at 3:34 pm

    #796192

    Thanks for your tips, I will keep them in mind.



    My blog

Viewing 12 posts - 1 through 11 (of 11 total)

You must be logged in to reply to this topic. Login to reply