"Sonos was unable to add the music folder"

Using a PC and followed every instruction. I can add individual folder but not add the entire library at one time .

John,

It has been awhile since I added libraries (and the restriction may have changed), but from what I remember, the music library can only be a "top/first level" node. For example, these are ok:
//myServer/MyMusic
c:\MyMusic

And these are not ok:

//myServer/first-node/second-node/MyMusic
c:\first-node\second-node\MyMusic

Just upgraded to Yosemite. Sonos took a dump. Not only can it not read the library folder, but it doesn't even recognize the computer. 

Get this shit fixed SONOS.

I'm having the same issue but I'm running OS X Yosemite as I'm beta testing it. Sonos may want to look into Yosemite as something in the new OS doesn't allow Sonos to share the Music folder I keep getting denied. I even tried manually.
I have the same problem and I have turned the firewall off!! is there a solution?

I'm having the same issue but I'm running OS X Yosemite as I'm beta testing it. Sonos may want to look into Yosemite as something in the new OS doesn't allow Sonos to share the Music folder I keep getting denied. I even tried manually.
There appears to be no solution, and none forthcoming. I have stopped using Sonos completely. If you are a Mac user, you are on your own. The last conversation I had with Sonos was I needed to call them on the phone from my home during their business hours and then give them access to my Mac to fix the problem. Basically, if you want to use a Sonos, get a windows machine.

First, Sonos tech support was very responsive. However, I corrected the issue without their assistance. Which isn't to suggest that this issue is NOT an issue. It is a massive pain-in-the-ass issue that needs to be solved by Sonos.

Here's what I found in my trial and error ... 

Note: it's worth mentioning that I replaced my iMac with an MPB during this process. The issues began with the upgrade to Mac Yosemite on my iMac and continued with a brand new Macbook Pro. 
- I followed every single suggestion I could find on the Sonos forums and support message boards to correct the issue. None worked.
- Changing the computer name. Changing the WIN name in network settings. Did not work.
- I tried mapping the controller to an external drive. This worked. Then stopped working. 

What I found with the new Macbook Pro:
- I ported over Sonos and all the support files
- Sonos found both libraries - external and local folder
- but NONE of the songs mapped - which means that all the playlists I had created couldn't find either local folder because it was still looking for the old mac.
- I deleted both libraries in Sonos. Unplugged Bridge. Unplugged my router. Plugged back in the router. Plugged back in Bridge. 
- Relinked the music libraries.
--- With the new Mac Sonos found the local Music folder. (I turned off the external HD to prevent Sonos from finding the backup music folder.)
- Even after all of this, I found that all of my playlists were jacked up. Half of the library played without a problem and half of the library would throw an error looking for music on the old (iMac) computer. 
- This is when I realized that Sonos has a problem overwriting playlists (paths to the music folder). It doesn't automatically update the song pathing either. 

In the end, I went through the entire process (three times) of resetting bridge, resetting my cable modem, resetting my router, deleting and relinking the music library in Sonos, and then REBUILDING ALL of my playlists to get the bloody Sonos app to read my music library. 

And I have no idea where along the line any of these steps "corrected" the issues that the Sonos app has "seeing" the local computer or the music library. But the entire process had me angrier than I've been in a long time. Especially because the very first time I set up Sonos, it took five minutes.

I wasted days trying to correct this problem after the upgrade to Yosemite and subsequent set up on a new machine. 

Sonos. This is a problem that needs to be corrected. And while you're at it ... let's get Spotify playlists hooked up too, shall we?

Look for Firewall rules that read like "Enable/Allow UPnP / DLNA". Assure you allow incoming as well as outgoing. This is often disabled by default as Torrent clients use UPnP to get through a firewall.

If you are attempting to add music files from a network share/drive assure NetBIOS ports are enabled as well.

For Mac users, if you installed Bonjour the ports should already be configured correctly.

Anyone know if there's a difference between "another location on my computer" and "networked device"?  They both appear to try to hit up \\hostname\iTunes for me.  Win7-64.

I wonder why if the library is on R:\iTunes it needs to know the hostname... and why it can't find it (I can navigate to both R:\iTunes as well as \\hostname\iTunes)

I am giving up. Sonos is just not serious about making their software work. It is simply ridiculous how difficult it is to get their stuff to work. Sonos, it you will give me my money back, I will gladly return your equipment.

Apple users, you are better off installing an apple TV and attaching a sound bar. I have had excellent luck with the Samsung sound bar. For about the same price as one Sonos Play 1 you can have a _stereo_ unit _with_ a sub-woofer and none of the problems of Sonos on a Mac.

Sonos, your stuff is just a joke. You should have fixed this long ago.

I'm having the same issue but I'm running OS X Yosemite as I'm beta testing it. Sonos may want to look into Yosemite as something in the new OS doesn't allow Sonos to share the Music folder I keep getting denied. I even tried manually.
not too sure what everybody problem is , i admit i had issues when i used Yosemite in the Beta version , but since the general release of the OS everything is working just fine , i have 2 mac on the network with their individual itunes library , adding them was a breeze , no problem at all .