none
WSS 3.0 Service Pack 1 Update-Error - "Configuration Failed" + "exception of type System.Data.SqlClient.SqlException"

    Question


  • Hey,
    My SharePoint Servicepack 1 update (wssv3sp1-kb936988-x86-fullfile-en-us.exe) fails to install.

    Server 1: WSS <-- Servicepack
    Server 2: SQL-DB (Workgroup Edition)

    My SharePoint installation is totally broken now. If I am trying to load my homepage I am getting this message:
    An error has occurred on the server.http://go.microsoft.com/fwlink?LinkID=96177

    I am receiving the following error with the service pack:
    Configuration Failed
    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 initiate the upgrade sequence.

    An exception of type System.Data.SqlClient.SqlException was thrown. Additional exception information: Ad hoc update to system catalogs is not supported.
    Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install.

    To diagnose the problem, review the application event log and the configuration log file located at:

    c:\....logs\pscdiagnostics....log


    Any help is highly appreciated! Please let me know if you have any ideas!

    Thanks,
    Bacco


    • Edited by Mike Walsh FIN Wednesday, May 27, 2009 9:38 AM "i need urgent help!!! " removed from text. These are forums - you wait. If the issue is urgent for you ring MS Customer Support Services. Don't pressure us here. (Also Title expanded)
    Friday, December 14, 2007 11:51 AM

Answers

  • Finally solved it!!! For all those who might be interested.

    I did a new sql query within the sql database:
    USE master;
    GO
    EXEC sp_configure 'show advanced option', '1';


    RECONFIGURE WITH OVERRIDE;
    EXEC sp_configure;


    And afterwards run:
    SharePoint Products and Technologies Configuration Wizard


    And guess what:
    It works!
    Friday, December 14, 2007 3:30 PM

