SCCM CB 1702 WSUS Config file did not Contain a Value InstanceName Error

SCCM CB 1702 WSUS and SUP configurations are important for 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 SCCM CB 1703 version. In this post, we will see the couple of issues and solutions. 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 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 SQL service account.

ERROR: Can't retrieve SQL connection. Exception: System.Data.SqlClient.SqlException (0x80131904): The target principal name is incorrect. Cannot generate SSPI context

Following are the SPN registration commands used to fix the remote SQL connectivity issues.

setspn -a mssqlsvc/SCCM01:1433 ACN\asqld
setspn -a mssqlsvc/ ACN\asqld

Config file did not Contain a Value InstanceName Error

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

After fixing the SPN issue the WSUS installation error for 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.


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

Config file did not Contain a Value InstanceName Error

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

The post installation process of WSUS got stuck with following errors.  FIRST TIME when I tried to perform WSUS Post installation process. This error got solved by deleting 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'.

SECOND TIME when I tried to perform WSUS Post installation process, it 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 has been 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


Sharing is caring!

Leave a Comment

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