Troubleshooting Your Initial Essentials Setup and Configuration

  • Article

Applies To: System Center Essentials 2010

If you encounter errors when you run the System Center Essentials 2010 Setup Wizard or the Configure System Center Essentials Wizard, use the following information to help diagnose and correct problems.

Installing Virtualization Management with WinHTTP Proxy configured

If you are installing Essentials 2010 with Virtualization Management selected and a Windows Hypertext Transfer Protocol (WinHTTP) proxy is configured on the server to which you are installing Essentials 2010, Setup installs Essentials 2010, but does not install the Virtualization Management feature. Try one of the following workarounds to resolve the issue.

  • Check to see whether you have a WinHTTP proxy configured. If so, either disable the proxy or configure WinHTTP proxy to use a bypass list that includes the server to which you are installing Essentials 2010, and then restart Setup to install Virtualization Management. For more information about configuring a proxy by using WinHTTP, see Netsh Commands for Windows Hypertext Transfer Protocol (WINHTTP) in the Windows Server 2008 and Windows Server 2008 R2 Technical Library.

  • Check to see whether firewall settings are blocking HTTP traffic. For more information about firewall settings, see Firewall Exceptions for System Center Essentials 2010.

Installing from a Network Share

If you run the System Center Essentials 2010 Setup Wizard from a network share and, in Server Manager, Internet Explorer Enhanced Security Configuration is enabled, a dialog box appears that prompts you to add the network share to the Trusted sites zone before Setup displays the installation options. This also occurs when you attempt to run Setup at a command prompt. Use the following steps to add the network share so that you can continue the installation.

To add the network share to the Trusted sites zone

  1. When the Internet Explorer dialog box appears, click Add.

    Important

    If the dialog box prompting you to add the network share does not appear, and Setup displays a blank screen, open Internet Explorer, click Tools, click Internet Options, and then click the Security tab. Click the Trusted sites icon, and then click Sites to display the list of sites, where you can type the name of the network share and add it to the list.

  2. When the Trusted sites dialog box opens, click Add to add the network share to the list, and then click Close.

After the network share has been added to the Trusted sites zone, System Center Essentials 2010 Setup displays the installation options.

If you want to remove this network share from Trusted sites, open Internet Explorer, click Tools, click Internet Options, and then click Security. Click the Trusted sites icon, and then click Sites to display the list of sites. Select the network share, click Remove, and then click Close.

Reporting Server URL

If you are installing Essentials 2010 with Reporting selected and Setup fails after selecting a SQL Server Reporting Services server (SSRS) instance with the following error message: "Unable to find a working HTTP site from the <URL> Internet Information Services (IIS) node," there may be several potential causes:

  • The Web site exists, but did not send a response in the time span that Essentials expected.

  • Proxy configuration settings are incorrect.

  • Configuration of the Web site for the SQL Server Reporting Services server is incorrect.

  • Configuration from an earlier installation of SQL Server Reporting Services might be incorrectly setting an encrypted channel to Reporting Services.

Try the following workarounds to resolve this issue:

  • Open the URL in a browser to confirm connectivity.

    • If the browser can open the site, click Next in Essentials Setup to detect the cause again.

    • If the browser cannot open the site, check to see if the Proxy settings are correctly resolving the Web site.

  • Check the SCE_ReportingMSI.log file for the following message: The operation you are attempting requires an encrypted channel (HTTPS). If you see this message, edit the rsreportserver.config file (usually located in %Program Files%\Microsoft SQL Server\MSRS10.<instancename>\Reporting Services\ReportServer\) as follows:

    1. Search for the line that reads <Add Key="SecureConnectionLevel" Value="2">.

    2. Change it to <Add Key="SecureConnectionLevel" Value="0"> and save the file.

    3. Restart Essentials 2010 Setup.

Selecting a Database During Setup

If you already have an instance of SQL Server installed on the computer but Setup reports that SQL Server Database Services are not found, you have the option to either install SQL Server 2008 SP1 on the computer or specify a remote instance of SQL Server later in Setup. If you get this message, check the following possible causes and resolutions.

  1. Cause: The user installing Essentials 2010 does not have the required permission to select the existing instance of SQL Server.

    Workaround: Make sure that the installing user has permissions on the existing instance of SQL Server; otherwise, Setup cannot determine if the instance is a valid version to use.

  2. Cause: The existing instance of SQL Server 2008 does not have the required Service Pack installed.

    Workaround: Update the existing instance of SQL Server 2008 to apply the latest Service Pack (SP1) and then restart Setup.

  3. Cause: The WSUS database is installed on another instance of SQL Server 2008 on the computer.

    Workaround: Move the WSUS database to the same instance of SQL Server that is used by Essentials 2010.

  4. Cause: The virtualization database is installed on another instance of SQL Server 2008 on the computer.

    Workaround: Move the virtualization database to the same SQL Server instance that is used by Essentials 2010.

  5. Cause: The Operations Manager database is installed on the instance of SQL Server 2008 that you are trying to use for Essentials 2010.

    Workaround: Remove the Operations Manager database from the instance of SQL Server chosen for Essentials 2010.

Reporting Server Name

If you install Essentials 2010 with the Reporting feature on a computer with a SSRS instance that contains an underscore character (_) in the name, the Reporting feature fails to install. Remove the underscore from the name of the SSRS instance and then try installing Essentials 2010 Reporting again.

Log Files

For more information about failures in installing or configuring Essentials 2010, refer to the error log files. Depending on the version of the operating system, setup and configuration log files are located in %LOCALAPPDATA%\SCE\LOGS. To locate these log files, click Start, click Run, type %LOCALAPPDATA% in the box, and then click OK or press ENTER.

For more information about failures in configuring Policy or Agentless Exception Monitoring in Essentials 2010, refer to the error log files. Depending on the version of the operating system, the error log files are also located in %LOCALAPPDATA%\SCE\LOGS, are named SCECert*[#]*.log. To find these log files, click Start, click Run, type %LOCALAPPDATA% in the box, and then click OK or press ENTER.

Note

For Windows Server 2003, the error log files are located in %USERPROFILE%\LOCAL SETTINGS\Application Data\SCE\LOGS.

Administrative Credentials

When you install Essentials 2010 for the first time, make sure that the domain account you use has local administrator rights.

If you selected to configure domain-based Group Policy, ensure the logged-on user account has Domain Administrator or Group Policy Administrator rights.

If the configuration of error monitoring (also named Agentless Exception Monitoring) ended with an error, make sure that the logged-on user account has administrator rights and permissions on the computer whose drive was selected as the upload location for application error reports.

See Also

Concepts

System Requirements and Supported Platforms for System Center Essentials 2010
Supported Topologies and Performance Guidance for System Center Essentials 2010
Local Policy vs. Group Policy in System Center Essentials 2010
Administration Accounts in System Center Essentials 2010
Log File Locations for Troubleshooting Essentials 2010
Character Validation
Selecting Database Locations in System Center Essentials 2010