System Center Updates Publisher can be installed manually by using the Setup Wizard or installed unattended at the command line. While completing the Setup Wizard, the database settings are validated and Setup will not continue without successfully connecting to the data source; however, there are other potential problems that can occur during Updates Publisher installation that are not identified in the wizard. When Updates Publisher is installed unattended, connectivity to the data source is not validated and the installation completes with no messages or notifications for both a successful and unsuccessful installation.

Use the following procedure to verify that the Updates Publisher installation completed successfully.

To verify that Updates Publisher installed successfully

  1. Navigate to the user %TEMP% folder on the Updates Publisher computer.

  2. Review the following Updates Publisher setup log files:

    • PTBootstrappersetup.log: Contains information about whether the minimum requirements have been met during the initial phase of the Updates Publisher Setup. Verify that this phase of Setup was successful by looking at the last three lines of the log file, which should read MSI installation complete, MSI finished with success message, and Setup completed successfully. If the installation failed, review the log file for errors related to meeting the minimum software requirements and the detection of SQL.

    • PTDatabase.log: Contains information about the creation of the Updates Publisher database during Setup. Verify that the database was created successfully by looking for DBCC execution completed in the log file. If Setup failed to create the database, review this log file for error messages that might indicate what caused the failure.

    • PublishingToolsetup.log: Contains information about the Updates Publisher Setup. Verify that Setup completed successfully by looking for Product: System Center Updates Publisher -- Installation operation completed successfully about ten lines from the end of the log file. If the installation failed, review the log file for error messages that might indicate what caused the installation to fail.

    The 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.

See Also