Restart Task Failed - Intermittently - VisualCron

Please note that VisualCron support is not actively monitoring this community forum. Please use our contact page for contacting the VisualCron support directly.

Welcome Guest! To enable all features please Login or Register.

keithdavis
Free support Topic Starter

2013-07-02T13:57:52Z

Just in the last week, I have a machine that started to have the error as this post here: http://www.visualcron.co....aspx?g=posts&t=2903 However, it only happens about every other time. We recently removed the credentials from the tasks for this system (and will be from all of our system) and instead are running the VisualCron service as the same user we were using for Credentials - the reason is to make the jobs more portable from machine to machine (see my several requests and complaints about needing to move and manage jobs across over a dozen machines.) For every other job we've used this method on, it's working great! This one job, to restart the local machine (every morning), fails about every other day. I'd understand if it failed every day, but why the inconsistency??

Edited by moderator 2013-07-02T21:40:08Z | Reason: Not specified

Sponsor

Forum information

Wanna join the discussion?! Login to your Forum forum account or Register a new forum account

Support
Official support

2013-07-02T21:42:31Z

1. Are you talking about Privilege not held error?
2. you get this only sometimes?
3. which version are you using?
4. are you using the Restart Task or powershell?

Henrik
Support
http://www.visualcron.com
Please like VisualCron on facebook!

keithdavis
Free support Topic Starter

2013-07-02T21:49:23Z

Originally Posted by: Support

1. Are you talking about Privilege not held error?
2. you get this only sometimes?
3. which version are you using?
4. are you using the Restart Task or powershell?

1. Yes, "Privilege not held" error.
2. Correct. This job runs every morning, and only fails about every other time (not exactly.)
3. Version 6.2.2
4. Restart Task

keithdavis
Free support Topic Starter

2013-07-05T15:25:59Z

Ok, check this out. On the days the job is failing, it's running twice! Why? I have no idea. The trigger is set for Daily at 6AM. I've attached the Job Log showing that on the days it failed, it was run twice and failing on the second run (which is why it's failing, due to system shutdown in progress I'm sure.)

keithdavis attached the following image(s):

Support
Official support

2013-07-08T07:31:01Z

Perhaps you have a Retry on failure in the On error tab? Or use some kind of Condition? The log should probably reveal this.

Henrik
Support
http://www.visualcron.com
Please like VisualCron on facebook!

keithdavis
Free support Topic Starter

2013-07-08T12:54:28Z

Originally Posted by: Support

Perhaps you have a Retry on failure in the On error tab? Or use some kind of Condition? The log should probably reveal this.

No retry on failure configured.
No conditions are enabled.

I can't tell from looking at the log. I've attached the relevant portion. One thing strange, if see how the time counts up to 6:00:27 AM, and then backs up to 5:59:54. What the heck is that all about?

Even the run missed jobs query looks wrong (end time is before the start time):

7/8/2013 6:00:10 AM Info Running missed jobs between 7/8/2013 6:00:22 AM and 7/8/2013 6:00:10 AM

Also, we've changed nothing on this machine, other than the change to the service logon user.

File Attachment(s):

vc_log.txt (5kb) downloaded 48 time(s).

Support
Official support

2013-07-08T14:25:39Z

The time change is related to a time change on the server. Probably the server clock is not working optimally and you have configured it to update against a NTP server. You should see this in the event viewer that this time.

It seems like the NTP update is done when the server is booting up.

Edited by user 2013-07-08T14:29:27Z | Reason: Not specified

Henrik
Support
http://www.visualcron.com
Please like VisualCron on facebook!

keithdavis
Free support Topic Starter

2013-07-08T17:08:02Z

Originally Posted by: Support

The time change is related to a time change on the server. Probably the server clock is not working optimally and you have configured it to update against a NTP server. You should see this in the event viewer that this time.

It seems like the NTP update is done when the server is booting up.

All of the machines use the Domain Controllers for NTP. This has not been a problem before. Besides, it's checking for any missed jobs. The job wasn't missed. Why is it determining that the job was missed?

keithdavis
Free support Topic Starter

2013-07-08T17:11:33Z

The local machine is synchronizing just fine:

Event Type: Information
Event Source: W32Time
Event Category: None
Event ID: 35
Date: 7/8/2013
Time: 6:00:08 AM
User: N/A
Computer: SILENTFAX
Description:
The time service is now synchronizing the system time with the time source dc07.pridedallas.com (ntp.d|192.168.0.23:123->192.168.0.6:123).

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp .

keithdavis
Free support Topic Starter

2013-07-08T17:22:33Z

#10

I don't see any issues on the server with it's NTP synchronization.

keithdavis
Free support Topic Starter

2013-07-09T13:12:55Z

#11

And for that matter, Run missed Jobs once at start is not checked for this Job.

Support
Official support

2013-07-09T14:48:13Z

#12

Originally Posted by: keithdavis

The local machine is synchronizing just fine:

