913 Error Code

I too got the update today. When I tried to add my music library to my Sonos, I ended getting an error code 913. One of the reason I I went to Sonos was to play my Apple I-Tunes music collection through there speakers. The ability to play my music collection just went away today. I was able to play my music when the new app first came out. If this is how it is going to be, I will be very upset with Sonos. 

Here is the fix for a PC. It takes two minutes:

1. Find a music folder that you want to “share” with SONOS (i.e. navigate to the folder on the PC).
2. Right click on the folder
3. Select “Properties” from menu
4. Select “Sharing” tab
5. Click “Share...” button (opens “Network Access” window)
6. Select your SONOS system from the pulldown menu in the center of the window.
7. Click “Share” button at the bottom of the “Network Access” window 
8. It took SONOS 10 minutes to add my library of 10K+ songs

Can’t you use the Apple Music service to do the same thing on Sonos?  Anything I have in iTunes is avaIlable in my local music library and also via Apple Music service on Sonos.  

Hi Giro, yes, I gad to do that too. Sorry I forgot to add that but it was my wifes Birthday and I'd had a beer 🍻  two!

Thanks 

Simon

Thank you very much for your Help. Problem solved !!! So Cool.

Any help on how to rectify using iOS grateful received.

What I don’t understand is why Sonos didn’t just transfer the settings over for the music library when updating.  There’s no reason to wipe it out during the update.  I know that Sonos isn’t supporting the outdated SMBv1 and HTTP protocols because of security reasons going forward, and that’s reasonable.  But once the update is complete, a good programmer should be able to create a procedure to check for these no longer valid protocols and warn users that the path to the music library is no longer allowed and they will need to adjust the protocols or recreate a new music library.  But local paths should be left alone.

Fair points!  Money influences all business decisions, good and bad.

Thanks to Scrubbrush and GIRO. I was able to add music files to PC using the solutions they provided. I wasted hours with Sonos customer service without any success. I was supposed to be making an appointment with escalation team that never happened. Very disappointed.

I would appreciate if someone can help. I have iPhone and iPads that have Sonos apps and connected to the Music files on PC via WiFi. Prior to this update, I could play music in subfolder in queue, add other files to the queue etc. Also there was a sleep timer. It’s not there. Any idea?

thank you.

I don't know why, but GIRO's solution doesn't work. I even tried different advanced sharing settings (read only, read/write). Still get that same annoying error. 

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 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.

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