locked
Databases running in compatibility range, upgrade recommended.

    Question

  • I am running Windows Server 2008 R2 and Sharepoint foundation 2010. Both the server install and sharepoint are new and I don't understad why I am getting the the following notification in my Sharepoint Central Administration Console:

    The SharePoint Health Analyzer has detected some critical issues that require your attention. View these issues. When i clicked view issues two issues which are as follows:

    1.

     

    Title

    Databases running in compatibility range, upgrade recommended.

    Severity

    2 - Warning

    Category

    Configuration

    Explanation

    The following databases have versions that are older than the current SharePoint software, but are within the backwards compatible range:
    SharePoint_Config_53245559-f688-46f8-9c1e-e6a5553fd80b,
    SharePoint_AdminContent_bdba18ef-0884-4062-ad0e-0e3674b9d814,
    WSS_Content,
    WSS_Logging.

    Remedy

    To achieve optimal results from these databases, use Upgrade-SPContentDatabase to upgrade Content databases, or psconfig.exe to upgrade other databases.  For more information about this rule, see "http://go.microsoft.com/fwlink/?LinkID=142697".

    Failing Servers

     

    Failing Services

    SPTimerService (SPTimerV4)

    Rule Settings

    View

    The problem is when i go to the links under the Remedy headings they are both not providing me with any clear solutions.

    For the first problem I am not sure which of the services in the list I am supposed to change the administratoring account to and for the second problem i am getting the sharepoint foundation hotfix download and when I requested it, the information sent back from microsoft made me think twice whether i should install it or not. I am really unsure if the hotfix is the right solution for my problem.

    Title

    The server farm account should not be used for other services.

    Severity

    1 - Error

    Category

    Security

    Explanation

    NT AUTHORITY\NETWORK SERVICE, the account used for the SharePoint timer service and the central administration site, is highly privileged and should not be used for any other services on any machines in the server farm.  The following services were found to use this account: SharePoint - 80 (Application Pool)
    SPUserCodeV4(Windows Service)

    Remedy

    Browse to http://am-pedia:5579/_admin/FarmCredentialManagement.aspx and change the account used for the services listed in the explanation. For more information about this rule, see "http://go.microsoft.com/fwlink/?LinkID=142685".

    Failing Servers

     

    Failing Services

    SPTimerService (SPTimerV4)

    Rule Settings

    View

     

    2.

    • Moved by Mike Walsh FIN Thursday, July 28, 2011 8:04 AM SP 2010 question (posted during my months off ...) (From:SharePoint - Setup, Upgrade, Administration and Operation (pre-SharePoint 2010))
    Tuesday, July 27, 2010 4:10 PM

Answers

  • I ran these hotfixes on my frontends:

    417831_intl_x64_zip.exe

    429437_intl_x64_zip.exe

    429440_intl_x64_zip.exe

    Restarted and followed by 1,2,3

    1. Open an Administrative command prompt.

    2. Change directory to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN

    3. Run PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures

    Wednesday, July 27, 2011 5:53 PM

