Providing software solutions since 1976

• Log in
• Create profile
• Welcome
  [Log out]
• Edit profile

• Print  |
• Feedback  |
• Share

  • E-mail

  
  
  

  E-mail This Page

  Your Name:*
  Your E-mail:*
  Recipient E-mail:*
  Send a copy to me
  Personal Message:
  
  

  * indicates a required field

When you try to update the SAS license on a Microsoft Windows Terminal
Server machine, applying the setinit file might generate the
following error messages:

   ERROR: A lock is not available for SASHELP.CORE.CATALOG, lock
   held by another process.
   ERROR: The site validation data cannot be updated. This is most
   likely due to the fact that the SASHELP catalog is not
   available in write mode, and/or that the SETINIT option has not
   been specified when using the SAS command.

To circumvent the problem, do the following:
   1. Make sure all users have exited out of SAS.
   2. Make sure the core.sas7bcat file is not set to read-only.

If you still receive the error messages, it might be due to a
phantom SAS process running on the server. If you are on a client
machine and disconnect from the server without exiting out of SAS
first, a phantom process continues running. This process is not
listed in the Task Manager.

To circumvent the problem do the following:
   1. Re-boot the Microsoft Windows Terminal Server machine.
   2. Make sure you are in admin mode.
   3. Re-apply the setinit file.

Also see SAS Note  #004956 .

Operating System and Release Information