When you install or deploy SAS^® Enterprise BI Server or SAS^® BI Server for SAS 9.2, the SAS Deployment Tester might fail to configure or deploy correctly.

In addition, you might see a configuration failure during a particular stage associated with the SAS Deployment Tester.

In reviewing the dproserver_configure_yyyy-mm-dd-hh.mm.ss.log file, you might see the following message in the "BUILD FAILED" section:

BUILD FAILED
O:\SAS Server\9.2\SASDeploymentTesterServer\1.3\Config\dproserver_config.xml:173: The following error occurred while executing this line:
O:\SAS Server\9.2\SASDeploymentTesterServer\1.3\Config\dproserver_config.xml:837: The following error occurred while executing this line:
O:\SAS Server\9.2\SASDeploymentManager\9.2\products\cfgwizard__92210__prt__xx__sp0__1\Utilities\configuration_scripts.xml:177: rc:2 output:The SAS [BIServer 9.2-Lev1] Deployment Tester Server service is starting..
at org.apache.tools.ant.ProjectHelper.addLocationToBuildException(ProjectHelper.java:541)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:418)
at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:105)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
at sun.reflect.GeneratedMethodAccessor24.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:357)
at org.apache.tools.ant.Target.performTasks(Target.java:385)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1329)
at org.apache.tools.ant.Project.executeTarget(Project.java:1298)
at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
at org.apache.tools.ant.Project.executeTargets(Project.java:1181)
at org.apache.tools.ant.Main.runBuild(Main.java:698)
at org.apache.tools.ant.Main.startAnt(Main.java:199)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)

When you examine the Windows Event Viewer, you might see the following message or error:

The system error 1067 is a generic message from Microsoft that does not provide a lot of information. However, the problem is likely caused by the user account when the service that it is using does not have sufficient authority to start the service.

To work around this issue, change the SAS Deployment Tester Service "Logon" from "LocalService" to run as "Local System." This enables the service to start.

To set up the service, use the steps that pertain to your system, as follows:

On a Windows XP system:

1. Click Start ► Settings ► Control Panel ► Administrative Tools ► Services.
2. Right-click the Deployment Tester Server service name and then select Properties.
3. Click the Log On tab of the Properties dialog box.
4. Select the option button for Local System account.

On a Windows 7 system:

1. Click Start ► Control Panel.
2. Click Administrative Tools.
3. Double-click Services.
4. Locate Deployment Tester Server in the list, right-click the name, and then select Properties.
5. Click the Log On tab of the Deployment Tester Server Properties dialog box.
6. Select the option button for Local System account.

By default, this service should be running as "LocalService." However, to work around the issue, it might be necessary to change this to another account that has more authority, such as the Local System account. Select the Local System account or specify a specific account to use.

Important: A disadvantage of selecting a specific account is that in the case of a password change, you have to change the service as well. Also, some security experts have reservations about running services using the Local System account. Consult with your Systems Administrator if you need help with choosing the best option.