All replies

  • I'd 1st recommend you do use an NT ID  (as stated above) and 2nd have you tried to use an old sharepoint db?


    Kris Wagner, MCITP, MCTS Twitter @sharepointkris Blog: http://www.sharepointkris.com/blog
    Wednesday, July 28, 2010 12:33 AM
    Moderator
  • For the first warning message, you can run this command: psconfig.exe -cmd upgrade -inplace  for detail, please refer to http://technet.microsoft.com/en-us/library/cc263093.aspx

     

    For the second error message, it says that the SharePoint -80 web application pool and the SPUserCodeV4 windows service is running under the same account with the SPTimerV4, which is not recommended. Since the SPTimerV4 is running under the account NETWORK SERVICE, I think you are running a standalone installation. The solution is quite clear in the Remedy section, you can change the SharePoint -80 web application pool account and the SPUserCodeV4 windows service account.

     

    Wednesday, July 28, 2010 2:06 AM
    Moderator
  • I ran the psconfig.exe -cmd upgrade -inplace command and it run for 4 steps and completed them successfully. I rebooted the server after completion and the warning is still there.

    As for the second problem I am having a problem figuring out this service is SPUserCodeV4 Windows services account as its not on the list of services

     

    Wednesday, July 28, 2010 7:23 AM
  • There were only two accounts, the Network Services and Local Services so I went on to create a third account as SharePoint - 80 (Application Pool) wouldn't move over to Local Services so now the SharePoint – 80 is running on the third account I created. My problem is I am unable to identify the SPUserCodeV4(Windows Service) as its not listed.

    As for the second problem, No I haven’t tried running an old SharePoint db. This is a fresh install.

    Wednesday, July 28, 2010 7:59 AM
  • After I changed the account from Network Services to the domain admin account I created users were unable to automatically login to SharePoint. It was requesting a username and password, upon entering user details the page just hang on a blank white page. I have since changed it back to Network Services to allow users to work.

    Wednesday, July 28, 2010 8:56 AM
  • Does anyone have any other ideas I could try out?

    Wednesday, July 28, 2010 2:30 PM
  •  

    1.       Could you please try the psconfig command with force parameter: psconfig.exe -cmd upgrade -inplace -force

     

    2.       By SPUserCodeV4, I mean the Windows Service Microsoft SharePoint Foundation Sandboxed Code Service.

     

    3.       After I changed the account from Network Services to the domain admin account I created users were unable to automatically login to SharePoint. It was requesting a username and password, upon entering user details the page just hang on a blank white page.  

    Have you run IISReset as required after changing the web application pool account?

    I currently do not have a standalone installation on hand to test, but it works well in the Contoso IW Demo VM: I created a new domain account, changed the SharePointContentAppPool account to this new account in Central Administration->Configure Service Accounts page, and run IISReset /noforce. The web applications work well, and I can see that the new domain account is added into Windows groups such as WSS_WPG automatically, and it is also added as user in content databases in SQL Server.

    Thursday, July 29, 2010 2:15 AM
    Moderator
  • The force upgrade worked and the warning has gone, thank you! 

    However I am still having problems changing the ''Sandboxed Code Services'' and ''SharePoint - 80 Services'' from the Network Services Account. When I changed both "Sandboxed Code Services'' and SharePoint - 80 (Application Pool) to the domain admin account the website refused to open. It had a login box and no credentials will grant access to the site, are there any other services that will have to be changed.  

     

    Thursday, July 29, 2010 4:59 PM
  • What kind of authentication do you use? You need to configure SPN if you use Kerberos. Please read what follows:

     

    http://blogs.msdn.com/b/russmax/archive/2009/10/20/configuring-kerberos-authentication-in-sharepoint-2010-part-1.aspx

    http://technet.microsoft.com/en-us/magazine/ee914605.aspx

    http://technet.microsoft.com/en-us/library/ee806870.aspx

     

     

     

    Gu Yuming

    TechNet Subscriber Support in forum

    If you have any feedback on our support, please contact tngfb@microsoft.com

    Tuesday, August 03, 2010 3:42 AM
    Moderator
  • Hi guys,

    "psconfig.exe -cmd upgrade -inplace -force" does'nt work for me but "psconfig -cmd -upgrade -inplace v2v -force -wait" works. however i still have the following warning.

    "The following databases have versions that are older than the current SharePoint software, but are within the backwards compatible range:
    WSS_Logging."
    Thanks in advance.
     
    Wednesday, August 18, 2010 7:31 AM
  • Hi,

    I just ran into this, I uninstalled SharePoint 2010 Foundation on Windows Server 2008 R2, reinstalled fresh every was fine. I applied windows updates and included one for SP2010 and lo and behold, it left my databases out of range, with no help. (It's a one click install with NTLM, no kerberos).

    I wasted time, found the -inplace v2v -wait and I'm now in the same place as RayTong101.

    I've only got the logging thats out of range, now what can we do to fix it.

    Why does microsoft break so much with these automatic updates!

    Any help would be appreciated.

    Anthony

    Monday, September 13, 2010 8:58 AM
  • I'm getting th WSS_Logging as the only database that is out of date as well.. I'm also getting an error similar to the one above except for mine references the "Visio Graphics Services " instead of the sandbox service.

    it seems there isn't much out there to help with stand alone installs.. I also am having a heck of a time setting up incoming email on the site. i don't have servicve accounts setup for anything since it was a standalone install, but i found these instructions with are pretty clear, http://sharepointgeorge.com/2010/configuring-incoming-email-sharepoint-2010/ - but I don't think they apply.

    any ideas?

    Wednesday, September 29, 2010 5:37 PM
  • I ran these hotfixes on my frontends:

    417831_intl_x64_zip.exe

    429437_intl_x64_zip.exe

    429440_intl_x64_zip.exe

    Restarted and followed by 1,2,3

    1. Open an Administrative command prompt.

    2. Change directory to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN

    3. Run PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures

    Wednesday, July 27, 2011 5:53 PM
  • Thank you Dameon. That command line of PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures allowed me to complete the process with no errors.

    Thanks!

    Saturday, October 15, 2011 3:10 PM
  • I ran these hotfixes on my frontends:

    417831_intl_x64_zip.exe

    429437_intl_x64_zip.exe

    429440_intl_x64_zip.exe

    Restarted and followed by 1,2,3

    1. Open an Administrative command prompt.

    2. Change directory to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN

    3. Run PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures


    The referenced EXE files dont seem to be available anymore, so I used Windows Update and applied all of the available patches.

    The command works as referenced up until the 'applicationcontent' entry. My console returned 'The applicationcontent command is invalid'.

    I entered the command without 'applicationcontent -install -cmd installfeatures' and it completed successfully.

    Here is the output:

    SharePoint Products Configuration Wizard version 14.0.4762.1000. Copyright (C) M
    icrosoft Corporation 2010. All rights reserved.

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

    Waiting to get a lock to upgrade the farm.

    Successfully initialized SharePoint Products 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...

    10.00%The farm is being upgraded in the timer service process. The task is 17.37
    % completed.

    The farm is being upgraded in the timer service process. The task is 18.30% comp
    leted.

    The farm is being upgraded in the timer service process. The task is 94.95% comp
    leted.

    Successfully upgraded SharePoint Products.

    Performing configuration task 4 of 4
    Finalizing the SharePoint Products configuration...

    Successfully completed the SharePoint Products configuration.

    Total number of configuration settings run: 4
    Total number of successful configuration settings: 4
    Total number of unsuccessful configuration settings: 0
    Successfully stopped the configuration of SharePoint Products.
    Configuration of the SharePoint Products has succeeded.

    Tuesday, December 06, 2011 7:12 PM
  • hi Jacob Alexander,

     

    any solution, have u fix it. me in same situation.

     


    iffi
    Tuesday, January 31, 2012 9:12 AM