Hi,

VisualCron have a serious problem running on Windows Server 2008 r1 and r2. We are using the "Job - Stop Job" task to stop running tasks, but this event sometimes crashes the server. The server reboots and starts up with the "Shutdown Event Tracker"

The problem has be recreated on 4 different Windows Server 2008 (r1 and r2) running on VMware.

To recreate the error install VC 5.5.9-4 on a Window Server 2008. Create and schedule the following jobs:

Job/Task "VcCrashTest START"
Triggers: Interval every 10 sec
Task Type: Execute : "LoggingConsole.exe"
❌ Don't start Task if process is running : "LoggingConsole.exe"

Job/Task "VcCrachTest STOP"
Triggers: Interval every 12 sec
Task Type: Job/Task control
Action: Job - Stop Job
Job: "VcCrashTest START"

LoggingConsole.exe + VC settings are attached.

This problem has been reported in another thread, but the problem was never fixed. Please recreate the same setup before reporting suggestions and workarounds.

Regards

Stig

Thanks for your report.

1. Do you know which other thread this was never resolved?
2. What kind of crash are we talking about? Is it a VisualCron or server crash? Can you supply the VisualCron log file?

---

We found an email conversation with Henrik at your company. The last email from him was:

"I have been looking more closely at the kernel dumps generated by our machines, and am beginning to suspect the problem is releated to an error in csrss.exe, and will as such not be sending anymore logs until we can upgrade our server to SP2.."

A week or two later we emailed you back if you had any update as we did not get any reply of the progress.

Did you try upgrading to SP2?

---

1. Do you know which other thread this was never resolved?
You are right, it was reported by e-mail.

2. What kind of crash are we talking about? Is it a VisualCron or server crash? Can you supply the VisualCron log file?
The OS crashes. Please do recreate the setup in a test envrioment. It is very easy to reproduce!

Did you try upgrading to SP2?
As I write I can reproduce the problem on both r1 and r2.


Regards,

Stig

1. Ok, have reproduced this in normal VMWare Client edition or are you using any special edition?
2. We assume that you are running 64 bit (maybe only one available)

---

1. Ok, have reproduced this in normal VMWare Client edition or are you using any special edition?
Great to hear, you have reproduced the crash?
I do not have access to the VMware version.

2. We assume that you are running 64 bit (maybe only one available)
Yes 64 bit in all cases.

Sorry,

forgot a "you" in the question.

1. Ok, have you reproduced this in normal VMWare Client edition or are you using any special edition?

We need to know if there is any special version of VMWare, otherwise we will use normal client version.

---

1) I’m not sure, but maybe I can get the information in a couple of days. Please do continue with the test. Normally the setup will crash within half an hour.

Stig

any news?

Stig

We will test this later tonight. We did not have that Windows version so we needed to order it.

---

good to hear

Hi,

we could reproduce it once.

1. It seems that the problem is in the Execute Task and not the stop Task right?
2. Have you tried running it in hidden mode?
3. have you tried running it Managed mode (instead of with API mode)

We have so far only received this once so we have not been able to test the above. Could you answer and test this?

---

great!

1) I'm not sure. I always thought it was the Stop Task.
2) We are already running with hidden mode.
3) No

Since you have managed to reproduce the error I would expect you to do the testing. We are paying for this production and having serious problems in our production environment.

In my test enviroment I could reproduce it every half hour.

Regards,

Stig

We will continue to try to reproduce this. So far only occured once. That is why we asked for help to speed up to see which setting is causing this.

1. Either it is the Run with API that could be switched to Managed mode
2. Something wrong with the Kill process (within the Execute Task)
3. it does not seem to be the Stop Task but this needs to be verified as well.

---

Any news?

Stig

We are still trying to reproduce this. Unfortunately we have only been able to reproduce this only once (running for days).

We need to reproduce this to know exactly where this happens.

If you can reproduce this quickly maybe you should try our test version and send us the updated logs?

---

OK lets do that, but please keep on running the test. How do I get access to the test version, and where do I find the logs?

Stiog

1. download and install this one: http://neteject.com/down...Cron/VisualCron5.7.0.exe 
2. start client and go to Server tab->Settings->Log and check "Extended debugging"
3. when it crashes - please send log_serverDATE.txt located in "log" folder of VisualCron directory to support@visualcron.com

---

Hi, I have just send the log.

Regards,

Stig

any news?

Stig

Unfortunately I have now experienced this several of time on a real Win 2008 server r2 (no VMware).

Did you use the KillProcess.exe we sent or the normal Kill Task when this happened?

---

Normal "Stop Job" task.

Unfortunately I have now experienced this several of time on a real Win 2008 server r2 (no VMware).

Ok, then we should be able to reproduce this if there isn't any special software or settings on that machine?

Are you seeing that it instantly crashes when the Task is run or some time after?

---

I think it happens right away. I have even tried to use "Stop" in the right click context menu and then the server crashed a second later!