PROC IMPORT via EG Keeps running

[shoin]

SAS 9.4TS1M5 on WIN 2012, OA install (Office Analytics) w' EG & AMO as main end user clients.

EG and Excel are 64 bit

Issue:

simple code like

PROC IMPORT OUT= WORK.a

DATAFILE= "\\path\to\an\test.xlsx"

DBMS=excel REPLACE;

Makes a connection, authenticates, and just keep spinning w' status as "Running".  Same in a parallel environment 9.3 works fine.

1. Successful 'File > Import Data' via EG same file stored locally and on the compute server (reads in fine, no issue, generates code)

2. PROC import keeps running

3. I have turned on work space server logs (trace) that do not show anything except waiting for the step (excel file has 1000 rows, few cols)

4. I also turned on local EG logging which shows the following but my search does not render anything meaningful:

#from SAS EG log

Main] INFO SAS.EC.Environment.ShlwApi [(null)] - GetExecutableRegisteredForExtension() - found C:\Windows\system32\LaunchWinApp.exe
2018-10-11 12:14:23,065 [Main] INFO SAS.EC.Environment.ShlwApi [(null)] - GetExecutableRegisteredForExtension() - found C:\Program Files\Microsoft Office\Office16\WINWORD.EXE
2018-10-11 12:14:23,072 [Main] ERROR SAS.EC.Environment.ShlwApi [(null)] - GetExecutableRegisteredForExtension() - Unable to find executable 31
2018-10-11 12:14:23,092 [Main] DEBUG SAS.EG.Utilities.AppDomainAssemblyResolver [(null)] - Loaded assembly C:\Program Files\SASHome\SASEnterpriseGuide\7.1\SAS.OLAPCommonUI.dll
2018-10-11 12:14:23,098 [Main

Both logs do not show 'ERROR' only 'DEBUG' and 'INFO'

Thank you in advance for any insight that you may have.

[shoin · Accepted solution]

Forgot to mention permission on the file system were read-write-execute.

[CaseySmith]

I recommend taking this one up with Tech Support.  If I were debugging, I'd probably start by getting a more detailed workspace server log to see what state it is in (already ran the proc import, but EG not notified?  never got the job?  stuck somewhere?)

Casey

[shoin]

Update

Sorry in replying update 

Two factors

1. Admin did not install the MS ACE driver

2. Once installed it was of wrong bitness, we corrected to 64 bit (in our case as all use MS Office 64 bit)

This then resolved the issue.