Error accessing compiled script over network

[edguy]

When accessing an AutoIt compiled script over a network I get

this error on one machine.

"This application has failed to start because the application

configuration is incorrect. Uninstalling the application may fix

this problem"

I get this error message on an XP Pro/SP2 machine when trying to run the

AutoIt compiled executable over a network connection. I DON'T get it when I copy

the EXE to the machine concerned and then run it there directly. I also

don't get it when running on an XP Home pre-SP2 machine from the same

network copy.

Does anybody have any idea what could be happening?

[SlimShady]

Please do the following:

- Make error box appear

- Launch Taskmanager

- Make sure tab "Applications" is focused/selected

- In Taskmanager: rightclick the error box task and choose "Go To Process"

- Tell us what the name is of the process

[edguy]

Please do the following:

- Make error box appear

- Launch Taskmanager

- Make sure tab "Applications" is focused/selected

- In Taskmanager: rightclick the error box task and choose "Go To Process"

- Tell us what the name is of the process

<{POST_SNAPBACK}>

The only application running is Windows Explorer.

The process is explorer.exe

Screenshot of relevant windows is at

http://www.guysoftware.com/imagea.jpg

System is XP Pro SP2 totally current.

[SlimShady]

I haven't upgraded to SP2 yet, but I have played with it.

It could be that SP2 is preventing you to run an executable from another computer.

Check the properties of the executable. At the bottom you see a new option.

Try setting and unsetting that option and see if it makes any difference.

[edguy]

I haven't upgraded to SP2 yet, but I have played with it.

It could be that SP2 is preventing you to run an executable from another computer.

Check the properties of the executable. At the bottom you see a new option.

Try setting and unsetting that option and see if it makes any difference.

<{POST_SNAPBACK}>

It isn't stopping other executables from the same network

folder from running - just the AutoIt ones.

It isn't just my (rather complicated) "SetUpClient" script - the same

problem occurs with simpler ones - even when I compiled the

calculator.au3 sample from the AutoIt supplied examples

(it's at www.guysoftware.com/autoitcalc.exe).

It will run fine on a local machine (Win98, WinXP Home pre-SP2, Win XP Pro SP2).

It will run fine from the Internet

(of course, it downloads it to a temp file first), it will run over the LAN

on a pre-SP2 XP Home, but it will NOT run over the LAN on a current

XP Pro SP2 machine (i.e. with all of the patches), giving the message I reported at

the top. Incidentally, a post in the INNO setup forum indicates that the

message is usually associated with "manifest problems".

I don't see any additional properties from the right-click menu when

I select the file over the network and right-click it.

I hope my script doesn't turn out to be the "canary in the coalmine" as

far as compiled AutoIt scripts being run over a LAN with XP Pro SP2

is concerned. If it is, lots of application deployment scripts are about

be "broken".

Incidentally, the problem occurs both with AutoIt 3.0 and 3.1.

[major4579]

Edguy,

I just experienced that same problem. A compiled Autoit script that has been working fine for W98, W2K and WXP-SP1 will not work with WXP-SP2.

I'm running across a Network and I get the exact same error message. I tried a couple of different scripts and they all gave the same error. My gut feeling is that it has something to do with the change in "security" in SP2.

Hope someone has an idea or two...

Thanks

[edguy]

I did a little more testing.

I ALWAYS get the error when running any AutoIt executable on an SP2 machine over a network when the exe is on a Win9X machine. I think it started with the March '05 patch, because I'm sure I'd run one OK before that update.

I don't get it when running it ON a pre-SP2 machine FROM a Win9X machine.

The GOOD news is that I don't get the error when running ON an SP2 FROM an XP pre-SP2 machine.

I'm not sure how many people will have Win9X servers and SP2 clients, but they will be the only ones seeing this.

[major4579]

edguy,

Nice job - that's my situation exactly. 7 mixed workstations (w95, w98, W2K, XP-SP1, XP-SP2) with a dedicated W98 computer that just does file sharing and tape backup. The XP-SP2 computer will not run the Autoit compiled logon script.

Considering that they are still running a W95 workstation, I will not be able to get them to spring for a new file server yet.

What I am going to try the next time I'm in is to set up a batch file to copy the autoit files from the server to the XP-SP2 workstatiuon and then run them locally. The copy command will ensure that if I update the login files on the server then the XP-SP2 machine will automatically get the updated files.

Thanks for your work on this!!!!

[PerryRaptor]

I've had excellent success with this copy function. I also work in a mixed Win2000 SP-4, WinXP SP-1, and WinXP SP-2. You might be able to adapt it to copy folder contents from a server to a client at client logon.

Func CopyFolder($Folder1, $Folder2)

Local $ProcID

$ProcID = Run(@ComSpec & ' /c xcopy /e /h /y "' & $Folder1 & '" "' & $Folder2 & '"', "", @SW_HIDE)

ProgressOn("Copying...", "")

$origfilesize = DirGetSize($Folder1)

Do

$copyfilesize = DirGetSize($Folder2)

$MB = dirGetSize($Folder2) / 1024 / 1024

$percent = $copyfilesize / $origfilesize * 100

$decimalplace = Round ($percent)

$decimalplaceMB = Round ($MB)

ProgressSet ($percent, $decimalplace & " % " & "(" & $decimalplaceMB & ") Mb has been copied.")

Sleep(500)

Until NOT ProcessExists($ProcID)

ProgressOff ()

$copyfilesize = DirGetSize($Folder2)

EndFunc

[PerryRaptor]

I wish I could figure out the

posting window that everyone use on these forums.

You can scratch the line "$copyfilesize = DirGetSize($Folder2)" near the end of the Function.

[Jos]

I wish I could figure out the

posting window that everyone use on these forums.

[post="71792"]<{POST_SNAPBACK}>[/post]

Paste the code in your post, select it and click on the CODE button.

-or-

Click CODE button which inserts: [code=auto:0]

Paste your code

Click again on the CODE button which will insert [ /code]

[buzz44]

Or when you are replying to a post look up and left and find the "Guided Mode" and "Normal Mode". Select "Guided Mode" and insert your code in the InputBox .

[edguy]

What I am going to try the next time I'm in is to set up a batch file to copy the autoit files from the server to the XP-SP2 workstatiuon and then run them locally.

That wouldn't work for my application, since it HAS to run from the same folder as the program files on the server - so it knows where they are (it sets up client shortcuts to server files).

There is something else funny about the AutoIt executables. I tried signing the executable with my Thawte certificate, to see if that helped. It didn't, and the signed executable wouldn't even work on the Win98 locally.

[PerryRaptor]

When do you want the WinXP SP-2 box to copy the files from the server? after bootup? When someone logs on?