BookmarkSubscribeRSS Feed
ThysCronje
Calcite | Level 5

Backgroud:

We are using SAS in a training environment at the North-West University and install SAS on stand-alone PC's in our SAS Training Lab.  Some of these PC's are connected to the University network and some are not. (The scale to small for pure Client Server route).

We are migrating from Win XP, SAS 9.2 & EM 6.2. to Win 7 (64 bit), SAS 9.3 & EM 7.1.  The installation and configuration of the PC's connected to the network completed without major issues but we are having problems with PC's not connected to the network.  During the configuration step the Remote Services fail to start, causing Jboss service not to start properly, causing issues with EM 7.1.

We presume that it have something to do with network address and the host name used for the configuration of this PC's. This had to be correctly specified during the installation and configuration of the PC's connected to the network. The PC's not connected to the network have no official IP-address or network host name.

If this is indeed the case, any suggestions?

We have send the error logs to SAS support for help but thought, while we was waiting for an answer, we might as well pose this question to the Deployment Community.

3 REPLIES 3
mgst170
SAS Employee

Hi,

It would have been useful to post the log here too Smiley Happy

What details are stored in Metadata for RS?

Check in SMC -> Foundation Services Manager -> Remote Services -> Core -> Platform Service Registry

Under TCPIp Connection, what host name is specificed.

Does this match your machine? is it local host? 127.0.0.1?

Also check the Event Broker Service -> Service Configuration -> Configuration ->Connections -> Edit, and check machine name.

Check that the entry in here exists in your hosts file and try to start RS.

If it was me, I would have localhost, on the assumption that Jboss is running on the same PC.

Any anti virus differences between Network PC and Not? perhaps multicast is being blocked?

Cheers.

mgst170
SAS Employee

there should be a RemoteServices.log ans _wrapper.log under config/Lev1/web/logs.

They will have further details on why RS didn't start.

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 

CLI in SAS Viya

Learn how to install the SAS Viya CLI and a few commands you may find useful in this video by SAS’ Darrell Barton.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 3 replies
  • 2957 views
  • 3 likes
  • 2 in conversation