Windows Media Service Not Start

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Bhavesh Vakil - 20 Apr 2004 08:51 GMT

Hello,

I have my dedicated "Windows 2003 Standard Edition" server co-located in
server farm.

My application is based on "Windows Media Server". I am heavily using "WM9"
environment in my application program.

I have this setup running since last 9 to 10 months and everything is
smooth. Last night I don't know what happen to my server farm but my machine
was unexpectedly restarted 3 times in 30 min.

Now problem is my "Windows Media Service" is not able to start on my
machine. This service is "Automatic" in service panel. But it is not
starting during window startup. When I try to start service manually, I am
getting following message

"Windows could not start the Windows Media Services on Local Computer. For
more information, review the System Event Log. If this is a non-Microsoft
service, contact the service vendor, and refer to service-specific error
code -1072884841"

On Event Log, I am getting following,

Type: Error
User: N/A
Source: Service Control Manager
Category: None
Description: The Windows Media Services service terminated with
service-specific error 3222082455 (0xC00D1397).

Urgent help require, Thank you,

Bhavesh

Reply to this Message

Ravi Raman - 21 Apr 2004 07:39 GMT

I am taking a guess here, so excuse me if I am off the
track. One possibility is that your servernamespace.xml
could've become corrupt. Did you happen to do any
upgrades recently w.r.to the server OS?

NOTE: Messing around with the servernamespace.xml file
can cause your server to be inoperable. The following
steps may remove all the Windows Media settings that you
have, so only if you are okay with it, proceed with these
steps in the next para. If you don't want to destroy your
server settings, you might want to find whether someone
edited the servernamespace file accidentally and try to
revert the change.

Copy the servernamespace.xml (from %WINDIR%\system32
\windows media\server) to a different location. Then,
delete the servernamespace.xml file and try to restart
the server. If server restarts, then your earlier
namespace file was corrupt and your server is operational
now. If not, something else could've gone wrong. In that
case see if a re-install of WM Server after deleting the
servernamespace.xml will help.

Thx,
Ravi
--
This posting is provided "AS IS" with no warranties, and
confers no rights.

>-----Original Message-----
>Hello,
[quoted text clipped - 33 lines]
>
>.

Reply to this Message