Windows 7 download.exe hang during launch deployment v2.1.1.1

[cyrill51]

First, I would like to thanks the OCS team for this excellent software!

Since we work with Windows 7 with the 2.0.0.20 agent and now 2.1.1.1 agent, we always have a problem during packages deployement on our machines.

Sometimes, the download.exe process hang during launch execution and never exit, even when we stop the OCS agent service.

In the interface, the package status still be "NOTIFIED".

in the download.log, we can see the launch command execution, but it stays on this action.

I put the debug flag at 2, but it doesn't give me more informations.

Sometimes it works, sometimes not.

I saw on the web that some people encounter the same problem.

I don't know what to do...

Could you please help me?

Thank you a lot!

[Didier Liroulet (dliroulet)]

Hi.

OCS agent starts a new process called download.exe to doanload and execute deployment packages. That's why stooping OCS Service does not stop currentky running deployment. You must kill download.exe process.

This process wait for launch or execute command exit code, and I think it never receive exit code in your case.

Is it system reboot in command package ?

Is the package always crashing or sometimes only hanging ?

Can you send me a sample package where you encounter the error ?

Cheers

[cyrill51 (cyrill51)]

hi Didier,

Thank you for the answer.

To respond to your questions, the problem is happening randomly, whatefer the package, and in general, works at the second try.

There is no reboot at the end of the script, and the computers stay power on.

for example, you can download an example of the package corresponding to to the dowload.log file attached to the bug here:

 http://filez.chu-stlouis.fr/fk79p

in general, we put an exe script coded with autoit into a zip file, and we launch the exe script.

I attach the .au3 script file. You can edit it with a simple edit text program.

The problem is occuring only on Windows 7 not on XP.

Thank you very much for what you can do.

Cyrill

[Rodney Yeo (rodyeo)]

Switch back to 2.1.0.1 Agent as this problem does not exist only if WMI engine corrupted it does not. capture bios serial number as blank data value.