Hi,   maybe i misunderstand your question, but from where are you trying to access your local data? Are you trying to submit this from a SAS client on your desktop or are you running SAS on the server??   Thanks Anja ... View more

Hi,   one way would be: ./sas-set-metadata-access -host localhost -port 8561 -user sasadm@saspw -password "BLA" "/System/Servers/test (ApplicationServer)" -addACT "Hide Server ACT" (ACT name) ... View more

Hi,   would you mind sharing what you used to get the info you needed?   Thanks bunches! Anja ... View more

Hi Naga,   what user ID are you using for running the migration? Are you using sasadm@saspw, or any other unrestricted user? One of the errors you are receiving is a 403, which is typically an indication for permission problems.   i understand you are getting this error during the SAS Content Server migration? Or are you referring to the Content Manager Server in DataFlux??   If Content Server, could you please go to SAS Management Console, Server Manager, and VALIDATE the Content Server? (right mouse click on Content Server, VALIDATE). In case it would come back with an error message, what error are you getting?   Thanks Anja     ... View more

Do you get this error when logging on, or, when users submit jobs? Does that happen for every user?   Could you provide a screenshot of this error message? Also, did you check the Metadata Server log and Object Spawner log? There is most likely more info that'll help to troubleshoot.   Did you run into these problems before using the ALTLOG option, meaning, did this ever work before?   Also, are you on 9.4, and, would Environment Manager be an option? It would nicely provide what you are looking for.     ... View more

Hi,   I am almost certain that the freeze is caused by the ALTLOG option that's being enabled for your environment. Do you have the Workspace Server log enabled? Especially the Workspace Server might cause problems as it writes a single log for each user. Given that, plus an option to "copy" a dup of logs somewhere, might be too much for the resources you have, the resources SAS uses.   Going in the opposite direction, if the ALTLOG is set up for the SAS Servers, yet the Workspace Server log is not enabled, it might run indefinitely, trying to find the Workspace Server log. Other log files are enabled per default, which is why I am highlighting the WS log.   As mentioned in a post earlier, one way to go would be using the Environment Manager:   What is Environment Manager: http://support.sas.com/documentation/cdl/en/evug/69029/HTML/default/viewer.htm#n1vpa7fca7lm6xn1193gvpd1m8h0.htm   Using the Report Center: http://support.sas.com/documentation/cdl/en/evug/69029/HTML/default/viewer.htm#n0icicjjqba5khn17he8it7wkozs.htm Take a look at the reporting, one of the features provided by Environment Manager, to see which objects, items and resources you can report on, and monitor. It is a great tool!   There is an Ask the Expert recording and upcoming sessions for Environment Manager, see http://support.sas.com/training/askexpert.html, under Administration.   Aside from Env Manager, here is a blog that talks about logging events http://blogs.sas.com/content/sgf/2015/09/30/part-1-auditing-data-access-who-did-what-and-when/   Hope this helps. Thanks Anja             ... View more

Hi,   At this point, I really think that you should work with SAS Tech Sup. They'll provide you with excellent guidance and am sure have it solved in no time.   Somewhere, a parameter is not set correctly, which causes the error. It doesnt even have to be SAS but a problem with the UNIX side of things?   Best Anja ... View more

I am not sure this is possible, at least from a SAS stand point. When you click the X to exit any sas session, it doesn't let you go back in any way. ... View more

Hi,   It looks like there is none for 9.2. The best option to verify this is by contacting SAS Tech Support. They'll be able to help you with this.   Please know that SAS 9.2 is B-Level support. See https://support.sas.com/techsup/support.html#general for details.   Thanks Anja ... View more

That's what I would go with: MetaCoda. For things like that, these plug-ins are extremely helpful. I "played" around with it a lot and it is a great complementing option for what SAS security already offers. ... View more

A few things to check:   - Do you/ the users, have write permissions on the ODBC.INI file? - Do you use mixed passwords, and, are you using quotes around the password? In the log you sent, it looks like the password is passed "through" without quotes around. Please try and change to "password" .. .does that work? - Does that error occur for all users, or only for you? If that's the case, and you are working in "admin mode"/"install mode", make sure you are logging on with a user ID that is not SAS Installer id. - Are there any changes needed on the env variables that might have not been made?   Hope that helps. Your best bet for a quick fix would be to contact Tech Support   Thanks Anja   ... View more