913 Error Code

Just spent 45 minutes with a useless individual at Sonos “non-support.”

Helpfully, he informed me that the destruction of my local library access is a “KNOWN ISSUE.”

Yes, I, and thousands of others are aware that this is a known issue. Thank you for that.

Unfortunately, his “workaround” did not, uhm, work. At all.

So I still have no local library access.

Thanks to those of you who have spelled out very specific steps for reacquiring my library. Unfortunately, my attempts using these steps failed, and SoNOs NonSupport attempted the same steps several different ways -a dn those all failed as well.

TO RECAP:

1. SoNOs deceived users into downloading an app that completely ruined the experience of thousands of previously loyal customers
2. SoNOs happily reported that they found themselves courageous in deceiving their customers
3. SoNOs have done *-ALL fixing the issues that they courageously caused
4. SoNOs, not satisfied having ruined the app, and refusing to revert to the prior app version, had THE BALLS to send out marketing emails to pissed off “users” about a pair of headphones you could NOT PAY ME TO USE
5. SoNOs, still not completely satisfied with the results of all their “couraging,” decide to jump into our desktop controllers and remove users’ access to their own local libraries - YOU SEE, it was not enough that they absolutely * local library access in the botched app
6. THEY HAD TO GO ALL THE COURAGEOUS WAY AND STEAL MY LOCAL LIBRARY ACCESS FROM MY OWN DESKTOP
7. BUT, WORRRY NOT, DEAR “USER” FOR THIS IS A KNOWN.* . ISSUE.

*Moderator Note: Modified in accordance with the Community Code of Conduct.

Thanks Scrubbrush and GIRO. This worked for me. I’m very grateful. I won’t repeat my thoughts on the new app. I have to try and accept that progress is sometimes painful at first.

Thanks to the Sonos community and DXNY for the Windows fix -- really quite simple. I don’t understand: a.) how Sonos’ update team didn’t have a test bed to catch this problem; b.) didn’t send out a prior notification of this kind of change; c.) didn’t embed a notice in the actual update itself; d.) could have sent out an update of this type just before a long weekend; e.) made users wait for 2+ hours for support call assistance; and f.) by now have sent out an apology to users for the disruption. Somebody in the service and support team needs to be looking for a new job.

it isn’t working for me either! 

That’s definitely not the problem for me - my NAS drive is already SMBv2, and I still get the 913 error. 

Did you download the Sonos Controller for PC/Mac and re-add the share, then let it index?  Then you may need to close out your mobile app completely and restart (or even reset the app and reconnect to your existing system). 

Scrubbrush and Giro,

My system was headed for the trash until I found this thread. ❤️❤️