Thanks Juan.   It's a non-distributed setup.   The users have valid e-mail attributes in their metadata identities. Two identities have been deleted and recreated...a retest is pending.   I'll to ask the UNIX admins to view /var/log/maillog to see if the operating system received the send mail requests. Our sister company has VA 7.3, and so I'll test report distribution to these e-mail addresses there. ... View more

We are getting a similar problem in VA 7.1, except that the report distribution process is working. Most users are receiving distributed reports (PDFs), while others in the same metadata group are not getting any report output, including me (an admin).   This seems to be related to accounts that are not being recognised, but there's no errors in the Designer log or in the HTML Link log. The job status also says completed successfully, but no e-mail ever arrives. E-mails sent from Linux with mailx, and with Base SAS on the same VA server, both work.   I will raise a track for this problem and review all hotfixes for VA 7.1. ... View more

A customer raised the same problem. I tried TEXTDECORATION = UNDERLINE, but did not work for ODS TEXT for whatever reason.   Only the following PROC ODSTEXT statement gave acceptable results in the PDF document. I also noted that PROC ODSTEXT does not inherit the UserText style elements that ODS TEXT uses.   proc odstext;    p "BUSINESS RULES" /        style=[font_size = 10pt                  foreground = black                  font_weight = bold                  borderbottomcolor = black                  borderbottomwidth = 0.1pt                  background = white]; run;   /* The next line also needed a top margin to apply line spacing */ ods text = "^S={font_size = 8pt font_style = italic margintopwidth = 8pt}Incidents Reported is based on head office received date."; ... View more

In more basic terms, is ODS OUTPUT via a LIBNAME reference a valid UNIX directory location for your ODS results files?   For example, if my customers forget to include FILE= or BODY= the ODS output files end up being written to the current UNIX directory that existed when $SASROOT/sas was executed.   Sometimes from EG this end up being config/Lev1/SASApp, which they don't have write access to, and therefore get an error. ... View more

This is the key bit: "Unexpected second use of a unique name." I'd check your data source thoroughly. This SAS Note mentions this error message: 54676 - "Unexpected second use of a unique name" error might appear when you open a SAS® Visual Analytics report ... View more

Silin, You or a programmer should be able to create a stored process that displays the VA expiration dates by looking at the PROC SETINIT log output. This would need to run against Base SAS on the VA server itself, for example via SASApp. Ideally, a scheduled report would alert you (via e-mail) to a looming VA expiration date. ... View more

Thanks very much, Kurt. Much appreciated. ... View more

If overruns could be blocked for standard users and yet allow critical system users (schedulers etc) to keep running, that sounds like an excellent capability to have. I'll look into quotas for our servers. ... View more

"Nope. Actually the system admin tools are THE way to go here." Sorry...what I meant was to have both in place, the standard UNIX system monitoring, and your own monitoring. At some sites, a generic UNIX server disk space alert can be received by techos who know nothing of the context and seriousness of the alert. And the threshold tends to be set high, e.g. 90% or more. For SAS WORK, you want to get early notification of WORK space usage creeping up, not wait until it's too late, and/or get SPAMed with system generated alerts and new incident tickets every 5 mins. If standard UNIX resource monitoring can run with a variety of rules, thresholds, notification recipients, etc, then all good....just use that. ... View more

We have 400GB allocated for about 20 active SAS developers, and several hundred ad hoc report requests during the day. UTILLOC is also in a separate folder. But what can happen is one step in one program can run a bad cartesian join against a database table. When SAS attempts to bring all of that down to WORK, the disk could fill up. And so what's essential is a smart disk space monitoring script or utility that sends alerts. Don't rely on the UNIX admin's tools. The shell script I wrote sends us e-mails when the WORK space usage goes past a threshold, e.g. 70%, and then sends a new e-mail if the usage % has increased since the last check 15 mins ago. I also get an alert on my phone via the e-mail app. The world record size for a WORK dataset we had was approx 140GB before I contacted the developer. I've also scheduled the SAS WORK clean-up utility to run every hour via CRON, but this was when we had less disk space. ... View more

Thanks Michelle. My search included "2G" and therefore I missed that SAS Note. ... View more

It depends on your server and application configuration. But being a Windows box, my guess is that SAS authenticates to Active Directory. ... View more