TV Rename won't recognize NAS

[Benny G]

Hey everybody,

for the last two days TV Rename doesn't find my network storage, which I use as a media library, anymore. I updated to the new version but that didn't help either. What really makes no sense to me is that it's been working fine for the last year and I haven't changed any of the settings!

If any of you have a suggestion I would appreciate it. I really don't want to go searching for another media management tool...

[Sparky53]

Hi,

Sorry to hear you are having troubles, but TVR definitely works with network drives

Couple of questions for you.

Can you take a look in the logs and see whether anything helpful is recorded there?

What is the format of your network paths? Any details of you nas setup might help.

Cheers

[Michael Hurwood]

Hi Benny,

Just thought I'd add that I too have all my shows on network drives with no problems, but quite some time ago I did move away from Drive Mappings (i.e. giving the network drive a drive letter) to using the UNC path (i.e. \\Server\Share\FolderEtc.) as I found that more reliable.

(And that's not just reliable for TVRename, but reliable for all windows programs. In my day job we regularly have problems where a drive letter gets given a "cross" on it in Explorer and programs stop working until you double-click on the bad drive which forces Windows to reconnect it, the cross disappears and software starts working correctly again.)

Cheers,

Michael 

[Benny G]

Had it using the UNC path. Unfortunately it is recognized as a network device, while TV Rename only appears to see computers in the network. Personally I've chamged to a different software, but I hope the problem will be adressed in the interest ofother users.

[Andy B]

Just a thought...

I'm sure I saw something similar to this a while ago where a Windows 10 Security Update broke access to CIFS shares that were on one of my NAS' boxes that happened to be in a different workgroup, I'm sure it blew out the ability to browse the device but if you knew the full path you could still read a file.

[Sparky53]

HI Benny,

Sorry to see you go. We'd like to resolve the issue in case you over come back or it is impacting others. Could you show us a screenshot of how the device looks in Explorer and what TV rename shows please? That might help us diagnose why TV Rename can't see the device

Cheers

[Sean Miller]

I started having this issue after I upgraded to 2.3.2 but never had an issue with it in any of the previous versions. I have attached a screenshot of both the tvrename add search folder screen as well as my network locations.

[Michael Hurwood]

Ah, OK, let's just be clear here...

When you say "doesn't find my storage", do you mean that if you manually type the path into a TV Show, it doesn't work and the program cannot process that folder (possibly giving extra error messages during a scan), or is it just the "Browse" interface which is at fault when you're first trying to set up a show?

Cheers,

Michael

[Sean Miller]

I just tried again today and now it is working. Not sure what changed but before I wasn't able to add my network search folder through the "Browse" interface.

[Michael Hurwood]

I'm pretty sure that whole dialog is just a standard Windows system call. I.E. we haven't designed that dialog at all and we have no control over what you see in it and what you don't. It's like the "standard" File Open and File Save dialog boxes that 95% of applications use.

A drive letter can disappear from a dialog like that if you're running as just the TVRename program as Administrator (or any account other than your standard one, for that matter) because drive mapping are part of your "Windows session"; launching a program as administrator starts a new session with no default drive mappings.

Could it have been something like that?

[Frank de Jong]

I'm working with 2.3.1 and have changed the base-folder for 1 show into an UNC location.

In this version it's working like a charm.

I'll update to the newest version and let you know whether or not it is still working.

-----------------------------------------------------------------------------------------------------------------------

UPDATED to 2.3.2

1. The UNC location is still working!
   
2. When using the "Browse"-interface, I can also add an UNC location.

My conclusion:The UNC problems are NOT related to TV Rename.

Personally I think they are caused by for instance an OS-update òr some other software that was installed.

The problems can even be caused by a change on the NAS!

[KB]

**POSSIBLE FIX**

I had the same problem sometimes as Sean on first install. It wouldn't find my network mapped drives in my NAS. 

But Michael gave the clue as to what it could be with the Dialogue being a Windows call.

Anyways this should fix it.

1. Open up task manager (CTRL + ESC)
2. Click on the details tab
3. Find Explorer process and right click and end task
4. Click File > Run New Task
5. Type explorer in the box and press enter

Basically explorer just need a swift kick up the pants to reset the dialogue box. Should find your drive after that. Also try running TV Rename as Admin.

Hope this helps someone.

[Steven K]

I find anytime the software is updated with a newer version or freshly installed, none of the network drives work until the program is shutdown and restarted again.

[Michael Hurwood]

This is correct. This is because the installer runs as Administrator, hence if you select the "Run after installation" option at the end of the installer then it will also run TVRename as administrator.

Problem is, your drives are only mapped for your regular User account, not for the Administrator account.

*Always* untick the "Run after installation" option at the end of installing an update and just start TVRename normally instead.

Really, we should remove the option to automatically launch TVRename from the installer. Nuke it from orbit even; it's the only way to be sure.

[Jürgen Schwarz]

You can change the behavior of Windows 10 regarding mapped drives. In the registry under:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System

Create a new DWORD (32 Bit) named EnableLinkedConnections and set the value to “1”.

Restart Windows after making the change. All applications should now see the same mappings regardless of being in User or Admin mode.