Event Type: Information
Event Source: W32Time
Event Category: None
Event ID: 35
Date: 7/8/2013
Time: 6:00:08 AM
User: N/A
Computer: SILENTFAX
Description:
The time service is now synchronizing the system time with the time source dc07.pridedallas.com (ntp.d|192.168.0.23:123->192.168.0.6:123).

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp .

Yes, it probably runs fine but it turns back the time - which is the purpose (synchronizing it). The log does not provide the information about which time it synced too but VisualCron captures all time changes and take actions.

Henrik
Support
http://www.visualcron.com
Please like VisualCron on facebook!

Support
Official support

2013-07-09T14:49:28Z

#13

Originally Posted by: keithdavis

And for that matter, Run missed Jobs once at start is not checked for this Job.

This is not related to "Run once". It is related to your scheduled run at 6:00. It is probably a bad time to schedule as you run the NTP server call at that time and there is a risk that the NTP server is correcting the time back on your server - resulting in that your Job runs again - according to schedule.

Henrik
Support
http://www.visualcron.com
Please like VisualCron on facebook!

keithdavis
Free support Topic Starter

2013-07-09T15:33:25Z

#14

Again, until about a week ago, this did never happened. Oh, and now it's happening every day.

I'll change the time to 6:15AM and see if that solves the problem.

Support
Official support

2013-07-09T16:05:50Z

#15

I could simply be the battery in the motherboard that is running out of juice (and cannot track time properly) - then you see this kind of problem.

Henrik
Support
http://www.visualcron.com
Please like VisualCron on facebook!

keithdavis
Free support Topic Starter

2013-07-09T16:19:05Z

#16

Good point.

keithdavis
Free support Topic Starter

2013-07-10T15:07:32Z

#17

That did not fix it:

From: SILENTFAX [mailto:SILENTFAX@pridedallas.com]
Sent: Wednesday, July 10, 2013 6:15 AM
To: # IT
Subject: VisualCron - SILENTFAX - Error - Restart SILENTFAX

Date/Time: 2013-07-10T06:15:21
Task: Restart SILENTFAX
Executed at: 7/10/2013 6:15 AM
Job Error: Exception in Task: Error occured:Privilege not held.

Support
Official support

2013-07-10T15:21:04Z

#18

Originally Posted by: keithdavis

That did not fix it:

From: SILENTFAX [mailto:SILENTFAX@pridedallas.com]
Sent: Wednesday, July 10, 2013 6:15 AM
To: # IT
Subject: VisualCron - SILENTFAX - Error - Restart SILENTFAX

Date/Time: 2013-07-10T06:15:21
Task: Restart SILENTFAX
Executed at: 7/10/2013 6:15 AM
Job Error: Exception in Task: Error occured:Privilege not held.

Please send the log again to support@visualcron.com

Henrik
Support
http://www.visualcron.com
Please like VisualCron on facebook!

keithdavis
Free support Topic Starter

2013-07-10T15:35:14Z

#19

Sent

Support
Official support

2013-07-10T16:04:56Z

#20

I think you are running into similar problems as before:

Time on computer before shutdown:

7/10/2013 6:15:24 AM Debug Shutdown of socket reached final stage

Time on computer at startup

7/10/2013 6:14:52 AM Debug InternalWorkerThreadClass was created

This makes the Task run at 6:15 again. Why it fails is unknown but I think the problem is that the whole server is in startup phase which causes this.

Henrik
Support
http://www.visualcron.com
Please like VisualCron on facebook!

keithdavis
Free support Topic Starter

2013-07-19T11:55:55Z

#21

So, how why did this just start? How do I fix it? Do you think replacing the CMOS batter might really have anything to do with this?

Support
Official support

2013-07-19T12:05:07Z

#22

I do not know but I would replace the CMOS battery to start with.

Henrik
Support
http://www.visualcron.com
Please like VisualCron on facebook!

keithdavis
Free support Topic Starter

2013-07-25T22:53:24Z

#23

Well, the issue stopped occurring on it's own (or hasn't in 5 days.) We replaced the battery anyway (2 days ago.)

keithdavis
Free support Topic Starter

2013-07-29T12:33:53Z

#24

Well, so much for that, it happened again this morning.

From: SILENTFAX [mailto:SILENTFAX@pridedallas.com]
Sent: Monday, July 29, 2013 6:15 AM
To: # IT
Subject: VisualCron - SILENTFAX - Error - Restart SILENTFAX

Date/Time: 2013-07-29T06:15:22
Task: Restart SILENTFAX
Executed at: 7/29/2013 6:15 AM
Job Error: Exception in Task: Error occured:Privilege not held.

Support
Official support

2013-07-29T13:58:11Z

#25

I am currently out of ideas regarding this one. Something sets the computer to the wrong time or does not update it correctly. This causes problems for VC as it is dependant on computer time.

Henrik
Support
http://www.visualcron.com
Please like VisualCron on facebook!

ABOUT VISUALCRON

Community forum

Please note that VisualCron support is not actively monitoring this community forum. Please use our contact page for contacting the VisualCron support directly.

Login