BookmarkSubscribeRSS Feed
_zeta_
Fluorite | Level 6

Has anyone else encountered this error in SAS Studio?
We know it's not a user code error, because it appears right after the workspace server's autoexec.sas file executes. We've already tried clearing the user node flows with:
filename _all_ clear and ods _all_ close, but neither command has resolved the issue, even temporarily.

4 REPLIES 4
Quentin
Super User

Can you post the log from running the autoexec?  Is that the only error message you see in the log?

_zeta_
Fluorite | Level 6

before the error we had this warning
WARNING: No logical assign for filename _GSFNAME.

 

_zeta__0-1763158308663.png

 

Quentin
Super User

If you don't get a helpful response here, I recommend you contact SAS tech support.

 

Note the earlier "Mapping error" in the IOM logic note.  I don't know what that is about, but typically with SAS the recommendation is to review the log and focus on the earliest error first.

gwootton
SAS Super FREQ
This looks like an issue being experienced by SAS Studio's pre-execution code that runs to produce results that SAS Studio can consume.
My guess would be something in the autoexec or compute server startup commands is putting the SAS session in a state where the studio pre-exec code doesn't function as expected.
_GSFNAME I believe is a temp filename for storing graph output, while _SASWSTEMP_ is set to the compute server's WORK library path.
--
Greg Wootton | Principal Systems Technical Support Engineer

suga badge.PNGThe SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment. 

Join SUGA 

Get Started with SAS Information Catalog in SAS Viya

SAS technical trainer Erin Winters shows you how to explore assets, create new data discovery agents, schedule data discovery agents, and much more.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 4 replies
  • 377 views
  • 0 likes
  • 3 in conversation