Export (0) Print
Expand All

Setup issues

Published: December 16, 2009

Applies To: Forefront Client Security

This topic contains the following sections:

Setup reports errors on the Verifying Data and Requirements page

Account validation fails

Server setup fails with an invalid password error

Server setup fails with code 3010

Server setup fails with error 0x80029C4A

Installation fails with error 1303

Server setup fails during collection server installation

Configuration wizard fails when importing reports

Evaluation download does not run.

Setup reports errors on the Verifying Data and Requirements page

Setup may report errors on the Verifying Data and Requirements page.

Background

This can occur for the following reasons:

  • Prerequisite software is not installed.

    For information about the software required to deploy each role, see the Client Security Deployment Guide (http://go.microsoft.com/fwlink/?LinkId=86652).

  • A required service is not started.

  • A SQL Server computer needed for setup cannot be contacted.

  • The reporting server URLs are not valid.

  • The computer has less than 1 gigabyte (GB) of RAM.

  • A user account or password specified for any of the accounts requested during setup has been entered incorrectly.

Solution

Click View Log on the Verifying Data and Requirements page of the wizard. The reason for the verification failure is listed in the log file. Remedy the reason for the failure, uninstall the components that successfully installed from Add or Remove Programs in Control Panel, and rerun setup.

Account validation fails

During setup, account validation may fail.

Background

For Client Security to validate the user accounts specified during setup, if the user name and password are entered correctly, the computer must be able to contact an Active Directory® directory service domain controller for the domain in which the account exists. The location of a domain controller is determined by a query to the Domain Name System (DNS) servers configured in the TCP/IP properties.

Solution

Ensure the following:

  • Domain controller is online and reachable.

  • User name and password are entered correctly. User names must be entered in the format of domain\username, with domain being a NetBIOS name.

  • Connection to the network has not been lost.

  • TCP/IP address and subnet mask are correct.

  • TCP/IP addressing information has the correct DNS addresses entered.

Server setup fails with an invalid password error

During server setup, a failure may occur due to an invalid password error.

Background

Server setup fails when a password for any Client Security account contains two spaces followed by a character that is not a space. This issue occurs with Windows Installer 3.1, which is present on Windows versions prior to Windows Vista.

Solution

Do not use a password with two spaces followed by a character that is not a space.

Server setup fails with code 3010

Setup might fail, and inspection of the ServerSetup.log file finds msiexec.exe returned exit code 3010.

Background

Exit code 3010 is not an error; it simply indicates that a restart is pending.

Solution

Click the Back button, and then click the Next button. The setup tasks will run again and should be successful. After Setup has completed, restart the computer.

Server setup fails with error 0x80029C4A

When installing Client Security on a system with double-byte characters in the installation path, Setup fails to install the MOM collection server. This results in error 0x80029C4A in the MomServer.log file.

Background

Client Security does not support installation in a path with double-byte characters.

Solution

Install Client Security into a path without double-byte characters.

Installation fails with error 1303

Installation might fail with error 1303, and event 11303 might be logged in the Application log of Event Viewer. The event would contain the following description: "The installer has insufficient privileges to access this directory: C:\Config.Msi".

Background

This issue can occur on slower computers, computers with slower hard disk drives, or computers experiencing heavy disk activity during the installation.

Solution

For more information, see Knowledge Base article 924876 (http://go.microsoft.com/fwlink/?LinkId=82197).

Server setup fails during collection server installation

Server setup might fail during the installation of the collection server.

Background

On the Completing Setup page of the Setup wizard, you see an error for the item Collection Server Disabling Rules. Upon looking at the ServerSetup_YYYYMMDD_HHMMSS.log file, you may see the following error:

 

Error message

Task(Collection Server Disabling Rules) Microsoft.EnterpriseManagement.Mom.MomSdkException: Execution against the runtime failed. See inner exception for more details. ---> System.Runtime.InteropServices.COMException (0x80080005): Retrieving the COM class factory for remote component with CLSID {8FB7B313-C81A-11D2-8D40-0090270D2552} from machine SERVERNAME failed due to the following error: 80080005

Additionally, you may see event ID 9029 in the Application log of Event Viewer.

Solution

This error can occur for two reasons. Their respective solutions follow:

  • A timing issue occurred. Click Back and Next again, and the Setup wizard should complete.

  • The accounts specified in the Setup wizard do not have sufficient privileges. Grant appropriate privileges to the accounts specified in the Setup wizard. For more information, see the Client Security Deployment Guide (http://go.microsoft.com/fwlink/?LinkId=86650).

Configuration wizard fails when importing reports

If during the Client Security Configuration wizard you use SSL in your reporting server URL (https://servername/reports), you may see that the Import Reports task shows "Failed" as the result. The Configuration wizard log file (ServerConfig_YYYYMMDD_HHMMSS.log) shows the following error message: "The request failed with HTTP status 413: Request Entity Too Large".

Background

If you are using IIS 6.0, this can happen when too much data is sent in the HTTPS request.

Solution

To resolve this issue, perform the following steps.

To resolve the HTTP 413 error
  1. On the reporting server, click Start, click Run, type cmd, and click OK.

  2. In the Command Prompt window, type the following command and press ENTER:

    cscript adsutil.vbs set w3svc/1/uploadreadaheadsize 500000

For more information, see Client cannot renegotiate request and returns an HTTP 413 error (IIS 6.0) (http://go.microsoft.com/fwlink/?LinkId=87385).

Evaluation download does not run

For the RTM evaluation version, the downloaded setup file might not run.

Background

The setup download is in ISO format. You cannot install the product by running the downloaded file.

Solution

Create a CD from the ISO image, and then install from the CD. For more information, see the instructions that came with your CD burner.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft