locked
Not able to open Shared Services from Central Admin RRS feed

  • Question

  • Hi,

    When im trying to open Shared Services from Central Admin in MOSS 2007, i'm getting an error as below.

    We have a single Farm and and a SQL Server

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

    Below is the log.

    The schema version (3.1.8.0) of the database PwCCanadaPortal_SharedServices_Content on CALIDCWNDB730CS is not consistent with the expected database schema version (3.1.11.0) on CALIDCWNSS750.  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.

    As per various blogs, i tried the below approaches.

    Approach 1:

    Ran the Sharepoint Wizard Manually, it failed at step8.

    Approach 2:

    Ran the below STSADM script.

    stsadm -o upgrade -inplace -url "Central Admin URL"

    still got an error. Below is teh log error.

    Failed to upgrade SharePoint Products and Technologies.
    Failed to upgrade SharePoint Products and Technologies.  Further information regarding this failure can be found at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS\Upgrade.log.
    An exception of type Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException was thrown.  Additional exception information: Failed to upgrade SharePoint Products and Technologies.
    Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException: Exception of type 'Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException' was thrown.
       at Microsoft.SharePoint.PostSetupConfiguration.UpgradeTask.Run()
       at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()

    Approach 3:

    psconfig -cmd upgrade -inplace b2b -wait -force

    This also failed with the below logs.

    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...

    Successfully initiated the upgrade sequence.

    Performing configuration task 3 of 4
    Upgrading SharePoint Products and Technologies...

    Failed to upgrade SharePoint Products and Technologies.

    An exception of type Microsoft.SharePoint.Upgrade.SPUpgradeException was thrown.
      Additional exception information: Upgrade completed with errors.  Review the u
    pgrade.log file located in C:\Program Files\Common Files\Microsoft Shared\Web Se
    rver Extensions\12\Logs\Upgrade.log.  The number of errors and warnings is liste
    d at the end of the upgrade log file.

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

    Can someone please help me on this.

    Thanks in advance,

    Sridhar S

    Monday, October 20, 2014 9:35 AM

Answers

  • Hi sridhar,

    as per the log details this is purely DB version mismatch issue.

    can you please try below steps

    Error1:
    Your backup is from a different version of Windows SharePoint Services and cannot be restored to a server running the current version. The backup file should be restored to a server with version ‘12.0.0.6318’ or later.

    Fix:
    Install Infrasturcture update for wss.
    (if done check for infra update for moss). sp1 for both moss and wss.

    mentioned in blog post

    http://rehmangul.wordpress.com/2009/03/10/moss-errors-and-their-fixes-or-workarounds/

    Hope that's helps you.

    Regards

    Soni K

    Monday, October 20, 2014 1:42 PM

All replies

  • look for errors in C:\Program Files\Common Files\Micros
    oft Shared\Web Server Extensions\12\LOGS\PSCDiagnostics_10_19_2014_5_17_49_868_9
    80508390.log

    you can start from the bottom of the log anf search for "ERR" making it case sensitive.

    come back with more details fro that log ...we need to check where the PSConfig is failing.

    the content database on which you have you SSP is not at same patch level as your config database ... you can further confirm this by checking dbo.version table for both config DB and Content DB of your SSP.


    Thanks, Noddy

    Monday, October 20, 2014 9:41 AM
  • if you just wanna troubleshoot it ... at extreme level ... detching the problematic database and attaching it back will upgrade its schema ... BUT ... there are possibilites that it might not get attached again ... hence make sure that you have backup of the Content DB before you try this.


    Thanks, Noddy

    Monday, October 20, 2014 9:44 AM
  • Hi,

    Please find the log info whith ERR

    10/19/2014 05:22:12  8  ERR            Task upgrade has failed with an unknown exception

    10/19/2014 05:22:12  8  ERR            Exception: Microsoft.SharePoint.Upgrade.SPUpgradeException: Upgrade completed with

    10/19/2014 05:22:12  8  ERR            An exception of type Microsoft.SharePoint.Upgrade.SPUpgradeException was thrown. 

    10/19/2014 05:22:12  8  ERR              Task upgrade has failed

    10/19/2014 05:22:12  1  ERR          Task upgrade SharePoint Products and Technologies failed, so stopping execution of the engine

    10/19/2014 05:22:12  1  ERR          Failed to upgrade SharePoint Products and Technologies.

    10/19/2014 05:22:12  1  ERR          One or more configuration tasks has failed or some tasks were not run

    10/19/2014 05:22:12  1  ERR        One or more configuration tasks has failed to execute

    10/19/2014 05:22:12  1  ERR          Configuration of SharePoint Products and Technologies failed.  Configuration must be performed in order for this product to operate properly.  To diagnose the problem, review the extended error information located at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS\PSCDiagnostics_10_19_2014_5_17_49_868_980508390.log, fix the problem, and run this configuration wizard again.

    10/19/2014 05:22:12  1  ERR      Post setup configuration was not run successfully when using the command line task driver

    Monday, October 20, 2014 10:22 AM
  • those errors give nothing ... lets try the PSConfig once more ..

    execute

    stsadm -o setproperty -pn command-line-upgrade-running -pv No

    then IISReset

    psconfig -cmd upgrade -inplace b2b -wait -force

    if this did not work .. then detaching - attching the content DB will be only thing ... but remember .. if it doesnt gets attached again, you might have to create a new SSP.


    Thanks, Noddy

    Monday, October 20, 2014 10:27 AM
  • and also one more thing that i noticed was..... everytime when i run the wizard or the STSADM commands, the Windows Sharepoint Timer Service stops and doesn't restarts again.
    Monday, October 20, 2014 11:05 AM
  • the PSConfig wizrd stops the timer service, you can notice when you run the wizard from GUI, it promps saying following services will be restarted ... there will be IIS, timer service and one more.

    in our case, since PSCOnfig is not completing successfully, the timer service is not getting restarted.

    but, if there are any issues with Tmer, there would be an event for this ... check your event viewer if you have aanything error or warning for sharepoint.


    Thanks, Noddy


    • Edited by Noddy_A Monday, October 20, 2014 11:31 AM
    Monday, October 20, 2014 11:31 AM
  • Thanks Noddy for all your previos replies. I got this blog http://www.topsharepoint.com/detaching-databases-in-moss-2007 , which explains about detaching and attaching an SSP Content DB. I will test this on stage environment and cross verify. Meantime can you please suggest whether is this the right approach that we can follow?
    Monday, October 20, 2014 12:49 PM
  • wait .. lets not do that yet ...

    try

    stsadm -o upgrade -inplace -url <URL of your SSP web application>

    if that doesnt work ... then do detach - attache .. (its good to do this in stagin env as it is risky ... and if it is single server installtion ... take a snapshot of the machine)

    dont use stsadm -o preparetomove (REF: http://blogs.msdn.com/b/toddca/archive/2009/01/30/preparetomove-away-from-running-this-command.aspx)

    A. detach the DB from GUI ...

    1. Open the Central Administration web site.
    2. Select "Content Databases".
    3. Drop down the box for "Web Application" and select "Change Web application".
    4. Select one application at a time until one gets to see the one using PwCCanadaPortal_SharedServices_Content .
    5. Click PwCCanadaPortal_SharedServices_Content to bring up the "Manage Content Database Settings" page.
    6. Make sure to write down the database name and the URL the application uses, for later use.
    7. Select the checkbox for "Remove content database".
    8. Select OK for the message that pops up.
    9. Select OK for the page.
      The database is removed from the farm.

    then ... execute

    stsadm -o setproperty -pn command-line-upgrade-running -pv No

    then IISReset

    then

    psconfig -cmd upgrade -inplace b2b -wait -force

    B . Attche the content database ...

    Stsadm  -o  addcontentdb  -url  http://yourapplicationsebsite/ -databasename PwCCanadaportal_SharedServices_Content


    Thanks, Noddy


    • Edited by Noddy_A Monday, October 20, 2014 1:30 PM database name correction
    Monday, October 20, 2014 1:28 PM
  • Hi sridhar,

    as per the log details this is purely DB version mismatch issue.

    can you please try below steps

    Error1:
    Your backup is from a different version of Windows SharePoint Services and cannot be restored to a server running the current version. The backup file should be restored to a server with version ‘12.0.0.6318’ or later.

    Fix:
    Install Infrasturcture update for wss.
    (if done check for infra update for moss). sp1 for both moss and wss.

    mentioned in blog post

    http://rehmangul.wordpress.com/2009/03/10/moss-errors-and-their-fixes-or-workarounds/

    Hope that's helps you.

    Regards

    Soni K

    Monday, October 20, 2014 1:42 PM