 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Windows Server Forum / Windows Media Server / September 2007Windows Media Services Fatal Error
We are running Windows Server 2003 R2 X64. Tonight one of our servers stopped working in the middle of a bunch of streaming. When I checked the server, I found that Windows Media Services had stopped. I tried to restart but it would not start. I checked the system error log and it said, "The Windows Media Services service terminated with server specific error 3222082455 (0xC00D1397)." I cannot get past this and get the service started again. I searched the error and can find nothing. I am dead in the water. Any ideas? start all over again, that what i do whenever WMS crash, in 2 years it only happened to me twice, first time, i did not know what to do. i re-installed the media service and had things running again. hope this help you fix your problem http://plentipeppa.com Archie > We are running Windows Server 2003 R2 X64. Tonight one of our servers > stopped working in the middle of a bunch of streaming. When I checked [quoted text clipped - 5 lines] > I cannot get past this and get the service started again. I searched > the error and can find nothing. I am dead in the water. Any ideas? > start all over again, that what i do whenever WMS crash, in 2 years it only > happened to me twice, first time, i did not know what to do. [quoted text clipped - 13 lines] > > - Show quoted text - I did some further digging into the event logs. I found this sequence in succession: Reporting queued error: faulting application WMServer.exe, version 9.1.1.3814, faulting module msvcrt.dll, version 7.0.3790.1830, fault address 0x0000000000052240. Faulting application WMServer.exe, version 9.1.1.3814, faulting module msvcrt.dll, version 7.0.3790.1830, fault address 0x0000000000052240. The Windows Media service failed to start. The configuration file 'C: \WINDOWS\system32\Windows Media\Server\NamespaceDelta.xml' cannot be parsed due to the following error: It is not possible to store a value in a namespace node that has a different security type.Line number: 0 Character position: 0 Line text: The failed configuration file was copied to ''. > > start all over again, that what i do whenever WMS crash, in 2 years it only > > happened to me twice, first time, i did not know what to do. [quoted text clipped - 35 lines] > > - Show quoted text - Am I reading this correctly that some call into the C++ Runtime Library caused my WMS Namespace to get wiped out? Anyone have any experience with any of this? I'd like to know what caused this before I simply rebuild. Hi Craig, This line: > Faulting application WMServer.exe, version 9.1.1.3814, faulting module > msvcrt.dll, version 7.0.3790.1830, fault address 0x0000000000052240. Tells me that you are running Windows 2003 R2 (SP2). The new 9.1.1 WMS dll was distributed in the R2 update to Windows 2003. Maybe your R2 windows update failed to update the XML file in question? Nobody can really tell you why that file is corrupted, though. There is a log file of the windows update progress that you could read in your spare time. It might tell you something. That log file is in the \WINDOWS directory named WindowsUpdate.log. Try re-applying your R2 (SP2) update to the server. There might be other files that were corrupted during the failed R2 update. WMSServer.exe version 9.0.0.3693 - Pre R2 WMS installation WMSServer.exe version 9.1.1.3842 - R2 WMS installation 9.1.1.3842 has some other quirkiness in it that makes it a "pain" for developers. If you continue to have problems, then remove the WMS using the Add/Remove Windows Components control panel, and then add the WMS again from your original Win2003 install CD set.  SignatureJacob W Anderson --- http://www.beyond-ordinary.com http://www.extremeplannerlive.com --- If you think it''''s expensive to hire a professional to do the job, wait until you hire an amateur. > > > start all over again, that what i do whenever WMS crash, in 2 years it only > > > happened to me twice, first time, i did not know what to do. [quoted text clipped - 40 lines] > experience with any of this? I'd like to know what caused this before > I simply rebuild. |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.