We have a problem with Windows Media Player 10 running on Windows XP
SP2.

The player runs in a web page, and constantly displays a constant
playlist of on-demand videos (WMV files).
Once in a while, the page reloads, and the player displays a live
stream.
After the live stream ends, the page refreshes again, and goes back to
displaying the on-demand playlist.

The problem is, that after a while, the player stops playing live
streams when required.

We get the following error from the player:

Windows Media Player cannot play the file because the specified
protocol is not supported. If you typed a URL in the Open URL dialog
box, try using a different transport protocol (for example, "http:" or
"rtsp:").

Re-installing the windows media player solves the problem, until the
next time.

What could be causing the problem?
What can be done in order to avoid it?
What is the procedure of opening a support call with Microsoft Windows
Media department?

Crosspost:

microsoft.public.windowsmedia
microsoft.public.windowsmedia.player
microsoft.public.windowsmedia.player.web
microsoft.public.windowsmedia.technologies

On 27 Dec 2005 02:21:29 -0800, ilya77@gmail.com wrote:

>We have a problem with Windows Media Player 10 running on Windows XP
>SP2.
>
>The player runs in a web page, and constantly displays a constant
>playlist of on-demand videos (WMV files).

Is this from a media server ? Or are the videos off a web server ?

>Once in a while, the page reloads, and the player displays a live
>stream.
>After the live stream ends, the page refreshes again, and goes back to
>displaying the on-demand playlist.
>
>The problem is, that after a while, the player stops playing live
>streams when required.

I would look at the currently playing URL and see if the ASX file has
some bug in it, specifying an incorrect URL to play (for example,
using the file:// protocol rather than the required rtsp, mms or http
protocol).

My take on this is your ASX file is broken somewhere.
Without seeing your content though, it's impossible to tell.

>We get the following error from the player:
>
> Windows Media Player cannot play the file because the specified
>protocol is not supported. If you typed a URL in the Open URL dialog
>box, try using a different transport protocol (for example, "http:" or
>"rtsp:").
>
>Re-installing the windows media player solves the problem, until the
>next time.
>
>What could be causing the problem?
>What can be done in order to avoid it?
>What is the procedure of opening a support call with Microsoft Windows
>Media department?
>
>Crosspost:
>
> microsoft.public.windowsmedia
> microsoft.public.windowsmedia.player
> microsoft.public.windowsmedia.player.web
> microsoft.public.windowsmedia.technologies

Hi Neil,

>Is this from a media server ? Or are the videos off a web server ?

The on-demand videos come from a local media server
(http://localhost/.../filename.wmv).

>I would look at the currently playing URL and see if the ASX file has
>some bug in it, specifying an incorrect URL to play (for example,
>using the file:// protocol rather than the required rtsp, mms or http
>protocol).

There is nothing wrong with the live stream URL. It's not even pointing
to an ASX file - it goes straight to mms://server/stream.
Same goes to on-demand clips. We are not using ASX files for this. The
clips are set using Player.URL once the previous clip finishes playing
(http://localhost/folder/file.wmv)

Any ideas?

On 27 Dec 2005 14:05:36 -0800, ilya77@gmail.com wrote:

>Hi Neil,
>
>>Is this from a media server ? Or are the videos off a web server ?
>
>The on-demand videos come from a local media server
>(http://localhost/.../filename.wmv).
>
>>I would look at the currently playing URL and see if the ASX file has
>>some bug in it, specifying an incorrect URL to play (for example,
>>using the file:// protocol rather than the required rtsp, mms or http
>>protocol).
>
>There is nothing wrong with the live stream URL. It's not even pointing
>to an ASX file - it goes straight to mms://server/stream.
>Same goes to on-demand clips. We are not using ASX files for this. The
>clips are set using Player.URL once the previous clip finishes playing
>(http://localhost/folder/file.wmv)
>
>Any ideas?

Hmm I don't really have any idea what could cause this.

The only thing I would do in your shoes is to run a bit of javascript
to check the error queue and report the actual URL in use when the
player barfs :

Something close to this might work

<script language="javascript1.2" for="MediaPlayer" event="error()">
player = document.getElementById("MediaPlayer");
errorCount = player.error.errorCount;
if (errorCount > 0) {
alert("Player URL set currently is
"+player.URL+"\r\nPlayer error details :\r\n" +
player.error.item(errorCount-1).errorDescription);
}
}
</script>

We've already taken all the precautions (including dumping the actual
URL and the error message into an error log).
We're pretty helpless in face of this problem.
Does anyone know how can we open a support call with Microsoft
regarding this issue?
It's extremely important for us to take control of this problem, or at
least to know what is causing it to avoid doing whatever breaks the
player...

On 3 Jan 2006 07:06:06 -0800, ilya77@gmail.com wrote:

>We've already taken all the precautions (including dumping the actual
>URL and the error message into an error log).
>We're pretty helpless in face of this problem.
>Does anyone know how can we open a support call with Microsoft
>regarding this issue?

I guess all they will do initially is point you to this page
http://www.microsoft.com/windows/win...00d_0x00000000

And ask you to provide the exact URLs used (which in all good faith,
is what I've asked and failed to establish).

Are we absolutely sure that this error affects all your customers, or
is it purely an in-house issue with proxies ? I'm still not able to
tell from your replies. These are the sorts of questions they'll want
to ask, in order to solve the problem.

>It's extremely important for us to take control of this problem, or at
>least to know what is causing it to avoid doing whatever breaks the
>player...

It would probably be useful to know where you're based in order to
sugest the best support call to make (or you can wait on hold all day
while you're transferred around ;-)

Examples are here :
http://support.microsoft.com/oas/def...spx?Gprid=7658

You may want to investigate any other support options built into your
contracts with microsoft, to see if you can do it cheaper than $250 a
pop.

HTH
Cheers - Neil