Windows Media Services (WMServer) not start

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Victor Y. Sklyar - 05 Feb 2008 13:05 GMT

after installation of service I can see in Event Viewer next lines

Event Type:    Error
Event Source:    Service Control Manager
Event Category:    None
Event ID:    7009
Date:        05.02.2008
Time:        12:47:30
User:        N/A
Computer:    MYCOMPUTER
Description:
Timeout (30000 milliseconds) waiting for the Windows Media Services
service to connect.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

-----

Event Type:    Error
Event Source:    Service Control Manager
Event Category:    None
Event ID:    7000
Date:        05.02.2008
Time:        12:47:30
User:        N/A
Computer:    MYCOMPUTER
Description:
The Windows Media Services service failed to start due to the
following error:
The service did not respond to the start or control request in a
timely fashion.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

what can I do with it?
reinstall of WMS not fix the trouble

It is window 2003 enterprise edition with sp2...

Reply to this Message

Neil Smith [MVP Digital Media] - 05 Feb 2008 22:11 GMT

Are you running IIS or another web server on that Server box ?

The startup messages are usually because WMS tries to bind to port 80
for HTTP streaming, but can't (because the web server grabbed it
first)

You could either move the web server to a different box, let it listen
on a different IP address bound to the same network adapter, bind it
to a separate network adapater (2 x NIC in the same server box) or
bind it ot a different port number like 8080 (least preferable)

Or turn off HTTP streaming in the media server if you know you won't
need it for your customers.

HTH
Cheers - Neil

>after installation of service I can see in Event Viewer next lines
>
[quoted text clipped - 36 lines]
>
>It is window 2003 enterprise edition with sp2...

------------------------------------------------
Digital Media MVP : 2004-2008
http://mvp.support.microsoft.com/mvpfaqs

Reply to this Message

Victor Y. Sklyar - 06 Feb 2008 17:37 GMT

On Feb 6, 12:11 am, "Neil Smith [MVP Digital Media]" <n...@nospam.com>
wrote:

> Are you running IIS or another web server on that Server box ?

Yes, I was. But now I uninstall IIS and all its services.

But result is the same again!

