Customer impact of a 500 Internal Server Error by WMS?

[Arrturk]

Greetings All

Yep... I'm one of those people who is desperately searching for an answer and joins a related forum in the hope that someone out there knows more than I do (which is FAR more likely than not)

Basically I'm seeing my Windows Media Servers issues a 500 internal server error after receiving a (possibly malformed) client render log from the Client (as seen in packet captures)

We've currently got a support case logged with Microsoft regarding the cause of these errors, however the burning question is what would the impact of these errors be to the end customer?

Unfortunately we are yet to be able to duplicate the error, and due to the sheer volume of traffic over the CDN, tracing a failed session back to an individual client is nigh on impossible in the time we have. Can anyone please point me in the right direction for a guage of the impact?

Cheers

[Arrturk]

In the off chance that anyone gets here looking for an answer, this is what I found:

The RTSP 500 status code is frustratingly generic, giving the response "Internal Server Error". What was found was that at the conclusion of an RTSP stream, the WMP client would attempt to send back a Client Render Log back to the server. If the server was not configured to process this XML data, it would in turn generate a 500 status code.

So in short, the ways around these errors are to either:

* Disable the forwarding of Client Render Logs back to the WMS9 server. This is what I have done as a band-aid measure on the intermediary content caches. Obviously these logs have some information that information that could be quite useful, so we are now looking into implementing the other possible solution...
* Enable processing of the Client Render Logs into something useful.

And to answer my original question, these errors do not appear to be customer impacting

Hope this comes in useful to someone out there on the interwebs

RT