TM1 Service not visible in Perspectives

[RaymondStokes]

I'm trying to use Net Start / "service name" as part of a Tubo Integrator process to start a TM1 service on a daily basis. The steps I followed were:

1. Schedule a server shut down on the target server
2. Create a start tm1 Bat file - Net start "TM1 Server / Test"
3. Schedule an Execute Command for the Bat file from a Control server running on the same box

As long as I'm connected using Remote Desktop everything works as intended. When I'm disconnected from the server everything works except I can't access the Tm1 server from Perspectives. The target server shuts down, the control server executes the chore and the target service even starts but still I can't access it from Perspectives.

I tried using "Scheduled Task" to execute the batch file and encountered the same result. The Tm1 Server started but I could not access it from Perspectives.

Thansk for your help.

[David Usherwood]

Erm...
If the TM1 service isn't running, how can the TI process execute? Or are you trying to start one TM1 service from another?

[Alan Kirk]

Erm...
If the TM1 service isn't running, how can the TI process execute? Or are you trying to start one TM1 service from another?

That's the way I read it. The "Target" server is one server session, the "Control" server is another server session. The Target server shuts down, the Control server runs the batch file to fire up the Target server again. The bit I didn't fully get was:

As long as I'm connected using Remote Desktop everything works as intended. When I'm disconnected from the server everything works except I can't access the Tm1 server from Perspectives.

I assume that means using an RDC to connect to the Windows server that the TM1 server is running on. However "everything works as intended" doesn't make it clear whether a Perspectives/Client/Architect session running on the windows server can see the restarted Target session, or whether he's just assuming that everything is OK because he can see the Target session running on the Windows server via Task Manager or similar.

Either way, I'm the key problem seems to be that he can't see the restarted Target server in a remote Perspectives session.

This suggests to me that either:
(a) The Target session isn't registering with the Admin Server, orrrr....
(b) The remote perspectives session was started before the Target server finished loading. In that case the list of available servers won't refresh itself automatically, and it would be necessary to either press [F5] in Server Explorer to refresh the server list, or do that via the menu option on the File menu.

(The latter would of course be the easier to diagnose and fix.)

[RaymondStokes]

In my case the situation I have is reflected by "A" The Target session isn't registering with the Admin Server. The Admin Server is running on the same physical machine as the Control and Target server.

To make the problem more annoying if I am using Remote Desktop to access the server when the control server chore executes the batch file to bring up the Target server the Target server starts and it does register with the Admin Server. It is only when all remote users have logged off of the Remote Desktop that the Target server starts but fails to register with the Admin Server.

I'm able to confirm that the target server did start using Task Manager but still can not see it via Perspectives. F5 from Perspectives has no effect on being able to see the server even though I can see it running in Task Manager.

Is there a better way to schedule a daily TM1 server restart than the method I've attempted?

[Steve Rowe]

Raymond,
I've not seen it mentioned but is it possible that you have the same port number in the config file for multiple servers? If you do then the second one that comes up won't be able to register itself with the admin server. The symptoms you describe seem like this but I haven't gone through the whole thread in detail...
Cheers

[RaymondStokes]

Thanks for the suggestion Steve. Unfortunately duplicate Port Number is not the issue because when I Remote Desktop into the server and execute the schedule (Windows Scheduler), TI Process or .Bat file manually the server is visible in Perspectives and I'm able to log into the TM1 server.

Thank You.

[dkleist]

Could the ports be blocked by network switch or client machine firewall?

[Steve Rowe]

Another thought is that you have the admin server running in the foreground as an application in the user session and also running as a service too?

Maybe there is a weird bug or something with the set up of the server that you are running that means that it is registering itself with an admin server running in the users RDC session. (you should be able to see this in the task bar). When the last user shuts down the the admin server shuts down and then you can only see your control server which is correctly registered with the admin server running as a service.

This kinda fits the facts....
Cheers,