Contributor I

Answered

Error Code 913 attempting to add Windows Folder to Music Library

Forum|Forum|2 years ago
May 19, 2024
73 replies
11309 views

This exact error has been widely reported here, but mostly for Macs. None of the official accepted “answers” for Windows provide a solution.

Running Sonos Controller for Windows 16.2.

This all started when I repped some of my CDs and tried to re-index the folder. It hung for hours. I let it run overnight, and it was still hanging. I closed and restarted the app. After that, any attempts to access the Music folder - or any subfolder - fails with the 913 error code.

I tried uninstalling and reinstalling the Controller. That has NO effect on this failure.

The Controller either suddenly won’t support WIndolws Folders, or it leaves some “residue” during indexing that cannot be removed by uninstalling the app. It could be hidden properties on the folders themselves, hidden Windows Registry keys, something.

This topic has been closed for further comments. You can use the search bar to find a similar topic, or create a new one by clicking Create Topic at the top of the page.

Best answer by bfbees

This solution worked for me:

Show previous replies

Lyricist III

Exactly!

Lyricist III

Actually here is what I am trying to add but when I hit next the infamous 913

Prodigy III

Sorry edited my previous reply…

Prodigy III

Right, so when you go into the wizard, choose network drive, the third option and enter

\\computername\music

Where computer name is your Windows PC’s name …

Lyricist III

Actually this is where the 913 occurs, it is pointing to my computer

Prodigy III

OK, so choose the third option, network drive and enter either

\\RK-HP-ENVY\Music

or

//RK-HP-ENVY/Music

and see if they get you further. Sometimes I’ve heard reports that slashes one way don’t work …

Lyricist III

No luck comes back the same thing. But it does take longer to respond, the Wizard response is 913 immediately. Let me play with it some more. If something works will let all of you know. Thanks

Prodigy III

OK the bit I’m not happy about is the fact your music is on your One Drive which I don’t think you have full control over as it’s in the cloud. Under

c:\users\richa

Create a Sonos folder, then copy some of your music, copy not move, into that folder and right click on it and select properties. Then select the sharing tab and it will say something like not shared with a Share… button. Click that. It will then ask you to select people to share with and in the drop down choose Everyone and permission level read.

Once done, and you re-run net share from the command line you should see Sonos in the list.

Then try and add again using the third option, but \\computername\\Sonos

And see if that changes anything. If it prompts for a username/password for now use your account details on Windows…

Lyricist III

Thanks for the ideas and input. I will in fact make a copy on a separate device attached to my computer that is visible to everything. Maybe it will work and that is fine. But for years I had my music on the One Drive local file and it worked fine. Starting around May after an update from Sonos, it just stopped working. They did something in the software that caused the library to not be found. I am not alone, someone else I know had exactly the same issue in the same time frame.

Prodigy III

Thanks for the ideas and input. I will in fact make a copy on a separate device attached to my computer that is visible to everything. Maybe it will work and that is fine. But for years I had my music on the One Drive local file and it worked fine. Starting around May after an update from Sonos, it just stopped working. They did something in the software that caused the library to not be found. I am not alone, someone else I know had exactly the same issue in the same time frame.

Unfortunately they made too many changes in one go and this was one of them. I think (not entirely sure) that the sharing via the wizards uses some kind of odd http sharing, not a network share. But, at the same time they rolled the new app, they also rolled new speaker firmware that disables SMB v1 and HTTP shares, so the speakers can no longer access the ‘old’ local library. If it is HTTP then it looks like they haven’t updated the wizards or just removed them. It’s just one giant mess that seems to be confusing many people.

I don’t think it’s SMB v1 related here as Windows doesn’t instal SMBv1 code these days by default and don’t think many would go and add it.

So, you now have to properly share a folder on the network for the Sonos speakers to see it. Transparent cloud drives probably get in the way here and this will be where peoples setups start to diverge quite a bit, OneDrive, iCloud, Google Drive etc…

Show more replies