WMI Process Iterator

FinalBuilder Discussion
1

Occassionaly, as in once in every 20 build attempts, my project stalls when running the WMI Process Iterator action. It trys to run the action for 5 minutes, 10 minutes or sometimes indefinitely. I usually have to stop the build and you could imagine how much of an inconvenience it is. Usually the WMI Process Iterator action takes less than a second to run....

Does anyone have any ideas why this would occur? I run the final Builder project on a Virtual Machine. I try and log off the VM regularly and close the FinalBuilder application whenever i'm not using it, and it seems to help, but it's not always the case.

This has never happened on any other action I use in any of my Final Builder projects.

Regards,

Cam

2

Hi Cameron

I don’t have a definitive answer for this, however if you are using it to check processes on other machines, then it might be windows firewall interfering. You don’t say what you are using to run your virtual machine, we have found with Virtual PC it’s advisable to have a dedicated network adapter for it rather than share the host pc’s network adapter. WMI is not the most reliable technology microsoft ever dreamed up.