Windows Media Services 9 Series:

SUPPORT SOLUTION:
In Windows Media Services server logs you may notice that there are log entries for clients that have successfully played entire videos but have the status code of 408 - Abnormal Disconnect.  There will be no client rendering information, such as the videocodec, for that log entry.  You may also notice that you only have 408 status codes for logs of longer videos..When longer playing content is fast cached and the player inactivity timeout is set to a low value the server can disconnect the client before the client finishes playing the video.  Once the video is cached using Fast Cache it will continue to play in Windows Media Player.  While the player is playing the content from cache, the server will consider the client connection idle since there is no video being transferred.  If this idle period is longer than the Limit player time out inactivity, the server will close the client connection and write a log entry with the status code of 408.  Once the player finishes playing the video it will attempt to post the playback statistics to the WMS server.  Since the connection is no longer valid, the server will not include the client statistical post in the log..On the Windows Media Server increase the Limit Player TimeOut Inactivity value.  This can be changed in the Windows Media Services administrative console under Windows Media Services\<server name>\Properties tab\Limits.. The default value for Limit Player TimeOut Inactivity is 3600 seconds (60 minutes).  The minimum value you should use for the inactivity limit would be:
Video length - time to cache video = minimum inactivity limit
Note that while the video is actively being cached, the server considers the connection active and will only start the inactivity timeout counter once the video has finished caching.
To disconnect the client, Windows Media Services will send an RTSP End-of-Stream message to the Windows Media Player client with AdministrativeDisconnection=true..Note This is a “FAST PUBLISH” article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use
(http://go.microsoft.com/fwlink/?LinkId=151500)
for other considerations..

For File Repair and Data Recovery, visit File Repair / Data Recovery