尔于也个人空间

Problem Note 47874: The Renew SAS® Software utility for SAS® 9.3 or SAS® 9.4 might fail and return "cannot open" error messages

Problem Note 47874: The Renew SAS® Software utility for SAS® 9.3 or SAS® 9.4 might fail and return "cannot open" error messages
 
When you use the Renew SAS Software utility (or click the SASRenew.exe file) for SAS 9.3 or SAS 9.4, the following error message might appear in Step 3, when you click Renew:
 
 
ERROR: Cannot open "C:\Program"
 
SAS option '-PATH' not set.
Check configuration file, SAS environment options or command line options.
SAS option '-RESOURCESLOC' not set.
Check configuration file, SAS environment options or command line options.
 
FATAL ERROR: WRCODE=80000803, MODULE='HIINIT': PATH OPTION UNAVAILABLE
 
SASTBTraceBackCtx has been called with a
string("vacrash") instead of a CONTEXT pointer.
Address Frame (DBGHELP API Version 4.0 rev 5)
000007FEFCD7CACD 0000000003AFE560 KERNELBASE:RaiseException+0x3D
000000000204155B 0000000003AFE568 tkmk:tkBoot+0x4053B
0000000002041329 0000000003AFEAB0 tkmk:tkBoot+0x40309
000000000203439A 0000000003AFEB00 tkmk:tkBoot+0x3337A
00000000037A3311 0000000003AFEB08 sashost:Main+0x139C41
0000000003670F59 0000000003AFEB60 sashost:Main+0x7889
0000000003661E41 0000000003AFEBD0 sashost:rtmdoit+0x241
00000000037310DD 0000000003AFEC10 sashost:Main+0xC7A0D
0000000003699DB7 0000000003AFECA0 sashost:Main+0x306E7
0000000003697ABD 0000000003AFECF0 sashost:Main+0x2E3ED
000000000366150D 0000000003AFEE50 0001:000000000000050D sashost.dll
0000000003669FBE 0000000003B2FC70 sashost:Main+0x8EE
000000000367BC57 0000000003B2FCB0 sashost:Main+0x12587
0000000003678A09 0000000003B2FF20 sashost:Main+0xF339
000000000367D12D 0000000003B2FF50 sashost:Main+0x13A5D
0000000076B2652D 0000000003B2FF58 kernel32:BaseThreadInitThunk+0xD
0000000076D5C521 0000000003B2FF88 ntdll:RtlUserThreadStart+0x21
 
ERROR: WYNEVER FATAL ERROR: WRCODE=ffffffff80000803, MODULE='HIINIT': PATH OPTION UNAVAILABLE
ERROR: SAS Is Terminating
 
 
The first line of the error includes part of the path to your particular SAS installation. So instead of C:\program, the error might report D:\program, or E:\program, or C:\progra~1\SASHOME\SASFound.
 
This problem occurs because Windows short folder names (8.3) are not created on your machine.
 
Three Ways to Renew the SAS Software on Your Machine
To renew SAS software on your machine, choose one of the following options:
 
Option 1: This method provides instructions for creating short folder names on the drive where SAS is installed, if possible, after which you can run the Renew SAS Software utility.
If you cannot enable short folder names, select one of the following, based on your version of SAS.
 
Option 2: For SAS 9.4 (TS1M1) and earlier installations. This workaround does not require short folder names. (You do not use the Renew SAS Software utility.)
Option 3: For SAS 9.4 (TS1M2) installations. This workaround does not require short folder names. (You do not use the Renew SAS Software utility.)
 
Option 1: Enable and Create Short Folder Names, If Possible
For SAS 9.4 (TS1M1), SAS 9.4 (TS1M0), and SAS 9.3 versions, the system requirements include enabling short folder names. To enable short folder names and create the necessary short folders, contact your IT department or use the instructions below.
 
The error occurs because the short folder names PROGRA~1 and possibly SASFou~1 are not created. Also, the value of a file system registry setting called NtfsDisable8dot3NameCreation might not allow this short folder name to be created. NtfsDisable8dot3NameCreation is located in the system registry at HKLM\SYSTEM\CurrentControlSet\Control\FileSystem. When NtfsDisable8dot3NameCreation is set to 0, the system creates both short folder names and long folder names. There are also values 1, 2, and 3. A qualified system administrator can locate and modify this setting if needed.
 
Note that page 1 of System Requirements for SAS® 9.3 Foundation for Microsoft Windows states that the 8.3 filename convention must remain enabled.
 
