VC Version: 6.1.4 (Prod Release)
OS Version: 2008 R2
Hardware: VMware VM running on ESX 4i (lastest version)

We have had a job named "TRIPS - Adjustments Inbound Faxes Transfer' scheduled since October 24, 2012. It used a file trigger to watch a folder for *.tif files and processed them accordingly.

Sometime between April 1st and April 2nd, the job disappeared. There are no entries in the log saying [User 'XXXXX XXXXX' - Deleted Job] like there should be if someone accidentally deleted the job. It just plain disappaeared and has not ran since.

The screenshot attached shows a filtered view of the log file showing any references to 'FAX' for the 1st and then the 2nd. No modification, deletion, etc.. noted on the 1st, just started/completed and then no entries at all on the 2nd.

Has anyone else had this happen? I can't believe I'm just hearing about this now from our Business Unit, if we had this happen on any other job in the server it'd get run up the chain pretty quickly.... We have big money transfers relying on other jobs (we're a large bank).

i'm going to restore the settings to another server also running 6.1.4 and clone the job back over to our production server, but this has me very concerned.

Brian

I understand the concern. Have you restarted the server recently?

---

I understand the concern. Have you restarted the server recently?

Last reboot of the server was March 17th, 2013 at 2:20am (we have a once per month maintenance window for this erver).

I was able to clone the job from my restored settings on our QA server back to our production server, and its working fine.

Is this something you've seen before?

Brian

I have only seen this at a restart because that is the only time the whole list of Jobs are reloaded. Besides that, only way to affect existing Jobs is to connect and delete.

Could you please send the log file to us so we can see if we can find anything strange?

---

I have only seen this at a restart because that is the only time the whole list of Jobs are reloaded. Besides that, only way to affect existing Jobs is to connect and delete.

Could you please send the log file to us so we can see if we can find anything strange?

I'll send a zip file with all the logs from March 31st until today on that server. I've also attached a screenshot showing the most recent Application Log (Windows EventLogs) entry for the 'VisualCron' source showing when it was last started.

One thing I thought i'd mention and hopefully you can just tell me I did it incorrectly, but when I had the 'new temporary VC server with imported settings' connected in the client as well as our production server and did a 'Stop Server' on the temporary one (I didn't want it running any of our production jobs and I saw no way to import a single job from backup... so I restored the all settings to this temp server), it stopped both the Temp and the Prod servers. Doing so inactivated (Unchecked) every single 'File Trigger' on all of our production jobs. i had to go back through every single job and make sure the File Triggers were actually 'Active'. none of them were, so I had to check the box every time. I thought this was worth mentioning.

To be specific I had the Admin Console open twice. I was using Remote Desktop on the TEMP server as well as another Remote Desktop session to PROD. Admin Console on the 'TEMP' server connected only to the TEMP server. The other Admin Console was on our production server... and also had it connected to the TEMP server so I could COPY the job from TEMP to PROD.

On the TEMP servers VC Console I told it to 'Stop Server' at which point I saw a message pop up on the Prod Server's Client telling me that the triggers wouldu be disabled (or something to that effect). Well, i figured it presented to the wrong instance of my ID so I hit 'OK'. Thats when both servers TEMP and PROD had all of their file triggers disabled.

Anyway, thought it was worth mentioning. I'd love a way to restore a single job from backups so I don't have to involve another server to do it.

I looked at the file. I found this line interesting:

4/8/2013 11:15:37 AM Info User 'Brian Busse' - Updated Job: TRIPS - Adjustments Inbound Faxes Transfer

Note that it says "Updated Job". This says that the Job is there - not sure how you updated it, if it was the import at that time or what.

---

I looked at the file. I found this line interesting:

4/8/2013 11:15:37 AM Info User 'Brian Busse' - Updated Job: TRIPS - Adjustments Inbound Faxes Transfer

Note that it says "Updated Job". This says that the Job is there - not sure how you updated it, if it was the import at that time or what.

Thats after I Copied it (since that was yesterday) from the restored TEMP server.

Brian

I was expecting to see "Added" before "Updated" somewhere but I could not see it. It only writes "Updated" if it already exists in the dictionary - but perhaps it existed under another name..

---

I was expecting to see "Added" before "Updated" somewhere but I could not see it. It only writes "Updated" if it already exists in the dictionary - but perhaps it existed under another name..

Well, maybe that speaks to what you had said before. Maybe had I restarted the service the job would maybe have showed up again. Unlikely though since the service had not been started since March 17th and the job disappeared (and stopped working, regardless of its name) sometime after 6:30pm on 4-1-2013, and you said the only time all the jobs get read in is at service startup.

I dunno. I'm at a loss.

Brian

Me too. This is the first time I have heard of a single Job disappearing - and not found the real reason.

---

Me too. This is the first time I have heard of a single Job disappearing - and not found the real reason.

Oh, and I never have my client grouping jobs and all filters are clear so I show all jobs... always. In case you think I am blind :)


Brian

I don't think so 😁 I just wish I had an explanation for this. 😊

---