TS Note 17681 provides a solution to the situation where you define a style and make it available to your E.G. session through Tools / Style Manager. I went through the process of creating a custom style, and redefined the style using a UNC so that any project calling on the style would not need to have the same drive mappings as my PC. When running on the LOCAL server, my client found and used the style, but when I redefined the project to the remote server, I got these messages in the log:
WARNING: Style MYTEAMDEFAULT not found; Default style will be used instead.
This happens because EG generates and ODS statement like the following:
ODS HTML ... STYLE=MYSTYLE STYLESHEET=(URL="path-to-MYSTYLE.css")...
The STYLE= value results in the warning if there is no ODS style template that matches that name. For the built-in styles (ANALYSIS, MEADOW, and so on), there are matching ODS templates. But when you define your own style sheet and give it a meaningful name, it probably won't match an installed template.
The warning is an annoyance, but not necessarily a problem since the output appearance will be controlled mostly by your custom style anyway. If you want to avoid the warning, you can create an ODS style template with PROC TEMPLATE (examples on the Base SAS focus area on the support site).
AND, good news, starting in 9.2, you will be able to turn a custom CSS file into an ODS style template by using the new IMPORT statement to create a STYLE template that could be used with HTML, RTF AND PDF -- as well as using the CSS file for EG and/or HTML.