call documents from UNC path
OS: windows 8.1
I just upgraded to 9.2.10.0. Prior to this upgrade I have been able to open a pdf document with the the UNC path to the document folder which is on a network server. Now when I try I get the message: the document cannot be found. I have tried the copying the entry in the filename field into Windows Explorer and the document open correctly.
If I replace the computer name with the IP address, the file will open, but doesn't respect the default pdf viewer, forces me to choose adobe, which most of the time I do not want to use.
Why would this have changed action?
All Comments (8)
Hi,
I don't remember anything that we changed. Could you export me your session with the UNC path and I will look into it. I know that I won't have the document and it's just to have the same scenario.
David Hervieux
When I replace the \clientftp with \10.254.254.250 it works. My default pdf reader is PDFlite and this now forces me to choose one of the listed PDF viewers in the drop-down.
RDM_Document_setup_broken.rtf
This is strange. Could you try to execute it directly in the Windows Run dialog to see if it works?
David Hervieux
I tried that before I wrote my first post and it works correctly.
Could you paste the exact error dialog you get? I want to see where it comes from exactly.
David Hervieux
very curious. Now when I click on the RDM session that has the UNC path, it is bringing up the file. The file not found message must have been due to a logon issue onto the server with the share.
It is still not respecting the default pdf reader setup in Control Panel->Default Programs.
Is there any way to add programs to the PDF Viewer drop down list?
Hi,
I have verified and we just invoke the command line. Could it be related to RDM 32 bit? Perhap the default is not the same in 64 bit?
David Hervieux
The 9.5 beta fixed this problem. I can now open the pdf documents using the UNC path and not get an error.
I like the looks of the beta.