none
"Server error: http://go.microsoft.com/fwlink?LinkID=96177" after SP2 (64-bit MOSS 2007; Win 2008; SQL Serv 2008)

    Question

  • Hi All,

    I'm having problem of "Server error: http://go.microsoft.com/fwlink?LinkID=96177 " after upgrading the WSS 3.0 SP2

    the background of my server is a single server farm which is consist of
    Windows 2008 Standard SP1
    MOSS 2007 SP1 Enterprise
    SQL 2008 SP1 Standard all in 64 bit environment

    what i did is that i upgraded SQL Server 2008 SP1 -> OK
    and then WSS 3.0 SP2 --> OK (wssv3sp2-kb953338-x64-fullfile-en-us.exe)
    but MOSS 2007 SP2 --> FAILED (officeserver2007sp2-kb953334-x64-fullfile-en-us.exe)

    here is the following command that i tried but failed.
    -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
    C :\ Program Files \ Common Files \ Microsoft Shared \ Web Server Extensions \ 12 \ BIN > STSADM . EXE - o upgrade - inplace - forceupgrade - url http : //mossdev01
    The specified SPContentDatabase Name = SharePoint_AdminContent_f632e5bf - cbd9 - 4d9f - a819 - 1811feb4f2b6 Parent = SPDatabaseServiceInstance Name = MOSSDB has been upgraded to a newer version of SharePoint . Please upgrade this SharePoint application server before attempting to access this object .
    -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
    C :\ Program Files \ Common Files \ Microsoft Shared \ Web Server Extensions \ 12 \ BIN > PSCONFIG . EXE - cmd upgrade - inplace b2b - wait - force
    SharePoint Products and Technologies Configuration Wizard version 12.0.6413.1000 Copyright ( C ) Microsoft Corporation 2005. All rights reserved .

    Performing configuration task 1 of 4
    Initializing SharePoint Products and Technologies upgrade ...

    Successfully initialized SharePoint Products and Technologies upgrade .

    Performing configuration task 2 of 4
    Initiating the upgrade sequence ...

    Failed to initiate the upgrade sequence .

    An exception of type Microsoft . SharePoint . Upgrade . SPUpgradeException was thrown .
    Additional exception information : The specified SPContentDatabase Name = SharePoint_AdminContent_f632e5bf - cbd9 - 4d9f - a819 - 1811feb4f2b6 Parent = SPDatabaseServiceIn
    stance
    Name = MOSSDB has been upgraded to a newer version of SharePoint . Please upgrade this SharePoint application server before attempting to access this object .

    Total number of configuration settings run : 2
    Total number of successful configuration settings : 1
    Total number of unsuccessful configuration settings : 2
    Successfully stopped the configuration of SharePoint Products and Technologies .
    Configuration of SharePoint Products and Technologies failed . Configuration must be performed before you use SharePoint Products and Technologies . For further
    details
    , see the diagnostic log located at C :\ Program Files \ Common Files \ Microsoft Shared \ Web Server Extensions \ 12 \ LOGS \ PSCDiagnostics_5_27_2009_20_26_50_793_1641045907 . log and the application event log.
    -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------


    any idea of how to get the MOSS site back again please ?

    Thanks
    /* Windows Infrastructure Support Engineer */
    • Edited by Mike Walsh FIN Wednesday, May 27, 2009 9:35 AM Title expanded after being moved around to initially save space
    • Edited by Senior System Engineer Wednesday, May 27, 2009 10:38 AM
    Wednesday, May 27, 2009 9:30 AM

Answers

  • Hi Albert,

     
    The Updates are applied in two steps

     

    1.     Install the Bits on the servers by running the downloads wssv3sp2-kb953338-x64-fullfile-en-us.exe & officeserver2007sp2-kb953334-x64-fullfile-en-us.exe

    2.     Update the db schemas PSCONFIG.EXE - cmd upgrade - inplace b2b - wait or SharePoint Products and Technologies Configuration Wizard
    Only run the SharePoint Products and Technologies Configuration Wizard or PSCONFIG.EXE - cmd upgrade - inplace b2b -wait command after the Bits have been deployed to every SharePoint Server in the environment

     

    It appears from the information you provided the (officeserver2007sp2-kb953334-x64-fullfile-en-us.exe) failed. Also, you proceeded to run the STSADM . EXE - o upgrade - inplace - forceupgrade - url http : //mossdev01 and when you ran the PSConfig Command it failed. In addition, you have now restored the file system to SP1 without restoring the Dbs to the same state.

     

    There are three Options

     

    Option 1

    1.     Restore the Dbs to a state prior to beginning the update tonight
    a.     Note: This will leave you at your previous state with the file system and Dbs in sync

     

    Option 2

    1.     Restore the Dbs to a state prior to beginning the update tonight

    2.     Run WSS (wssv3sp2-kb953338-x64-fullfile-en-us.exe)

    a.     Note Do NOT run SharePoint Products and Technologies Configuration Wizard or run PSCONFIG.EXE - cmd upgrade - inplace b2b - wait until after running (officeserver2007sp2-kb953334-x64-fullfile-en-us.exe)

    3.     Run (officeserver2007sp2-kb953334-x64-fullfile-en-us.exe)

    4.     Run PSCONFIG.EXE - cmd upgrade - inplace b2b - wait or SharePoint Products and Technologies Configuration Wizard


    Option 3

    1.     Restore the Dbs to a state prior to beginning the update tonight

    2.     Run WSS (wssv3sp2-kb953338-x64-fullfile-en-us.exe)

    a.     Note Do NOT run SharePoint Products and Technologies Configuration Wizard or run PSCONFIG.EXE - cmd upgrade - inplace b2b - wait until after running (officeserver2007sp2-kb953334-x64-fullfile-en-us.exe)

    3.     Run (officeserver2007sp2-kb953334-x64-fullfile-en-us.exe)

    4.     Remove the content Dbs run STSADM.EXE o deletecontentdb for each Web Application

    5.     Run PSCONFIG.EXE - cmd upgrade - inplace b2b - wait or SharePoint Products and Technologies Configuration Wizard

    6.     Add the content Dbs to the Web Applications run STSADM.EXE o addcontentdb

     

    Removing the content dbs using stsadm will not delete them from SQL. Adding the content dbs using the stsadm command will upgrade them to the current version installed on the file system.

     

    There is one other issue if the GroupBoard WorkSpace is installed it should be removed prior to removing the content dbs in Option 3 or running PSConfig in Option 2 http://support.microsoft.com/default.aspx/kb/941678/



    -Ivan


    Ivan Sanders http://linkedin.com/in/iasanders http://dimension-si.com/blog
    Thursday, May 28, 2009 10:11 AM

