WMC error

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Nige - 09 Oct 2005 13:58 GMT

Hi
For many months I have had no problems with Windows Media Connect(WMC) but
now I get the error message "The Network Service is not responding" when I
try to start WMC.
There is no more info given. I have uninstalled then reinstalled but it
makes no difference. Otherwise my Home network and Internet connection works
fine.
Any help appreciated.
Many thanks
Nige

Reply to this Message

Alan Ludwig [MSFT] - 10 Oct 2005 17:20 GMT

Please check the event log for any additional information on what may be
causing the problem.

Signature

Alan Ludwig
Software Design Engineer
Windows Media Devices Group
Microsoft Corp.

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

Reply to this Message

Nige - 10 Oct 2005 18:38 GMT

Hello Alan

The following Error in the Event Viewer occurs when "wmccds" is activated. I
should say that both Slimserver and MusicMatch work perfectly with my Roku
device at the moment and WMC did work up until I went on holiday in
September. Sadly, my earliest system restore point is 28 September and all
that happens when I restore at that date is Windows Media Connect sits there
for hours saying its starting and nothing else!

I don't know if this will help (but looking at the exception type) the only
thing I can think that has changed in the past month is I've put my USB wifi
adapter into a new USB2 port!?

Event Viewer info:
System.TypeInitializationException: The type initializer for
"System.Net.IPAddress" threw an exception. --->
System.TypeInitializationException:
The type initializer for "System.Net.Sockets.Socket" threw an
exception. ---> System.Net.Sockets.SocketException: An operation on a socket
could not be performed because the system lacked sufficient buffer space or
because a queue was full
at System.Net.Sockets.Socket.InitializeSockets()
at System.Net.Sockets.Socket..cctor()
--- End of inner exception stack trace ---
at System.Net.Sockets.Socket.InitializeSockets()
at System.Net.IPAddress..cctor()
--- End of inner exception stack trace ---
at System.Net.IPAddress..ctor(Int64 newAddress)
at
Microsoft.ContentDirectory.HttpServer.HttpServer.StartMonitoringAddress(UInt32
ipAddressLong)
at
Microsoft.ContentDirectory.Protocols.ProtocolManager.OnStartMonitoringAddress(UInt32
address)
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Thanks
Nige

> Please check the event log for any additional information on what may be
> causing the problem.

Reply to this Message

Alan Ludwig [MSFT] - 11 Oct 2005 04:12 GMT

Yikes, a "sockets" exception. I'm afraid to say that I've never seen that
problem before. Did you recently change your network card or update
drivers or install some other netowrk centric applicaion?

Signature

Alan Ludwig
Software Design Engineer
Windows Media Devices Group
Microsoft Corp.

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

Reply to this Message

Nige - 11 Oct 2005 09:11 GMT

Hi

Yes, I have made some changes.

Just recently I added a card reader (USB) to the system - this caused the
system to lock and hang on occasion.

I've had this system hang happen before and have found it probably due to
the IRQ for my USB2 PCI card and the graphics card being the same. This
seemed to cause some conflict between the graphics card and the USB Network
WiFi adapter (found by trial and error) which was connected through the USB2
PCI card. What I did then was to move the NW adapter to an on-board PC USB1
port (with a different IRQ) and everything worked OK.

Well, when I added this card reader and got a similar problem to above I
thought I had better do something about the IRQs. So, researching similar
problems on the Internet I decided that re-installing PCI cards may be the
answer. So I removed all PCI cards except the graphics card and re-installed
one-by-one with the USB2 PCI card being first. Eventually I got a set of
IRQs, with some conflict but of (then) seemingly little importance since
everything connected to the PC through USB ports worked fine with no system
hangs - even my NW adapter was back on the USB2 PCI card!

However, now it appears that everything else works hunky dory except WMC
although, as I've said earlier, SlimServe and MusicMatch work perfectly.

I have noted that this problem of an error message "The Network Service is
not responding" has been reported by one or two via internet postings but
with no definitive answer given by anyone! BTW, what is a 'socket'?

Here's my IRQ summary:

Resource Device Status
IRQ 9 Microsoft ACPI-Compliant System OK
IRQ 11 NVIDIA GeForce4 MX 440 OK
IRQ 11 Creative SB Live! Value (WDM) OK
IRQ 11 VIA Rev 5 or later USB Universal Host Companion Controller OK
IRQ 14 Primary IDE Channel OK
IRQ 15 Secondary IDE Channel OK
IRQ 5 VIA Rev 5 or later USB Universal Host Controller OK
IRQ 5 VIA Rev 5 or later USB Universal Host Controller OK
IRQ 5 VIA Rev 5 or later USB Universal Host Companion Controller OK
IRQ 10 Creative AudioPCI (ES1371,ES1373) (WDM) OK
IRQ 12 VIA USB Enhanced Host Controller OK
IRQ 0 System timer OK
IRQ 8 System CMOS/real time clock OK
IRQ 13 Numeric data processor OK
IRQ 6 Standard floppy disk controller OK
IRQ 4 Communications Port (COM1) OK
IRQ 3 Communications Port (COM2) OK
IRQ 1 Logitech PS/2 Keyboard OK

Thanks
Nige

> Yikes, a "sockets" exception. I'm afraid to say that I've never seen that
> problem before. Did you recently change your network card or update
> drivers or install some other netowrk centric applicaion?

Reply to this Message

Alan Ludwig [MSFT] - 13 Oct 2005 18:28 GMT

> Hi
>
[quoted text clipped - 23 lines]
> However, now it appears that everything else works hunky dory except
> WMC although, as I've said earlier, SlimServe and MusicMatch work

"Sockets" is the general name for the low level network programming
API's. So basically we're doing some network call and that is throwing
an exception. This is happening down in the guts of the network drivers
and is "below" WMC.

I'm not surprised that MusicMatch and company has different networking
code than we do. We actually provide some security and they don't.

I don't know exactly what is causing the exception in the networking
code, but given your recent changes it wouldn't be unexpected to think
that the error is related.

Sorry I couldn't be more help,

Signature

Alan Ludwig
Software Design Engineer
Windows Media Devices Group
Microsoft Corp.

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

Reply to this Message

Nige - 16 Oct 2005 14:58 GMT

>> Hi
>>
[quoted text clipped - 36 lines]
>
> Sorry I couldn't be more help,

Alan

Thanks for your help but with all due respect about the security issue -
sometimes you don't need it. My home network sits behind a h/w and a s/w
firewall using several security options. I really don't need another layer
in WMC - maybe a switch should be provided to turn any security off in WMC.
I would prefer no security and a working application to what I've got at the
moment!

Regards
Nige

Reply to this Message