Enterprise Guide - Proc Gchart issue

[mjadams1]

Recently we replaced our SAS licences and today were seeing an issues in Enterprise Guide when it tries to produce a chart

using Proc Gchart. Has anyone seen issues like this after stopping SAS and replacing licensing information?

Here is what was seen in the Log:

NOTE: 10833 bytes written to /sas/work/SAS_workE6BA00630052_efkxdwn11/SAS_workE79A00630052_efkxdwn11/gchart3.png.

ERROR: Insufficient authorization to access /sas/BIServer/config94/Lev4/SASApp/gchart.png.

ERROR: Physical file does not exist, /sas/BIServer/config94/Lev4/SASApp/gchart.png.

Thanks,

Mike Adams

[SuryaKiran]

Show us the code your trying to run.

[mjadams1]

Here is the code:

goptions device=png;
ODS LISTING CLOSE;
ODS NOPROCTITLE;

ODS HTML(ID=EGHTMLA)
FILE=
"/usr/HTTPServer/htdocs/sasweb/300mm/reitmeyer/dynamic_boost_lots_boosted.html" (TITLE='Dynamic DDMS Boost')
HEADTEXT="<style>p,hr {display:none}</style> <meta http-equiv=""refresh"" content=""300"">"
STYLE=Meadow;

%_sas_pushchartsize(700,360);
PATTERN1 COLOR=CXFF9900;
PATTERN2 COLOR = _STYLE_;
PATTERN3 COLOR = _STYLE_;
PATTERN4 COLOR = _STYLE_;
PATTERN5 COLOR = _STYLE_;
PATTERN6 COLOR = _STYLE_;
PATTERN7 COLOR = _STYLE_;
PATTERN8 COLOR = _STYLE_;
PATTERN9 COLOR = _STYLE_;
PATTERN10 COLOR = _STYLE_;
PATTERN11 COLOR = _STYLE_;
PATTERN12 COLOR = _STYLE_;
Axis1
STYLE=1
WIDTH=1
MINOR=NONE

;
Axis2
STYLE=1
WIDTH=1

;
TITLE;
TITLE1 "Lots Boosted";
TITLE2 "Updated on %TRIM(%QSYSFUNC(DATE(), NLDATE20.)) at %TRIM(%SYSFUNC(TIME(), TIMEAMPM12.))";
FOOTNOTE;

PROC GCHART DATA=QueryHistoryFile;
VBAR Date
/
SUMVAR=Count_Boost
CLIPREF
FRAME DISCRETE
TYPE=SUM
OUTSIDE=SUM
COUTLINE=CXFF6600
RAXIS=AXIS1
MAXIS=AXIS2;
RUN; QUIT;

TITLE; FOOTNOTE;
%_sas_popchartsize;
PATTERN1;

ODS HTML CLOSE;ODS _ALL_ CLOSE;

[ballardw]

You may need to share the code for the %_sas_pushchartsize macro. Or run the program with OPTIONS MPRINT; so the LOG shows more detail of generated code and the error in relation to submitted code.

From the name I would guess you may be using GOPTIONS statement to set display size. If this also sets values for GSFNAME or other of the graphic output file statements the path might be relative to execution and so is attempting to write in the executable directory of the SAS install instead of a location you have write permissions to.

When we ask for the code that was run best is to copy the submitted code and warning or error messages from LOG and then paste into a code box opened using the forum's {I} menu icon. The main message windows will reformat code and error messages possibly making any diagnostics that appear in the log out of place.