Skip to main content

Following the recent Sonos update, the desktop application refuses to add the library. Despite numerous results on search, Sonos seemingly is refusing to resolve the 913 issue.

It was suggested I move the library to an external hard drive. Which I did and now I get the 1002 error. Sonos resolution to this is meaningless and doesn’t help. 

Apple Music will play through Sonos but the Sonos app refuses to load the library which means I can’t play any music using either the desktop or the mobile app.

Has anyone found a solution this to and please in plain English. 
There are a lot of answers which are gobbleeegook...

I’m having the same issues. The 913 error switched to the 1002 after changing file sharing settings.

It’s infuriating. 2 month + without access to my library.


Issue is something to do with the SMB versions. 

The work around is to share each folder up to the point where the music file is stored. This could be quite tedious and time consuming.

The other option is to copy your music to a separate hard drive, which can be plugged into your computer, then map the NAS drive to that drive. The permissions are different for a networked drive than for a system drive, where your iTunes folder is.


Issue is something to do with the SMB versions. 

The work around is to share each folder up to the point where the music file is stored. This could be quite tedious and time consuming.

The other option is to copy your music to a separate hard drive, which can be plugged into your computer, then map the NAS drive to that drive. The permissions are different for a networked drive than for a system drive, where your iTunes folder is.

Unfortunately I’ve spent a considerable amount of time trying both work arounds with no success. I’m going to have to accept defeat with Sonos and move onto a more reliable set up. 


Sorry to hear that. Good luck.


I have exhausted everything I have even tried Sonos chat and was #15 in queue. After 25 minutes I didn’t move from 15 so I quit chat. I have spend hours and hours trying to get this 1002 error resolved and am finally giving up and moving to Devon Bluetooth speakers. Too bad for Sonos as I was looking too update my system but not anymore. Any company that rushes a software update, takes great functionality out of their app and gives us a broken system is either totally incompetent or run by idiots.


I have run into the same problem.  My music is on an external drive on an iMac 27.
I had to move my music/audiobooks to an external drive due to the size they had become but SONOS 2 wouldn't add the folder.
It was because the drive was formatted in Apple APFS format.  I moved all the files to my the drive I had purchased to build an NAS -- a 12 hour process.  I reformatted the external music drive to Mac OS Extended (Journaled) which is the HFS+ format that SONOS says it wants.  I moved the music files back to the now reformatted drive.  Still no joy.  SONOS 2 refused to recognise the folder.  I note after reading all of the comments here that all levels of folders had been made shareable.  I moved a few folders of music to the default Music folder on my main iMac drive.  SONOS 2 still refused to add the folders.  Same error message.  

Sonos was unable to add the music folder

Unable to add the shared folder “BFCiMac/Music”to your Music Library (913).

My eMail to Support@eMail.Sonos.com and SONOS@eMail.Sonos.com have not received any response.  I’m trying to forward the previous messages to Patrick Spence — SONOS CEO <CEO@SONOS.com>

 

SONOS 5, 4 x SONOS One, SONOS Boost, and SONOS Arc.  Only the Arc is of any use these days as it is attached to my TV.


Any help?


Only the NAS based solution seems to work with the current controller version. And by NAS I mean a box (with disk storage) which hold your music but is connected to your router (via Ethernet), not an external drive connected directly to your computer. How the NAS drive(s) are formatted does not matter, as the data is accessed via the SMB protocol. The only caveat is that the NAS must support either SMB2 and/or SMB3 to be compatible with Sonos S2.


Same issue here. Cannot access my music library on my Mac - get error 913 each time. Have put some music on my old Apple AirPort NAS device but either get 1002 error or told to check UserID and Password each time I try to connect to it. What on earth is Sonos doing to fix these issues1!

 


What I ended up doing was adding Sonos to the System > Privacy & Security > Full Disk access (whether this made any difference)

Then I had added my Desktop as a folder, then I added the folder I wanted. e.g Users/MyName/Music/Downloaded  (I didnt manually type it, chose browse and selected the folder)

If I tried to add the actual music/downloaded folder first it would fail and show that 1002 error claiming couldnt add the shared folder.

Im using Sonos S1 Controller on a Macbook Pro with Sequoia if that helps anyone since the OS update.


I know this is going to seem odd, but… even though the Mac desktop controller has three options to add your music library, 2 of them do not work and never will again. For some reason, even though Sonos have released minor updates to the desktop controller since the new App release, Sonos have left these broken wizards in place which is confusing. 

The *only* way to allow Sonos to access drives on a Mac is to enable File Sharing in settings and add the folder contains your music there. If you give everyone read access that ought to be enough. 

The Airport I believe only supports SMB1 which was removed from Sonos speakers at the same time as the new App was released. The broken two options in the desktop controller installed a Sonos written HTTP service that the speakers used to access music. At the same time Sonos dropped SMB1 access, they also dropped HTTP… 

For S1 on Sequoia, you may need to add the Sonos HTTP helper service if you can find it to allow it to have access to folders etc. This is something that Apple may automatically address in a later update if enough people complain. Else the sharing method above may function, I’m not sure if S1 supports SMB2 or 3. SMB1 is unlikely to be enabled by default. 


S1 only supports SMB v1, there isn’t enough space in the memory for those devices to hold a kernel that will support higher versions of SMB. IMHO, that’s one of the reasons for not only more memory on newer devices, but a motivating force for S2. Amongst others, I’m sure.