Local Content from mapped drive

I have switched to running Channels DVR on Windows 10, and I’m having trouble getting “Local Content” from a mapped drive.

Before running as service, the mapped drive was able to be chosen directly from the settings area. (Drive L:\Movies_Storage). When I configured it this way, I got the following error: 2021/06/06 08:24:27.792541 [ERR] Failed to read directory L:\Movies_Storage: Readdir L:\Movies_Storage: The system cannot find the path specified.

So I searched the forum, and discovered that some solve this by running Channels as a windows service, so I did that. Now, channels can’t see drive L at all, so I need to configure it as a network location. When I do so, I get the following error: 2021/06/06 13:58:59.413400 [ERR] Failed to read directory \zLab-Titan\Video_on_Titan\Movies: Readdir \zLab-Titan\Video_on_Titan\Movies: The system cannot find the path specified.

What are the troubleshooting steps to take this to a solution? I re-mapped all of my mapped drives, and I also edited the service to log in as my user account, rather than the default.

Please help…

Window Services cannot not see mapped drives.

Could he use a UNC path like \\192.168.0.12\Movies_Storage
I think you would have to use curl to put the path in the settings though.

UNC will work.

You might try this ....

How to map network shares into drives to a Windows service permanently (ibm.com)

Services running as the default “Local System” won’t have access to network resources. You should try running it as a user that has permissions on the share, or you could try the built in “network service” user.

Thanks for all of the replies, guys!

  1. I switched to a UNC path when I switched to running as a service. This didn't help.
  2. I'm running the Windows Service as the same user account that has full control privileges to the share.
  3. I updated to the beta release just now... No change.
  4. I switched the UNC path to the IP Address, rather than the name of my file server. Here's the error message:

2021/06/06 16:34:21.850106 [ERR] Failed to read directory \zLab-Titan\Video_on_Titan\Movies: readdir \zLab-Titan\Video_on_Titan\Movies: The system cannot find the path specified.
2021/06/06 16:36:12.381585 [ERR] Failed to read directory \192.168.1.14\Video_on_Titan\Movies: readdir \192.168.1.14\Video_on_Titan\Movies: The system cannot find the path specified.

Can you post a screenshot the the Web page where the unc path is defined ...

This is what it looks like right now.

I think you have to end it in a \ after movies

Example Enter UNC path to network share, i.e. \\COMPUTERNAME\SHARENAME\

Screenshot 2021-06-06 182140

Ok, wow, I never imagined that this path could only be one directory deep. I created a new share on my file server, and go directly to this path, and this is the error that I’m seeing now: (tried by name, and then by IP)

  • 2021/06/06 20:42:19.403057 [ERR] Scanner error walking \zLab-Titan\Movies: Rel: can't make \zLab-Titan\Movies\American Made (2017).mp4 relative to \zLab-Titan\Movies
    2021/06/06 20:42:22.993360 [ERR] Scanner error walking \zLab-Titan\Movies: Rel: can't make \zLab-Titan\Movies\American Made (2017).mp4 relative to \zLab-Titan\Movies
    2021/06/06 20:43:13.995003 [ERR] Scanner error walking \zLab-Titan\Movies: Rel: can't make \zLab-Titan\Movies\American Made (2017).mp4 relative to \zLab-Titan\Movies
    2021/06/06 20:45:01.193881 [ERR] Scanner error walking \192.168.1.14\Movies: Rel: can't make \192.168.1.14\Movies\American Made (2017).mp4 relative to \192.168.1.14\Movies
    2021/06/06 20:45:05.967341 [ERR] Scanner error walking \192.168.1.14\Movies: Rel: can't make \192.168.1.14\Movies\American Made (2017).mp4 relative to \192.168.1.14\Movies
    2021/06/06 20:50:38.220986 [ERR] Scanner error walking \192.168.1.14\Movies: Rel: can't make \192.168.1.14\Movies\American Made (2017).mp4 relative to \192.168.1.14\Movies
    2021/06/06 20:55:38.456972 [ERR] Scanner error walking \192.168.1.14\Movies: Rel: can't make \192.168.1.14\Movies\American Made (2017).mp4 relative to \192.168.1.14\Movies

It can be more than one directory deep has to end in a \

These are mine and it works ....

2 Likes

Thank you for helping me! That was it! I needed a final backslash at the end of the UNC Path.

It’s weird, because the log shows the backslash is present, even though it wasn’t in my config. (Although the text in the dialog box clearly say I needed it.)

Again, thank You!

2 Likes

The issue with the trailing slash requirement should be fixed in v2021.06.08.1721.

I know that will fix the "Rel: can't make x relative to y" error.

But not sure about the "The system cannot find the path specified." issue.

1 Like