Usage Note 41710: The SAS® Download Manager might not launch when you use it to download a SAS Software Depot
The SAS Download Manager might not launch when you use it to download a SAS Software Depot. Although the initial screen for the SAS Download Manager appears, the screen soon disappears.
A message that is similar to that which follows might be written to the 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
The bootstrap.log file is located in C:\Documents and Settings\user-ID\Local Settings\Application Data\SAS\SASDeploymentWizard\9.2.
This problem might be caused by your anti-virus software, which might prevent the SAS Download Manager from launching.
To work around this issue, perform the following steps:
- Disable your antivirus software.
- In Microsoft Windows Task Manager, stop any background processes that are associated with your antivirus software.
- Restart the SAS Download Manager.
If the SAS Download Manager still does not launch after you disable your antivirus software, the following error message might appear in the bootstrap.log:
Couldn't get lock for \\your-path\private\Local Settings\Application Data\SAS\SASDeploymentWizard\9.2\SDW_%u.log
The following error might also appear:
Couldn't get lock for \\vmware-host\Shared Folders\SDW_%u.log
To resolve this issue, use the -datalocation <dir> option to redirect the path of the log files. Perform the following steps:
- Select Start ► Run.
- Type the path to your SAS® Download Manager.
The default path is C:\Program Files\SAS\SASDownloadManager\1.4\esdclient.exe -datalocation c:\temp).
Note: Ensure that the c:\temp folder exists when you redirect the log file path, using the -datalocation <dir> option.
- Restart the SAS Download Manager by using the above path and option.
Operating System and Release Information
| SAS System | SAS Download Manager | Microsoft® Windows® for 64-Bit Itanium-based Systems | 1.4 | | | |
| Microsoft Windows Server 2003 Datacenter 64-bit Edition | 1.4 | | | |
| Microsoft Windows Server 2003 Enterprise 64-bit Edition | 1.4 | | | |
| Microsoft Windows Server 2003 Datacenter Edition | 1.4 | | | |
| Microsoft Windows Server 2003 Enterprise Edition | 1.4 | | | |
| Microsoft Windows Server 2003 Standard Edition | 1.4 | | | |
| Microsoft Windows Server 2003 for x64 | 1.4 | | | |
| Microsoft Windows Server 2008 | 1.4 | | | |
| Microsoft Windows Server 2008 for x64 | 1.4 | | | |
| Microsoft Windows XP Professional | 1.4 | | | |
| Windows 7 Enterprise 32 bit | 1.4 | | | |
| Windows 7 Enterprise x64 | 1.4 | | | |
| Windows 7 Home Premium 32 bit | 1.4 | | | |
| Windows 7 Home Premium x64 | 1.4 | | | |
| Windows 7 Professional 32 bit | 1.4 | | | |
| Windows 7 Professional x64 | 1.4 | | | |
| Windows 7 Ultimate 32 bit | 1.4 | | | |
| Windows 7 Ultimate x64 | 1.4 | | | |
| Windows Vista | 1.4 | | | |
| Windows Vista for x64 | 1.4 | | | |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
The SAS® Download Manager does not launch when it is invoked. The initial splash screen appears but then disappears.
| Type: | Usage Note |
| Priority: | medium |
| Date Modified: | 2011-05-26 15:44:53 |
| Date Created: | 2010-11-30 12:14:25 |