Sdílet prostřednictvím

Troubleshooting Export Issues

  • Článek

This topic contains information to help troubleshoot issues that might occur when exporting software updates 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 can be published to the update server:

  • The user initiating the export action must have Full Control permissions to the export path specified in the Export Wizard.

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

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 exports software updates to a catalog, the following entries are written to UpdatesPublisher.log:

Export: Export finished successfully.

Export: Exported Updates at:

Export: Export Path: export path

When the export process fails, review UpdatesPublisher.log for error messages that might indicate what caused the failure.

Common Export Issues

The following sections list common issues for when Updates Publisher exports software updates, possible causes for the issues, and a list of possible resolutions.

Failed to Export at <Folder Location>

When exporting software updates, the following error messages displays on the Confirmation page of the Export Wizard:

  • Error 1: Failed to Export at export path

This error message can be displayed for more than one issue. Each issue is identified in the UpdatesPublisher.log.

Access to the path is denied

The following log entries are written to UpdatesPublisher.log:

ExportForTest : Caller does not have access. Access to the path 'export for test path\export file name' is denied.

ExportForTest : Failed to create a complete test bundle at export for test path

Export : Export For Test failed.

Export : Export Failed.

When troubleshooting this error, verify the following:

  • The user has Writepermissions to the folder specified on the Specify Export for Test Path page of the Export Wizard. This error occurs for only the Export selected updates to a test catalog XML file and supporting scan files for testing option in the Export Wizard.

Validation error: deprecated rule

The following log entries are written to UpdatesPublisher.log:

Export : Checking for deprecated rules...

Verifying update 'update name' is valid.

Validation error: deprecated rule 'rule name'

Update 'update name' is invalid or contains deprecated rules and will be skipped.

Export : Did not find any valid update data to export.

Export : Export failed.

When troubleshooting this error, verify the following:

  • There are one or more deprecated rules in the software update identified in the log file. Remove the deprecated rules from the software update definition and then initiate the export process again. For more information, see the Deprecated Rules section in Upgrading to Updates Publisher.

Update '<update name>' is a bundle and will be skipped

In Updates Publisher 4.0, the following log entries are written to UpdatesPublisher.log:

Export : Checking for invalid updates...

Verifying update 'update name' is valid.

Update 'update name' is a bundle and will be skipped.

Export : Did not find any data to export.

Export : Export For Test failed.

Export : Export Failed.$

When troubleshooting this error, verify the following:

  • There is one or more update bundles selected when exporting for test. Updates Publisher 4.0 does not support exporting for test update bundles.

Could Not Export the Following Updates

When exporting software updates for testing in Updates Publisher 4.0, the following error message displays on the Confirmation page of the Export Wizard:

Could not export the following updates:

<name of update> - Drivers cannot be exported for test

Updates Publisher 4.0 does not support exporting for test drivers or update bundles.

See Also

Tasks

How to Export Software Updates

Concepts

About the Export Wizard
Log Files for Updates Publisher
Security Considerations for Updates Publisher
Upgrading to Updates Publisher

Other Resources

Exporting Software Updates
Troubleshooting Updates Publisher