To check for the short folder names, complete the following steps:
 
Make sure you are logged on with a user ID that has local administrator rights. Access a DOS command prompt as follows:
Click Start.
 
In the Search Program and Files command box, type cmd.
 
Locate the cmd.exe command in the list, right-click cmd.exe, and click Run as administrator.
 
Type cd\ and press the Enter key, so that you are at the root of the current drive letter. If you need to select a different drive first, type D: or the desired drive letter and press Enter.
Type dir progr*.* /x and press the Enter key. The results display possibly two columns that contain the short and long folder names.
 
Look for PROGRA~1 associated with the Program Files folder. You might not have a PROGRA~1 folder or it might exist. Go deeper into the SAS installation folder structure by typing cd program files\SASHOME and press the Enter key.
 
Enter the dir /x command to see the folders.
 
You might have a SASFoundation folder, but check to see whether there is an associated SASFOU~1 folder.
 
Most likely, either the short folder name PROGRA~1, SASFOU~1, or both are not present.
 
Enter exit to exit the cmd prompt.
 
Contact the IT department at your company to help create the necessary short folder names. Your IT department might be able to use the Microsoft command mklink /J to create a directory junction. However, this method has not been tested by SAS. Or, you might be able to create the short folder names with the Microsoft utility called fsutil.
 
To use the fsutil command, follow these steps:
 
Make sure you are logged on with a user ID that has local administrator rights. Access a DOS command prompt and enter cd\ to get to the root of the drive letter.
 
If there is no PROGRA~1 folder, enter this command to create it: fsutil file setshortname "Program Files" PROGRA~1
 
If you receive the message ERROR: access is denied, reboot the machine in Safe Mode with Command Line and try the fsutil command again.
 
You can enter a dir /x command now to see the newly made folder.
 
If the SASFOU~1 folder is not present, type cd program files\SASHOME
 
Enter the fsutil command to create the SASFOU~1 folder: fsutil file setshortname "SASFoundation" SASFOU~1
 
You can enter a dir /x command now to see the newly made short folder name.
 
Enter exit to exit the cmd prompt.
 
Now that you have a PROGRA~1\SASHOME\SASFOU~1 folder structure, run the Renew SAS Software utility again:
 
Select Start ► Programs ► SAS ► Utilities.
 
Right-click Renew SAS Software and click Run as Administrator.
 
If SAS is installed in a Microsoft Windows Server operating environment, such as Windows 2008 Server or Windows 2012 server, you might have to run the Update the SID File in Metadata task after SAS is renewed successfully. (See instructions below.) After renewing all SAS® Foundation installations on all other machines in the environment, restart any Windows Services related to SAS in the correct order.
 
Instructions for Updating SID File in Metadata
 
If your SAS deployment includes specific SAS solutions software, such as SAS® 9.4 Enterprise BI Server, SAS® Enterprise Miner™, or SAS® Visual Analytics (see Note below), you must perform an additional renewal step before restarting the Windows Server machine or SAS Windows Services. Perform "STEP D: Update the SID File in Metadata" shown in the SAS 9.4 for Microsoft Windows Software License Renewal Instructions for Planned Deployment document. If needed, see instructions in "STEP E: Restart SAS Servers and SAS Spawners."
 
Note: For a complete list of applicable SAS solutions and SAS products, see SAS Note 49750: "To extend the expiration date for particular SAS solutions, you must perform the 'Update SID File in Metadata' task."
 
If short folder names cannot be enabled at your company, then use the workarounds described in Option 2 or Option 3 below.
 
Option 2: For SAS 9.4 (TS1M1) and earlier installations
Important: This workaround does not renew SAS® LASR™ Analytic Server if it is installed. For SAS 9.4 (TS1M2) installations, use Option 2. For SAS 9.4 (TS1M1) and earlier installations that include SAS LASR Analytic Server, contact SAS Technical Support.
 
Note: This workaround for SAS 9.3 and SAS 9.4 renews SAS Foundation products only and bypasses the need to run the Renew SAS Software utility.
 
If SAS is completely expired and does not open, proceed to the next section for Option 2.
 
If you can open SAS, complete the following steps:
 
Make sure you are logged on with a user ID that has local administrator rights.
 
Open the SAS installation data file (SID file) in Notepad.
 
Close all SAS sessions. Select Start ► All Programs ► SAS, right-click SAS 9.3 (English) or SAS 9.4 (English), and click Run as administrator.
 
