You receive error code 25213 and Event ID 10005 is logged in the Application log when you run the System Center Reporting Manager batch file to install the ReportingDataSource.msi file on an SMS 2003 server (917667)

SYMPTOMS

You add a Microsoft Systems Management Server (SMS) 2003 data source to Microsoft System Center Reporting Manager (SCRM) 2006. You run the SMSSrcSetup_datasourcename.bat file on the destination computer. When you do this, you experience all the following symptoms:

You receive the following error message:
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 25213.
The following event is logged in the Application log on the destination computer:

Event Type: Error
Event Source: MsiInstaller
Event Category: None
Event ID: 10005
Description: Product: Microsoft Systems Management Server Data Source for SCRM 2006 -- The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 25213. The arguments are: -2147023564, No mapping between account names and security IDs was done.

The following error information is logged in the %WINDIR%\SC2006SMSSrcSetup.log file:

MSI (s) (38:C0) [14:09:13:595]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI29D.tmp, Entrypoint: AddUserAccountToLocalGroup

AddUserAccountToLocalGroup: Custom action data. SC DW SMS DTS <DOMAIN NAME>\<ACCOUNT NAME>  SC DW SMS DTS .\<ACCOUNT NAME> 

AddUserToLocalGroup: Failed to lookup an account. Error Code: 0x80070534. .\<ACCOUNT NAME>

AddUserAccountToLocalGroup: Failed to add an account to group. Error Code: 0x80070534. .\<ACCOUNT NAME>

MSI (s) (38!80) [14:09:17:937]: Product: Microsoft Systems Management Server Data Source for SCRM 2006 -- The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 25213. The arguments are: -2147023564, No mapping between account names and security IDs was done.

Note The SMSSrcSetup_datasourcename.bat file is used to install the System Center Reporting Manager 2006 Data Source component (ReportingDataSource.msi) on the destination SMS 2003 computer.

CAUSE

This issue occurs if the SQLSERVERAGENT service on the destination computer is configured to use a local account to log on.

When you view the properties of a service, and then click the Log On tab, a local account appears in the following format:

.\accountName

The process that performs the ReportingDataSource.msi installation tries to add the SQLSERVERAGENT service account to the SC DW SMS DTS group. However, this process is not able to parse an account that starts with the period and backslash (.\) characters.

RESOLUTION

To resolve this issue, configure the SQLSERVERAGENT service to use the local SYSTEM account or to use a domain account to log on. To do this, follow these steps:

On the computer that is running SMS 2003, click Start, click Run, type services.msc, and then click OK.
In the Services dialog box that appears, double-click SQLSERVERAGENT.
Click the Log On tab, click Local System account, and then click OK.

Note If you want to configure a domain account instead of the local SYSTEM account, follow these steps:
1. Click This account, and then type the name of the account in the domain\username format.
2. Type the account password in the Password box and in the Confirm password box, and then click OK.
3. If you receive the following message, click OK: The account username has been granted the Log On As A Service right.
On the following message that appears, click OK:The new logon name will not take effect until you stop and restart the service.
Click Restart to stop, and then restart the SQLSERVERAGENT service.