Hi, it is documented here: http://support.sas.com/documentation/cdl/en/bimtag/68217/HTML/default/n0nakjyj6hlqmvn11p9p04l25j9n.htm   Just skip the parts of HTTPS and secured.   Wouldn't you prefer to re-deploy? ... View more

Sorry, but it is a bit hard to know what is about without further details. Could you give a look to the log that is in the link, at least?     ... View more

Hi,   I believe you might be interested on the Audit reports for SAS Visual Analytics entry created by AnnaBrown/ https://communities.sas.com/t5/SAS-Communities-Library/Getting-started-with-SAS-Visual-Analytics-7-1-Audit-Reports-for/ta-p/223514   And you could give a look also to: https://www.youtube.com/watch?v=KRKNzobd0AI http://www.slideshare.net/FrancescoMarelli/keinavo-sas-forum-milano-2015 ... View more

Hi Jim,   I believe that what you need is the logconfig.xml file that is under each ObjectSpawner and SAS servers as the SAS Workspace Server.   Please find the official documentation here: http://support.sas.com/documentation/cdl/en/bisag/68240/HTML/default/viewer.htm#n1365xislvhmbun1cc1gmrqo53tu.htm   But in short: - those xml have a line as :   <param name="FileNamePattern" value="E:\SASLogs\Lev3\ObjectSpawner_%d_%S{hostname}_%S{pid}.log"/> and other lines where you can change any configuration of the log.   - For the  SAS servers under SASApp  - to take the configuration effect, you need to ensure that your sasv9.cfg or your sasv9_usermods.cfg (if you need to make a change, better on the usermods, otherwise your change will be lost on your next platform update or migration) has a line as: -logconfigloc "E:\SAS\Config\Lev3\SASAppFF\WorkspaceServer\logconfig.xml"   Then, when you make the change, if you restart the Object spawner (or refresh the SASApp from the SAS Management Console, which has a minumum impact on your user sessions), the changes will take effect. ... View more

Hi,   is your deployment working with SSL/HTTPS?   Could you read and followed the Post-Configuration Steps on your Instructions.html after your configuration?   I mention this, because to me it looks very much as: -  there is no communication between the SAS Environment Agents with the SAS Env. Manager Server through sasevs@saspw (which is normally solved through following those steps in Instructions.html) - the validate.sh – level 2 it sounds to me a lot as part of the quick start guide named : SAS_Environment_Manager_Service_Architecture_Quickstart.pdf. Is this the case?   If you are following the document SAS_Environment_Manager_Service_Architecture_Quickstart.pdf, this is for setting up the EMI framework, which is is a log collection and reporting area of the SAS Environment Manager, but it is not the SAS Environment Manager (the monitoring tool) itself.   I hope that this can help to clarify a bit. Let us if you have more questions and how it goes. ... View more

Hi,   to me this looks like your metadata or SASApp cannot find the process manager and/or your login/Authentication Domain. My initial guess would be that you might not be in the group for Scheduling.... but let's review the steps.   What I would check, just with this information is, starting from the basics:   - First:       + Check you have installed LSF and Process Manager (with hotfixes if required) and you tested it, as is:       LSF_Shared is accessible, your LIM, RES, SBD, and Platform Process Manager services are started and running fine, you can log in to LSF, run commands, send a process to be executed, you can log in Flow Manager, etc.   - Second:      + You have the configuration on the SMC: your Platform Process Manager is configured under Server Manager:       It should have the correct version, the connection should have an Authentication domain (eg LSFAuth), the hostname of your compute server where LSF is installed, and the port number.       Note: very important that, if you have more than one compute or SASApp, the Platform Process Manager should be registered under the server/Object Spawner of your SASApp for MA(!!)     + Then, you should hace an Scheduling group where you and all the users with scheduling permissions (and OS account) are included.      This group should have an account registered, your lsfuser or lsfadmin account. And this account should have the Authentication domain as specified above (eg LSFAuth)   - Third:     + Restart your Object Spawners and your SAS Middle tier.      + At this stage, if everything above is correct, you should be able to test if you can schedule with the Schedule manager or with DI, into the Process Manager. If this works, you can test also with MA, it should work too.   Let us know how it goes! 🙂 If you still get problems with this configuration, maybe the logs of your MA/Customer Intelligence web application can help to identify the issue. ... View more

Hi,   is this happening to you on the Viewer? That is my current understanding, from your screenshot.   Maybe you can give a look and search for errors in your log file (or ask your SAS Administrators to search for it) for the SASVisualAnalyticsViewer.   Without some additional information it is a bit hard to find the root cause of your problem.   In the meantime, besides search for the log, I would recommend to: - Try with a different Web browser - Change from the modern(HTML5) to the classic (Flash) theme or the other way around. - Read the log (or share with us the log, we can help) - Open a track with SAS Technical Support if none of the above help you. - ... View more

- Sas Enterprise Guide: http://support.sas.com/documentation/installcenter/en/ikeguidesr/63984/PDF/default/sreq.pdf - Sas Base: http://support.sas.com/documentation/installcenter/en/ikfdtnwx6sr/66390/PDF/default/sreq.pdf - Sas Data Integration Studio: http://support.sas.com/documentation/installcenter/en/iketlsrvofrsr/67833/HTML/default/index.html - Sas OpRiskVar: http://support.sas.com/documentation/installcenter/en/ikorvarofrsr/67712/HTML/default/index.html ... View more

http://support.sas.com/resources/sysreq/   And this one? somehow after "sysreq\" there should not be "index.htm" ... View more

Hi,   which Operating system and platform (32bit or 64bit) are we speaking about?   http://support.sas.com/resources/sysreq/index.html    Last version of the products you can find it on the overview of the product, e.g, for SAS EG: http://support.sas.com/software/products/guide/index.html  ... View more

Hi,   Well, my feeling is still that there is something strange in your network settings, or your VM is corrupted, as proposed on a different post.   Would be an option for you to download again SAS University Edition and follow all the steps from step 0? ... View more

Hi,   I think there is no other quick workaround in your case, because WRS reports, or srx files are stored in your metadata and the content server (as XML files). If you try something else, you would corrupt your reports, metadata and content server.  Something really not desirable. Sorry, at least that is my experience and current knowledge. ... View more