SCCM CB WSUS Config file did not contain a Value InstanceName Error | ConfigMgr | MEMCM? SCCM CB 1702 WSUS and SUP configurations are important for the software updates/patching process.
The latest introduction of Windows 10 and Office 365 servicing to SCCM increased the importance of WSUS integration. Lately, I’ve been facing issues with WSUS installation and then the configuration of it with the SCCM CB 1703 version.
In this post, we will see a couple of issues and solutions. The second issue which I’m going to cover today is “Config file did not contain a Value InstanceName Error”.
This is a random post that covers the issues which I faced during the build of the new SCCM CB infra.
How to fix SPN issue for remote SQL server
The WSUS installation on remote SCCM CB 1702 SUP was stopped because of connectivity issues to remote SQL DB. This got resolved by adding proper SPN values to the SQL service account.
- ERROR: Can’t retrieve SQL connection. Exception: System.Data.SqlClient.SqlException (0x80131904): The principal target name is incorrect. Cannot generate SSPI context
Following are the SPN registration commands to fix the remote SQL connectivity issues.
- setspn -a mssqlsvc/SCCM01:1433 ACN\asqld
- setspn -a mssqlsvc/SCCM01.ACN.com:1433 ACN\asqld
How to Fix WSUS/SUP Installation Issue with SQL Default Instance?
After fixing the SPN issue, the WSUS installation error changed to something else. I came to know from logs that WSUS configuration file didn’t have the details of SQL instance.
As my remote SQL was on default instance, I didn’t put the instance name. The solution to fix WSUS connectivity was to provide the default SQL instance name.
The content directory is I:\WSUS.
Start: GetConfigValue with filename=UpdateServices-DB.xml item=InstanceName
Config file did not contain the value “InstanceName.“
Microsoft.UpdateServices.Administration.CommandException: A required configuration value was not found in the system.
How to Fix WSUS/SUP Configuration issues with SQL DB Deadlock
The post-installation process of WSUS got stuck with the following errors. FIRST TIME when I tried to perform WSUS Post-installation process. This error got solved by deleting the WSUS pool from IIS.
- 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.
- 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
Anoop is Microsoft MVP! He is a Solution Architect in enterprise client management with more than 20 years of experience (calculation done in 2021) in IT. He is 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……………