Hi,   do you still have a SAS install on your machine right now?   If so, what you could try is uninstalling the existing one, and then try and install from the media/depot you have. Please make sure you back up your environment before going that route!!!   Are you installing from media or from a software depot? Something must have gone wrong with your SAS files when the environment was upgraded from 32-bit to 64-bit.   What version of SAS are you running? Are you trying to do a SAS version upgrade at the same time?   What are the exact steps you go when trying to install?   Check with your administrator if you have permissions to install.   These are a lot of questions, but hopefully the answers will bring us a bit closer to what is going on   Thanks Anja ... View more

Hi,   One of the things you mentioned is "the ad user are translated to a shared use", and "I prefer that the users sign manual up every time they use an authdomain", and "access to raw data".   First question: How are your users currently reading these raw data into SAS/access the raw data? Via BASE SAS, EGuide, DI? One the raw data is imported and data sets are created, are the data sets stored in metadata libraries? Since you mentioned SASMC, I assume that all your users are registered in Metadata, and that your libraries are created in metadata and tables are registered, folders have been created?    If this is the case, your users generally authenticate through the DefaultAuth, whether the authentication behind the scenes is AD or any other direct or indirect authentication.   The DefaultAuth defaults to the Metadata Server and the SAS servers it is using, such as Workspace Server.   If you have databases, such as Oracle, you can create additional Auth Domains in SASMC, such as OraAuth, using the DBMS userID and pwd for each DBMS connection. Example: For each user ID, you'd either have to add an additional authentication domain, such as OraAuth, using their Oracle user ID. This would authenticate each individual user. Whether they are prompted or not depends on whether passwords are stored in Metadata or not.   Alternatively, if you would not want to authenticate the users individually, you'd use the shared accounts you mentioned in your original post, and create a shared user in SASMC. This user would use the DBMS' user ID. The individual users would then have to be added to that shared user ID (as members). In this scenario, only the shared account would be authenticated, not the individual user.   If you create/work with metadata, as described above, you'd have more control over the "who, where and when". Auditing, logging would provide you with more details on what your users are doing.   "Directing"/setting up authentication might be easier as you'd have more control.   Examples for authentication mechanism   PAM http://support.sas.com/documentation/cdl/en/bisecag/67045/HTML/default/viewer.htm#n0bggv0uyqm3m0n1ngn9g94i70nz.htm   LDAP http://support.sas.com/documentation/cdl/en/bisecag/67045/HTML/default/viewer.htm#p1k1qcvnbfsy0en1lzbiztlgt264.htm   http://support.sas.com/documentation/cdl/en/bisecag/67045/HTML/default/viewer.htm#p0fpi70ptqcdldn1sovre4lpvzmv.htm     Thanks Anja ... View more

Hi   take a look at the following SAS Note: http://support.sas.com/kb/57/406.html     Thanks Anja ... View more