Custom update publish in WSUS causes error "Unable to find database configuration value"

Si applica a: Windows Server 2012 StandardWindows Server 2012 StandardWindows Server 2012 Essentials

Symptoms


Assume that you use Windows Server Update Services (WSUS) in Windows Server 2012. When you try to publish custom updates, the publishing fails, and you receive the error message:
Unable to find database configuration value.

Cause


This problem occurs in the following scenario:
  • The WSUS content folder is hosted on a Uniform Naming Convention (UNC) file share.
  • WSUS uses a remote WSUS database (SUSDB).
  • A WSUS remoting API, such as Remote Server Administration Tool or Microsoft System Center Configuration Manager (SCCM), is used on a different server to publish the custom updates.
When the WSUS server is configured to host update content on a UNC file share, the API retrieves the path to the share from the database. However, instead of calling remote WebService to query SUSDB information from remote WSUS, the API tries to connect locally to a database. Because WSUS is not installed locally, the API cannot find a database, and the publication of custom updates fails.

Resolution


Hotfix information

A supported hotfix is available from Microsoft Support. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, go to the following Microsoft website: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

There are no prerequisited for installing this update.

Registry information

To enable this fix, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any previously released hotfix.

Workaround


To work around this issue, use one of the following methods:
  • If you use only one WSUS content folder, make this folder a local folder instead of using a UNC path.
  • Run Local Publishing on the WSUS server.
  • Copy the “SQL registry keys” WSUS setup to the following registry key on the Local Publishing computer

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Update Services\Server\Setup\SQL*]

Status


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

References


Learn about the terminology that Microsoft uses to describe software updates.