Monitoring Applications May Cause Windows Media Services to Stop Responding (282808)
The information in this article applies to:
- Microsoft Windows Media Services 4.1
This article was previously published under Q282808 SYMPTOMS
Some server health-monitoring applications or hardware that test to see if a Windows Media Services server is running may cause Windows Media Services to get overloaded, and an interruption in service can occur. These applications are usually used in a server farm where multiple Windows Media Services servers are load balanced.
CAUSE
Health-monitoring applications may use ports 1755 or 80 for monitoring. Typically, they make a TCP connection to either one of these ports and ensure that they get a valid response. Some monitoring applications may not correctly close the connection to the Windows Media Services server, and can cause the services to stop responding.
RESOLUTION
A fix is available through the following Knowledge Base article: 281256 Handle Leak in Windows Media Server Unicast Service
STATUSMicrosoft has confirmed that this is a problem in Windows Media Services version 4.1.
| Modification Type: | Major | Last Reviewed: | 10/16/2002 |
|---|
| Keywords: | kbbug kbQFE KB282808 |
|---|
|