Submit a ticketCall us

Webinar: Web Help Desk for HR, Facilities and Accounting Departments
This webinar will focus on use cases for HR, Facilities and Accounting.

Having a unified ticketing and asset management system for all the departments in your company can provide end-users with a seamless experience and make things easier for your IT team. Yet, with different business tasks and objectives, many departments don’t fully understand the capabilities of Web Help Desk and how the software can be customized for effective use in their departments.
Register Now.

Home > Success Center > Patch Manager > Failed to publish Remote Registry Memory Leak Fix - KB2699780. Unable to find database configuration value

Failed to publish Remote Registry Memory Leak Fix - KB2699780. Unable to find database configuration value

Updated June 16, 2017


The following error message is displayed after deploying a created custom package using the Update Management Wizard:

The summary of the results of publishing the packages:

Package: Remote Registry Memory Leak Fix - KB2699780

Status: Failure

Message: Failed to publish Remote Registry Memory Leak Fix - KB2699780. Unable to find database configuration value.


The following errors are also found in the stack trace log:

2017/06/14 13:09:31:723 PID: 5456 TID: 3008 [ERROR] UpdateServer::ShouldOnlyRevisePackage() failed.
Message: The specified item could not be found in the database.
Stack Trace: at Microsoft.UpdateServices.Internal.BaseApi.SoapExceptionProcessor.DeserializeAndThrow(SoapException soapException)
at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccessProxy.ExecuteSPGetUpdateById(String preferredCulture, UpdateRevisionId id)
at Microsoft.UpdateServices.Internal.BaseApi.Update.GetById(UpdateRevisionId id, UpdateServer updateServer)
at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer.GetUpdate(UpdateRevisionId id)
at EminentWare.UpdateServices.Administration.UpdateServer.ShouldOnlyRevisePackage(PublishSoftwareItem item, String sdpxmlfile)
2017/06/14 13:09:32:425 PID: 5456 TID: 3008 [ERROR] Failed to publish update: custom package trying to publish KB123456 Message: Unable to find database configuration value. Stack Trace:
at Microsoft.UpdateServices.Internal.DatabaseConfiguration.GetDatabaseConfiguration(String& serverName, String& databaseName, AuthenticationMode& authenticationMode, String& userName, String& password, String& windowsInternalDatabaseInstanceName)
at Microsoft.UpdateServices.Internal.DatabaseConfiguration.Load()
at Microsoft.UpdateServices.Internal.ClassFactory.CreateWellKnownType(Type type, Object[] args)
at Microsoft.UpdateServices.Internal.ClassFactory.CreateInstance(Type type, Object[] args)
at Microsoft.UpdateServices.Internal.GenericDataAccess.ExecuteSP(String spName, DBParameterCollection args, IExecuteSPHandler handler, Int32 queryTimeoutInSeconds)
at Microsoft.UpdateServices.Internal.DatabaseAccess.CommonDataAccess.ExecuteSPSingleValue(String spName, DBParameterCollection args, Int32 queryTimeoutInSeconds)
at Microsoft.UpdateServices.Internal.BaseApi.Publisher.SignPackageCab()
at Microsoft.UpdateServices.Internal.BaseApi.Publisher.PublishPackage(String sourcePath, String additionalSourcePath, String packageDirectoryName)
at EminentWare.UpdateServices.Administration.UpdateServer.PublishUpdates()


  • Patch Manager 2.1.1
  • Remote WSUS and SQL Server database


The following are the causes of this issue:

  • This is known bug in Microsoft.
  • 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 the remote WebService to query the SUSDB information from the 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.


Apply the Microsoft hotfix to resolve this issue.

(© 2017 Microsoft, available at, obtained on June 15, 2017.)


Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.


Last modified
00:19, 16 Jun 2017