This section contains information to help troubleshoot issues that might occur during System Center Updates Publisher installation. It also includes the installation and security requirements that must be met before Updates Publisher can be installed, describes the log files that Updates Publisher creates during Setup, and lists troubleshooting solutions for common issues.
Before Updates Publisher can be installed on a computer, there are operating system requirements that must be considered. The computer must also have specific software installed, including Microsoft Management Console (MMC) 3.0, Windows Server Update Services (WSUS) 3.0 or WSUS 3.0 Administrator Console, and Internet Explorer 6 SP1 or later. For more information about Updates Publisher requirements, see Requirements for Updates Publisher.
Remote Updates Publisher Database
When a remote computer running SQL Server is specified during Updates Publisher installation, the database must be created on the remote computer before installing Updates Publisher. For information about creating the Updates Publisher SQL Server database, see How to Create the Updates Publisher Database.
The following security rights are required before Updates Publisher can be installed:
- The user who initiates the Updates Publisher
installation must be a member of the Administrators group on the
- The user who initiates the Updates Publisher
installation must have rights to create a database when the
database will be on the local computer and has not already been
created. When the Updates Publisher database is on a remote
computer, the database must be created on a remote computer running
SQL Server prior to running Updates Publisher installation.
For more information about the security requirements for Updates Publisher, see Security Considerations for Updates Publisher.
Updates Publisher Setup writes information to log files to help diagnose issues that might occur during installation. Each log file is created in the temporary folder for the user running Setup, located by default at %USERPROFILE%\Local Settings\Temp. There are up to three phases during Updates Publisher Setup and during each phase Updates Publisher writes to a different log file.
|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.|
The minimum software requirements are verified on the local computer during the initial phase of Updates Publisher installation. As Setup verifies each software requirement it writes to PTBootstrapper.log, and when Setup successfully completes this phase of Updates Publisher installation PTBootstrappersetup.log will contain the following log entries:
MSI installation complete.
MSI finished with success message.
Setup completed successfully.
When the software requirements are not met, review PTBootstrappersetup.log for detailed information.
The Updates Publisher components are installed on the local computer during the next phase of Updates Publisher installation. When Setup successfully completes this phase, PublishingToolsetup.log will contain the following log entry:
Product: System Center Updates Publisher --
Installation operation completed successfully
When the installation is unsuccessful, review this log file for error messages that might indicate what caused the installation to fail.
When the Updates Publisher database is not created prior to installing Updates Publisher and Setup is configured to use a local database, Setup writes log entries to PTDatabase.log. When Setup successfully creates the local database, PTDatabase.log will contain the following log entry:
DBCC execution completed
When Setup fails to create the local database, review this log file for error messages that might indicate what caused the failure.
Common Setup Issues
The following sections list common issues that may occur when Updates Publisher is installed, possible causes for the issues, and a list of possible solutions.
Unable to verify the database connection with the provided information
When configuring the Remote Database setting in Updates Publisher Setup the following error message displays:
Unable to verify the database connection with the
When troubleshooting this error, verify the following:
- The Updates Publisher database is on the
remote computer running SQL Server. When using a remote
Updates Publisher database, a script that creates the mscuptdb
database and System_Center_Updates_Publisher_User database role
must be run on the remote computer prior to running Setup.
- The user installing Updates Publisher has
permissions to the remote computer running SQL server. The user
must have at least User privileges on the remote computer running
SQL Server, and have a user login in SQL Server that has
the System_Center_Updates_Publisher_User database role membership
on the mscuptdb database.
- The Database Server or SQL
Instance setting is valid for the remote SQL Server
- If a firewall is enabled on the computer
hosting the remote Updates Publisher database, verify that the
firewall is configured to allow access to the instance of the
Microsoft SQL Server Database Engine.
Prompted to install SQL 2005 Express Edition when SQL Server is Already Installed
During Updates Publisher installation, the Setup Wizard lists SQL Server 2005 Express Edition as a requirement even though the Updates Publisher computer has a local instance of SQL Server 2005 64-bit. To install the Updates Publisher on a local computer running SQL Server 2005 64-bit, you must use the following workaround:
- On the computer running SQL Server 2005
64-bit, follow the procedure in How to Create the
Updates Publisher Database. Then, Remote Database must
be selected when running Updates Publisher Setup even though the
database server is on the local computer. In the Database
Server field, enter the name of the local computer and the
instance of SQL Server.