Error Code 913 attempting to add Windows Folder to Music Library

Having read many of the posts about this problem, and having it myself, I have sent the following email to the CEO. It will be interesting if I get an answer, and hopefully a solution:

Good morning

I have returned from a business trip to find that I can no longer play my iTunes library through my Sonos system. I have used this facility succesfully for at least 5 years.

I have tried everything to remedy this, but the iTunes folder will simply not load - and error code 913 is shown every time. I have checked the file, and sharing is enabled / allowed. I run Windows.

Looking on your forum, I see this is a new problem and everyone seems to have it who tries to play their iTunes library through Sonos..

What are your plans to rectify this please? If you are not going to rectify it, my Sonos system is no use, and I really would not expect that.

I would also ask, why does Sonos not reply to the thousands of comments on your own platform (Sonos community) relating to this issue?

I look forward to your reply, and a solution.

Just joining the THOROUGHLY FRUSTRATED club. Came back from holiday to find my music library removed from Sonos app after 10 years. S2 controller App updated to version 16.2, Mac Air running on 14.5. I have spent hours trying all the possible fixes as per the Community to no avail. Where is Sonos support when you need it? 

Hi - I just want to emphasize one aspect of the solution to the 913 issue kindly documented above by davefromtennessee. I am running Windows 10 and the latest Sonos PC controller build. 79153290. Simply adding a share for your Music Folder (Properties->Sharing ) is not enough. You need to utilize Advanced Sharing ( Properties->Sharing->Advanced Sharing->Share this Folder(check this). While I was there I also did the following from this screen:Permissions->Add->Advanced->Find Now->click Sonos->OK->OK. After that I went back into the Sonos PC Controller and it successfully added the Music Library. I’m providing a screen shot of the nested Permissions screen below. Also, before doing this, I had a chat with Sonos Support and their diagnostic said that I was trying to use SMB1 so they told me that was the problem. I doubted this based on my own experience and as you see it had nothing to do with the problem so watch out - I know they are trying hard but their own diagnostics may be giving bad info. Good luck. 

Hi - I just want to emphasize one aspect of the solution to the 913 issue kindly documented above by davefromtennessee. I am running Windows 10 and the latest Sonos PC controller build. 79153290. Simply adding a share for your Music Folder (Properties->Sharing ) is not enough. You need to utilize Advanced Sharing ( Properties->Sharing->Advanced Sharing->Share this Folder(check this). While I was there I also did the following from this screen:Permissions->Add->Advanced->Find Now->click Sonos->OK->OK. After that I went back into the Sonos PC Controller and it successfully added the Music Library. I’m providing a screen shot of the nested Permissions screen below. Also, before doing this, I had a chat with Sonos Support and their diagnostic said that I was trying to use SMB1 so they told me that was the problem. I doubted this based on my own experience and as you see it had nothing to do with the problem so watch out - I know they are trying hard but their own diagnostics may be giving bad info. Good luck. 

 

My screenshot looks different, but I had also added Sono to give it explicit permissions. It didn’t fix the problem.

Xris,

Sorry you’re still having trouble. I am guessing that you got this screen from the Security tab when  you opened up Properties on your Music folder. So I just want to verify that you also did everything outlined above by daveintennessee from the Sharing tab. If you did then I’m stumped.

Has anyone solved this for Mac’s yet?    Was told by online chat to phone tech support but it’s a 75 min wait right now

Thanks!

I have the same issue on my Mac - as above I have tried everything the Community have identified. We are now mid June - I thought there was to be an updated Controller App which would solve the issue by now?

Has Magsy29 received a response from the Sonos CEO?

Will have to try that 75min wait for a Sonos tech some time - still frustrated

BernieCM

If it says “expected wait time” of 75 minutes by the automated answer, it will be at least an hour and a half before Level 1 picks up! Don’t bother, they simply don’t have the answer. They read about the fix (for most Windows users) from here just like us. I am supposed to get a Level 2 scheduled appointment (re-escalated a second time) but they have not honored that commitment -- I think Level 2 has no idea either. Sonos is truly disrespectful of its customers. Fend for yourself seems to be the answer. It will be a Harvard Business School case soon on how to destroy a franchise.

Thanks

Thanks to some extremely good comments in this thread I was able to solve this.

From this it is clear to me that with some clear and well articulated instructions, and some warning in advance, this would not be a problem.  As it is -- Sonos has really created a giant clusterfork for nothing.  What a ridiculous fiasco.

They did send out a warning, but IMHO, it wasn’t sufficient.  It merely stated that SMB v1 and HTTP sharing will no longer be supported.  They should’ve done more to let people know in less technical terms what to expect and how to rectify.