topic Re: ERROR: Connect: The Microsoft Access database engine cannot open or write to the file in SAS Programming

ERROR: Connect: The Microsoft Access database engine cannot open or write to the file

timeless — Wed, 24 Jan 2018 14:26:59 GMT

Following Libname statement works in SAS EG but not in Base SAS (when deployed a scheduled job through SAS Mamagement console).

BASE SAS:

libname CSCData access path='\\xxxxxx\00. Datastore\xxxxxData1.accdb';

ERROR: Connect: The Microsoft Access database engine cannot open or write to the file '\\xxxxxx\00. Datastore\xxxxxData1.accdb'. It is already opened exclusively by another user, or you need permission to view and write its data.
ERROR: Error in the LIBNAME statement.

SAS EG:

libname CSCData access path='\\xxxxxx\00. Datastore\xxxxxData1.accdb';
NOTE: Libref CSCDATA was successfully assigned as follows:
Engine: ACCESS
Physical Name: \\xxxxxx\00. Datastore\xxxxxData1.accdb

Any solution is greatly appreciated. Is there a OPTION statement to resolve this issue.

Re: ERROR: Connect: The Microsoft Access database engine cannot open or write to the file

Kurt_Bremser — Wed, 24 Jan 2018 14:30:05 GMT

My first guess is that the user used to run the scheduled job does not have the necessary permissions for the accdb file.

Re: ERROR: Connect: The Microsoft Access database engine cannot open or write to the file

timeless — Wed, 24 Jan 2018 14:35:02 GMT

User is the same, login with the same ID

Re: ERROR: Connect: The Microsoft Access database engine cannot open or write to the file

ballardw — Wed, 24 Jan 2018 15:04:51 GMT

You also need to investigate the first part of the error

ERROR: Connect: The Microsoft Access database engine cannot open or write to the file '\\xxxxxx\00. Datastore\xxxxxData1.accdb'. It is already opened exclusively by another user,

If someone else is using the file access is blocked.

Re: ERROR: Connect: The Microsoft Access database engine cannot open or write to the file

timeless — Tue, 30 Jan 2018 12:56:09 GMT

Sorry folks, it was a SAS server problem. When I deployed the code in a different SAS server it worked.