In Notepad, copy the part of the SID file from PROC SETINIT down to SAVE; RUN; and paste this code into the SAS Editor window.
 
Submit the SAS code by selecting Run ► Submit.
 
Check the bottom of the SAS Log window for this message: Siteinfo data have been updated. If this message is displayed, then your SAS Foundation installation is now renewed. Close SAS. Note: If errors occur, open a track with SAS Technical Support, email the entire contents of the SAS Log window starting with the copyright information, and email the renewal SID file. Do not run the Renew SAS Software utility, because the same error listed above will occur.
 
Start SAS 9.3 (English) or SAS 9.4 (English) again. Enter the SAS code PROC SETINIT; RUN; and submit it. Check the SAS Log window to verify the new expiration dates.
If SAS is installed on a Microsoft Windows workstation, such as Windows 7 or Windows 8, and the new expiration dates are in the SAS Log window, then the renewal process is now complete.
 
If SAS is installed in a Microsoft Windows Server operating environment, such as Windows 2008 Server or Windows 2012 server, after SAS is renewed successfully, then run the Update the SID File in Metadata task, if required.  (See instructions below.) After renewing all SAS Foundation installations on all other machine in the environment, restart any Windows Services related to SAS in the correct order.
 
Instructions for Update SID file in Metadata: If your SAS deployment includes specific SAS solutions software, such as SAS® 9.4 Enterprise BI Server, SAS® Enterprise Miner, or SAS® Visual Analytics (see Note below), there is an additional renewal step before restarting the Windows Server machine or SAS Windows Services. Perform "STEP D: Update the SID File in Metadata" in the SAS 9.4 for Microsoft Windows Software License Renewal Instructions for Planned Deployment document. If needed, see instructions in "STEP E: Restart SAS Servers and SAS Spawners."
 
Note: For a complete list of applicable SAS solutions and SAS products, see SAS Note 49750: "To extend the expiration date for particular SAS® solutions, you must perform the 'Update SID File in Metadata' task."
 
If SAS is completely expired, complete the following steps:
 
Make sure you are logged on with a user ID that has local administrator rights.
 
Close any SAS expiration error messages that appeared when you attempted to start SAS.
 
Open the SID file in Notepad.
 
Select Start ► All Programs ► Accessories, right-click Notepad, and click Run as administrator.
 
Note: This opens a second Notepad window.
 
Copy the part of the SID file from PROC SETINIT down to SAVE; RUN; and paste this code into the new Notepad window.
 
Close the Notepad window that contains the original SID file.
 
In the Notepad window that contains only the PROC SETINIT down to SAVE; RUN; code, select File ► Save As. Navigate to your SAS installation folder. For example, the default folders are:
SAS 9.3:
C:\program files\SASHOME\SASFoundation\9.3\
C:\program files\SASHOME\x86\SASFoundation\9.3\
 
SAS 9.4:
C:\program files\SASHOME\SASFoundation\9.4\
C:\program files\SASHOME\x86\SASFoundation\9.4\
 
In the Notepad Save As dialog box, navigate to the C:\temp folder or another folder in which you have the rights to save a file. Note the exact path, because you will need to enter it in the command prompt window in Step 11 in place of C:\temp.
 
Then, change the Save as type option from Text Documents (*.txt) to All files (*.*). Type setinit.sss in the File name field and click Save.
 
Select File ► Exit to close Notepad.
 
Select Start ► All Programs ► Accessories, right-click Command Prompt, and click Run as administrator.
 
Enter the following on one line, using the folder for your SAS installation:
 
"C:\program files\SASHOME\SASFoundation\9.3\SAS.EXE" -sysin "C:\temp\setinit.sss" -setinit
 
Press the Enter key. Note: If errors occur, open a track with SAS Technical Support, and email a screen shot of the entire Command Prompt window, a screen shot of any error messages, and the renewal SID file. Do not run the Renew SAS Software utility, because the same error listed above will occur.
 
Verify the new expiration dates by selecting Start ► All Programs ► SAS and selecting SAS 9.3 (English) or SAS 9.4 (English). Type in the SAS code PROC SETINIT; RUN; and submit the SAS code. Check the SAS Log window to verify the new expiration dates.
 
If SAS is installed on a Microsoft Windows workstation, such as Windows 7 or Windows 8, and the new expiration dates are in the SAS Log window, then the renewal process is now complete.
 
