This is a really weird issue. Did you try this multiple times with the same results every time? Also, what version of WinAutomation are you running? Did the error show up in WinAutomation's logs? If yes, what is the exact error message (you can either copy and paste it along with the additional info in the logs viewer, or you can just atach the logs.dat file)?

One last question: do you happen to have SnoopFree installed in your machine?

Hi,

Nope, no SnoopFree.

I am running the version 3.0.3.410.

Yes, it happens every time. I am not getting the exceptions lately, but my Senuke crashes every time I record with WinAutomation. I`ve been trying to record this for like 6 hours today.

After one recording I saw that in WinAutomation, there are hundreds of processes created although I just mad a few click myself. So I thought maybe it tracks what Senuke does as well, and this is why Senuke crashes. Then I recorded just the part until I click "Start" on Senuke, so WinAutomation could just run it for me, and Senuke would keep on running. But Senuke still crashes, saying there`s some other application running. It works fine when I am not recording from start though.

I deleted all my "unsuccessful" jobs already so no logs, but if I get one, I will definitely add it here.

Is there anything I could ask Senuke support?

I still hope there is some way to get this running :)

Big thanks!

Ok, I got the error message. Here is what it says: (edited, see attached txt file)

I got this as soon as I stopped the recording, right after starting the Senuke to run. Senuke crashed in about 10 seconds.

I will stop trying for now as I haven`t done anything else today except for this. Hopefully someone here can help :)

Hi guys,

Any ideas? Please ;)

Thanks!

Regarding the internal exception that is logged (i.e. Internal Exception: RMSI01), I'm pretty sure that it is not relevant to the issue that you are facing.

Since I am not familiar with the SENuke software that you are referring to, I cannot give you specific answers. However, I can tell you what WinAutomation does: whenever you press the "Start Recording" button, WinAutomation starts monitoring your mouse moves and keystrokes. After you have finished recording, it automatically converts them into actions ("Move Mouse", "Send Mouse Click", "Send Keys" etc).

Does SENuke try to create any "hooks" to the keyboard in order to record keystrokes? If this is the case, I'm guessing that there might be a conflict with WinAutomation there.

Hi codex,

you might be right IF the process was not working as a whole. But the thing is, I stop recording with Winautomation, right after I click START on Senuke. Which means, it should not conflict at all, and should only START Senuke (that is, open the application, load a specific document, and click on START). But they both crash - that`s why it is so weird.

I will appreciate any thoughts.

Hello user,

I have tried to reproduce the specific issue in our labs but with no success. The steps that I followed can be found below:
1) I have installed SENuke (latest version) and WinAutomation (latest version) in a clean Windows XP SP3 machine,
2) created a new job in WinAutomation and started the recording process,
3) recorded the mouse clicks and keystrokes that are needed to launch SENuke,
4) launched the Web 2.0 Account Creation Module,
5) generated random information for username and password,
6) hit the Start button.

There was no crash on either application, so I converted my recording to actions and I executed the job. The steps were executed perfectly and no crash occurred. 

Do you notice any differences between the steps that you are recording and the steps that I am recording?

Thomas Minitsios
 

Hi Thomas,

Thank you.

The only difference in the steps is that I run the "Social Network Nuke" module. But it works the same way, and the steps are very similar.

Another thing - I use Windows 7. Might this cause the issue? I might be able to get another computer to try on, for the weekend, if you think this could help.

Thanks!

Hello user,

Yes, if you could test the specific scenario in some other computer, the results could provide me with some really helpful information. Specifically, we could eliminate (or embrace depending on the results) the "machine specific" cause for the problem. 

Let me know as soon as you have tested the scenario in some other machine.

Best regards,
Thomas

Hi Thomas,

Thanks. I will do my best to try it on another machine this coming weekend. Will let you know how it goes.

Thank you!