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

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...
167 comments
Read more

KB5025885: How to manage the Windows Boot Manager revocations for Secure Boot changes associated with CVE-2023-24932

By
This article outlines the protection against the publicly disclosed Secure Boot security feature bypass involving the BlackLotus UEFI bootkit (CVE-2023-24932). It includes steps to enable the necessary mitigations and provides guidance on creating bootable media. I will provide: - An overview of the CVE issue. - Pre-requisite actions within ADK. - Detection and remediation scripts for CVE-2023-24932. - Instructions for creating a WinPE Boot.wim file to support systems that have undergone remediation. - A breakdown of the files changed and how to boot WinPE to support systems before remediation. 1. Secure Boot Security Feature Bypass Vulnerability CVE-2023-24932 see MSRC CVE-2023-24932 is a security vulnerability involving the BlackLotus UEFI bootkit, which allows attackers to bypass Secure Boot protections. This vulnerability enables the execution of malicious code at the UEFI level, potentially leading to persistent and evasive threats. Mitigations for this issue include updates to th...
Post a Comment
Read more

Java 7 update 21 (1.7.0_21) Enterprise Repackaged Security Medium Deployment with SCCM

By
------------------------------------------------------------------------------------------------- Java 7 update 45 Enterprise deployment complete walk through http://www.syswow64.co.uk/2013/10/java-7-update-45-enterprise-deployment.html -------------------------------------------------------------------------------------------------- The issue on many blogs and articles is around creating the 'deployment.config' and 'deployment.properties' files for an enterprise deployment.  In my case i wanted to set the security level to 'Medium', but everytime I open the Java control panel it was set to the default HIGH setting. Solution 1 Create the following directory path 'C:\Windows\sun\java\deployment' 2 Create a file called 'deployment.config' in this directory and open with Notepad. Copy the two line below #################### deployment.system.config = file\:\\C\:\\WINDOWS\\Sun\\Java\\Deployment\\deployment.properties deployment.system...
15 comments
Read more