PROC TEMPLATE: Unable to write to template store

[JohnSAScom]

Hi,

We have 2 people each using their own workstation machine.  Eerily, the following works on one of person's workstation, but not on the other person's workstation:

 proc template;                                                        
     define style styles.notsominimal; 
          parent=styles.minimal;                                           
          style Table / cellpadding = 3;                                               
    end;                                                               
 run;         

For the person for which it does not work (on their own workstation), the resulting error is:

 NOTE: Writing HTML Body file: sashtml.htm
 ERROR: Template 'Styles.Notsominimal' was unable to write to template store!

For the other person for which it does work (on their own workstation), the notes are:

 NOTE: Overwriting existing template/link: Styles.Notsominimal
 NOTE: STYLE 'Styles.Notsominimal' has been saved to: SASUSER.TEMPLAT

The status of the SASUSER.TEMPLAT is UPDATE. 

What could be causing this to work on one person's workstation but not the other's?

John

[Cynthia_sas]

Hi, off hand, it sounds like one person might have write access to SASUSER and the other person doesn't. Is one person using Enterprise Guide or running code in a Virtual machine???

You could have the "non-working" person try this:
ods path work.testtemp(update) sasuser.templat(update) sashelp.tmplmst(read);

proc template;
define style styles.notsominimal /store=work.testtemp;
parent=styles.minimal;
style Table / cellpadding = 3;
end;
run;

ods html file='mytest.html' style=styles.notsominimal;
proc print data=sashelp.class;
run;
ods html close;

you can also do an ODS PATH SHOW; on both systems. Or, I suppose it might be possible that both folks are access the same server session of SAS and sharing a SASUSER library -- that seems unlikely though.

This might be a question for Tech Support if you can't work it out.

cynthia

[JohnSAScom]

Hi Cynthia,

The ODS PATH for the "non-working" person looks ok:

   Current ODS PATH list is:

   1. SASUSER.TEMPLAT(UPDATE)
   2. SASHELP.TMPLMST(READ)

I assume it's ok for the "working" person as well.  They both have SAS locally-installed on their workstations.  Could this have something to do with their user profiles? 

I'll try your suggestion...

Thank you,

John

[Tim_SAS]

Does the "non-working" user have the RSASUSER option in a config file? Is the "non-working" user's SASUSER directory write-protected?

[JohnSAScom]

Hi Tim,

Great questions!  I'll get the answers and get back to you...

Thank you,

John

[JohnSAScom]

Hi Tim and Cynthia,

Sorry for the long delay.  When I visited the user I asked them to try it again, and it worked without error. They could not explain why and neither could I. I checked RSASUSER in the config file and it looked ok.  I also checked to see if they were able to write to the directory that the SASUSER.TEMPLAT library is mapped to, and they are were. 

The fact that the issue "resolved itself" is not very satisfying from a technical standpoint, and I suspect it may arise again. 

I'll keep posting updates if the issue resurfaces.

Thank you,

John