:-(

And I cannot understand what it is reason why it doesn't work :-(

Any ideas?

Reply to this Message

Neil Smith [MVP Digital Media] - 06 Feb 2008 22:09 GMT

>On Feb 6, 12:11 am, "Neil Smith [MVP Digital Media]" <n...@nospam.com>
>wrote:
[quoted text clipped - 3 lines]
>
>But result is the same again!

Go to Start -> Run, cmd

Type in netstat -an <enter>

What (other) services are listening on port 80 on that box ?

HTH
Cheers - Neil
------------------------------------------------
Digital Media MVP : 2004-2008
http://mvp.support.microsoft.com/mvpfaqs

Reply to this Message

Victor Y. Sklyar - 07 Feb 2008 08:13 GMT

On Feb 7, 12:09 am, "Neil Smith [MVP Digital Media]" <n...@nospam.com>
wrote:

> On Wed, 6 Feb 2008 09:37:56 -0800 (PST), "Victor Y. Sklyar"
>
[quoted text clipped - 17 lines]
> ------------------------------------------------
> Digital Media MVP : 2004-2008http://mvp.support.microsoft.com/mvpfaqs

Active Connections

Proto Local Address Foreign Address State
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1025 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1027 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1032 0.0.0.0:0 LISTENING
TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING
TCP 0.0.0.0:9661 0.0.0.0:0 LISTENING
TCP my.ip.address.here:139 0.0.0.0:0 LISTENING
TCP my.ip.address.here:1331 209.85.137.125:5222 ESTABLISHED
TCP my.ip.address.here:1347 195.19.148.138:60320 ESTABLISHED
TCP my.ip.address.here:1408 dns.ip.address.here:3128
ESTABLISHED
TCP my.ip.address.here:1413 dns.ip.address.here:3128
ESTABLISHED
TCP my.ip.address.here:1415 dns.ip.address.here:3128
TIME_WAIT
TCP my.ip.address.here:1416 dns.ip.address.here:3128
ESTABLISHED
TCP my.ip.address.here:1417 dns.ip.address.here:3128
TIME_WAIT
UDP 0.0.0.0:445 *:*
UDP 0.0.0.0:500 *:*
UDP 0.0.0.0:1028 *:*
UDP 0.0.0.0:1029 *:*
UDP 0.0.0.0:1293 *:*
UDP 0.0.0.0:1294 *:*
UDP 0.0.0.0:1295 *:*
UDP 0.0.0.0:1297 *:*
UDP 0.0.0.0:4500 *:*
UDP 0.0.0.0:9661 *:*
UDP 127.0.0.1:123 *:*
UDP 127.0.0.1:1307 *:*
UDP 127.0.0.1:1333 *:*
UDP my.ip.address.here:123 *:*
UDP my.ip.address.here:137 *:*
UDP my.ip.address.here:138 *:*

Reply to this Message

Victor Y. Sklyar - 07 Feb 2008 19:32 GMT

> On Feb 7, 12:09 am, "Neil Smith [MVP Digital Media]" <n...@nospam.com>
> wrote:
[quoted text clipped - 60 lines]
> UDP my.ip.address.here:137 *:*
> UDP my.ip.address.here:138 *:*

so, no one service or application doesn't keep 80 port...

Reply to this Message

Victor Y. Sklyar - 08 Feb 2008 15:21 GMT

> > On Feb 7, 12:09 am, "Neil Smith [MVP Digital Media]" <n...@nospam.com>
> > wrote:
[quoted text clipped - 64 lines]
>
> - Показать цитируемый текст -

Does exists in nature tools which can show me mistakes in my registry
(about WMS)?

Reply to this Message

Neil Smith [MVP Digital Media] - 08 Feb 2008 18:36 GMT

>On
>> > Proto Local Address Foreign Address State
>> > TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
>>
>> so, no one service or application doesn't keep 80 port

Agreed.

>Does exists in nature tools which can show me mistakes in my registry
>(about WMS)?

I am wondering about the startup order of services, do you happen to
know the CPU usage when the WMS service is trying to start ? It could
be possible that another process is taking a long time to start, which
WMS depends on.

You might be able to see some clues in the event log in WMI, just
before the WMServer emits this error (that will be in the log too).

I'm still thinking about what *else* might cause this, no main clues
yet from the port list above. Perhaps SQL server is running and
causing the slow server start, and it takes more than 30 seconds to
begin running ?

I notice port 9661 above is frequently linked to eMule file sharing
(or W32 virus) either of which isn't something I'd ever want to run on
a server BTW

http://forum.people.net.au/showthread.php?t=4230
http://www.symantec.com/security_response/writeup.jsp?docid=2007-100312-3341-99&
tabid=2

Cheers - Neil
------------------------------------------------
Digital Media MVP : 2004-2008
http://mvp.support.microsoft.com/mvpfaqs

Reply to this Message

Victor Y. Sklyar - 11 Feb 2008 08:21 GMT

> On Fri, 8 Feb 2008 07:21:05 -0800 (PST), "Victor Y. Sklyar"
>
[quoted text clipped - 9 lines]
> be possible that another process is taking a long time to start, which
> WMS depends on.

WMS depends on only one service - it is RpcSs - 'Remote Procedure Call
(RPC)' and it works.

I try to start WMS after system was loaded.
In services.msc addon I select WMS and press button Start.

I dont't see any delay or CPU loading.
Only error messagebox:

---------------------------
Services
---------------------------
Could not start the Windows Media Services service on Local Computer.

Error 1053: The service did not respond to the start or control
request in a timely fashion.

---------------------------
OK
---------------------------

> You might be able to see some clues in the event log in WMI, just
> before the WMServer emits this error (that will be in the log too).

> I'm still thinking about what *else* might cause this, no main clues
> yet from the port list above. Perhaps SQL server is running and
> causing the slow server start, and it takes more than 30 seconds to
> begin running ?

I have not MSSQL or something like it.

> I notice port 9661 above is frequently linked to eMule file sharing
> (or W32 virus) either of which isn't something I'd ever want to run on
> a server BTW

9661 port under Skype, but I check it when skype disabled and I see no
changes.

> http://forum.people.net.au/showthread.php?t=4230http://www.symantec.com/security
_response/writeup.jsp?docid=2007-1003...

I was check it, and I have not it on my PC.

So, the question is still opened...

Reply to this Message

Victor Y. Sklyar - 15 Feb 2008 08:06 GMT

> > On Fri, 8 Feb 2008 07:21:05 -0800 (PST), "Victor Y. Sklyar"
>
[quoted text clipped - 52 lines]
>
> So, the question is still opened...

so.... no idea how to fix it? :-((((

Reply to this Message

Victor Y. Sklyar - 01 Mar 2008 08:29 GMT

> > > On Fri, 8 Feb 2008 07:21:05 -0800 (PST), "Victor Y. Sklyar"
>
[quoted text clipped - 56 lines]
>
> - Show quoted text -

so people from MVP cannot help me?

Reply to this Message

Vladimir Polischuk - 03 Mar 2008 15:34 GMT

Hi Vitya,

I think you should reinstall you broken Windows and possibly you need to use
other copy of the distributive.

P.S.
Are you working with WMS project at IDE Group now?

Regards,
Vovan

> > On 8 ÆÅ×, 20:36, "Neil Smith [MVP Digital Media]" <n...@nospam.com>
> > wrote:
[quoted text clipped - 59 lines]
>
> - Show quoted text -

so people from MVP cannot help me?

Reply to this Message

Victor Y. Sklyar - 05 Mar 2008 09:38 GMT

On Mar 3, 5:34 pm, "Vladimir Polischuk" <v...@exclusivesoft.com>
wrote:

> Hi Vitya,
>
[quoted text clipped - 74 lines]
>
> - Show quoted text -

Hi, Vova.

I think you are right.
I can't solve this problem without reintallation OS.
You know what it mean... Kill many time...
Now, I install other distibution on VirtualBox and made port
forfarding.
But it is delirium as you understand.

Reply to this Message