All replies

  • Finally solved it!!! For all those who might be interested.

    I did a new sql query within the sql database:
    USE master;
    GO
    EXEC sp_configure 'show advanced option', '1';


    RECONFIGURE WITH OVERRIDE;
    EXEC sp_configure;


    And afterwards run:
    SharePoint Products and Technologies Configuration Wizard


    And guess what:
    It works!
    Friday, December 14, 2007 3:30 PM
  •  

    I had to do that for an issue I was encoutnering as well.  The log files in SharePoint could be a bit easier to read, but are helpful.
    Friday, December 14, 2007 3:36 PM
  • That's not an Service Pack issue. It also occurs with the normal installation. I encountered the problem several times while installing MOSS with clients. I used the same fix.

     

    Although I do not know what causes the problem. It always occurs when I'm installing MOSS and using an existing database that already contains data from other applications (CRM, Biz talk, ...)

     

    Glad you could fix it.

     

    Regards,

    --W

    Tuesday, December 18, 2007 9:20 AM
  • I have the same issue with my Sharepoint 3 install using MS SQL Express 2005. I see your solution but I'm not sure of the steps to complete the task. If you wouldn't mind adding some of the details that would help me for sure. I open SQL manager. I open the database for Sharepoint. I click new Query and that is where I am stuck.

    Wednesday, December 19, 2007 1:57 PM
  • I had the same issue.  I put a fix up on my blog http://fnoja.blogspot.com/2008/01/sharepoint-service-pack-1-crash.html

     

    But here's how to fix it, simply run this from a command prompt:

     

    psconfig -cmd upgrade -force

    Then run the config wizard after that.  If you still have the problem, let me know.

    Monday, January 07, 2008 12:03 AM
  • Try running this command:

     

    psconfig -cmd upgrade -force

     

    then run the config wizard after it finishes.

    Monday, January 07, 2008 2:36 AM
  • Hi el_Bacco,

     

    Within which SQL database did you perform the query? There are many within my install of SharePoint and several versions of sp_configure....

     

    Regards,

    SA Showman

     

     

     

     

    Friday, January 25, 2008 4:23 AM
  • Hi

     

    i have the same problem but the installation was successful.

    But when ever i browse my application it is throwing this error

    An error has occurred on the server.http://go.microsoft.com/fwlink?LinkID=96177 

     

    Any pointers will be highly appreciated

    Thanks in advance

    Satish

     


     

    Tuesday, March 11, 2008 10:41 AM
  • did you try following the steps i listed on

     

    http://fnoja.blogspot.com/2008/01/sharepoint-service-pack-1-crash.html

     

    Specially stsadm -o upgrade -forceupgrade

     

    You also have to say if you want the installation inplace or with the current one.  Once you run that step, try running the SharePoint Wizard again and let me know how it goes.

    • Proposed as answer by kaizawa Tuesday, May 05, 2009 6:10 PM
    • Unproposed as answer by Mike Walsh FIN Wednesday, May 27, 2009 9:39 AM
    Tuesday, March 11, 2008 10:48 AM
  • Success !!

    executing stsadm –o upgrade -inplace worked for me.

    Thanks a lot.

    But application pages in layouts folder are throwing 'Unknown' error.

    Any idea ?

     

    Regards

    Satish

    • Proposed as answer by kaizawa Tuesday, May 05, 2009 6:11 PM
    • Unproposed as answer by Mike Walsh FIN Wednesday, May 27, 2009 9:39 AM
    Tuesday, March 11, 2008 2:55 PM
  • I was able to resolve the issue but it was buy examining the application log and finding out that it said that the WSS_SEARCH_SHAREPOINT database was full or something to that effect.

     

    Our SP install was single server and I think that means we got the express edition of SQL Server and the true problem was that the WSS_SEARCH_SHAREPOINT database had exceeded the maximum database size for that edition.

     

    Running DBCC Shrinkdatabase reduced the file sizes enough for the upgrade process to complete.

     

    The really scary thing is that we haven't made much use of SP at all and we maxed out that database size limitation.

     

    I would say that Bill REALLY wants us to do the server farm set up and buy another SQL license.

     

    HTH

    Tuesday, March 11, 2008 9:39 PM
  • i tried both the commands neither worked.

     

    its sometimes failing saying the its trying to update the owstimer service, then sometimes saying something about diagnosticsservice.

     

    fails around the end at step 5 of 9 in the config wizard, sharepoint site is currently toast, any other ideas out there?

     

    Monday, March 17, 2008 1:51 AM
  • Running stsadm -o upgrade -inplace fixed the problem of central admin only. I can open CA now. but not the ssp and other web applications i had. I tried also stsadm -o upgrade -url http://moss:401 -inplace -forceupgrade for another web application, but still getting error. Server error: http://go.microsoft.com/fwlink?LinkID=96177.

     

    Event logs show the following error.

     

    The schema version (3.0.149.0) of the database moss401db on dbserver is not consistent with the expected database schema version (3.1.4.0) on mossserver. Connections to this database from this server have been blocked to avoid data loss. Upgrade the web front end or the content database to ensure that these versions match.

     

    Is there a way to upgrade only the database. it seems that the moss server is upgraded already.

    Saturday, April 05, 2008 6:01 AM
  •  

    Did you run the config wizard after the upgrade?
    Sunday, April 06, 2008 5:22 AM
  • I did run the config wizard.

    Sunday, April 06, 2008 6:57 AM
  • Any update???

    Saturday, April 12, 2008 6:36 AM
  • it looks like I'm getting the exact same problem as you softmoss... Sad

    all the command line comands dont work, it fails at step 3 of 4 if I run the force upgrade command and when i run the config it fails at step 9

    I've added registry entries as suggested elsewhere and I'm getting no joy anywhere.

    I'm currently trying to focus my efforts on this error

    "The schema version (3.0.149.0) of the database WSS_Content on servername\OfficeServers is not consistent with the expected database schema version (3.1.3.0) on SPSVRSP01.  Connections to this database from this server have been blocked to avoid data loss.  Upgrade the web front end or the content database to ensure that these versions match."


    Thursday, April 17, 2008 2:57 PM
  • Has anyone got any ideas please??
    Friday, April 18, 2008 12:52 PM
  • I was also getting the same error today....

     

    An error has occurred on the server.http://go.microsoft.com/fwlink?LinkID=96177

     

    And tried the command stsadm -o upgrade - inplace

     

    It worked for me   Thank you all... 

     

    Friday, April 25, 2008 8:34 AM
  • I found two instances of sqlsrv  process running. Killed on of them (took a guess as to which).

    That got me onto the next step.
    Thursday, August 07, 2008 5:36 PM
  • >where is the executable file location in Windows Server 2008 ?

    Is this relevant to this thread ?

    If not you should post it as a new thread and delete your post here.

    (Moderator)

    WSS FAQ sites: http://wssv2faq.mindsharp.com and http://wssv3faq.mindsharp.com
    Total list of WSS 3.0 / MOSS 2007 Books (including foreign language) http://wssv3faq.mindsharp.com/Lists/v3%20WSS%20FAQ/V%20Books.aspx
    Wednesday, May 27, 2009 9:41 AM
  • Yes,

    the Website still inaccessible even though i typed the following command:

    1. STSADM.EXE -o upgrade -inplace -forceupgrade -url http://mySite for each web application, then
    2. psconfig -cmd upgrade -inplace b2b -wait -force
      Please share any other way of fixing this problem after update.

    /* Windows Infrastructure Support Engineer */
    Wednesday, May 27, 2009 10:45 AM
  • Thanks all,

    I have problem same darryns
    "The schema version (3.0.149.0) of the database WSS_Content on servername\OfficeServers is not consistent with the expected database schema version (3.1.3.0) on SPSVRSP01.  Connections to this database from this server have been blocked to avoid data loss.  Upgrade the web front end or the content database to ensure that these versions match."

    I run command:  STSADM.EXE -o upgrade -inplace -forceupgrade -url http://mySite
    then
    It's lived again

    YOU SAVE ME
    Wednesday, July 29, 2009 8:55 AM
  • I had the same error when i traiyed to install WSS 3.0 SP2, and Basically, I went into Central Administration and stopped the Windows SharePoint Services Help Search and then started it again and created a new database. Then when I ran:

    psconfig -cmd upgrade -inplace b2b -wait -force


    then

    STSADM.EXE -o upgrade -inplace -forceupgrade -url http://mySite for each web application



    and it works again

    the problem comes from the database that does not connect propetly. If necesary create a new config database or doble check the user and password on database
    Tuesday, August 25, 2009 4:47 PM
  • el_bacco, you rock!! Solved my issue and saved me all sorts of time.

    Monday, November 02, 2009 9:14 PM
  • I have the same problem when I try to install wss 3.0 sp2 , the file I'm installing is: wssv3sp2-kb953338-x86-fullfile-en-us.exe

    I was able to restore a previous configuration but I need to update moss 2007.
    Any advice for a correct wss 3.0 sp1 upgrade procedure to wss 3.0 sp2 .

    thank you
    Carlo
    Friday, January 08, 2010 10:47 AM
  • Dude, this is awsome idea.. i wasted half day solving this.. done finally.. thanks a lot :)

     

    MS even has bugs in upgrades.. just kidding

    • Proposed as answer by Sammaor Tuesday, October 25, 2011 2:23 PM
    Wednesday, June 02, 2010 3:11 PM
  • I had the same problem, after updating to Sharepoint 2007 Service pack 2.

    I tried STSADM.EXE -o upgrade -inplace -forceupgrade and checked the upgrade log .

    I  found in that one of the content databases was in Read only state  (i set it a few months ago before permanently deleting a site).

    so i bought it back online and re run STSADM.EXE -o upgrade -inplace -forceupgrade , this time it run for longer time (i have 40 Databases)  it completed with and error, but i was able to access all my sites.

     next i run the SharePoint Products and Technologies Configuration Wizard and it completed successfully.

     

    Tuesday, October 25, 2011 2:23 PM