If SAS is installed in a Microsoft Windows Server operating environment, such as Windows 2008 Server or Windows 2012 Server, after SAS is renewed successfully, then run the Update the SID File in Metadata task, if required. (See instructions below.) After renewing all SAS Foundation installations on all other machine in the environment, restart any Windows Services related to SAS in the correct order.
 
Instructions for Update SID File in Metadata: If your SAS deployment includes specific SAS solutions software, such as SAS 9.4 Enterprise BI Server, SAS Enterprise Miner, or SAS Visual Analytics (see Note below), there is an additional renewal step before restarting the Windows Services related to SAS. Perform "STEP D: Update the SID File in Metadata" in the SAS 9.4 for Microsoft Windows Software License Renewal Instructions for Planned Deployment document. If needed, see instructions in "STEP E: Restart SAS Servers and SAS Spawners."
 
Note: For a complete list of applicable SAS solutions and SAS products, see SAS Note 49750: "To extend the expiration date for particular SAS® solutions, you must perform the 'Update SID File in Metadata' task."
 
Option 3: For SAS 9.4 (TS1M2) Installations
If you start SAS 9.4 (English) on your machine and the top of the SAS Log window displays NOTE: SAS (r) Proprietary Software 9.4 (TS1M2), use this workaround because it does not require that short folder names are enabled.
 
Important: This process renews the SAS LASR Analytic Server if it is installed and included in the renewal SID file.
 
Make sure you are logged on with a user ID that has local administrator rights. Open a Command Prompt window as an administrator. One way to accomplish this is to select Start ► All Programs ► Accessories, right-click Command Prompt, and click Run as administrator.
In the Command prompt window, change to the \SASHOME\SASDeploymentManager\9.4\ folder. For example, enter the following:
CD "c:\program files\SASHOME\SASDeploymentManager\9.4"
Press the Enter key.
 
In the Command Prompt window, type the following:
sasdm.exe -renew
Press the Enter key.
 
Note: These steps enable the Renew SAS Software option in SAS® Deployment Manager.
 
Complete the Renew SAS Foundation process.
Note: If errors occur, open a track with SAS Technical Support, email a screen shot of the error message, and email the renewal SID file. Do not run the Renew SAS Software utility, because the same error listed above will occur.
 
Verify the new expiration dates by selecting Start ► All Programs ► SAS and selecting SAS 9.4 (English). Type in the SAS code PROC SETINIT; RUN; and submit the SAS code. Check the SAS Log window to verify the new expiration dates.
 
If SAS is installed on a Microsoft Windows workstation, such as Windows 7 or Windows 8, and the new expiration dates are in the SAS Log window, the renewal process is now complete.
 
If SAS is installed in a Microsoft Windows Server operating environment, such as Windows 2008 Server or Windows 2012 server, after SAS is renewed successfully, then run the Update the SID File in Metadata task, if required. (See instructions below.) After renewing all SAS Foundation installations on all other machine in the environment, restart any Windows Services related to SAS in the correct order.
 
Instructions for Update SID File in Metadata: If your SAS deployment includes specific SAS solutions software, such as SAS 9.4 Enterprise BI Server, SAS Enterprise Miner, or SAS Visual Analytics (see Note below), there is an additional renewal step before restarting the Windows Server machine or SAS Windows Services. Perform "STEP D: Update the SID File in Metadata" in the SAS 9.4 for Microsoft Windows Software License Renewal Instructions for Planned Deployment document. If needed, see instructions in "STEP E: Restart SAS Servers and SAS Spawners."
 
Note: For a complete list of applicable SAS solutions and SAS products, see SAS Note 49750: "To extend the expiration date for particular SAS® solutions, you must perform the 'Update SID File in Metadata' task."
添加日期:2019/11/3   浏览量:1807   来源:
  • / 2021/3/13 6:27:28
  • / 2021/4/24 3:16:20
  • / 2021/5/13 1:06:09
  • / 2021/7/29 12:21:51
  • / 2021/7/29 20:07:23
  • / 2021/7/31 19:40:43
  • / 2021/8/2 5:34:39
  • / 2021/8/3 8:39:24
  • / 2021/8/5 8:00:35
  • / 2021/9/3 17:10:33
  • / 2021/10/3 20:37:17
  • / 2021/11/17 23:30:45
  • / 2021/11/18 15:36:10
  • / 2022/3/31 14:19:48
  • / 2022/9/1 15:28:10
昵   称:
内   容:
验证码: