|SAS Companion for the Microsoft Windows Environment
This section describes errors you may receive while trying to
use the SAS System to access files (either external files or SAS files). Whenever
you have trouble accessing files, always check the validity of your FILENAME
and LIBNAME statements and functions to make sure they point to the right
files. Also, be sure you are using the correct fileref or libref.
Core catalog cannot be initialized. Please verify the system's
- The date or time stamp of the SAS System's
CORE catalog is in the future. Make sure the date and time on your machine
are set correctly. This message is issued in conjunction with internal error
602 (see Resolving Internal Errors).
Error: Date/time is in the future.
- The date or time stamp of the file you are
trying to access is in the future. Make sure the date and time on your machine
are set correctly.
Error: File is in use, filename.
- The file you are trying to access is in
use by another Windows process, such as another Windows application.
Error: File not found loading filename-1.
File contributing to error: filename-2.
- A DLL-dependent file cannot be found when
the requested file is loaded. For the SAS System, the !SASROOT\CORE\SASEXE
file (usually specified with the PATHDLL system option in the SAS configuration
file) may have become unavailable. This may be due to a network error or other
drive failure. Ensure that PATHDLL specifies the location of !SASROOT\CORE\SASDLL.
ERROR: Member or library filename
unavailable for use.
- The file filename
is being used by another Windows application.
ERROR: Module module-name not
found in search paths.
- This error is caused by one of the following:
- incorrect PATH system option in the SAS configuration
- the product you called is not installed
- a dependent image is not
ERROR: Unable to clear or reassign the library library-name because it is still in use.
- You are trying to reassign a libref while
the library is in use.
ERROR: Operating system error number n
occurred while accessing filename.
- An unexpected return code has been received
by the SAS System from the operating system. For more information, see Resolving Operating System and Windows Error Messages.
ERROR: Physical file does not exist filename.
- The file you are trying to access does not
exist. Verify that you have specified the correct drive and directory. This
error can also occur if you are trying to write to a write-protected diskette.
ERROR: Write access to member member-name is denied.
- You are trying to update a file on a write-protected
diskette or you are trying to update a file marked as read-only.
Copyright 1999 by SAS Institute Inc., Cary, NC, USA. All rights reserved.