Error: Error opening the destination file

[DavidWBrown]

On compile I get this error. File is NOT Hidden or Read-only

I'm running the latest version of AutoIT on Vista Ultimate.

Help!

-- David

[Airwolf]

On compile I get this error. File is NOT Hidden or Read-only

I'm running the latest version of AutoIT on Vista Ultimate.

Help!

-- David

Post your code and we'll try to help.

[DangerousDan]

I just downloaded from your website and am getting the same error. I tried compiling locardwins excelCOM UDF and got the same error.

I was compiling the code below:

Func _ExcelBookNew($fVisible = 1)
    Local $oExcel = ObjCreate("Excel.Application")
    If NOT IsObj($oExcel) Then Return SetError(1, 0, 0)
    If NOT IsNumber($fVisible) Then Return SetError(2, 0, 0)
    If $fVisible > 1 Then $fVisible = 1
    If $fVisible < 0 Then $fVisible = 0
    With $oExcel
        .Visible = $fVisible
        .WorkBooks.Add
        .ActiveWorkbook.Sheets(1).Select()
    EndWith
    Return $oExcel
EndFunc ;==>_ExcelBookNew

_excelbooknew(0)

[DangerousDan]

installed the "full" version and it works fine

[netman74501]

I have the same exact problem. Even with a simple script like:

Msgbox(0, "Test", "This is a test.")

What do you mean by "full" version? If you are referring to the full installation that includes AutoIt, Aut2exe, AutoItX, and SciTE, I have that and it does not work. I don't know what version I had before I reinstalled windows the other day but this new version does not work no matter what I do. Even tried older versions, so something has changed. I am running, (currently) the latest version of AutoIt with Windows Vista Home Premium.

[netman74501]

Also, I installed the latest version on my grandma's computer, (running XP) and it had the same exact error. I installed an older version and it worked. So, now at least I can compile my scripts, but it is getting to be too big of a hassle. I've tried versions as far back as May 07 on my Vista machine though. All of them having the same exact error!

[netman74501]

Any news on a fix to this?

Edit: NM. I just figured it out. My anti-virus evidently kept deleting the file before it was fully compiled, (the upx one). I had read that it may be the anti-virus but it never worked when I exited it. So tonight I gave it one more shot and instead of exiting AVG I just disabled the resident shield. I thought the resident shield was disabled when you exit AVG but evidently not. SO. For future reference, make sure your anti-virus is FULLY disabled before trying it again. Thanks anyway. (Now I have to figure out how to exclude resident shield from scanning my build files.

P.S.

By the way, turning off UPX compression did not help. The only thing that helped was to FULLY disable AVG.

Edit again:

I found a workaround besides Emailing AVG that it is a false positive. I made a directory for when I compile, put my scripts in there and added the directory to AVG's exceptions list. Once the EXE is compiled AVG does not see it as a threat.

Edited July 16, 2008 by netman74501

[laurin1]

I am having this same problem on Windows 7, on three different machines, and disabling my AV (eTrust) does not fix the problem.

[laurin1]

Mine seems to be only when I compile to a network share, something I've done for years. Locally it works fine. I'm compiling to a Server 2003 machine, as well as to Windows 7.

[JohnOne]

I get the same from time to time, but was the same in 3.3.0.0

It will fail, try again and it works.

Wierd but no big deal for me.

[laurin1]

Weird. What ist the difference in Build and Compile (in Scite)? I normally just use F7 (Build) in Scite to compile.

After some more testing, it appears once I run a script through the compiler via right-click in Explorer, then I can F7 (Build) in Scite without a problem.

[laurin1]

I get the same from time to time, but was the same in 3.3.0.0

It will fail, try again and it works.

Wierd but no big deal for me.

Well, today it was failing for me every time (I could not compile) until I figured out what I said in my last post.

[Jos]

Are you sure you have the proper rights to the share?

Can you show me the SciTE output pane information when it fails for you on a new EXE?

Jos

[laurin1]

Are you sure you have the proper rights to the share?

Can you show me the SciTE output pane information when it fails for you on a new EXE?

Jos

Yes, it has worked fine on all of these shares before and I yes, we have permission on all of them. Like I said, once I compile it with right-click Compile with Options, it works fine from F7 (I have to do each script that way.)

[Jos]

Yes, it has worked fine on all of these shares before and I yes, we have permission on all of them. Like I said, once I compile it with right-click Compile with Options, it works fine from F7 (I have to do each script that way.)

I understood that but that could still mean you do not have Create rights within a SciTE session but do have Modify rights.

Anyways: I know one has to be careful with asking 2 questions but I did it anyways.

[laurin1]

I understood that but that could still mean you do not have Create rights within a SciTE session but do have Modify rights.

Anyways: I know one has to be careful with asking 2 questions but I did it anyways.

I am an Administrator over the machine, Domain Users have Full Control (Share), and Administrators have Full Control (Security.)

[Jos]

I ment with my last remark:

Are you sure you have the proper rights to the share?

Can you show me the SciTE output pane information when it fails for you on a new EXE?

Jos

Edited January 11, 2010 by Jos