AutoIT v3.3.13.5 not working on new laptop - works fine on desktop - Please advise

[TaShumbria]

Deleting

Edited March 3, 2023 by TaShumbria

[Danp2]

Are you sure about that version number? Even if you meant 3.3.14.5, that' was released almost 5 years ago.

FWIW, the error you posted isn't coming from AutoIt. Even if it was, a screenshot of an error doesn't yield much info beyond the fact that it can't find the file as shown. However, the file path shown in error error dialog appears to be different from the path shown in Explorer. This appears to be more of an environment issues (user rights, drive mappings, etc) than one caused by AutoIt.

 

[argumentum]

"a picture is worth a thousand words", but in this case it say nothing.
There is no permission hence no access. VNC viewer ?!. Anyway, sharing details is better. Do you run as Admin and have no access due to user mode login ?

Nice cursor  

[SamuelAngervil]

Deleting

Edited March 3, 2023 by SamuelAngervil

[argumentum]

2 minutes ago, SamuelAngervil said:

then opens a mapped file that uses AutoIT.

mapped drive, not file. That does not need AutoIt to map a network drive to a drive letter.
The popup say "VNC viewer", unless a script run the VNC viewer with the given path.

6 minutes ago, SamuelAngervil said:

Are there configurations in AutoIT that can be changed? Not sure where else to do from here.

well, unless you can share a script to see what the code does, nether can anyone. So screenshots would not help.

The latest version of AutoIt may very well be the reason it does not work. You may need an older version. Again, without the code, who know what is going on.

[JLogan3o13]

2 hours ago, SamuelAngervil said:

Any help would be greatly appreciated. Thank you. I can provide more screenshots if needed of the process Ta'Shumbria is doing to connect.

The error generated very clearly shows a failure to find/connect to HOL-Ta'Shumbria.Miller-o6.vnc. I am assuming you have confirmed the user can manually connect to this file just by browsing to it?

[SamuelAngervil]

Deleting

Edited March 3, 2023 by SamuelAngervil

[TJHart85_2]

As mentioned a couple of times, that VNC Viewer error is indicating that it can't access a .vnc file:

     

Have you tried to manually 'walk the path' through:
\\slcgateway01.dealersocket.net [other screenshots for slcgateway01 don't include .dealersocket.net ... please make sure you include it when you attempt manually to make sure you're attempting in the same way that the scripts are attempting)

Then go to:  hol build

Then go to: AWS VNC Files

Then attempt to manually open:  HOL-Ta'Shumbria.Miller-06.vnc

And see what happens?