Problem Note 40409: The SAS® PC Files Server stops working when you use the EXCELCS, ACCESSCS, and PCFILES engines in SAS® Enterprise Guide®
When using the ExcelCS and AccessCS engines with the IMPORT and EXPORT procedures in SAS Enterprise Guide, you can receive the following error in a separate Microsoft Windows message dialog box:
PCFSERVER.EXE has stopped working
Check online for a solution and close the program
In the SAS Enterprise Guide log, you can see the following message:
Error: Failed to connect to server
In addition, if you use a LIBNAME statement with the PCFILES engine, you can receive this error:
ERROR: The PC Files Server process died before communicating with SAS.
These problems occur in SAS Enterprise Guide even when the same code runs without errors in Base SAS® software.
The problem can occur when SAS and the PC Files Server are running on the same machine. This is because the User ID is not in the Microsoft Windows Administrators group, which is normally required in order to spawn the pcfserver.exe executable under these conditions. When SAS and the PC Files Server run on the same machine, the PC Files Server uses AutoAuthentication and AutoStart on that service.
Widows Services in this case use Windows Authentication, which runs the PC Files Server as the particular user ID that is connected to the workspace server.
Other causes occur because of the problem of timing with PC Files Server and the Microsoft Access Connectivity Engine itself.
To resolve the problem do one or more of the following depending on the cause:
The SAS PC Files Server stops working and errors are generated when you use the EXCELCS, ACCSESCS, and PFCILES engines with a group ID that is not a Windows Administrator group ID.
Type: | Problem Note |
Priority: | high |
Date Modified: | 2011-01-26 14:05:57 |
Date Created: | 2010-07-21 15:09:46 |