My bad, I always thought VBA is owned by SAS Institute.  And oh, I never knew files generated from ExcepXP are in native Excel format and neither did I know that MSOffice2K supports all the formatting options that ExcelXP does.  And this is also new to me that libname Excel and PROC EXPORT do support all the formatting options that ExcelXP does!!   Password protection on Excel files was a joke with Microsoft Excel versions prior to 2007.  Note this, that Microsoft has been using AES-128 bit encryption with Excel 2007 and later so it not a joke anymore.  Now, that could just be one layer in securing your email report distribution in combination with 2) encrypting an entire email message at your corporate Exchange server and 3) using Transport Layer Security or TLS for transmission and this would not be a joke of slightest nature. ... View more

VBScript method might work it one has to password protect the files manually.  This is not a fool-proof method for a batch execution where you have dozens of file to passowrd protect and distribute.  What if the VBScript does not at all run?  You will end-up distributing unprotected file.  SAS does not provide any guarantee.  Please read the fineprint.   I believe this is time when SAS should cease its reliance on these VBScripts and come up with native mehtods.  Examples are 1) Generating rich Excel reports, 2) Converting XLS (OpenXML document) to native XLS or XLSX file format, 3) Password protection of Excel files as metioned in this topic. ... View more

  Hello Anja/others,   Yes, this documentation exists but the problem is, this backup will not be useful from my perspective if you are unable to bring your SAS Servers up and running due to corrupt config or any other bad installation and configuration related reasons.  You need to have a healthy SAS environment to recover something from the backup mentioned in this SAS documentation.   This backup might be more useful when a developer or user deletes some metadata object (table, report etc) by mistake.   But there has to be a plan to take the backup at the OS or file system level as other also mentioned in this thread.  I was going to post a new thread but found this one relevant and here is my post.   All - Please advise.   =============================================================================================== Hello SAS Administrators,   If you are a SAS Administrator on Windows Server operating system, I am pretty sure you would have encountered the 200 characters Windows directory path limit problem while taking the backup of SASHome or SASConfig directories (mostly the SASConfig directory on the middle/web tier machine that has light-year-lengthy directory paths that stubbornly deny to get copied) whenever you intended to update, upgrade, hotfix your SAS environment.   Another problem you might have encountered is the symbolic links in SASHome directory, if you copy and paste them, they become an actual Windows directory with the same name.  You have to use maklink.exe to recreate the symbolic links.   So, if you intend to take the backup of SASHome and SASConfig directories by copying and pasting them to some location, this does not work.   My organization uses Tivoli Storage Manager to take "incremental" backup of the servers, but let me tell you this did not help me when I had to recover SASHome and SASConfig from this backup once.   I might have taken the “clone” of *.vmdk or *.vhd file if I had a Virtualized SAS Environment, but fortunately/unfortunately I have been dealing with physical machines.   So, my question to you all is, do we have any better backup strategy for the backup of overall SAS installation that is sitting on a physical server/machine? Or migrating to a virtualized environment is the only way to go?   Thanks and regards, Jitendra Pandey ... View more

I received this error today.  My environment had SAS VA 6.3 with SAS 9.4_M1 and I updated/upgraded to SAS VA 7.2 wit SAS 9.4_M2 last month.  My environment had Lev1, Lev2 and Lev3.  I had to reconfigure my Lev2 due to some problems and I used the original plan file that was used for VA 6.3 installation. ... View more

*figured ... View more

Has anyone figure out the cause of this problem and the solution? Thanks and regards, Jitendra Pandey ... View more

Thanks Catherine!!  Sure, I got that.  Our organization is still testing IE11 before it is rolled out to the users.  But as of now, I am good with Google Chrome. Thanks and regards, Jitendra Pandey ... View more

I was having similar problem today when I updated from VA 6.3 to 7.2.  I opened VA Hub in Internet Explorer Version 9 (9.0.8112) and it would not load.  IE always said "Loading" with some circles beneath the text, everything in relatively light blue (as compared to VA 6.3) background. It's weekend so I cannot reach SAS Technical Support.  Tried to search about the problem on internet but did not find anything relevant other than this thread. Then it just clicked me and I opened SAS VA Hub in Google Chrome and it loaded the newer version of VA Hub successfully (after displaying some cool loading graphics, which were static in IE9). @Rahul - Request you to post what your problem was and what resolved it. @Justin - SAS has provided very limited resources to troubleshoot any problem with the VA suite as an admin.  It would have been helpful it SAS support site had more tips and error message documentation to troubleshoot the problems.  SAS Tech Support does help but it takes a while and exchange of emails and files (config and log files) before the problem is understood and resolved.  Where as so many small problems can be resolved by the admins themselves if we have a good documentation of error messages. Thanks and regards, Jitendra Pandey ... View more

It looks like the value of VA.AutoLoad.Enabled extended attribute of Visual Analytics Public LASR Library is set to "No". Please log-on to SAS Management Console > Data Library Manager > Libraries > Visual Analytics Public LASR Library > Properties > Extended Attribute > VA.AutoLoad.Enabled Manually change the value of VA.AutoLoad.Enabled to "Yes". ... View more