This topic contains information to help troubleshoot issues that might occur when importing software updates catalogs in System Center Updates Publisher. It also includes the security requirements required before software updates can be exported, describes the log file used to help diagnose issues, and lists troubleshooting solutions for common issues.

Security Requirements

The following security rights are required before software updates catalogs can be imported to the update server:

  • The user must have access to the source location for software updates catalogs to successfully import them into Updates Publisher.

  • The user must have a SQL login created on the publishing tool database (mscuptdb) and be assigned System_Center_Updates_Publisher_User database role membership rights.

For more information about the security requirements for Updates Publisher, see Security Considerations for Updates Publisher.

Log File

Updates Publisher writes information to the UpdatesPublisher.log file to help diagnose issues that might occur when opening and using the console. The log file is created in the temporary folder for the user opening the console, located by default at %USERPROFILE%\Local Settings\Temp.

Important
The Updates Publisher log files must be opened with a simple text editor, such as Notepad. Opening the log files in a full text editor might not display the contents of the log file correctly.

UpdatesPublisher.log

When Updates Publisher successfully imports a software updates catalog from a file, the following log entries are written to UpdatesPublisher.log:

import : Starting Import Wizard at date time

import : Doing a Manual Import

Copying file: import path\catalog file to %USERPROFILE%\Local Settings\Temp\catalog file

import : Starting Import From File: catalog XML file

import : Imported 1 out of 1 updates.

Deleting temp file: %USERPROFILE%\Local Settings\Temp\GUID\catalog XML file

Deleting temp folder: %USERPROFILE%\Local Settings\Temp\GUID\

import : Finished Manual Import at : date time

Importing software updates from the import list contains similar log entries. When the import process fails, review UpdatesPublisher.log for error messages that might indicate what caused the failure.

Common Updates Publisher Import Issues

The following sections list common issues that may occur when importing software updates catalogs into the Updates Publisher database, possible causes for the issues, and a list of possible solutions.

CST Compliance Failed

When importing a software updates catalog, the following error message displays on the Confirmation page of the Import Software Updates Catalogs Wizard:

CST Compliance failed.

When troubleshooting this error, verify the following:

  • The software updates catalog that is being imported does not satisfy the predefined schema standard.

The File Specified Does Not Exist

When importing a software updates catalog, the following error message displays on the Confirmation page of the Import Software Updates Catalogs Wizard:

The file specified import path\file name does not exist.

The following log entry is written to UpdatesPublisher.log:

import : Access to the path 'import path\catalog file' is denied.

When troubleshooting this error, verify the following:

  • Verify that the user has Read permissions to catalog specified on the Select File page of the Import Software Updates Catalogs Wizard. The wizard validates that the import path is valid, but does not verify that the user has Read permissions on the file.

The Digest Attribute is Not Declared

When importing a software updates catalog, the following error message displays on the Confirmation page of the Import Software Updates Catalogs Wizard:

The ‘Digest’ attribute is not declared

The following log entries are written to UpdatesPublisher.log:

import : System.Xml.Schema.XmlSchemaValidationException: The 'Digest' attribute is not declared.

import : The 'Digest' attribute is not declared.

When troubleshooting this error, verify the following:

  • At least one software update definition in the catalog contains the Digest: (SHA1) attribute in the File Exists rule. Updates Publisher no longer supports software update definitions using the Digest: (SHA1) attribute in the File Exists rule. Modify the software update definition, by using the version of the publishing tool that created the software update definition, to exclude the deprecated rule. For more information, see the Deprecated Rules section in Upgrading to Updates Publisher.

Invalid Child Element 'RegBinary' in Namespace

When importing a software updates catalog, the following error message displays on the Confirmation page of the Import Software Updates Catalogs Wizard:

…invalid child element 'RegBinary' in namespace

The following key log entries are written to UpdatesPublisher.log:

import : System.Xml.Schema.XmlSchemaValidationException: The element 'IsInstalled' in namespace 'http://schemas.microsoft.com/wsus/2005/04/CorporatePublishing/SoftwareDistributionPackage.xsd' has invalid child element 'RegBinary' in namespace

When troubleshooting this error, verify the following:

  • At least one software update definition in the catalog contains the Registry Binary Value rule. Updates Publisher no longer supports software update definitions using the Registry Binary Value rule. Modify the software update definition, by using the version of the publishing tool that created the software update definition, to exclude the deprecated rule. For more information, see the Deprecated Rules section in Upgrading to Updates Publisher.

See Also