When you are installing SAS 9.2, the SAS Deployment Wizard might not launch. A message similar to the one below might write to bootstrap.log:

ERROR: ExeProc::ReadFromPipe=Standard output
java.io.IOException: Couldn’t get lock for
\\nscfsc02\person$\F\Furlow_Gerri\private\Local Settings\Application Data\SAS\SASDeploymentWizard
\9.2\SDW_%u.log at java.util.logging.FileHandler.openFiles(Unknown Source)
at java.util.logging.FileHandler.(Unknown Source)
at com.sas.ssn.Logging.createLog(Logging.java:47)
at com.sas.ssn.Kit.main(Kit.java:1297) Exception in thread "main" java.lang.NullPointerException
at com.sas.ssn.Logging.createLog(Logging.java:59) at com.sas.ssn.Kit.main(Kit.java:1297)
Wed Nov 25 13:35:17 2009
INFO: ExeProc::ExeandDisplay::GetExitCodeProcess=1

Your antivirus software might be preventing the SAS Deployment Wizard from launching.

To work around this issue, follow these steps:

1. Disable your antivirus software.
2. In Microsoft Windows Task Manager, stop any background processes that are associated with your antivirus software.
3. Restart the SAS Deployment Wizard.

If the SAS Deployment Wizard still does not launch after you disable your antivirus software, the following error message might write to bootstrap.log:

Couldn't get lock for \\your-path\private\Local Settings\Application Data\SAS\SASDeploymentWizard\9.2\SDW_%u.log \SDW_%u.log

To resolve this issue, redirect the path of the log files by using the -datalocation option as follows:

1. Select Start ► Run.
2. Type the path to your SAS^® Deployment Wizard(for example, the default path is C:\SAS Software Depot\setup.exe -datalocation c:\temp).
Note: Make sure the c:\temp folder exists when you redirect the path to the SAS Deployment Wizard.
3. Restart the SAS Deployment Wizard.

Operating System and Release Information