<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: proc template error message in ODS and Base Reporting</title>
    <link>https://communities.sas.com/t5/ODS-and-Base-Reporting/proc-template-error-message/m-p/39920#M5511</link>
    <description>Thanks for your response.&lt;BR /&gt;
&lt;BR /&gt;
The ODS PATH statement did not change.  SASUSER is the first library on the ODS PATH list, followed by SASHELP.  There have been no file protection changes.</description>
    <pubDate>Tue, 19 Aug 2008 20:38:58 GMT</pubDate>
    <dc:creator>polingjw</dc:creator>
    <dc:date>2008-08-19T20:38:58Z</dc:date>
    <item>
      <title>proc template error message</title>
      <link>https://communities.sas.com/t5/ODS-and-Base-Reporting/proc-template-error-message/m-p/39918#M5509</link>
      <description>I've been getting the following error message anytime I use the template procedure: &lt;BR /&gt;
&lt;BR /&gt;
Error: Template 'Styles.Custom' was unable to write to the template store!&lt;BR /&gt;
&lt;BR /&gt;
Prior to a month ago, I had never seen this error message.  Now I get the error every time I use the template procedure.  Can anyone tell me what might be the cause?  I suspect that this error might be hardware related.</description>
      <pubDate>Mon, 18 Aug 2008 19:35:28 GMT</pubDate>
      <guid>https://communities.sas.com/t5/ODS-and-Base-Reporting/proc-template-error-message/m-p/39918#M5509</guid>
      <dc:creator>polingjw</dc:creator>
      <dc:date>2008-08-18T19:35:28Z</dc:date>
    </item>
    <item>
      <title>Re: proc template error message</title>
      <link>https://communities.sas.com/t5/ODS-and-Base-Reporting/proc-template-error-message/m-p/39919#M5510</link>
      <description>Did your ODS PATH statement change, or did the file protection on the default write library change?&lt;BR /&gt;
&lt;BR /&gt;
Perhaps you are trying to write to SASHELP or some other location you can't by default write to.</description>
      <pubDate>Mon, 18 Aug 2008 21:24:50 GMT</pubDate>
      <guid>https://communities.sas.com/t5/ODS-and-Base-Reporting/proc-template-error-message/m-p/39919#M5510</guid>
      <dc:creator>JackHamilton</dc:creator>
      <dc:date>2008-08-18T21:24:50Z</dc:date>
    </item>
    <item>
      <title>Re: proc template error message</title>
      <link>https://communities.sas.com/t5/ODS-and-Base-Reporting/proc-template-error-message/m-p/39920#M5511</link>
      <description>Thanks for your response.&lt;BR /&gt;
&lt;BR /&gt;
The ODS PATH statement did not change.  SASUSER is the first library on the ODS PATH list, followed by SASHELP.  There have been no file protection changes.</description>
      <pubDate>Tue, 19 Aug 2008 20:38:58 GMT</pubDate>
      <guid>https://communities.sas.com/t5/ODS-and-Base-Reporting/proc-template-error-message/m-p/39920#M5511</guid>
      <dc:creator>polingjw</dc:creator>
      <dc:date>2008-08-19T20:38:58Z</dc:date>
    </item>
    <item>
      <title>Re: proc template error message</title>
      <link>https://communities.sas.com/t5/ODS-and-Base-Reporting/proc-template-error-message/m-p/39921#M5512</link>
      <description>Hi,&lt;BR /&gt;
Are you by any chance sharing SASUSER with another id or with another job you have setup? Could any other process or user hold SASUSER open? This note talks about how you can get sharing violation errors:&lt;BR /&gt;
&lt;A href="http://support.sas.com/kb/4/739.html" target="_blank"&gt;http://support.sas.com/kb/4/739.html&lt;/A&gt; &lt;BR /&gt;
&lt;BR /&gt;
Or, is there any chance that your template code is trying to parent from itself?&lt;BR /&gt;
&lt;A href="http://support.sas.com/kb/10/651.html" target="_blank"&gt;http://support.sas.com/kb/10/651.html&lt;/A&gt;&lt;BR /&gt;
&lt;BR /&gt;
Are you running SAS/IntrNet???&lt;BR /&gt;
&lt;A href="http://support.sas.com/kb/11/745.html" target="_blank"&gt;http://support.sas.com/kb/11/745.html&lt;/A&gt;&lt;BR /&gt;
 &lt;BR /&gt;
The bottom line, I think, might be to open a track with Tech Support so they can help you get to the solution for the problem.&lt;BR /&gt;
 &lt;BR /&gt;
cynthia</description>
      <pubDate>Tue, 19 Aug 2008 21:18:06 GMT</pubDate>
      <guid>https://communities.sas.com/t5/ODS-and-Base-Reporting/proc-template-error-message/m-p/39921#M5512</guid>
      <dc:creator>Cynthia_sas</dc:creator>
      <dc:date>2008-08-19T21:18:06Z</dc:date>
    </item>
    <item>
      <title>Re: proc template error message</title>
      <link>https://communities.sas.com/t5/ODS-and-Base-Reporting/proc-template-error-message/m-p/39922#M5513</link>
      <description>Yes.  Another user recently installed SAS on their computer.  Because we share many of the same programs, her config file was changed so that her SASUSER library was in the same physical location as mine.  I never thought that their SAS installation could cause error messages on my machine.&lt;BR /&gt;
&lt;BR /&gt;
Thanks!</description>
      <pubDate>Wed, 20 Aug 2008 16:16:14 GMT</pubDate>
      <guid>https://communities.sas.com/t5/ODS-and-Base-Reporting/proc-template-error-message/m-p/39922#M5513</guid>
      <dc:creator>polingjw</dc:creator>
      <dc:date>2008-08-20T16:16:14Z</dc:date>
    </item>
  </channel>
</rss>

