ods html can't write image via sgplot, but can print proc report

[abak]

Hi,

I have a weird issue with ods html.

I have the basic sgplot code like so:

proc sgplot data=example;

 title "Example title here";

 series = time y=output;

 run;

I can use ods pdf and print out the results. BUT, when I try using

ods html body = "test.html";

proc sgplot data=example;

 title "Example title here";

 series = time y=output;

 run;

ods html close;

it results in the following error "cannot write image to . Please ensure that proper disk permissions are set".

Other things:

-I can write a html output with proc report only and it does just fine.

-I can write proc sgplot out with pdf and it does just fine.

-I tried ods html5 as well

-I am writing this on a linux server within a personal folder area and I tried using chmod +x foldername to change read/write permissions

-I need this in html output, not in pdf format.

[Cynthia_sas]

Hi:
Typically, when you use body= or file= without a path= option, you are telling ODS and SAS to try to write to the default working folder location on your operating system.

Which is lovely, if you have write access to that location. And with a local install of SAS, you frequently do have write access to that location. However, in some installations, your working folder is not write-able -- such as when you are using SAS University Edition or Enterprise Guide or when SAS is on a server.

My guess is that if you change the code to be more like this:
ods html path="c:\temp" body="test.html";
...your sgplot code...;
ods html close;

That you'll be able to fiddle around with a path= location until you find one where you have write access. Of course, instead of fiddling around in a server scenario, it might be faster to ask your SAS Admin where you can get or find or be allocated a folder with write access.

Cynthia

[ballardw]

---

@Cynthia_sas wrote:

Hi:
Typically, when you use body= or file= without a path= option, you are telling ODS and SAS to try to write to the default working folder location on your operating system.

Which is lovely, if you have write access to that location. And with a local install of SAS, you frequently do have write access to that location. However, in some installations, your working folder is not write-able -- such as when you are using SAS University Edition or Enterprise Guide or when SAS is on a server.

---

Or your IT staff lock down the entire Programs folder on your local install.