I have one licensed copy of 24x7 running on a Production server,
we like the product and want to use it in a distributed enviornment-
I am testing how it would be used on some development servers
Testing enviornment:
AppSvr to run 24x7 as a service, this would be my master
DRAppSvr to run 24x7 as a service, for failover
FSSvr to run 24x7 remote agent as a service, to run jobs on FSSvr
PC running 24x7 remote control

I can not run 24x7 as a service on any of the servers and connect to it via remote control

Setup AppSvr as 24x7 Master as a service:
network: DistrSvcMode is enabled, winsock, 1096, [ip address]
service: run as service, start auto, normal
actual service: domain login
on the PC running remote control: winsock, 1096, [ip address]
tried to connect using a remote control from a PC... "connection failed, Requested server not available"
tried to connect using a remote control from the Appsvr... "connection failed, Requested server not available"

Setup FSSvr as 24x7 remote agent in service mode:
network: DistrSvcMode is disabled, winsock, 1096, [ip address]
service: run as service, start auto, normal
actual service: domain login
on the PC running remote control: winsock, 1096, [ip address]
I tried to connect using a remote control from a PC... "connection failed, Requested server not available"
I tried to connect using a remote control from the FSSvr... "connection failed, Requested server not available"

So I tried
different ports (keeping the same number on both ends)... connection failed
changed the service to log on as local service account w/ interact... connection failed

but If I stop the serivce and launch 24x7 on AppSvrr, or launch 24x7 remote agent on FSSvr
then try to connect with remote control it works!
But I really wanted was, all the instances of 24x7 to run as services,
so someone doesn't have to log on after a reboots

1) So is it possible to have your Master run as a service accessable via remote control?
if yes, what is wrong with the configs I tried?

2) Is it possible to have 24x7 remote agent run as a service accessable via remote control?
if yes, what is wrong with the configs I tried?

Your problem is likely caused by the domain login, which doesn’t have access to the network when running in interactive mode. As a result services under that login cannot access network too. Try the domain admin account for the service and see if that works.

: I have one licensed copy of 24x7 running on a Production server,
: we like the product and want to use it in a distributed enviornment-
: I am testing how it would be used on some development servers
: Testing enviornment: AppSvr to run 24x7 as a service, this would be my master
: DRAppSvr to run 24x7 as a service, for failover
: FSSvr to run 24x7 remote agent as a service, to run jobs on FSSvr
: PC running 24x7 remote control

: I can not run 24x7 as a service on any of the servers and connect to it via
: remote control

: Setup AppSvr as 24x7 Master as a service: network: DistrSvcMode is enabled,
: winsock, 1096, [ip address]
: service: run as service, start auto, normal
: actual service: domain login
: on the PC running remote control: winsock, 1096, [ip address]
: tried to connect using a remote control from a PC... "connection failed,
: Requested server not available"
: tried to connect using a remote control from the Appsvr... "connection
: failed, Requested server not available"

: Setup FSSvr as 24x7 remote agent in service mode: network: DistrSvcMode is
: disabled, winsock, 1096, [ip address]
: service: run as service, start auto, normal
: actual service: domain login
: on the PC running remote control: winsock, 1096, [ip address]
: I tried to connect using a remote control from a PC... "connection
: failed, Requested server not available"
: I tried to connect using a remote control from the FSSvr... "connection
: failed, Requested server not available"

: So I tried
: different ports (keeping the same number on both ends)... connection failed
: changed the service to log on as local service account w/ interact...
: connection failed

: but If I stop the serivce and launch 24x7 on AppSvrr, or launch 24x7 remote
: agent on FSSvr
: then try to connect with remote control it works!
: But I really wanted was, all the instances of 24x7 to run as services,
: so someone doesn't have to log on after a reboots

: 1) So is it possible to have your Master run as a service accessable via
: remote control?
: if yes, what is wrong with the configs I tried?

: 2) Is it possible to have 24x7 remote agent run as a service accessable via
: remote control?
: if yes, what is wrong with the configs I tried?

Sorry, I meant to say "in non-interactive mode"

: Your problem is likely caused by the domain login, which doesn’t have access
: to the network when running in interactive mode. As a result services
: under that login cannot access network too. Try the domain admin account
: for the service and see if that works.

: Sorry, I meant to say "in non-interactive mode"

when I stated "actual service: domain login"
the login I used was a member of the domain admin group
but that didn't work.
The connection failure always states that the
[computername] not found, Requested Server is not active
Is there a way I can check that the service is accepting requests?
Are there some commands that I can use to talk to the service,
ie: helo, what version r u?, etc

You can run netstat on the server to verify 24x7 is actually listening on port 1096

Although, I still think your problems are caused by network connections, please re-check that you use the same port 1096 in all places. On the server run 24x7 in GUI mode, open Tools/Options menu click Network tab and verify it uses 1096. When you connect from your workstation using 24x7 Remote Control click the Edit button and verify that Host profile also uses port 1096.

1. Also please make sure you are not trying to run an unregistered trial version.
2. You use different license keys for the 24x7 master and 24x7 remote control.
3. You don’t any related errors in the schedule.log file in 24x7 home directory and the NT Application event log.

: when I stated "actual service: domain login"
: the login I used was a member of the domain admin group
: but that didn't work.
: The connection failure always states that the
: [computername] not found, Requested Server is not active
: Is there a way I can check that the service is accepting requests?
: Are there some commands that I can use to talk to the service,
: ie: helo, what version r u?, etc

: 1. Also please make sure you are not trying to run an unregistered trial
: version.
: 2. You use different license keys for the 24x7 master and 24x7 remote
: control.
: 3. You don’t any related errors in the schedule.log file in 24x7 home
: directory and the NT Application event log.
I don't see any errors in either log, just the service starting and stopping
Looks like #1 & #2 could be it
I have one licencesed copy in production.
The others on AppSvr, FSSvr, and the PC are all trials running on development servers
So I can not test the enviornment with Trial versions?
We would really like to test the app in a distruted enviornment before purcahsing.
Is this possible?
Outside of this test we are ready to purchase some more licenses,
As long as we were assured this will work, we can purchase without testing.

Trial versions can run as services only if you run them under LocalSystem account with "Allow Service to Interact with Desktop” option set in the Services applet. This way the service can display on your Desktop the evaluation reminder dialog. If you don't use the LocalSystem you cannot see the dialog and the service sits there waiting for you click on the invisible Continue button. On the other hand the LocalSystem account cannot access the network. So you are pretty much limited to trying it without the remote control feature. As a workaround I suggest that you run the licensed copy on the server and use trial version for the remote control.

PS. Running it in service or on-service mode actually makes no difference. The only thing that you are going to proof is that when it is running as a service you can still connect to it.

: I don't see any errors in either log, just the service starting and stopping
: Looks like #1 & #2 could be it
: I have one licencesed copy in production.
: The others on AppSvr, FSSvr, and the PC are all trials running on development
: servers
: So I can not test the enviornment with Trial versions?
: We would really like to test the app in a distruted enviornment before
: purcahsing.
: Is this possible?
: Outside of this test we are ready to purchase some more licenses,
: As long as we were assured this will work, we can purchase without testing.