(In reply to comment #0)
I can confirm the same behavior on my end.  It's probably important to note that the crash only seems to occur with WMC running on the same machine as SlimServer.  If I run WMC on a different machine, I do not experience the issue.  I've only tested this with WMC 2.0.

TheEndless

event viewer messages????

(In reply to comment #2)
> event viewer messages????
>

I've attached a SlimServer log file with -d_upnp enabled.

Only error in the event log is:

Event Type:	Error
Event Source:	Service Control Manager
Event Category:	None
Event ID:	7034
Date:		11/6/2006
Time:		1:33:51 PM
User:		N/A
Computer:	DESTRUCTION
Description:
The SlimServer service terminated unexpectedly.  It has done this 6 time(s).

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

Created attachment 1696 [details]
SlimServer log of crash with -d_upnp

Please try a 6.5.1 nightly.  I have tested with WMC and it should work fine.

Andy,
                 I tried 6.5.1 before I posted this a couple days back. I am still running 6.5.1 and am seeing the same failures. The 6.5.1 that I tried three days ago is the same as the 6.5.1 that you just suggested, right? It would have a different build number or verision if it were not,right? (I'm new to all this bug and error reporting so please bear with me).
Thx, Matt


(In reply to comment #5)
> Please try a 6.5.1 nightly.  I have tested with WMC and it should work fine.

Sorry yes I see that, I should not reply to bugs first thing in the morning. :)

I actually don't think the "Read search result failed:" is causing the crash, since it happens earlier in your log without a problem.  What version of WMC are you running?

(In reply to comment #7)
The log I posted is from WMC 2.0.  I'm pretty sure Matt is running the WMP 11 integrated version.  When I first figured out that WMC was the culprit, I thought it might have to do with the fact that it's broadcasting itself on all four network interfaces on the machine.  I'm running VMWare which is responsible for two of them, but I was surprised to see it broadcasting to localhost, too.  Any chance there could be a problem there?

Are there any other debug flags that would be helpful?

Steve

One thing worth trying if you have another box (or use VMWare) is to run SlimServer on a different box than WMC just to see if it still crashes.

(In reply to comment #9)
> One thing worth trying if you have another box (or use VMWare) is to run
> SlimServer on a different box than WMC just to see if it still crashes.
I mentioned that in my first post: "It's probably important to note that the crash only seems to occur with WMC running on the same machine as SlimServer."  The crashes don't occur when WMC is running on a different machine (at least not for me).

Andy, I can't do that (my other box is a 98SE machine). But if I disable WMC via contraol panel, SlimServer runs and never has an issue. The WMC I am running is the embeded verison in Windows Media Player 11, not WMC like Steve is running.Thx, Matt

(In reply to comment #9)
> One thing worth trying if you have another box (or use VMWare) is to run
> SlimServer on a different box than WMC just to see if it still crashes.

Andy, are you able to reproduce this?  Shall I (or Ross) have a look?

If you guys can reproduce that would be great.  I'm pretty sure I tested SS on the same XP VM as WMC before.

Created attachment 1707 [details]
Crash log with all debug flags on.

Here's a log file with every debug flag turned on.  It doesn't look like there's any more helpful information in there, but I don't really know what I'm looking for, so...

Note: this is an idle SlimServer (no connected clients)

Is there some kind of trick to getting WMC to run?  It looks like it's part of WMP11, but although I have it installed, I don't see anything in the services or processes that looks like WMC.

There shoild be an option to "Share Media" under the Library tab (or under tools). If not, try WMC2
http://download.microsoft.com/download/9/e/5/9e5dee3c-4338-4094-9823-592938dd058a/wmcsetup.exe
I think that is what Steve was using?

Hmm.  After I initially tried WMC2, after listening to local content for about 15 minutes, the music suddenly stopped.  I looked over at the player and I caught a brief glimpse of a 'timeout' error in the upper left corner before the screen went blank.  However, Slimserver still appeared to be running, although slowly.  Double-clicking the systray icon eventually brought up the web UI, and a few seconds after that, the player UI returned as well.  There was no message in the event log or anything interesting in the Slimserver log.

This happened twice more in quick succession, so I figured this was probably the error and it was only a matter of time until it actually crashed.

However, it has now been playing for a half hour with no disruption.  

I'll keep poking at it.  Very frustrating.

Chris,
Just last night I was wanting to access some content via WMC, so I started the service up (I have it set to manual now) and within 2 minuites, I noticed the little green dots on the SS icon in the Sys-Tray were gone, and sure enough, the SS service was not running. If I start the service (SS)again, it runs for a tad, then same thing. So right now, I keep the WMC service off, unless I know I am not going to use SS for a little bit. I do have plenty of times were I need both service to run at the same time. 

What can I do to help you? I can take a phone call or what ever you need. Just let me know...

Are you using a true XP box or something else with an emulator?

Regards, Matt

(In reply to comment #17)
> Hmm.  After I initially tried WMC2, after listening to local content for about
> 15 minutes, the music suddenly stopped.  I looked over at the player and I
> caught a brief glimpse of a 'timeout' error in the upper left corner before the
> screen went blank.  However, Slimserver still appeared to be running, although
> slowly.  Double-clicking the systray icon eventually brought up the web UI, and
> a few seconds after that, the player UI returned as well.  There was no message
> in the event log or anything interesting in the Slimserver log.
> This happened twice more in quick succession, so I figured this was probably
> the error and it was only a matter of time until it actually crashed.
> However, it has now been playing for a half hour with no disruption.  
> I'll keep poking at it.  Very frustrating.

My PC at home is Xp Pro (Pentium CPU) and I am using the embedded version of WMC. It crashes.

At work the PC is XP Pro (Celeron CPU), I just tried WMC 2.O with SS 6.5.X (11/14) build and it's fine, I can even mount the WMC service from SS and use it's library. So is it the Celeron, the newer version of SS or something else? I'll try the latest build of SS tonight and see what my home PC does. I am going to let the two of these services run overnoight here at work and see what happens in the morning.


Steve, What are you running? WMC 2.0 (not WMC 1.0 or the embedded version in WMP11) via XP? Is your CPU an Pentium or Celeron?

Perhaps good news...
Home PC (XP Pro (Pentium CPU), using the embeded WMC within WMP11 seems to work with SSv6.5.1[build-11/14].
With the past version of 6.5.X, I would see the name WMC assigned to the service with in the SS web interface. However, if I clicked on it, nothing happened, or it (the WMC name seen in SS) would disapear.

With this build, I see it, I can click on it and untill you allow access via WMC, SS will display a UPnP error (non-fatal) on the screen. Once you allow the service to let SS access it, then when you click on the WMC name in SS, you then get to see the library, just like I was able to do at work too..

CRUD..It just stopped... 

Anyway, I'll see if SS is still running on the unit at work when I go back tommorrow.

Well, the PC at work with both the WMC2.0 and SS 6.5.1[11/14]services running; is still running now. It's been over 20 hours since I launched both services.
I will list the difference between work and home...
The work PC uses a Celeron CPU, there are no clients to talk to the running services, using WMC2.0 and not the intergrated version from WMP11 and that's all I can think of right now.
As stated, I think Steve is using WMC2.0.

What are you using to access your content via WMC?

Roku M1000 Soundbridge. Just for the record, the Roku has been in the setup since I was running SS6.2 and SS6.3, but then again, to play devil's advocate, there have been firmware updates for the Roku too.

(In reply to comment #22)
> What are you using to access your content via WMC?

Sure.  I'm just thinking in addition to having WMC running, perhaps I ought to try actually exercising it to see if it makes the problem more reproducible for me.

Chris, I was able to have SS and WMC work togehter w/o SS stopping itself. The way I did it was to leave my Roku HD1000 unpluged. Since the Roku Photobridge (HD1000) sleeps and does not turn off, I unplugged it and everything was fine. I started with all my DMR's unplugged and then added one a time untill I saw the issue.

Since the Roku HD1000 and Slimserver can play nice together when the WMC server is not running, and WMC an play nice with SS when the HD1000 is unplugged. What do you think is happening?

Is there a some packet of data between the HD1000 and WMC freaking Slimsever out and casuing it to shut down? With SS 6.3 there was no conflict to my knowlege, but 6.3 didn't have UPnP support, right?

Should I run one of the Intel UPnP snoop tools and see what packets are flying around when the HD1000 gets plugged in?

Regards, Matt

Still haven't been able to reproduce.

Matt, can you pin it down to something you *do* with WMC?  Or does it just always happen if you have WMC on?  How long does it take?  Shortest/average/longest times? (best guesses).

I've been playing with Rhapsody and WMC 2.0 for much of the afternoon, listening with the 6.5.1 nightly, and trying out a Cidero upnp 'controller' application I found, and it all seems very solid!

Could I interest you in posting an exported report from msinfo32?  This is a little-known utility that comes with windows XP.  You run it by pressing the Start button -> Run -> and typing in msinfo32.  On the file menu there is an 'export' option that will output a ton of your system information as a text file.

It would probably be easier to upload after being compressed into a zip file.

I'm trying to figure out why your system might be experiencing these symptoms and mine is not by just comparing other differences.

Created attachment 1729 [details]
Intel Device sniffer

1.100 is my PC running SS and WMC. 1.103 is the Roku PhotoBridge. SS was fine, I plugged in the PB and after the 1.103 packets popped up on the sniffer, I could hear my hard drive, then SS stopped (lilttle green dots gone from SS systray icon) and then pakcets that I assume are from SS (port 1900 is SS, right?) popped up.
Does this help you any?

Chris, It seems that the HD1000 does something with WMC that then in turn kills/crashs/stops SS.

I can have SS fail/stop almost like clock work if I do the following.
WMC running, SS running, then plug in my Roku HD1000 Photobridge (then let it boot).
Here's the kickers..
With WMC diabled, plugging in the HD1000 has no effect. SS and the HD1000 will run for days.
With WMC runing and SS running without the HD1000 pluged in will run for days.
It's a combo of the three things. 

Would the MSinfo32 help you with this?

(In reply to comment #26)
> Still haven't been able to reproduce.
> Matt, can you pin it down to something you *do* with WMC?  Or does it just
> always happen if you have WMC on?  How long does it take? 
> Shortest/average/longest times? (best guesses).

Andy do you have any ideas of other info that Matt could provide that might be helpful in pinning this problem down?  

I finally found a upnp renderer device to test with have shared my content using WMC 2.0, and have been listening to tracks on it and my transporter at the same time all afternoon using the 6.5.1 nightly.

Y'all have a Roku HD1000 photobridge in the lab that you can fire up? It seems that the combo that kills SS is WMC running with SS running and a HD1000 being pluged in (just turning the HD1000 off will still crash SS since the HD1000 just goes to sleep per se, you have to unplug the unit to get it out of the picture and then SS is happy playing with WMC).
Sorry this has turned into such a pain for y'all. Matt

(In reply to comment #29)
> Andy do you have any ideas of other info that Matt could provide that might be
> helpful in pinning this problem down?  
> I finally found a upnp renderer device to test with have shared my content
> using WMC 2.0, and have been listening to tracks on it and my transporter at
> the same time all afternoon using the 6.5.1 nightly.

To echo what Steven said, it seems that SS only crashes if WMC and SS are running on the same PC.

I am running three instances of WMC on another PC connected to my LAN and there no issues.
I can disable WMC on the PC that is running SS and keep WMC running on the other PC and everybody is happy.
The only caveat is, the other PC is not staying on my LAN past x-mas, so this can not be a workaround for me.

Hope this is helpful, Matt

What version and patch level of XP are you guys running?  Mine says it's Windows XP Professional Version 2002 Service Pack 2.  Do you have something different?

Any progress over the holiday?
Regards, Matt Burkhard

I still believe that you are seeing this problem Matt, but I just haven't been able to reproduce it here.  I'd be interested in more inforamtion about your system so we can continue to try to reproduce it here.  There's a program that comes with windows called 'msinfo32'.  Would it be possible for you to run this program (by going to start -> run and typing in 'msinfo32', then going to the File menu, and selecting Export, then attaching the resulting data file to this bug?

It seems to be something in a data packet generated from the Roku HD1000 when talking to WMC (whilst SS is running) that is causing this. Look at a couple of my older posts and I tried to explain what I saw. 

I am a little leary about sending that info (msinfo32) to be hosted on the internet (I'm a worry wart). Is there personal info in that file? Can I email it to you directly verse hosting it? Worse comes to worse, I can do this, but wouldn't the packets of data being transfered on my netwrk right before, during and after the crash work better? I can make it fail like clock work now.

Do you have access to a Roku HD1000 photobridge?

Thanks again for looking at this and since I don't know anything about this (SS and UPnP stuff) and y'all do, let me know and I'll do it (even sending the msinfo32 file to here if I have to).
Thanks, Matt


(In reply to comment #34)
> I still believe that you are seeing this problem Matt, but I just haven't been
> able to reproduce it here.  I'd be interested in more inforamtion about your
> system so we can continue to try to reproduce it here.  There's a program that
> comes with windows called 'msinfo32'.  Would it be possible for you to run this
> program (by going to start -> run and typing in 'msinfo32', then going to the
> File menu, and selecting Export, then attaching the resulting data file to this
> bug?

Created attachment 1761 [details]
MSinof32 per Chris

Here ya go Chirs...
I hope you find something!
Thanks, Matt

Chris, what that the data (msinfo32) that you needed? In other words, did I do it right?
Thanks, Matt

Same issue occurs with Vista 32 bit Enterprise and WMP (wmc built into WMP)

Any updates?

Andy, is there a reason why we still have UPNP in Slimserver?  Do we even need it any more?  Can it be disabled per user somehow?

Yeah it's needed for Rhapsody UPnP mode.  It can be disabled with the command-line switch --noupnp.

(In reply to comment #41)
> Yeah it's needed for Rhapsody UPnP mode.  It can be disabled with the
> command-line switch --noupnp.

So do I make a shortcut (Windows) and in the target, add "--nonupnp" to the end of it?

That should work, Matt.  Or for a test you could shutdown slimserver using slimtray, and launch it from the command line.  Please keep us updated!

(In reply to comment #43)
> That should work, Matt.  Or for a test you could shutdown slimserver using
> slimtray, and launch it from the command line.  Please keep us updated!
I used this in the shortcut 
"C:\Program Files\SlimServer\SlimTray.exe" --start --noupnp
and it still crashed with WMP11 running with Media Sharing enabled (WMC).
Did I doit right?

Command-line options don't work on SlimTray, they have to be passed to slim.exe:
C:\Program Files\SlimServer\server\slim.exe --noupnp 

Hmm, wonder how hard it would be to have SlimTray pass along any options it gets to the server... 

Also, I assume you're running the latest 6.5.2 build?

(In reply to comment #45)
> Command-line options don't work on SlimTray, they have to be passed to
> slim.exe:
> C:\Program Files\SlimServer\server\slim.exe --noupnp 
> Hmm, wonder how hard it would be to have SlimTray pass along any options it
> gets to the server... 
> Also, I assume you're running the latest 6.5.2 build?

I'll try again tonight, I am running the 6.5.1 build from the main download site, not a nightly build. Should I do both, use the lastest beta/nightly and use the command line option via Slim.exe?
So I should be able to kill Slim.exe via task manager and then open a cmd window and type in "C:\Program Files\SlimServer\server\slim.exe --noupnp" and that should respawn the process with the right switch, right?
Thanks, Matt

Please just dump 6.5.1 and use the latest 6.5.2 build.  It's very stable and may even fix this bug.

(In reply to comment #47)
> Please just dump 6.5.1 and use the latest 6.5.2 build.  It's very stable and
> may even fix this bug.

I have not dumped the 6.5.1 build yet, I'll try that on Sunday. HOWEVER, the switch works. I disabled the upnp and it have been running since last night w/o issue.
Thanks! 
Now how do I make SlimServer spawn itself this way when I turn my PC on? Right now the SlimTray is off, it does not even know SS is running. I also found out the hard way, I have to keep the MS CMD window open, for SlimServer to run with the --noupnp switch, I guess it's like a DOS shell?

This shure beats using the 400Mhz PC I loaded with SS to run on my LAN to not have SS crash!
Reagrds, Matt

Well, it may have been serpendipity or by plan, but 6.5.2 does not seem to have this issue. I downloaded it today (7/4/07) and SS has been running and serving content for several hours without issue. All the time WMC is running in the background as well.
Thanks y'all!

Marking fixed.