LOCAL server could not be connected

don21 — Wed, 30 May 2018 11:46:18 GMT

Hi,

I am trying to schedule my programs using SAS MANAGEMENT CONSOL, for that I need to set up the connection (LOCAL atleat as there is no server). When tried I get the below message: Please advise:

Connection failed
Could not establish a connection to the SAS server on the requested machine. Verify that the SAS server has been started with the -objectserver option or that the SAS spawner has been started. Verify that the port Combridge is attempting to connect to is the same as the port SAS (or the spawner) is listening on.

-------------------------- Technical Information Follows --------------------------

Exception Details:
----------------------------------------
Exception type: SAS.EC.Directory.Metadata.MetadataException
Message: Connection failed
Source: EC.Directory
Target Site: MakeConnection
Data:
m_HostName : localhost
m_Port : 8561
m_Userid : Sindu

Stack Trace:
at SAS.EC.Directory.Metadata.OMSProvider.MakeConnection()
at SAS.EC.Directory.Metadata.OMSProvider.Connect()
at SAS.EG.SDS.Dialogs.ProviderConnectDlg.Connect(Object sender, DoWorkEventArgs e)

Inner Exception Details:
----------------------------------------
Exception type: System.Runtime.InteropServices.COMException
Message: Could not establish a connection to the SAS server on the requested machine. Verify that the SAS server has been started with the -objectserver option or that the SAS spawner has been started. Verify that the port Combridge is attempting to connect to is the same as the port SAS (or the spawner) is listening on.
Source: SASObjectManager
Target Site: CreateObjectByServer

Stack Trace:
at SASObjectManager.ObjectFactoryMulti2Class.CreateObjectByServer(String Name, Boolean synchronous, ServerDef pIServerDef, String LoginName, String Password)
at SAS.EC.Directory.Metadata.OMSProvider.MakeConnection()

Re: LOCAL server could not be connected

Kurt_Bremser — Wed, 30 May 2018 11:55:42 GMT

Do you have a metadata server licensed at all? It needs to be configured and started.

(I guess you need Integration Technologies licensed for the metadata server to work)

Re: LOCAL server could not be connected

don21 — Thu, 31 May 2018 02:55:35 GMT

@Kurt_Bremser sorry if my query sounds stupid but, how do I find out if I am licensed for that?

Thanks

Re: LOCAL server could not be connected

Kurt_Bremser — Thu, 31 May 2018 05:47:40 GMT

To see your licenses, run proc setinit.

Who set up the SAS system? That person could easily tell you if (s)he needed to configure the metadata server.

And you should be able to identify a running metadata server by its starting script, which would be called from SASCONF/Lev1/SASMeta/MetadataServer.

topic Re: LOCAL server could not be connected in SAS Enterprise Guide

LOCAL server could not be connected

Re: LOCAL server could not be connected

Re: LOCAL server could not be connected

Re: LOCAL server could not be connected