SCCM CB WSUS Config File did not Contain a Value InstanceName Error

Let’s discuss the SCCM CB WSUS Config File, which did not contain a Value InstanceName Error. SCCM CB 1702 WSUS and SUP configurations are essential for software updates/patching.

The latest introduction of Windows 10 and Office 365 servicing to SCCM increased the importance of WSUS integration. I’ve been facing WSUS installation and configuration issues with the SCCM CB 1703 version.

In this post, we will see a couple of issues and solutions. The second issue I will cover today is “Config file did not contain a Value InstanceName Error“. This random post covers my issues while building the new SCCM CB infra.

The WSUS installation on remote SCCM CB 1702 SUP was stopped because of connectivity issues with the remote SQL DB. This was resolved by adding proper SPN values to the SQL service account.

Patch My PC

How to Fix SPN Issue for Remote SQL Server – SCCM CB WSUS Config File did not Contain a Value InstanceName Error

Let’s discuss how to fix the SPN issue for the remote SQL server. Following are the SPN registration commands to fix the remote SQL connectivity issues.

  • ERROR: Can’t retrieve SQL connection. Exception: System.Data.SqlClient.SqlException (0x80131904): The principal target name is incorrect. Cannot generate SSPI context
  • setspn -a mssqlsvc/SCCM01:1433 ACN\asqld
  • setspn -a mssqlsvc/SCCM01.ACN.com:1433 ACN\asqld
SCCM CB WSUS Config File did not Contain a Value InstanceName Error - Fig.1
SCCM CB WSUS Config File did not Contain a Value InstanceName Error – Fig.1

How to Fix WSUS/SUP Installation Issue with SQL Default Instance?

After fixing the SPN issue, the WSUS installation error changed to something else. The logs revealed that the WSUS configuration file didn’t have the details of the SQL instance.

I didn’t put the instance name as my remote SQL was on the default instance. To fix WSUS connectivity, I provided the default SQL instance name.

  • SCCM01\MSSQLSERVER,1433

The content directory is I:\WSUS.
Start: GetConfigValue with filename=UpdateServices-DB.xml item=InstanceName
The config file did not contain the value “InstanceName.
Microsoft.UpdateServices.Administration.CommandException: A required configuration value was not found in the system.

Adaptiva
SCCM CB WSUS Config File did not Contain a Value InstanceName Error - Fig.2
SCCM CB WSUS Config File did not Contain a Value InstanceName Error – Fig.2

How to Fix WSUS/SUP Configuration Issues with SQL DB Deadlock

The post-installation process of WSUS got stuck with the following errors.  The FIRST TIME when I tried to perform the WSUS Post-installation process. This error was solved by deleting the WSUS pool from IIS.

  • The log file is located at C:\Users\anoop\AppData\Local\Temp\2\tmpC600.tmp
  • Post-install is starting
  • Fatal Error: Invalid object name ‘SUSDB.dbo.tbSchemaVersion’.

When I tried to perform the WSUS Post-installation process, the SECOND TIME got stuck with SQL DB deadlock.

  • The log file is located at C:\Users\anoop\AppData\Local\Temp\2\tmp5A82.tmp
  • Post-install is starting
  • Fatal Error: Transaction (Process ID 100) was deadlocked on lock resources with another process and chosen as the deadlock victim. Rerun the transaction
  • ALTER DATABASE statement failed.

The resolution was to run the following command to unlock the SQL DB

  • USE MASTER;
  • ALTER DATABASE [SUSDB] SET MULTI_USER

Resources

We are on WhatsApp now. To get the latest step-by-step guides, news, and updates, Join our Channel. Click here. HTMD WhatsApp.

Author

Anoop C Nair is Microsoft MVP! He is a Device Management Admin with more than 20 years of experience (calculation done in 2021) in IT. He is a Blogger, Speaker, and Local User Group HTMD Community leader. His main focus is on Device Management technologies like SCCM 2012, Current Branch, and Intune. He writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc.

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.