Importing ~1GB Access DB file: pipe communication routine failed error.

[JohnJPS]

I've already done a web serch on this one, and found a link that recommended newer drivers, but we're already on the latest. Has anyone seen this error: 

ERROR: A pipe communications routine failed: The pipe has been ended. (109)
ERROR: A pipe communications routine failed: The pipe is being closed. (232)
ERROR: A pipe communications routine failed: The pipe is being closed. (232)

PS: we're on Windows Server; and it is pulling from a network share location; users did not have this issue prior to us moving to from client-only to client-server, though; but may be useful info.

Any ideas on working around this sort of error?

Thanks!

[ballardw]

Most likely cause is a network issue of some sort. Whether between your server and the data source or your SAS and the Server is a question.

Work arounds may depend on how you are communicating with the DB. You might share some details of that as specific DB may have different options for poor network traffic.

Or is this taking long enough that a higher priority user is "bumping" your access to the data?

[JohnJPS]

The database is just a MS Access "database" flat file. Agreed it's probably something with the network... hopefully it isn't chronic though.

[Reeza]

Well without the code+log we can't really say anything else. 

[SASKiwi]

You should talk to your IT network folks. I'm wondering if there are timeout rules in firewalls and/or network connections causing the problem.

[Reeza]

Were the paths in the pipe properly updated to use the server path/UNC path?

[JohnJPS]

Sorry for not responding sooner.  Discoveries since last time, using a more sterilized test involving both an Excel file and a smaller .accdb from an accessible UNC path.

Excel file:

• Works from EG
• Works running SASBatch from the server manually (logged on as ultra powerful SAS account)
• Works running SASBatch from our scheduling system (using system-spcific service account)

AccessDB file

• Works from EG
• Works running SASBatch from the server manually (regardless of DBMS=ACCESS or DBMS=ACCESSCS)
• Fails running SASBatch from our scheduling system (with a system-specific service account)
  • With DBMS=ACCESS, gives generic dump and says to conctact support (which is in play)
  • With DBMS=ACCESSCS, give the errors noted in original post

Anyway, so it's in flight with SAS Tech Support and I'll update the thread when I have something, but it sure seems permissions related... but the permissions only take effect with the .accdb file, not with the .xlsx file.

If anyone has any ideas around that angle (e.g. some subfolder somewhere to which we need to give our service account access; or some permission within SAS, etc...), I'm all ears.

Thanks!

[JohnJPS · Accepted solution]

Another follow-up. Giving our service account that runs the process local admin status on the server running the job resolves the problem.

Esentially, it needs access to a registry key "Access Connectivtiy Engine." -- making the account Local Admin solved the problem..