Sounds like you may have an authentication issue to the ArcGis Server.  Check out the instructions for ArcGis authentication here...   http://support.sas.com/documentation/cdl/en/biwaag/68048/HTML/default/viewer.htm#n0anhaozpvuwi1n1gmkfihqfg16m.htm   If you continue to have issues after ensuring you've followed the above doc, a call to Tech Support is likely in order. ... View more

There's a description of how to check out memory usage of the LASR server and loaded tables in the Monitoring Server Memory Use and Monitoring Table Memory Use sections of the SAS LASR Analytic Server Reference Guide at http://support.sas.com/documentation/cdl/en/inmsref/68736/HTML/default/viewer.htm#p050lknh5xepngn1s2kaa5nijrer.htm   ... View more

From a Metadata Server perspective, the primary node is known as the "master," and it can change in the case of failover.  You can determine the master node by following the instructions under Monitoring Clustered Metadata Servers at http://support.sas.com/documentation/cdl/en/bisag/68240/HTML/default/viewer.htm#n1qmrerr6rvigxn132cnapd3r2c1.htm.   From a Middle Tier perspective, if you've forgotten which machine is your primary node, there are certain Web apps which are not clusterable, and therefore only live on the primary node.  You can find the list of such apps in the Exceptions to the Middle-Tier Cluster Support section of http://support.sas.com/documentation/cdl/en/whatsdiff/66129/HTML/default/viewer.htm#n1roydrale7528n14alj43gi257f.htm.   From a SAS Application Server (compute tier) perspective (I'm assuming you're not talking about SAS Grid Manager), there's not really a primary node.  You just have peer machines which host multiple servers (workspace, stored process, pooled workspace, etc.).   ... View more

In many cases, the absence of tables or data in the set of Environment Manager data sets is due to there not being corresponding activity.   ARTIFACT.AUDITACCESSCONTROLDETAIL tracks activity related to modifying access control information in metadata.  If no such activity has occurred, it wouldn't be surprising for this data set to be missing.  Similarly, AUDIT.AUDITIM is intended to capture Information Map activity (or at least it was in earlier versions).   Did you receive any errors when you attempted to run emi_init or master_apm_etl scripts?   If you *did* receive errors, or you continue to have an empty ARTIFACT.AUDITACCESSCONTROLDETAIL data set after access control info is modified in your environment (and the subsequent EV APM job is run by hand or automatically overnight), it would be good to give Tech Support a call to investigate further. ... View more

I think you're going to have to get Tech Support involved.  The symptoms appear to be fairly specific with the Object Spawner apparently having difficulty communicating with the SHARE Server.  On the bright side, Tech Support is pretty good at diagnosing reproducible behavior. ... View more

There have been a number of SAS users who have had success installing various products within AWS.  There was some content released at SGF last year related to this topic.  For example, a white paper on hosting a SAS Grid Manager deployment in AWS can be found at https://support.sas.com/rnd/scalability/grid/SGMonAWS.pdf.  A high level Tech Talk on deploying SAS in AWS can be found at https://www.youtube.com/watch?v=XHaLA7JSQyU.  There are certainly security topics you should consider when deploying to AWS, specifically those governed by security groups and access keys.  It should also be noted that going to the cloud obviously doesn't absolve you of all administrative tasks.  Yes, it outsources your hardware and provides very quick ways to spin up machines running Windows and Linux.  But you're still on the hook to manage and secure your software running in it.   I would be interested in hearing the experiences of others who have migrated SAS deployments to AWS or other cloud IaaS providers.       ... View more

Starting with 9.4M3, SAS ships an open source trusted Certificate Authority (CA) bundle and allows users to add site-signed or third-party signed certificates to it.  All applications with the exception of Java Web Start (JWS) applications use this trusted CA bundle.  This is done by default by the SAS Deployment Wizard, or as a post-deployment step via the SAS Deployment Manager.  JWS applications leverage user-supplied JREs, and SAS does not automate certificate management for them.  Users can copy the aforementioned certificate bundle (trustedcerts.jks) from a SAS machine which hosts one of the aforementioned applications into their JRE's lib/security directory with the name of jssecacerts, and the JWS applications will use it.   For more information on certificate management, you can consult the "Setting up Cetificates for SAS Deployment" in the SAS 9.4 Intelligence Platform: Installation and Configuration Guide. ... View more

Microsoft introduced better date/time data types in this version of their Microsoft SQL Server Native Client OLE DB Provider.  That's why SAS is able to properly input them as SAS dates.  You can find more information about the additional data types on Microsoft's site here.  This provider is one of the ones shipped with SQL Server 2008 R2, and is described here.  You can view its capabilities, as well as those of previous and subsequent versions from this site. ... View more