11-24-2015 06:45 AM
I was trying to connect local client to SAS remote server. But it was always failed.
I can connect the server through SAS EG. The connection confidential is connect. But when I use these confidentials to connect through SAS Foundation. It failed.
In order to connect the server, I run code as blow:
options metaserver="pdccjd010" metaport=8561 metauser="myusername in EG" metapass="mypassword in EG"; signon serverv="SASApp";
It returned the information of the server, like
Server= SASApp - Connect Server Remote Session ID = local ServerComponent ID = ******** Remote Host = pdccjd013.site ........... Notify = No
Then when I executed
signon server="SASApp" or signon server="SASApp - Connect Server"
It returned the error message:
ERROR: No logins found. Retrieving login information based on AuthenticationDomain from the SAS Metadata Server failed. Unable to retrieve the SAS/CONNECT server definition "SASApp". Remote signon to SASApp conceled.
Is there any experts can help me to find how to pass this failure. I am not sure the problem is because of my connection code, or there are any restrictions to connect to the server.
Thanks for anyone would give help !!!
11-24-2015 08:10 AM
Are you sure that a SAS/CONNECT server and Connect spawner is defined in metadata?
And you have the necessary rights to access/connect to it?
Also, verify that you have SAS/CONNECT licensed on both local PC and remote server.
11-24-2015 07:52 PM
Thanks for your replys.
1. Are you sure that a SAS/CONNECT server and Connect spawner is defined in metadata?
I am not sure whether the Connect spawner is defined in metadata. I can connect the server through EG. Does it mean the spawner is defined?
2. And you have the necessary rights to access/connect to it?
I am not sure. How can I verify the rights to access?
3. Also, verify that you have SAS/CONNECT licensed on both local PC and remote server.
Yes. My licenses is not expired on both local PC and remote server.
11-24-2015 01:50 PM - edited 11-24-2015 05:18 PM
The question I have is why do you want to signon to remote SAS from local SAS when you can use EG to connect to both your local and remote SAS server through the EG connection profile?
Also it looks like your first signon was successful. What happens if you then run a test RSUBMIT:
rsubmit; proc options; run; endrsubmit;
11-24-2015 08:27 PM
Thanks for your replys
Part my job is downloading data table from server to my local client. This job is regularly. I did it manually in EG with a menu way which is not very convient. Now I want to finished it automatically in a coding way. That is why I am tring to connect the server in SAS foundation. If it can finish my job in EG automatically, that is also very good. After all, EG has a more convenient interface than SAS foundation ().
In the end, I tested rsubmit. It returned the error message is :
Invalid or unspecified remote session ID. Set OPTIONS REMOTE=session_id. Remote submit to UNKNOWN canceled.
Thanks again for your replys! Have a good day!
11-25-2015 02:15 AM
Your log suggests that your remote session ID is called local.
rsubmit local; proc options; run; endrsubmit;
Remember that the above code should be run on your PC Foundation SAS immediately after the SIGNON statements.
11-26-2015 10:09 PM
Thanks for your patient reply.
I tried again recently. Unfortunately it still didn't work. However, I found an expert have already talked about this issue in 2012. He wrote an EG plug-in to solve this problem.
He talked about this story in this blog below. I hope it is also helpful for you.
Thanks again for your help.