Tranquil IT Forum

Hello,

I'm having trouble creating the wapt agent.
When the loading bar reaches the end, I get an error message:

"Error while creating waptagent.exe: System error, (OS Code 2): The specified file could not be found. : Error in C:\wapt\waptsetup\custom_waptsetup.iss: The process cannot access the file because it is being used by another process.
Compile aborted."

I found a thread on your forum about a problem with wapt in the "Program Files (x86)" folder which gives the same error message, but my wapt is definitely in c:\wapt.

I should mention that the problem is occurring on a Windows Server 2012 R2 which has both a private and a public IP address (the server is hosted externally). I did my proof of concept for wapt on a Windows 7 machine, and I never encountered this problem.

I've thoroughly searched through all the posts and haven't found a solution.

Thank you in advance for your reply.
Sincerely,

Have a good day.

Was the console launched as administrator?

Yes, the console was launched with "Run as administrator".
And the WAPT server was also installed with "Run as administrator".

Good morning,

I have the same problem

I installed the agent setup for 1.7.3.5 in community.

I am indeed launching the console as administrator (right-click > run as administrator) and have even put it in compatibility mode. (on two different versions of Windows 10)
However, it keeps telling me to run the console as admin when I want to launch the agent's wizard.
Then I also get this error message

Okay, I tried using the "waptconsolepostconf.exe" tool after deleting waptagent.exe from the server; it compiles until it reaches the .crt file where I get an error and it stops there.
The same thing happens if I create a new certificate and its key pair; the compilation crashes in the same place: C:\Program Files (x86)\wapt\ssl\xxx.crt

So still stuck on my 1.7.3.5 I await your help

It's not the most elegant solution, but:

I managed to compile my agent using the console by installing it on a Windows 7 x86 system.
I didn't get any errors like "console not admin" messages, nor any compilation errors. But instead, it asked for the key password, as it should have on Windows 10.

So if you have the same problem, you know what to do...

Regards,

Hello,
I'm experiencing the same problem after updating to version 1.8 (see attached image).
Has anyone found a solution since?
Thanks.

Hello,
I'm replying to myself.
Actually, my ESET antivirus was deleting a file essential to the agent's construction; I disabled it and it's perfect!