ExtraService failed while processing [EpisodeFolderCreatedEvent]: The network path was not found

Sonarr version (exact version): 2.0.0.4389
Mono version (if Sonarr is not running on Windows):
OS: Windows 10
((Debug logs)):
(Make sure debug logging is enabled in settings and post the full log to hastebin/pastebin/dropbox/google drive or something similar, do not post them directly here)
Description of issue:
System.IO.IOException: The network path was not found.

at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
at System.IO.FileStream…ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
at System.IO.StreamWriter.CreateFile(String path, Boolean append, Boolean checkHost)
at System.IO.StreamWriter…ctor(String path, Boolean append, Encoding encoding, Int32 bufferSize, Boolean checkHost)
at System.IO.File.InternalWriteAllText(String path, String contents, Encoding encoding, Boolean checkHost)
at System.IO.File.WriteAllText(String path, String contents)
at NzbDrone.Common.Disk.DiskProviderBase.WriteAllText(String filename, String contents) in M:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Common\Disk\DiskProviderBase.cs:line 235
at NzbDrone.Core.Extras.Metadata.MetadataService.ProcessSeriesMetadata(IMetadata consumer, Series series, List`1 existingMetadataFiles) in M:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Core\Extras\Metadata\MetadataService.cs:line 223
at NzbDrone.Core.Extras.Metadata.MetadataService.CreateAfterEpisodeImport(Series series, String seriesFolder, String seasonFolder) in M:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Core\Extras\Metadata\MetadataService.cs:line 124
at NzbDrone.Core.Extras.ExtraService.Handle(EpisodeFolderCreatedEvent message) in M:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Core\Extras\ExtraService.cs:line 119
at NzbDrone.Core.Messaging.Events.EventAggregator.PublishEvent[TEvent](TEvent event) in M:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Core\Messaging\Events\EventAggregator.cs:line 56

Make sure Sonarr can actually access the network path and if you’re running Sonarr as a service you’re not using a mapped network drive as explained in the ((FAQ))

If you’re still having issues we’ll need to see the full ((debug log)) as requested when you opened this thread.

The exe is launched from the startup folder. I was setup using UNC paths. I have 3 NAS devices and 2 where failing. I am not using mapped drives. I am currently using symbolic links… I did this trying to get around the errors and the files not getting moved to the nas drives. One of the NAS drives is still working fine and is using symbolic links… I did this for all of them trying to get it fixed. I can do what ever you like me to do with it.

I have enable the debug and all the files are located here:

https://drive.google.com/drive/folders/0B7mvVzVX8inWa1p6TGtCekkyWk0?usp=sharing

I don’t see that particular problem in the debug logs, but there are other errors copying files.

So the symbolic links join all 3 NAS devices so Sonarr sees them as one?
Are you able to move files around in Windows explorer using the same symbolic links that Sonarr is using?

Yeah. It is the coping of the files that I am having an issue with. The symbolic links are just local pointers to the unc paths. They are working from windows fine. Currently after a reboot Sonarr is seeing the paths now as well. But it will break again. The links are not making the NAS appear as one but just makes them appear to be a folder on the local C drive. I am able to move files around in windows fine. I notice is broken when files are starting to fill up my downloads folder since they are not being moved and processed. These were all setup with UNC paths and worked until about 2-3 weeks ago. I am not sure if an update of Sonarr casued the issue but I saw in the change log there was a change that had to do something wilh filebrowser. If i open that to say add a new show and I go to the unc path or the local folder that has the symbolic links it is not able to see into the folders.

Can I send you anything else that would help?

I can’t think of anything that would have changed that would have affected how Sonarr accesses them. The errors are generic errors coming from .net which is failing to get it from the OS. Could be another update outside of Sonarr that affected it, but not much to go on.

The only thing that would give more information would be ((trace logs)), but it wouldn’t give more details on the error.

Were you able to find anything in the trace logs?

No, you need to enable trace logging and post them somewhere first. The lone trace log on Google docs show nothing beyond the startup logging.

ok. I have uploaded the trace files and all the debug info as well.

https://drive.google.com/drive/folders/0B7mvVzVX8inWa1p6TGtCekkyWk0?usp=sharing

How is Sonarr being run? If it’s via a Windows service, try running NzbDrone.exe or NzbDrone.Console.exe as it may be related to: https://github.com/Sonarr/Sonarr/wiki/FAQ#why-cant-sonarr-see-my-files-on-a-remote-server just surfacing a different way due to the symlinking.

Also try having Sonarr connect directly to the shares, bypassing the symlinked folders to see if the issue persists.

it is being ran via the startup folder. I can add the folder by \UNC\path but that is the way I started with and was getting the error. Then I changed over to the symlinking. I will try the different exe link you sent

What did you see in the trace files? Look like I am running via the startup like is recommended. I will change a show to point to the UNC path and run a debug and trace again

They both do the same thing in the end, running the other one won’t change anything except get you a console window or a tray icon depending which one you’re running now.

Same errors as before plus System.IO.IOException: The parameter is incorrect..

They’re coming from trying to create folders (which is not normally an issue) in the trace log I looked at. Tough to say exactly what is causing it, but it seems related to the environment,

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.