Skip to content
Trending
Simplify Windows Devices to Run Only the Required Applications using Intune Enhance macOS Compliance with Custom Security and Compliance Checks to Improve Device Security using Microsoft Intune Manage Samsung Galaxy Firmware Versions to Improve Security and Compliance using Microsoft Intune MS Intune Adds Windows Registry Data Collection to Device Inventory for Single Values All Key Values and Subkeys Updated Windows Device Sync Experience Enhances Per-Device Troubleshooting Configure Windows Sandbox vGPU Policy using Intune for Better Graphics Performance or Reduced Attack Surface Simplify Windows Devices to Run Only the Required Applications using Intune Enhance macOS Compliance with Custom Security and Compliance Checks to Improve Device Security using Microsoft Intune Manage Samsung Galaxy Firmware Versions to Improve Security and Compliance using Microsoft Intune MS Intune Adds Windows Registry Data Collection to Device Inventory for Single Values All Key Values and Subkeys Updated Windows Device Sync Experience Enhances Per-Device Troubleshooting Configure Windows Sandbox vGPU Policy using Intune for Better Graphics Performance or Reduced Attack Surface
SCCM CB WSUS Config File did not Contain a Value InstanceName Error

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

Written By Anoop C Nair
Last Updated August 2, 2024
Posted In SCCM
SHARE

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.

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.

Written by

Anoop C Nair is Workplace Technology solution architect with 25+ years of experience in global enterprise organizations such as JP Morgan, Capgemini, etc. Microsoft Certified Trainer. Microsoft MVP from 2015 onwards for consecutive 11+ years! He also conducts Intune and modern workplace tech training for enterprise organizations. He is Blogger, Speaker, and Founder of HTMD Community and HTMD Conference. His main focus is on Device Management technologies like Intune, Windows, Cloud PC. He writes about technologies like Intune, SCCM, Windows, Cloud PC, Windows, Entra, Microsoft Security.

Discussion

Join the discussion

Your email address will not be published. Required fields are marked *

Related guides

Intune

Windows 11 KB5101650 KB5099414 July 2026 Patch and 3 Zero Day Vulnerabilities and 570 Flaws

Key Takeaways Windows 11 KB5101650 KB5099414 July 2026 Patch and 3 Zero Day Vulnerabilities and 570 Flaws! In the July 2026 Patch, Microsoft introduced new features designed to improve the overall Windows experience. The update adds enhancements to Windows Update for more flexible update management and introduces Point-in-Time Restore, providing an additional recovery option for […]

AC Anoop C Nair 9 min read
Intune

2026 June KB5094126 KB5093998 Windows 11 Patch | 3 Zero Day Vulnerabilities and 200 Flaws

Key Takeaways 2026 June KB5094126 KB5093998 Windows 11 Patch | 3 Zero Day Vulnerabilities and 200 Flaws! The June 2026 Windows 11 Patch Tuesday update brings several improvements to File Explorer. It adds support for additional archive formats, including UU, CPIO, XAR, and NuGet Packages (NUPKG). The update also preserves View and Sort preferences in […]

AC Anoop C Nair 10 min read
Intune

2026 May KB5089549 KB5087420 Windows 11 Patch | 0 Zero Day Vulnerabilities and 120 Flaws

Key Takeaways The Windows 11 May 2026 Patch KB5089549 KB5087420 Update brings important security fixes, performance improvements, and reliability enhancements across the operating system. The update introduces new features such as Xbox Mode for gaming, File Explorer improvements, enhanced input and sharing experiences, better taskbar and Windows Hello reliability, and additional enterprise management capabilities for […]

AC Anoop C Nair 8 min read
SCCM

ConfigMgr 2603 Introduces New Early Update Enrollment Process

Key Takeaways In this post we are discussing the ConfigMgr 2603 Introduces New Early Update Enrollment Process. Microsoft has officially released Configuration Manager version 2603 to the Early Update Ring, giving organizations an opportunity to test upcoming improvements before the global production rollout. The release is targeted at enterprises running ConfigMgr version 2409 or later […]

AC Anoop C Nair 3 min read