BookmarkSubscribeRSS Feed
kohlat
SAS Employee

Hi All,

 

Just wanted to check if anyone encountered this kind of issue with Remote Services in SAS 9.1.3 ?

 

Usually, what we should see on the Remote Services log for a successful start is this:

 

 

------------------------------------------------------------------

Services deployment info for:

 

OMRMetadataSource {

software component: Remote Services

group: BIP Remote Services OMR

group: BIP Stored Process Service

host: xxx.xxx.xxx.xxx

port: 8561

}

 

 

Repository info:

-------------------------------

   protocol = omi

   name = Foundation

   host = xxx.xxx.xxx.xxx

   port = 8561

   domain = DefaultAuth

   base = Foundation

   autoConnect = true

 

Repository info:

-------------------------------

   protocol = omi

   name = Foundation

   host = xxx.xxx.xxx.xxx

   port = 8561

   domain = DefaultAuth

   base = Foundation

   autoConnect = true

 

Repository info:

-------------------------------

   protocol = omi

   name = Foundation

   host = xxx.xxx.xxx.xxx

   port = 8561

   domain = DefaultAuth

   base = Foundation

   autoConnect = true

 

Repository info:

-------------------------------

   protocol = omi

   name = Foundation

   host = xxx.xxx.xxx.xxx

   port = 8561

   domain = DefaultAuth

   base = Foundation

   autoConnect = true

 

Repository info:

-------------------------------

   protocol = omi

   name = Foundation

   host = xxx.xxx.xxx.xxx

   port = 8561

   domain = DefaultAuth

   base = Foundation

   autoConnect = true

 

Repository info:

-------------------------------

   protocol = omi

   name = Foundation

   host = xxx

   port = 8561

   domain = DefaultAuth

   base = Foundation

   autoConnect = true

 

Remote server info:

-------------------------------

   ApplicationProtocol = RMI

   hostName = sooner3.corp.acxiom.net

   port = 5099

 

 

 

However, we have an environment where we only see this part on the log:

 

------------------------------------------------------------------

Services deployment info for:

 

OMRMetadataSource {

software component: Remote Services

group: BIP Remote Services OMR

host: xxx.xxx.xxx.xxx

port: 8561

}

 

 

It seems the remote services is not getting information from the metadata server (which is on another box)

 

This in turn seems to be the issue why our Web app server is not starting.

 

Please advice, what could be the reason and things I can check 

 

Thanks in advance,

1 REPLY 1
SimonDawson
SAS Employee

If you have the SAS Management Console deployed on the same host as where the SAS Remote Service is deployed can you logon to the SAS Metadata Server?  This installation is old so has been working for a long time. What has changed recently?  Perhaps take a look into the SAS Metadata Server logs at the time this service was started. Any errors?

 

 

 

Did you know your version of SAS is nearly old enough to apply for a drivers license here in Australia? You really should think about upgrading. It's only dinosaurs who'll know much about this installation soon.

suga badge.PNGThe SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment. 

Join SUGA 

Get Started with SAS Information Catalog in SAS Viya

SAS technical trainer Erin Winters shows you how to explore assets, create new data discovery agents, schedule data discovery agents, and much more.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 1 reply
  • 562 views
  • 0 likes
  • 2 in conversation