Dear Community,
I am working with sas for months, but now this error message is showing up everytime I start my SAS 9.4.
WARNING: One or more libraries specified in the concatenated library SASHELP
WARNING: do not exist. These libraries were removed from the concatenation.
I also cannot import my excel sheets anymore. Does anybody know what to do and how to fix the problem?
I always get that error message when I try to import:
ERROR: Connect: Das angegebene Modul wurde nicht gefunden.
ERROR: Error in the LIBNAME statement.
I have a 64bit SAS and 32bit Excel btw, which may cause the Problem
Thanks 🙂
I tried both
Libname saspms "C:\PMS";
proc import out=work.datensatz
datafile="C:\PMS\Anzeigen2.xls"
DBMS = EXCEL;
run;
or:
Libname saspms "C:\PMS";
PROC IMPORT OUT= work.datensatz
DATAFILE= "C:\PMS\Anzeigen2.xls"
DBMS=EXCELCS REPLACE;
RANGE="Sheet1$";
SCANTEXT=YES;
USEDATE=YES;
SCANTIME=YES;
RUN;
Well, you would need to be more specific, run the code and show the log each time. From a look through:
- This is not used in the first part:
Libname saspms "C:\PMS";
This engine does not match the file type:
datafile="C:\PMS\Anzeigen2.xls"
DBMS = EXCEL;
XLS file type is old binary, and may not be the same Excel engine, so that may be causing you issues. Remove the dbms and let it choose which engine to use.
Same here, not sure excelcs should be the engine:
DATAFILE= "C:\SAS_PMS\Datensatz_PMS.xls"
DBMS=EXCELCS REPLACE;
Are you sure the paths are correct as in 1:
Libname saspms "C:\PMS";
And in 2;
Libname saspms "C:\SAS_PMS";
Does one or either of those exist (and do you have write permission to them.
Check out the files which are run with startup like autoexec.sas. It sounds like there is a libname statement referencing folders on your computer that don't exist.
As for opening Excel 32 bit on 64 SAS, not sure that is possible. Use pcfiles, or better yet, save to CSV and read in a CSV file with proper datastep import - avoid a guessing procedure like proc import.
Been a while since I have used desktop SAS. It is a SAS file which should be in the SAS install location which is run as the system starts up. Search for autoexec.sas. You want to see any line in there which has network or local paths.
Looks like you have a damaged SAS installation; SASHELP is spread over several directories, and part of them are missing.
Look in sasv9.cfg for the paths that constitute SASHELP, and see what's missing, so you can restore it from the backup.
WARNING: One or more libraries specified in the concatenated library SASHELP
WARNING: do not exist. These libraries were removed from the concatenation.
To remove the warning message that appears when you launch SAS, go to the "nls" folder on your PC, folder path - "C:\Program Files\SASHome\SASFoundation\9.4\nls".
Locate the "SASCFG" folder in one of the folders present in the "nls" folder. Copy it and paste it into the "en" folder. To do so, you must have administrative rights.
When you reopen SAS, the warning message will no longer appear in the log.
Join us for SAS Innovate 2025, our biggest and most exciting global event of the year, in Orlando, FL, from May 6-9. Sign up by March 14 for just $795.
Learn how use the CAT functions in SAS to join values from multiple variables into a single value.
Find more tutorials on the SAS Users YouTube channel.
Ready to level-up your skills? Choose your own adventure.