Desktop productivity for business analysts and programmers

WARNING: Style URAC not found; Normal style will be used instead.

Not applicable
Posts: 1

WARNING: Style URAC not found; Normal style will be used instead.

When trying to set a style that is not one of the defaults in EG I get the above Warning and my style is automatically converted back to normal style.

The solution it says is as follows:1.Close SAS Enterprise Guide. Add code similar to the following to the AUTOEXEC.SAS file on the SAS server:
proc template;
define style MyStyle_1;

However when i add this information to the server file the code does not run at all.

Has anyone run into this error and have they found a solution as to successful add the above coding?
Community Manager
Posts: 3,462

Re: WARNING: Style URAC not found; Normal style will be used instead.

Posted in reply to Uracsaslw
You'll get the Style not Found message when you:
- Define a new custom CSS style using the EG Style Manager with a new name (such as "MyStyle"), and…
- You don't have a corresponding ODS STYLE on the server with the same name. You would have to define that using PROC TEMPLATE.

It's because EG generates ODS statements like:

ODS HTML STYLE=MyStyle STYLESHEET=(URL="path-to-styles\MyStyle.css")…

In this case, "STYLE=MyStyle" won't be found, because it doesn't exist as a style in any ODS template itemstore.

In 9.2, you can use PROC TEMPLATE to read in a CSS file and turn it into an ODS STYLE. However, there isn't a process in EG that makes that easy, so you would need to get the CSS file to the SAS session and then write the program yourself.

Placing that PROC TEMPLATE in the Autoexec might not be enough. You also need to make sure that the ODS PATH option is set to look in the appropriate place to resolve the styles. And sometimes SAS-server-based autoexec files don't initialize the session the way you would expect for EG use, so you might experiment with putting this code in the Tools->Options->SAS Programs->"Submit code on server connection" option.

Ask a Question
Discussion stats
  • 1 reply
  • 2 in conversation