What Does Sonos Error 913 Mean and How Do I Fix Music Library Share Problems?
- Share is configured with SMBv1
- Folder was added with unsupported method
- Permissions on shared folder are incomplete
Problem Description
Sonos Error 913 appears when the app cannot access a music share using a supported SMB protocol. In many setups the share is still configured as SMBv1 or added using outdated folder methods. Sonos expects network-path sharing with SMBv2 or SMBv3.
Symptoms
- Error 913 appears when adding music library
- Library share works on computer but not Sonos
- NAS folder is visible but cannot be added
- Issue started after NAS or OS update
- Sonos desktop app share method fails
- Network path add succeeds for some shares only
Recognize these? Here's what usually causes it.
Common Causes
- Share is configured with SMBv1
- Folder was added with unsupported method
- Permissions on shared folder are incomplete
- Network path format is incorrect
- NAS protocol settings are legacy
- Credential mapping differs from expected path
Most fixes happen in the first 3 steps.
Do not rely on legacy local-folder shortcuts in desktop app flows because Sonos library sharing now expects network path methods.
Tools & Requirements
These tools will help you complete this fix.
As an Amazon Associate we earn from qualifying purchases.
Step-by-Step Solution
Identify the exact share type failing
Confirm whether the failing library is on Windows, macOS, or NAS. Error 913 behavior differs slightly by source, but all paths point to protocol or share-method mismatch. This first split helps you apply the right corrective path quickly.
Needed for this step
1200Mbps WiFi Extender Signal Booster for Home,...
$25.99Verify SMB protocol level on source
Check that the shared folder uses SMBv2 or SMBv3. Sonos does not support SMBv1 for this workflow. On NAS devices, update SMB settings in the admin panel and save before retrying library add in Sonos.
Use network path based library add
Add the library by explicit network path instead of deprecated local folder shortcuts in desktop app flows. Sonos documents this as the supported approach for current library-share behavior and it resolves many recurring 913 errors.
Review share permissions carefully
Confirm the share account has read access and that path credentials are correct. Partial permissions can look like protocol failure. Clean permission mapping is required before Sonos can index and browse the library successfully.
Re-add share and validate indexing
Remove stale failed entries, add the corrected share path again, and run a library update. Verify artists and albums populate normally. If 913 persists on NAS after SMB changes, check vendor docs for per-folder protocol override settings.
Quick Solutions
Still having issues? This is usually the deeper cause below.
If this comes back after following these steps, check whether a recent app or firmware update reset a default setting — the fix works, but the setting gets reverted silently.
Error 913 is usually protocol and share-path configuration, so fix SMB settings before reinstalling Sonos controllers.
This issue almost always looks more complex than it is — the majority of cases trace back to a single setting, a stale credential, or a default that shipped wrong.
- Share is configured with SMBv1
- Folder was added with unsupported method
- Permissions on shared folder are incomplete
- Network path format is incorrect
- NAS protocol settings are legacy
Before you go — try one of these (they fix most cases).
Official Manufacturer Manual
Sonos provides official product documentation through their online manual rather than downloadable PDF. Access setup guides, troubleshooting steps, and product specifications for your Sonos Music Library Share Access.
Source: sonos.com
Need More Help? Sonos Support
Note: The contact information below connects you directly to Sonos's official customer support team, not Trunetto. They can help with warranty claims, device replacements, and advanced technical issues.
