error on network processing when opening file from system viewer

[jrjdavidson]

Kia ora,

We have a strange bug that occurs only when a user opens a psx file on a network drive using the system viewer. If the file is opened by double clicking on a psx file in the file explorer, if a user tries to launch a network processing job, the nodes will throw this error:
Error: Can't open file: The system cannot find the file specified (2): C:/Windows/system32/auto-project.psx
( the file is acutally located on a network drive \\file\Shared\...\auto-project.psx)
If the same job is started by opening Metashape, and opening the file via the GUI, this error doesn't occur.

[Alexey Pasumansky]

Hello jrjdavidson,

Do you see a correct path to the project (via  \\file\Shared\...) in the Console pane when the project is opened by double-clicking on PSX file? Also please check that correct root path is defined in the Network Preferences tab of Metashape, when you open the project by double-clicking.

Please also specify the OS version used and file explorer (if it is different from Windows Explorer). Is it possible that there is another Metashape executable assigned to PSX/PSZ files open?

[jrjdavidson]

Yes, the console pane displays the correct path (Load Project: path =\\file....)
The root path is undefined regardless of project opening method.
 
The full path is not defined when viewed in the network monitor( see attached)

Windows 10 using windows file explorer. I don't think it is an executable assignment issue, we can reproduce this error on different machines.

[jrjdavidson]

Just to clarify, the image in the previous post show two network jobs that were launched from the same project. The top one was launched form a project that was opened through the file explorer, and the full path is missing.

[Alexey Pasumansky]

Hello jrjdavidson,

Does it help, if you set up the root path in the Network Preferences tab (should correspond to the root path used on the network processing nodes), close the application and try to start the network processing batch using either of the methods?

[jrjdavidson]

Yes that fixes it, however I did have to set a root path on the node as well.

Note that we rely on UNC global paths without setting a root on any of our machines, and this pattern work well apart for this one little bug.