Error 76-Path not found-on network with both 32-bit and 64-bit PCs

A client of mine has our application installed on a network. The data is shared among three users. The setup is as follows:

The application is hosted on a SAN with full permissions to the share granted to users 1, 2, 3, and the domain administrators.

For each user the shortcut properties indicate a local Target for the application executable, while the Start In points to the shared data folder residing on the server.

User 1 can access the application without issue from a Windows 10 32-Bit machine.

User 2 gets ‘Error 76: Path Not Found’ when trying to launch the application from a Windows 10 64-Bit machine.

User 3 gets ‘Error 76: Path Not Found’ when trying to launch the application from a Windows 10 64-Bit machine.

Any ideas as to what could be causing this conflict? The IT tech at this client has tried uninstalling and reinstalling the application to no avail. Other clients have the same setup with no issues.

Thank you,
Barb

The application is installed on the local C: drives as well as the network server drive. Each PC runs its own copy of the executable, but they all point to a shared folder that contains the data so that they all look at the same data. As I stated in my original post, other clients have this same setup with no issues. For this client the issue only seems to be with their 64-bit PCs. Those return the "Path not found" error message. Their 32-bit PC accesses the shared folder just fine.

Yes, thank you, this has been done. Also, we double and triple-checked the typing on the Start In parameter of the shortcut properties, to make sure it points to the shared data folder on the server drive.

Windows Explorer has no problem accessing and opening the folder in question.

To answer your second question, here is the structure that our application uses. I will use FOLDER to indicate the main folder that contains the executable and all of its necessary files, SUBFOLDER to indicate the subfolder that contains the data files particular to each client, APP.exe to indicate the application executable, and X to indicate the drive letter they have designated for their server.

The FOLDER and its SUBFOLDER reside on the server drive. This is also the case on each PC, where it resides on the C: drive, not in Program Files (x86) folder.

The desktop shortcut on each PC for this application has the following parameters:

Target = C:\FOLDER\APP.exe
Start In = X:\FOLDER\SUBFOLDER

This works just fine for all our clients who are running this on multiple PCs and sharing the data over a network.

Again, this client has no problems with the 32-bit PC; it's just the 2 64-bit PCs that get the Path not found error.

Thank you.

The app code is the same for either type of machine. It's known to run just fine at other locations on a 64-bit. In fact, my PC is a 64-bit, although mine doesn't run on a network.

Anyway, my client just installed it today on another 32-bit, which is running fine. So now she has two 64-bits that can't launch the app from the SAN location and two 32-bits that can. Again, she IS able to open the folder across the network from the 64-bits using Windows Explorer; she just can't start the local app from that location.

I believe her next option is to try to reinstall the application on one of the 64-bits, to see if that fixes something in the registry (DLLs are installed there during application installation).

Thanks again.