The specified path does not exist

Help & Support
1

Slightly odd situation which I'm hoping someone can shed some light on. I've noticed that when attempting to open files under a certain network share I get the following error:

{full network path}\filename
The specified path does not exist.
Check the path and then try again.

in Dopus I can rename the file, and copy and paste it. If I right click the file I can open it using eg "Edit with Notepad++", or "Open With.. -> Notepad". It's just when opening via double-click or right-click | Open that I get the error.

Note: I can open via double-click if I'm using Windows Explorer.

Other network shares are okay and (so far) the only difference that I can see is that the share which has the error is one where I've only been given read (and write) access to a particular folder and its children, but not all folders within the path.

eg the files are in \networkdrive\docs\project\subproject\files but I've only been given access to the \networkdrive\docs\project\subproject folder and below (ie can't access \networkdrive\docs\project).

I get the issue whether I access the share via a mapping (eg X:\subproject\files) or fully qualified location (as above).

Any advice, etc welcomed! :slight_smile:

2

Is the error coming from Opus (i.e. is it an Opus dialog displaying it) or from something else?

3

Hmmm, good point. I think it may be Windows (7 64-bit). The error looks like this: http://answers.bitrock.com/upfiles/error.png

4

This MS KB article seems relevant - http://support.microsoft.com/kb/2669244.

Though I'm still confused why it works via Windows Explorer and not Dopus.

5

The only suggestion in that article that I think could be relevant is the virus checker one (I'm assuming you do have permission to access the file since you're able to copy it). You could try disabling your AV to see if it makes a difference.

Alternatively Process Monitor may be able to show exactly where the error is coming from (filter on the name of the file to make it easier to locate relevant actions).

6

Thanks will give Process Monitor a try tomorrow.

It's not a major deal as it only impacts one network share I use a handful of times a week. Worst case I might create a right-click option to open the containing folder in Windows Explorer for the times I need it! :slight_smile: