topic Re: EG: Errors importing excel files do not show up as error in SAS Enterprise Guide

EG: Errors importing excel files do not show up as error

snoopy369 — Thu, 19 Sep 2013 17:13:00 GMT

Running EG 6.1, when I have an error importing an excel file (File Not Found, etc.) with dbms=xlsx, it shows up as plain text in the log, not highlighted as an error (or even a note). Is there a setting for this, or is this just a bug?

Specifically, this log:

28         proc import file="c:\temp\blahblahblah.xlsx" out=test dbms=xlsx replace;
29         run;

ERROR: XLSX file does not exist -> c:\temp\blahblahblah.xlsx

NOTE: The SAS System stopped processing this step because of errors.
NOTE: PROCEDURE IMPORT used (Total process time):
      real time           0.00 seconds
      cpu time            0.00 seconds

The ERROR is not in red, nor is it seen as an error by EG.

Re: EG: Errors importing excel files do not show up as error

SASKiwi — Thu, 19 Sep 2013 20:14:11 GMT

I see the same behaviour with EG 5.1 SAS 9.3M1.

Re: EG: Errors importing excel files do not show up as error

atmesh — Wed, 11 Jun 2014 04:37:43 GMT

even i have got the same problem....i cant create library too.

It throws error: Library not assigned.

Someone help!!

Re: EG: Errors importing excel files do not show up as error

Scott_Mitchell — Wed, 11 Jun 2014 04:45:04 GMT

I am not experiencing this problem using EG 4.1 and SAS 9.3 1M0.

Re: EG: Errors importing excel files do not show up as error

jakarman — Wed, 11 Jun 2014 07:21:58 GMT

Eg is a client, the real sas processing can run on a complete different machine.

As that other machine is not accessing your desktop your error is a common logical one .

Using eg accessing excel is possible by dedicated eg tasks. They will do the translation of excel into a sas data step upload that and run it to sas.

What is proc import doing with eguide?...nothing

Re: EG: Errors importing excel files do not show up as error

ChrisHemedinger — Wed, 11 Jun 2014 12:38:32 GMT

This behavior is bug, I think. The problem is that in this case, the IMPORT procedure isn't generating a genuine "error" line.

ERROR, NOTE, and WARNING lines are tagged with a special 2-byte prefix in the log file generated by SAS. These prefixes provide the cue to EG that there are errors or warnings, and they also are used for determining the line color in the log you see displayed.

I checked internally, and this behavior is set to be fixed in 9.4M2, due out just little bit later this year.

Chris

Re: EG: Errors importing excel files do not show up as error

snoopy369 — Mon, 21 Jul 2014 18:33:14 GMT

Thanks Chris! I look forward to the updated version (and the improved functionality).