We have a 3 tier environement for our SAS software and we publish our SAS application using a client installed on citrix. When a user runs a job using SAS EG it fails with the error below, but if they run the job again it works. We even made a new excel file to prove no one was in it and still got the SAS error. Now if the user schedules the job using the SAS scheduler it works fine. We installed 64 bit microsoft products on the server and verifed the drives are there.
ERROR: Connect: The Microsoft Access database engine cannot open or write to the file ''. It is already opened exclusively by another user, or you need permission to view and write its data. ERROR: Error in the LIBNAME statement.
this can be 2 things. Or either your own user does not have the right permissions on the shared folder (from the server, just ask an admin to test the UNC path for you), or your server does not have registered properlly the SPNs> I would bet that is its more likely the first option.
So we added the service accounts we used for SAS to the storage locations and it worked. We don't know why, we figured if it didn't have the right security it shouldn't work at all. The other thing why would we need to add service account ID's to the security of the data?
1)Shouldn't the security you use in a SAS session be the ID you created in your SAS profile within SAS EG
2) Is there some process in the back ground when your in SAS that uses a service account?
3) The security on the folder used to store the data: if we added the user shouldn't that be enough?
Thanks for your time, I hope this information helps other.