During a planned installation of SAS 9.2, a configuration failure message similar to the following might appear:
This error indicates that the SAS Metadata Server service could not be started and configured. Often, this error might occur because duplicate SAS services are listed from either a previous installation of SAS or from a previous failed installation of SAS.
If this error message appears, review the metadatasrv_configureMetadata_yyyy-mm-dd-hh.mm.ss.log file that is linked to in the Configuration Failure dialog box. Also, you should review the "Warnings and Notices" section in the Instructions.html file. The default location for the Instructions.html file is C:\SAS\planfile_name\Lev1\Documents. Your Instructions.html file might contain information similar to the following:
Warnings and Notices The following issues occurred during the automated portion of your configuration and must be addressed before proceeding. ${instructions.notices.singleuser} Some of the clients in your environment may need access to the SAS/GRAPH Java applets to view graphical output generated by SAS processes. If so, add the APPLETLOC option to the sasv9_usermods.cfg file located in each SAS Application Server context directory specifying the location to be used in generating graphical output. APPLETLOC should point to a network accessible copy of the SAS/GRAPH Java applets. WARNING: One or more issues were encountered during the creation of the service SAS [EMDesktop-Lev1] SASMeta - Metadata Server. Typically this occurs when a service with the same name already exists. The dependency chain for this service, and any other services that might depend on it, could be compromised. Use the Services Manager to verify that the properties of this service are correct. If they are incorrect, uninstall this configuration and reconfigure. ${instructions.notices.item}
To verify that you do not have any duplicate SAS services, check your list of Windows services by doing the following:
If there are duplicate SAS services present, then you need to remove these services by using one of the following methods:
Whichever method above that you use, ensure that the SAS configuration directory (C:\SAS) is removed from your machine and that the SAS services are no longer listed in the Windows services dialog box.
You can use the SAS Deployment Manager to remove an existing SAS 9.2 configuration from your machine, which also removes SAS 9.2 services. For more information about removing a SAS 9.2 configuration from your machine, see SAS Note 35275, "Rerunning the configuration phase of a SAS® 9.2 installation."
When you have finished performing the recommendations in SAS Note 35275, you still need to delete the SAS configuration directory (C:\SAS) from your machine.
Finally, rerun setup.exe from the C:\SAS Software Depot folder. When you rerun setup.exe, do the following:
After completing this process, you should have a working SAS 9.2 configuration.
However, the SAS Deployment Manager might not remove all of the SAS services. If you need to remove SAS services manually after using the SAS Deployment Manager, then use the sc delete command or remove the service keys directly from the Windows registry.
To use the sc delete command, at the command prompt, type sc delete service-name. You might have to include double quotation marks around the SAS service name for the command to work properly. For example:
C:> sc delete "SAS [EBIserver -Lev1] SASMeta - Metadata Server"
For more information about the sc delete command, see Sc delete on the Microsoft Web site.
To remove SAS service keys directly from the Windows registry, open the registry. Navigate to the registry key that contains SAS 9.2 services:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
The names of SAS 9.2 service keys look similar to the following:
SAS [EBIserver -Lev1] SASMeta - Metadata Server
Caution: Always back up your registry before you make any changes to the registry. You can find more information about the registry in Windows Help, in Microsoft documentation, or on the Microsoft Windows Web site. For more information about backing up the registry, see How to back up and restore the registry in Windows XP on the Microsoft Support Web site.
SAS is not responsible for any modifications that you make to your Windows registry. Changes made to the Windows registry can cause your machine to not operate appropriately. In rare cases, you might have to reinstall the Windows operating system to make your machine functional again. Consult with the Windows systems administrator at your organization or your designated IT staff for assistance before you make changes to the Windows registry.
Product Family | Product | System | SAS Release | |
Reported | Fixed* | |||
SAS System | N/A | Microsoft® Windows® for 64-Bit Itanium-based Systems | 9.2 TS2M3 | |
Microsoft Windows Server 2003 Datacenter 64-bit Edition | 9.2 TS2M3 | |||
Microsoft Windows Server 2003 Enterprise 64-bit Edition | 9.2 TS2M3 | |||
Microsoft Windows XP 64-bit Edition | 9.2 TS2M3 | |||
Microsoft® Windows® for x64 | 9.2 TS2M3 | |||
Microsoft Windows Server 2003 Datacenter Edition | 9.2 TS2M3 | |||
Microsoft Windows Server 2003 Enterprise Edition | 9.2 TS2M3 | |||
Microsoft Windows Server 2003 Standard Edition | 9.2 TS2M3 | |||
Microsoft Windows Server 2003 for x64 | 9.2 TS2M3 | |||
Microsoft Windows Server 2008 | 9.2 TS2M3 | |||
Microsoft Windows Server 2008 for x64 | 9.2 TS2M3 | |||
Microsoft Windows XP Professional | 9.2 TS2M3 | |||
Windows 7 Enterprise 32 bit | 9.2 TS2M3 | |||
Windows 7 Enterprise x64 | 9.2 TS2M3 | |||
Windows 7 Home Premium 32 bit | 9.2 TS2M3 | |||
Windows 7 Home Premium x64 | 9.2 TS2M3 | |||
Windows 7 Professional 32 bit | 9.2 TS2M3 | |||
Windows 7 Professional x64 | 9.2 TS2M3 | |||
Windows 7 Ultimate 32 bit | 9.2 TS2M3 | |||
Windows 7 Ultimate x64 | 9.2 TS2M3 | |||
Windows Vista | 9.2 TS2M3 | |||
Windows Vista for x64 | 9.2 TS2M3 |
Type: | Problem Note |
Priority: | medium |
Date Modified: | 2010-09-24 14:27:24 |
Date Created: | 2010-09-16 16:25:06 |