Skip to main content

ConfigMgr 2012 Service Pack Upgrade - Unsupported ConfigMgr database version

By
ConfigMgr 2012 Service Pack Upgrade
(SCCM 2012 R2 SP1 upgrade)

I was performing the initial Test Database command from the SMSSETUP\BIN\X64 directory of the installation media run the following command:
(Setup.exe /testdbupgrade <database_name> )

Once the Pre-requistite check runs it references 'Unsupported ConfigMgr database version' and log states 'Failed to connect to SQL Server to verify site version'.
If you search else where you may think this is a permissions based issue (definately check) but in my case this was not the case and i knew the database was supported.


===== INFO: Prerequisite Type & Server: SQL: =====
<<<RuleCategory: Database Upgrade Requirements>>>
<<<CategoryDesc: Checking the target ConfigMgr database is ready to upgrade...>>>
INFO: CheckTestDBVersion start ...
ERROR: Failed to connect to SQL Server to verify site version.
Unsupported ConfigMgr database version;    Error;    For the site database upgrade to succeed, the database version must be Configuration Manager 2012 R2 or later.
INFO: Start checking SQL Native Client 11.
INFO: SQL Native Client 11 is already installed on local machine.
Sql Server Native Client;    Passed
INFO: SQL Server computer <Name.Domain.COM>
INFO: SQL Server named instance <>
INFO: Cannot connect to registry key.


Resolution: It was an issue in the Syntax on the command line. It is quite common for the database name to resemble CM_P01 or CM_P02 etc.  However, in this case it was CM_PO1 and CM_P02 etc.
If you look closely there is a difference.  Check whether its a ZERO (0) or a letter O

Setup.exe /testdbupgrade <database_name>
Labels:

Comments

  1. AnonymousAugust 2, 2016 at 3:11 AM

    Yes, not a very intelligent bit of code behind this error evidently. It also means, as you discovered, "The specified database was not found".

    ReplyDelete
  2. Innocent MkSeptember 27, 2017 at 12:20 AM

    Locking or two-phase locking is a leading method for initiating concurrency control to facilitate the management of databases. kpi dashboards

    ReplyDelete
  3. Kavin cookOctober 23, 2017 at 4:39 AM

    Database security is done periodically by the administrator of the company's website for closely monitoring the activities of the users who have access to the database. create dashboard for oracle

    ReplyDelete

Post a Comment

Popular posts from this blog

SCCM Unknown computer not able to see Task Sequences after installing Current Branch 1702

By
Soon after installing SCCM CB 1702 we were unable to see Task Sequences deployed to the unknown collection. This issue was identified as a random system taking the GUID of the 'x64 Unknown Computer (x64 Unknown Computer)' record. As a result it was now a known GUID; as we were only deploying Task Sequences to the Unknown collection none were made available. 'x64 Unknown Computer (x64 Unknown Computer)' record 'x86 Unknown Computer (x86 Unknown Computer)' record To get the GUID of your unknown systems open SQL management studio and run the following command: --Sql Command to list the name and GUID for UnknownSystems record data select ItemKey, Name0,SMS_Unique_Identifier0 from UnknownSystem_DISC Using the returned GUID (SMS_Unique_Identifier0) we can find the hostname that has been assigned the 'x64 Unknown Computer (x64 Unknown Computer)' GUID by running the query below. --x64 Unknown Computers select Name0,SMS_Unique_Identifier0,Decommissioned0 from Sys...
161 comments
Read more

Windows 7 Offline files will not go Online when connected to network

By
Issue Several laptop users move between networks, domain, home, etc and when they attempt to access DFS shares explorer status is working offline.  The issue only resolves it self after a reboot. Connecting directly to the share works and i am able to ping network resources.  This behavior occurs for VPN users as well. Possible Causes "slow-link mode". In win7 (with default settings) a client will enter slow-link mode if the latency to the server is above 80ms. In slow-link mode all writes are made to the local cache and a background sync only happens every 6 hours.  Depending on your connection the default slow link detection speed is 64,000 bps On client computers running Windows 7 or Windows Server 2008 R2, a shared folder automatically transitions to the slow-link mode if the round-trip latency of the network is greater than 80 milliseconds, or as configured by the "Configure slow-link mode" policy. After transitioning a folder to the slow-link mode, Offline Fil...
151 comments
Read more

SCCM Software Update - Job error 0x80004005 Failed to Add Update Source for WUAgent

By
SCCM Software Updates - Failed to Add Update Source for WUAgent  Today I have been looking at a range of servers (Server 2008 /R2 2012 /R2) that were failing to communicate with the Software Update Point (SUP) in SCCM and retrieve deployment policy. The UpdateDeployment.log was reporting the Job error 0x80004005 Job error (0x80004005) received for assignment ({af7a48e6-d550-4070-dd9b-ecc234567584}) action UpdatesDeploymentAgent 12/6/2017 10:32:27 AM 2096 (0x0830) The WUAHandler.log  was reporting "Unable to read existing WUA Group Policy object" and "Failed to Add Update Source for WUAgent " Unable to read existing WUA Group Policy object. Error = 0x80004005. WUAHandler 12/6/2017 3:41:00 AM 2828 (0x0B0C) Failed to Add Update Source for WUAgent of type (2) and id ({3AAB6A76-CE2D-4E8A-9F11-123AE69612A1}). Error = 0x80004005. WUAHandler 12/6/2017 11:03:31 AM 2276 (0x08E4) Until the agent can report back to the SUP, SCCM will not be able to summarize Software Update sta...
4 comments
Read more