InstallAware

Hello again!

I have a setup that won't start on a XP computer. Not even the uncompressing is done. I already used Admin-Account and also cleaned %TEMP% folder but it seems that nothing is happening. I created a Procmon Logfile to see what the setup is doing, but I am not really smarter afterwards. MAYBE YOU CAN HELP ME ?

Attached please find the log file, open it with sysinternals procmon 32bit.

Is the problem related to msvcp60.dll or ligitech mouse driver, because there is an entry before setup is closing.

In the log file you can find that I started the setup twice: 14:25 and 14:26.

Hope you can find something.

Let me see... but anyway, we do not distribute any of those suspected files.

Regards

Yes of course. But you know what an IA Setup is soing on initialization. Maybe it needs such a DLL and it is a wrong version or something else. I have no idea what is going wrong there. And I don't know what to tell the customer...

Dear Alibaba,

honestly, I am not able to see any relation with your "possible" error and those dlls and excluding several "NAME NOT FOUND" (reg key operations), by your log the process seems to complete without errors (Process Exit).

Regards

So I don't understand why the setup did not start any dialogs at all. As you can see in the log file the .exe runs only for one second.

Have you any idea what is going on there?

How can I debug further if procmon doesn't help?

If you place a Message box at the very beginning of your main script, is it displayed?

Regards

I placed a log entry (WriteToLogFile - Camelot Plugin). But this Log entry is not done. The script does not start at all. The setup is not even unzipped...What to check now?

Dear Alibaba,

First of all, in case you are using a recent IA version (as, 15, 16 and so on) I don't if the Camelot Plugin works correctly.

If there is any possibility to have your files... I'll try to have a look.

Regards

I am using IA 17, the latest version. And the setups runs fine on most systems. I only know from two systems that have this problem. So I think you won't find anything since I am also not able to reproduce the error here.

Is there nothing you or an IA developer could find in the procmon log files?

Did you check if any Anti-Virus is causing the issue?

Regards

Yes I checked Anti-Virus, Temp-folder and Admin rights, all seemed okay. That's why I created a procmon log file.

Dear Alibaba,

how did you check if the AV is the cause? Lately I've seen the weirdest things caused by AV.

Please excuse me if I still insist on this ... I have experienced very very strange errors caused by AV and often, not even clearly identifiable with procmon.
Unfortunately I found that frequently, just with removing the AV I was able to find the cause.

Then also, does the problem happens with a specific setup package only?

Regards

I only disabled the AV. You mean the customer should completely uninstall the Antivirus software and try again?

I only tested one package at the customer, maybe I can try to check another.

Dear Alibaba,

in my case, Visual Studio stopped to work suddenly and without any apparent valid reason ... I solved with completely removing my AV.

Let me kow if the problem still persist with using a different package.

Regards

Hi Francesco,

I have new information on this:

1. I cannot start the package with left klick.

2 If I right-klick the package I get directly an error message that some files inside tha package could not be read!

These files are indeed password protected. They are installed with the application but should not be changed or even viewed, that is why they are protected by a password.

I cannot open the context menu becaue of this error. Normally I can open the context menu of our installation. I think on the computer is some software installed that tries to check all files in the setup (cab) and is not able to do this for the password protected ones and that is why the complete .exe does not start.

What do you think? Do you know such a software? On the computer was Microsoft security essentials installed and I disabled it by killing the processes MsMpEng.exe and msseces.exe. But this did not help. Seems there is some other software causing this error.

See error message attached.