Script Executor don´t work anymore

[Anon Anon]

Hello everyone.

 

Since a week we have the problem that our scripts stop working and we get the message "Script Executor stopped working - A Problem has prevent the executing of a program. Close the program".

 

I took a look at the event viewer of windows and got the following:

 

Name of the faulty Application: taskexec.exe, Version: 5.0.30.1, Time-stamp: 0x52eb9ee6
Name of the faulty Moduls: mfc90u.dll, Version: 9.0.30729.6161, Time-stamp: 0x4dad06e1
Exceptioncode: 0xc0000005
Faultoffset: 0x0006af59
ID of the faultry Process: 0xd7c
Starttime of the faulty Application: 0x01cf5f60829145e7
Path of the faulty Application: C:\Nimsoft\e2e_scripting\bin\taskexec.exe
Path of the faulty Moduls: C:\Windows\WinSxS\x86_microsoft.vc90.mfc_1fc8b3b9a1e18e3b_9.0.30729.6161_none_4bf7e3e2bf9ada4c\mfc90u.dll
Report Identifier: c074907f-cb53-11e3-b681-24be0511b3ce

 

We had two changes last week: Windows 7 security updates and our users for the robots lost their local admin privileges (we work with the Avecto Privilege Guard).

 

Is this problem known? Has it to do with the local admins?

 

Kind regards

Jessica

[Anon Anon]

Hi,

 

Looks like a problem with the vc redistributable 2008 libraries. I don't think april security bulletin had updates that should affect that, but you never know. Did you try reinstalling the vcredist or removing most recent patches?

 

Does the script run properly if you run it yourself?

 

-jon

[Anon Anon]

Hi jonhcw.

 

Thank you for your fast answer.

Whats the vc redistributable 2008 libraries? How can I reinstall it?

 

We coulndn't re-enact this by hand. This happened sometimes without a reason on several robots. We don`t see a reason because everything looks fine and all works the whole day or 2 days and then it happened again. Really strange!

 

Kind regards

[Anon Anon]

Oh hmm, that's weird then, I thought it happens all the time. I guess the problem lies elsewhere then..

 

You can find the vc redist installation packages in your robot dir, under their own folders.

 

-jon

[Anon Anon]

Yes, really weird!!!!!

 

I tried now to reinstall this vc redist! Now I must wait if it happened again or not.

 

But thank you for your help! I will write the reulst in some days! :-)

[Anon Anon]

Sadly we still have the same problem! :-(

[Anon Anon]

I just noticed that it often happened on the same step in the script. And it happend, when we want to start the QoS timer with nimInit() and nimQoSStart().

[Anon Anon]

Just as information: after an half year the problem is finally solved. It was an error in the NimRecorder which was caused by an security patch of Microsoft.