Yes!  I've experienced this myself.  The only way I can prevent emails is by setting this property (environment variables) for the flow: LSB_JOB_REPORT_MAIL=N   Select the flow -> Properties -> Job Properties Create the environment variable. No more emails. ... View more

  I generally agree with both @Kurt_Bremser and @AnandVyas  For admin user, we're talking about an Platform admin as specified in the js.conf file, not a SAS admin in metadata. There is this concept of a Group Administrator in the Platform doc.  I've always wanted to try it and see if it addresses the issues posed in this thread.  Does anyone have experience with Group administrator in Platform? https://support.sas.com/rnd/scalability/platform/PSS11.1/pm10.2_admin.pdf   Process Manager Group administrator: Users that are specified as GROUP_ADMIN in LSF user groups in the lsb.users file when JS_ENABLE_GROUP_ADMIN=true in js.conf. Group administrators can view flow definitions, flows, and calendars owned by all users. Group administrators can control flows and jobs on behalf of users who are members of the same LSF user group.   ... View more

Hey @SASKiwi ,   This looks very familiar.  I've attached links to the two SAS notes that I use when setting up SQL Server connections.   https://support.sas.com/kb/42/605.html https://support.sas.com/kb/48/348.html As you can see from 42605: Important note: This type of authentication does not support supplying a user ID in the form of Domain\Userid from the connection in SAS. Authentication of the user ID is done through the use of Kerberos in the operating system. No user ID or password are required on the connection string in SAS.   That seems to be what we're seeing here with your situation.  Even though you have the AuthDomain defined correctly, the actual authentication is being done via Kerberos.  The user/password, or in this case, the AuthDomain, is not actually passed to the database.   I hope these notes help.  I refer to them often when setting up MS Sql Server connections.  We have some that use database id's and require AuthDomains, and some that use Kerberos.   Hope this is helpful.   ... View more

In response to your question about having the AD users schedule flows, you are correct that it can get messy and you have the potential of having the same flow scheduled by multiple users.  We use a service account or batch user, something named "marketing_batch" or similar.  When scheduling the flow, we use that user. That doesn't help with your problem, though.  I feel like you're really close as you've described your auth domains.  Of course, they are the key to doing what you want.   My only advice is to make sure your connection in the server object specifies the authentication domain that matches what you have in your metadata group.  From the description, it seems like there's a slight adjustment necessary somewhere. What you've described is entirely possible.   ... View more

We do daily SAS Backup and Recovery Utility backups. Operating system level backups (incremental)   BUT, before we do an upgrade, as others have suggested, I do a basic "cold, no SAS services" tarZ backup of SASHome and the Config directory.  The idea, that like others said, TSHTF, I can simply untar and resume from that point. YMMV ... View more

I like @Criptic ideas. But I also wonder if you're even making it far enough in the process that the Workspace server is being launched.  Have you checked the metadata log to see if the user is being properly authenticated? We have our logs in a central location: <LevN>/Logs/SASMeta_MetadataServer_2019_xxxx.log I'd check for valid or invalid client connections: 2019-05-07T09:35:00,139 INFO [20001221] 928359:<installer id> - Client connection 928359 for user <userid> closed. 2019-05-07T09:36:51,683 INFO [20001240] :<installer id> - Access denied. Then at least you will know if your user id is being authenticated properly to the metadata server (i.e. log in to DI Studio).  If so, then @Criptic may be correct that the workspace server is not being launched with the correct credentials.   Just a thought... Hope it points you in the right direction. ... View more

This is several months late, but just searched for ways to share code and this popped up. Repositories for sharing tasks and code snippets was available with Studio version 3.6, but I do not see it in my newer release.  Wondering if this feature is going to be supported moving forward.   For the record, I used a GIT repository to share snippets.   ... View more