I get the same error every time 😠 (running desktop client on mac osx)...any help is appreciated:
'//AlexMBP/Music' is no longer available. The device where the music files are stored may not be powered on, or the path may have changed.
Go to Manage > Music Library Settings to check the path name
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.
There's an incursion limit error showing in your diagnostic report. This usually happens when your Sonos system is trying to index a shared folder that has many other folders within it, many levels deep. If your GoFlex public folder has some nested folders, how many folders deep do they go? Would it be possible to point your Sonos system at a more specific folder for your music share so your system doesn't try to index quite as many folders?
Help others find useful content by clicking the like button and selecting the best answer to your question.
I have the exact same problem as everyone else here. I have many music files (~40k) that iTunes files into folders, as I'm sure you're aware of. Is this indeed the issue?
If so, it is absolutely bewildering as to why Sonos hasn't taken this into account, as the whole philosophy of the company would seem to be providing high quality audio hardware to people who enjoy many styles of music.
Essentially, because we like music so much, and have accrued so much over the years, we are not able to listen to them -- is that what you're saying?
Hi Geod,
This started happening to me after the latest update. But the workaround suggested by Jeff S worked for me. The NAS share I had previously pointed the Sonos application to at looked something like this:
\\NAS\Public\
but I made it more specific as something like:
\\NAS\Public\Audio\Music
after which the problem disappeared. I may miss some files in other directories but at least it works.
I suspect a developer changed a 'maximum recursion path length' constant somewhere.
I appreciate the input, Rex. Unfortunately, I don't have an NAS -- all of my music is on my computers and iPhone. At this time, I don't feel the need to (or feel I should HAVE to) purchase and set up an NAS, for this specific application.
I spent a significant amount of money for my Sonos system, in order to have a wireless system through my house that was touted as easy and seamless integration with my current technologies. It's extremely frustrating to me that I would need to purchase even more hardware in order to make this work, just because of a lack of foresight in software development by Sonos.
I REALLY want to like this company, because the quality of the hardware is exceptional, and their customer service is supposed to be great, but after all of these troubleshooting steps taken (I've tried all that are mentioned in any relevant thread except for things NAS-related, of course), I'm still left without a solution.
I'm always willing to try anything else that anyone might be able to suggest, though.
Hmm that would be too bad if Sonos can't support that; you may have exposed a bug introduced in the last release, IMO. Run a diagnostic and record the report number - I'm hoping for you that Sonos staff will ask you for it, then investigate.
That's what I'm hoping is the case as well. Just a pre-emptive action here -- for any Sonos staff that see this conversation, my report number is 6532682. Let's talk.
Thanks for the attempted help, Rex. Much appreciated.