AUTHORS
CATEGORIES
- Airsoft (2)
- Austin (8)
- Books (9)
- Cooking For Engineers (20)
- Credit Cards (2)
- Current Events (9)
- Deals (4)
- Dining (37)
- Fanpop (4)
- Food (808)
- Games (5)
- Hairy (6)
- Kitchen Gear (7)
- Life (24)
- Miscellaneous (6)
- Movies (15)
- Orthogonal Thought (6)
- Personal Computers (10)
- Photography (158)
- Rant (9)
- Ruby on Rails (2)
- San Francisco (5)
- Soap Making (5)
- Television (11)
- Texas (1)
- Things We Like (11)
- Travel (11)
- Wear or Not (1)
- Web 2.0 (9)
- What I Ate (861)
- Wikipedia (5)
- Windows 10 (3)
- Windows Mobile (1)
- WordPress (1)
ARCHIVE
- September 2018 (1)
- September 2017 (1)
- March 2017 (1)
- September 2016 (2)
- August 2016 (2)
- September 2015 (1)
- November 2014 (1)
- August 2014 (1)
- January 2014 (1)
- September 2013 (1)
- December 2012 (1)
- November 2012 (3)
- September 2012 (1)
- August 2012 (2)
- June 2012 (2)
- February 2012 (1)
- January 2012 (4)
- December 2011 (4)
- October 2011 (2)
- September 2011 (5)
- August 2011 (1)
- July 2011 (2)
- April 2011 (2)
- February 2011 (5)
- January 2011 (12)
- December 2010 (37)
- November 2010 (30)
- October 2010 (25)
- September 2010 (30)
- August 2010 (32)
- July 2010 (34)
- June 2010 (31)
- May 2010 (35)
- April 2010 (35)
- March 2010 (33)
- February 2010 (34)
- January 2010 (33)
- December 2009 (30)
- November 2009 (31)
- October 2009 (30)
- September 2009 (31)
- August 2009 (34)
- July 2009 (34)
- June 2009 (34)
- May 2009 (33)
- April 2009 (32)
- March 2009 (42)
- February 2009 (38)
- January 2009 (57)
- December 2008 (40)
- November 2008 (30)
- October 2008 (33)
- September 2008 (22)
- August 2008 (5)
- July 2008 (5)
- June 2008 (11)
- May 2008 (13)
- April 2008 (10)
- March 2008 (29)
- February 2008 (18)
- January 2008 (28)
- December 2007 (1)
- November 2007 (4)
- October 2007 (5)
- September 2007 (10)
- August 2007 (14)
- July 2007 (10)
- June 2007 (9)
- May 2007 (21)
- April 2007 (21)
Fixing SONOS "Unable to play" song / "Unable to connect" to local music library problem on Windows 7
Posted 7 November, 2014 at 4:52pm by Michael Chu(Filed under: Personal Computers)
In general, I've been quite pleased with my Sonos units, but I've been plagued with a problem accessing my personal music library for more than a few days at a time. I think i have a fix for my problems now.
I run the Sonos application on a Windows 7 machine which I use as a file server and media server (running a variety of transcoding software for various devices around the house). My music library is stored on a local drive on that machine (this detail is probably unimportant as Sonos never accesses the library locally and always uses the network share for the library). My first problem was the Error 900 problem which occurs when the stack size of the network server is too small to buffer the data (or something). The solution was to use regedit (Start->Run->regedit.exe) and modify key:
Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanmanServer\Parameters\IRPStackSize
from the default value of 15 (decimal) to either 18 or 24 (decimal). I upped mine to 24 and it got rid of the Error 900 problem, but I would still routinely lose connection to the music library. (See Sonos Error 900 FAQ.)
When I say "lose connection", I mean that when I try to play a particular song I get the following error:
Unable to play 'SONG NAME' - unable to connect to //SERVER_NAME/Music
In addition, when browsing through my albums, the album images do not load (this is a faster/easier test so for months I used this quick check to see if I'd lost the ability to connect to the music library or not). When I contacted Sonos Customer Service, they suggested I try increasing the IRPStackSize in increments of 3 (but didn't recommend going past 24) as well as disabling other shares on the server (not an option). I did find that restarting the Windows Server service (Services -> Server -> Restart service) which did allow Sonos to reconnect so for a while I did that and eventually wrote a batch command that I could issue to speed up the process. However, that still meant that the library was unavailable most of the time and needed manual intervention to get it to reconnect (not ideal when trying to explain the process to my wife).
A couple weeks ago, I found a fix related to other network limit issues that seems to work in resolving this library issue. I used regedit and modified key:
Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanmanServer\Parameters\Size
and set it to 3 and have not had a problem since. No more service restarts; no more "unable to play" and "unable to connect" errors.