TMS Services stopping Still connection to SQL via App Pool

[sheldeane]

Hi All,

We are running TMS on a 64bit 2008 Win box and accessing an 08 SQL instance.

We are setting up an SQL mirror at another site and for DR purposes we need to repoint existing TMS server to new SQL Mirror instance.

The issue is we stop all TMS services on the TMS server except the IIS services and the TMS connection drops to the SQL connection. However when we start up a web sessions to the single TMS server the connection to the database re-establishes itself and therefore the application works 100% correctly. This includes reviewing existing meetings and being able to create new meetings.

We have investigated the issue and we have found that the "w3wp.exe" process is initiating a connection to the database without the need of the TMS services being started. After further investigation using sysinternals process monitor the file is showing that it is using the registy entry located here:

"[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Tandberg\TANDBERG Management Suite]" and reading the tmsngdb entry to create the connection.

Does this mean that the TMS services are no longer required and that the connection is now being established using the Application Pool within IIS.

Thanks

[Magnus Ohm]

Hi Dean

Indeed the TMS GUI will be operational even if you disable the services however each services has each a function in assisting the TMS perform certain tasks.

I.e the Liveservice is responsible for sending dial commands to the MCU so if this is disabled, you can book the conference but it will not automatically start since the Liveservice will not send the dial commands.

And the Database scanner service updates the systems status in TMS. If this is shut down you will have inconsistent statuses etc.

You can read more about the real functions of the TMS services in the TMS admin guide located here:

http://www.cisco.com/en/US/docs/telepresence/infrastructure/tms/admin_guide/Cisco_TMS_Admin_Guide_13-1.pdf

Hope this was of help.

/Magnus