Hi @MariaD ,   there is certainly one or more differences between your UAT and your Production servers. Hard to identify from here. Starting from the basics: is Production under Linux and UAT in Solaris? What versions/distribution?   I am not sure if we can help a lot from here. Perhaps you could start with a proc contents data=_A._all_; on both servers.   I still think you need someone to look at your server and logs. For this action. the communities is not the best media, SAS Technical Support or SAS Professional Services, or a SAS Partner, are better equipped for this, specially from a compliance point of view.       ... View more

Hello @MariaD ,   should I understand this is related to your environment that is moved from Linux to Solaris, with SAS 9.4 M6? https://communities.sas.com/t5/Administration-and-Deployment/SAS-Slow-Performance/m-p/687604 These details usually matter.   This being said, I would check the encoding and language settings of the OS and the SAS session on both environments that you are comparing.   The message UNIX errno = 0 is not a good signal. It means that your underlying OS did not manage to recognize the exact nature of the error. I would try to get support from your system admins (to check the system logs) and perhaps from SAS.   In any case, at folder and file level, and as best practice, I would not deviate from UNIX standards, avoiding those characters.     ... View more

OK let us keep it simple.   a) remove metadata from the equation: Does the library works OK when you define it via code in SAS EG, DI, Studio or Foundation?   b) When above works, it means your authentication domain is incorrectly set up. Look at the database server connection definition where the Auth Domain is, look at the Usergroup where the auth domain is set up and ensure the user and password is correct, and check again the library and the authentication method. Please, do not use the DefaultAuth authentication domain.   c) When step #a does not work, you should work with your DBA. Before that, perhaps you could debug a little bit the connection, with the SASTRACE option https://documentation.sas.com/?docsetId=acreldb&docsetTarget=n0732u1mr57ycrn1urf24gzo38sc.htm&docsetVersion=9.4&locale=en   ... View more

Hello @Madhan_cog1 ,   is your issue still open? I see that it is running for actually quite a while.   Just in case it is still open, I will keep it real simple:   - I advise your organization security/certificate experts to generate the certificate for you, for an Apache server. - Just in case you still need to do it, a FAQ that should resolve all your questions. When in doubt, google the errors: https://httpd.apache.org/docs/2.4/ssl/ssl_faq.html   - In any case, what has to be known is:   a) SAS needs all the certificates in the path, in PEM base64 format, and the private key, in same format, and created for the alias you will use in the SDW deployment of your SAS web server.   b) you will need to provide it in the SDM and/or SDW: all the servers needs to have it, and every client with a Java SAS client (eg SAS Management Console) will need to import it with SDM. ... View more

Hello @helannivas88 ,   by any chance is your user having the Metadata unrestricted role, either directly or indirectly by any group? You shouldn't. ... View more

Hi @FCB2020 ,   I would give a look into the following documentation:   https://support.sas.com/en/documentation/install-center/94/guide-for-unix.html   ... View more

  @Ololade , for your issue I would like to suggest you to  open a different thread in the communities. An issue on Metadata server installation looks very likely it is not the same issue than an already running Object Spawner.   I hope it helps. Best regards, Juan ... View more

Hello @Madhan_cog1 ,   Mainly you will need to follow this document (and links in it), to switch the SAS Web server to HTTPS https://documentation.sas.com/?docsetId=bimtag&docsetTarget=n0nakjyj6hlqmvn11p9p04l25j9n.htm&docsetVersion=9.4&locale=en   Do you need to change the SAS Web Application Server(s) to HTTPS? In that case you would need to follow these steps as well: https://documentation.sas.com/?docsetId=bimtag&docsetTarget=n1enfdk7f1fjcqn1ggbrx79lm9i0.htm&docsetVersion=9.4&locale=en   Normally with the first document is enough, given that is the only requirement from your Security Office. Best regards. Juan ... View more

@gboggs let us know how it goes and the approach you took in the end 🙂 Curious about it ... View more

Hello @Sanket ,   it should be in the SAS RTDM 6.6 documentation https://documentation.sas.com/?activeCdc=rdmcdc&cdcId=cicdc&cdcVersion=6.6&docsetId=rdmug&docsetTarget=titlepage.htm&locale=en   I would expect to find the documentation in the Administration Guide, you will need the access key. If you have the license for it, SAS Technical Support should be able to provide it to you, if you don't have it yet.   If it is an upgrade in place, it should not be very different from other upgrades in place, considering the particularities, of course, for 6.5 to 6.6.   Best regards, Juan ... View more

Hello @StuartRogers ,   thank you, your explanation helps a great deal. I would add kudos to your reply if I could.   I appreciate very much your effort on getting this information through, as I am sure many others can appreciate it as well.   Would you (or someone else) be able to provide any update when a documentation update happens on this topic? Thank you, Best, Juan ... View more