All replies

  • and I've got the following Error logged in the EventViewer:

    Log Name:      Application
    Source:        Windows SharePoint Services 3
    Date:          27/05/2009 7:24:39 PM
    Event ID:      5617
    Task Category: Topology
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      MOSSDEV01.domain.com
    Description:
    The schema version (3.1.3.0) of the database MySite_ContentDB on MOSSDEV01\MOSSDB is not consistent with the expected database schema version (3.1.8.0) on MOSSDEV01.  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.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Windows SharePoint Services 3" />
        <EventID Qualifiers="0">5617</EventID>
        <Level>2</Level>
        <Task>807</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2009-05-27T09:24:39.000Z" />
        <EventRecordID>216355</EventRecordID>
        <Channel>Application</Channel>
        <Computer>MOSSDEV01.domain.com</Computer>
        <Security />
      </System>
      <EventData>
        <Data>The schema version (3.1.3.0) of the database MySite_ContentDB on MOSSDEV01\MOSSDB is not consistent with the expected database schema version (3.1.8.0) on MOSSDEV01.  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. </Data>
      </EventData>
    </Event>
    /* Windows Infrastructure Support Engineer */
    Wednesday, May 27, 2009 9:35 AM
  • Again, this is what I've got after restoring the MOSS 2007 SP1 image from the tape drive which is quite old, any idea to get it back again is very much appreciated.

    Thanks.

    Log Name:      Application
    Source:        Report Server Windows Service (MOSSDB)
    Date:          28/05/2009 6:01:04 PM
    Event ID:      140
    Task Category: Startup/Shutdown
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      MOSSDEV01.domain.com
    Description:
    The application domain WindowsService_0 failed to initialize. Error: Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerDatabaseUnavailableException: The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing. ---> System.Data.SqlClient.SqlException: Cannot open database "ReportServer$MOSSDB" requested by the login. The login failed.
    Login failed for user 'NT AUTHORITY\NETWORK SERVICE'.
       at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
       at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
       at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
       at System.Data.SqlClient.SqlConnection.Open()
       at Microsoft.ReportingServices.Library.ConnectionManager.OpenConnection()
       --- End of inner exception stack trace ---
       at Microsoft.ReportingServices.Library.ConnectionManager.OpenConnection()
       at Microsoft.ReportingServices.Library.ConnectionManager.ConnectStorage()
       at Microsoft.ReportingServices.Library.ServiceController.ServiceStartThread(Object firstStart).
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Report Server Windows Service (MOSSDB)" />
        <EventID Qualifiers="0">140</EventID>
        <Level>2</Level>
        <Task>9</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2009-05-28T08:01:04.000Z" />
        <EventRecordID>214831</EventRecordID>
        <Channel>Application</Channel>
        <Computer>MOSSDEV01.domain.com</Computer>
        <Security />
      </System>
      <EventData>
        <Data>WindowsService_0</Data>
        <Data>Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerDatabaseUnavailableException: The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing. ---&gt; System.Data.SqlClient.SqlException: Cannot open database "ReportServer$MOSSDB" requested by the login. The login failed.
    Login failed for user 'NT AUTHORITY\NETWORK SERVICE'.
       at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
       at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
       at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
       at System.Data.SqlClient.SqlConnection.Open()
       at Microsoft.ReportingServices.Library.ConnectionManager.OpenConnection()
       --- End of inner exception stack trace ---
       at Microsoft.ReportingServices.Library.ConnectionManager.OpenConnection()
       at Microsoft.ReportingServices.Library.ConnectionManager.ConnectStorage()
       at Microsoft.ReportingServices.Library.ServiceController.ServiceStartThread(Object firstStart)</Data>
      </EventData>
    </Event>
    /* Windows Infrastructure Support Engineer */
    Thursday, May 28, 2009 8:30 AM
  • Hi Albert,

     
    The Updates are applied in two steps

     

    1.     Install the Bits on the servers by running the downloads wssv3sp2-kb953338-x64-fullfile-en-us.exe & officeserver2007sp2-kb953334-x64-fullfile-en-us.exe

    2.     Update the db schemas PSCONFIG.EXE - cmd upgrade - inplace b2b - wait or SharePoint Products and Technologies Configuration Wizard
    Only run the SharePoint Products and Technologies Configuration Wizard or PSCONFIG.EXE - cmd upgrade - inplace b2b -wait command after the Bits have been deployed to every SharePoint Server in the environment

     

    It appears from the information you provided the (officeserver2007sp2-kb953334-x64-fullfile-en-us.exe) failed. Also, you proceeded to run the STSADM . EXE - o upgrade - inplace - forceupgrade - url http : //mossdev01 and when you ran the PSConfig Command it failed. In addition, you have now restored the file system to SP1 without restoring the Dbs to the same state.

     

    There are three Options

     

    Option 1

    1.     Restore the Dbs to a state prior to beginning the update tonight
    a.     Note: This will leave you at your previous state with the file system and Dbs in sync

     

    Option 2

    1.     Restore the Dbs to a state prior to beginning the update tonight

    2.     Run WSS (wssv3sp2-kb953338-x64-fullfile-en-us.exe)

    a.     Note Do NOT run SharePoint Products and Technologies Configuration Wizard or run PSCONFIG.EXE - cmd upgrade - inplace b2b - wait until after running (officeserver2007sp2-kb953334-x64-fullfile-en-us.exe)

    3.     Run (officeserver2007sp2-kb953334-x64-fullfile-en-us.exe)

    4.     Run PSCONFIG.EXE - cmd upgrade - inplace b2b - wait or SharePoint Products and Technologies Configuration Wizard


    Option 3

    1.     Restore the Dbs to a state prior to beginning the update tonight

    2.     Run WSS (wssv3sp2-kb953338-x64-fullfile-en-us.exe)

    a.     Note Do NOT run SharePoint Products and Technologies Configuration Wizard or run PSCONFIG.EXE - cmd upgrade - inplace b2b - wait until after running (officeserver2007sp2-kb953334-x64-fullfile-en-us.exe)

    3.     Run (officeserver2007sp2-kb953334-x64-fullfile-en-us.exe)

    4.     Remove the content Dbs run STSADM.EXE o deletecontentdb for each Web Application

    5.     Run PSCONFIG.EXE - cmd upgrade - inplace b2b - wait or SharePoint Products and Technologies Configuration Wizard

    6.     Add the content Dbs to the Web Applications run STSADM.EXE o addcontentdb

     

    Removing the content dbs using stsadm will not delete them from SQL. Adding the content dbs using the stsadm command will upgrade them to the current version installed on the file system.

     

    There is one other issue if the GroupBoard WorkSpace is installed it should be removed prior to removing the content dbs in Option 3 or running PSConfig in Option 2 http://support.microsoft.com/default.aspx/kb/941678/



    -Ivan


    Ivan Sanders http://linkedin.com/in/iasanders http://dimension-si.com/blog
    Thursday, May 28, 2009 10:11 AM
  • Wow, that's quite complex, thanks for providing me with the solution Ivan.

    My MOSS 2007 deployment is very simple only in one single server. I wonder how do people do in the real world production farm, it must be a very big problem for the admin.

    anyway, I'd better be waiting for SP 2010 because MOSS 2007 SP2 feature doesn't worth the hassle.

    Thanks once again.

    Cheers.
    /* Windows Infrastructure Support Engineer */
    Thursday, May 28, 2009 1:08 PM