This has been posted previously here and still not clear as to why this happens or get a resolution since it appears to be hit and miss with workstations.

Trying to load Inventory via the workstation setup and get the following error:

"Windows cannot access
\\Adagio\softrak\Inventory\WKSETUP\Setup_RedistribsODV3.exe"

Then followed by:

"Could not execute the external program:
\\Adagio\softraqk\Inventory\Wksetup\Setup_RedistribsODV3.exe"

What is odd as this is hit or miss. Some workstations no issues others a problem.

Do you think this is network related or workstation related?

I went back and looked at my original post from last December and the postings that went back and forth with Bruce and Vickie and tried the copy files to those directories but no luck.

Ledger workstation install no problem. Now both Receivables and Order Entry crapped out on their workstation installs but all I did their was make the call to the EXE files in each case and they run without issue. Not so for Inventory on either the call to the exe or when trying to install from the workstation setup.

Would be happy to hear any suggestions as to how to get around this issue.

Thanks in advance.

Do they all have the same anti-virus? And if so, what is it?

Have you tried uninstalling the AV and then installing Inventory?

Yes all workstations have the same anti virus software and version installed - Webroot Secure Anywhere Endpoint Protection V9.0.30.75

I haven't tried the uninstall but will have to do a test run on one of the workstations in question to see if that does the trick. Will have to get their IT guys to uninstall one of the workstations in question so my result to post here could be a couple of days.

Thanks for the posts and will keep you posted.

Well update that there is no update. Disabling and then uninstalling AV did not get by the error.

I compared the other workstations where Inventory runs successfully and did notice that for those machines MS Redistributable C++ 2015-2019 (x86) version was installed. The machine bombing out did not have this installed. But to no avail installing it made no difference.

Any suggestions support?

Have you tried logging in to the workstation as administrator?

Yep. First thing I tried this morning before the AV testing.

A little frustrating since this has happened before (not with me but with other users) and there doesn't appear a clear answer on why this happens or how to resolve.

Thanks for your input.

Is this a new workstation or an upgrade? If it was an upgrade did you install the modules on the order the version was released?

Are you using ALLWRKST or individual workstation setups?

Re Format Workstation and Re Install Windows had similar issues with different flavors of windows that came pre-installed from Dell and HP. Brand new systems but had issues.. Did not worth the effort to figure out what changed in Microsoft OS, if Adagio works on some desktops, clone one of those PC and deploy..If ALL did not work then it would be an issue... The fact that you, like me have to work alongside (IT Guys)- Network Administrators, let them fix the PC so that it will connect .... It may be a Microsoft BUG ...

Finally - RE-Boot the SERVER...

Thanks for the latest responses.

First in each and every case (successful or not successful) I used the executable from the X:\Softrak\Inventory\WKSETup\wksetup.exe file.

To further cloud the issue on a couple of the "successful" installs a workstation setup was not even done as it turns out. The workstation install would crap out so I then would simply make the call to run the Inventory.exe file. When I did this I could log in successfully and run the program even though a workstation install was not done.

So on the unsuccessful workstations I tried the same thing. But with these ones instead of going into the program the workstation install initiates and then eventually craps out with the error that started this thread and I can get no further than that.

I will ask their IT guys what the difference is between the "successful" workstations and "unsuccessful" workstations to see if it is some sort of version issue and or network rights issue.