1. TMSProbleUrl Service is NOT running in primary server ! there is NO service by this name under services panel ! i could not figure out where is this service , also the same service is NOT available at all in Secondary TMS server.
A quick way to fix IIS permissions can be to re-install TMS on the server that isn't working properly - this usually repairs the IIS permissions and sets them back to what they should be.
Wayne -- Please remember to rate responses and to mark your question as answered if appropriate.
Wayne
Please remember to mark helpful responses and to set your question as answered if appropriate.
TMSProbeURL is not a Windows service. It's tied a web page within IIS, look under Admin Tools > TMS Server Maintenance, there is a TMS Redundancy section where you'll find a web address for the Probe URL. You need to configure your NLB to probe this URL on all TMS servers every 5 seconds, the result will either be a 200 OK for the active node or 503 Error for the passive node, the NLB will need to send all requests to the active node.
The probe URL also serves as a way for both TMS nodes to keep track of how often it is accessed. If a node stops receiving probe requests to the URL, it will assume that the network link between the NLB and itself is down, and mark its own IIS service as being inactive. If this happens on the active node, it will trigger a failover.
All of the above is covered in the TMS Install Guides when setting up a redundant deployment with a NLB.
" That service can not be restarted, it depends of loadbalancer and redundancy configuration.
On the side of TMS, the probeURL service is reliant on the probe from the F5 load balancer. Since it is not a installed service on the TMS box, with the NLB probes TMS - it will display this as a service to show that the NLB is probing TMS and all is working correctly. In use - the NLB should always be probing and if ever in TMS that service is not shown - from a TMS perspective it looks like the NLB is not probing the TMS. "
You need to setup a monitor on the F5 to check the status of that URL and send all requests to the server that responds with 200 OK. There is an example F5 configuration in the TMS install guides that your F5 admins can go by.
Learn, share, save
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
