Broadcast publishing point stops

From: Harry (anonymous_at_discussions.microsoft.com)
Date: 06/09/04


Date: Wed, 9 Jun 2004 15:08:01 -0700

Broadcast publishing points stop and do not restart if the
stream is interrupted.

The problems have been random, but here is a precise
scenario:

Radio station k123 has a WM 7.1 encoder and broadcasts to
our W2003 server running WM9 Services. The publishing
point is set to pull, and the plug-in "start publishing
point when a client connects" is disabled. The encoder
computer crashes. The publising point stops. The encoder
computer reboots and starts encoding again, and looks
normal through pcAnywhere. Clicking on a link to listen to
that stream gives an error message "Windows Media Player
cannot play the file because the server is busy. Try again
later."

However, this is a powerful but lightly loaded server. It
has gigabit connections and typically never runs more than
1-2% cpu occupancy. At the moment this particular event
occurred it was only at 1% with only 15 unicast clients
connected.

Then I changed the plug-in to ENABLE "start publishing
point when a client connects". Now try to connect with a
player and the player is able to receive the stream and
the publishing point status turns to "on".

We've had other such events that caused similar problems.
Yesterday a tech in the datacenter overloaded the circuits
on the rack and popped a circuit breaker causing several
of our servers to go down. We experienced the same kind of
problem on a couple of streams. We have just upgraded to
W2003/WM9, but previously had similar problems on a
cluster of six W2000/WM7 servers wherein a stream had hung
on four of the servers in the cluster, but was still
working on two of the servers.

We seem to have had the same type of failures whether or
not the plug-in is enabled.

Our customers stream live 24x7, and this kind of
unreliability is intolerable. btw, I noticed that someone
else asked the same kind of question about 3 months ago,
with no answer

thx
Harry Emerson
hemerson at surfernetwork.com



Relevant Pages

  • Re: WMContentBitrate - not working on distribution server
    ... Im running WM9.0 on W2k3 Enterprise servers. ... Limit at 60000 on individual publishing points, umm, where do you do that? ... ive tryed limiting the publishing point on the "limit the bw per stream per ... to distribution servers. ...
    (microsoft.public.windowsmedia.server)
  • Windows Media Services 9.0 mountpoint drops connectivity when unde
    ... The two servers are both Gigabit enabled and connected to a fibre backbone ... source encoded stream. ... The encoder connection was fine and could be connected to and played from ...
    (microsoft.public.windowsmedia.server)
  • "Limit bandwidth per stream per player" problem
    ... can be enabled on a publishing point that will deny Play ... >where Internet users have access only to 24 and 19 Kbps ... >intranet users be able to receive the 48 Kbps stream too. ... >It appears that you cannot limit the bandwidth per stream ...
    (microsoft.public.windowsmedia.server)
  • Cant Connect to Publishing Point
    ... Can you actually stream any other content from the ... publishing point and then select "Allow new client ... >I'm trying to get Windows Media Services to stream some ... >a Windows Server 2003 Standard box. ...
    (microsoft.public.windowsmedia.server)
  • Keeping a publishing point up and running
    ... I'm building a semi-complex media streaming infrastructure for broadcasting internal communications and I'm running into a problem that publishing points don't stay up if they aren't receiving a signal. ... The encoder then sends the encoded video to a "master" Windows Media Server in a data center (I'm currently pulling the stream because I can't seem to get Push to work, but that's another issue.) That master Media Server then sends a Unicast stream to "slave" Windows Media Servers in multiple branch offices in the organization. ... I have pre-defined Multicast only publishing points because we have the user go to our portal and pick their location and click go and they receive the .NSC file and all for that location, and I don't to have to update the .NSC file every time I want to stream another speech. ...
    (microsoft.public.windowsmedia.server)

Loading