I've been struggling with error reporting from VC for some time and still cannot get the errors reporting out into emails. I have a job that is called On Error that resets a coulle database objects then sends error emails. I am having trouble pulling the error details from the job that is called. I also tried to set variables but I cannot seem to get variables to work either. I would appreciate any assistance...

"[Error in SetVariables, string: Job {JOB(Active|Name)}
Ran: {JOB(Active|LastRun|M/d/yyyy h:mm tt)}
Failed On Step: {TASK(Active,Name)}
Result: "{TASK(Active,Result)}"
Last run: {TASK(Active,LastRun,M/d/yyyy h:mm:ss.ff tt)}
Last exited: {TASK(Active,LastExited,M/d/yyyy h:mm:ss.ff tt)}
Execution time: {TASK(Active,ExecutionTime)} seconds
PrevTask Result: "{TASK(PrevTask,Result)}", err: Object reference not set to an instance of an object.]"

Derek Randles
Dell Services

This post seems like a duplicate to:

http://www.visualcron.co....aspx?g=posts&t=2089 

---

This post seems like a duplicate to:

http://www.visualcron.co....aspx?g=posts&t=2089 

Yes you are right. I could not find the original post. As you can see, I'm still struggling with the usage of internal varialbes and variable usage and/or error trapping. 😲

drandles,
I was using remote desktop to log into our server that has VC installed on it. I started getting the same weird error messages, then I noticed that one of the tasks in my job got stuck in 'running' mode under the 'status' column. I tried killing the task but it wouldn't die. I killed the application and restarted, but the task kept running. I cloned the job and then deleted the original job and it seemed to kill the task to where it didn't show it was running still, but upon the first run of the job, I was back to the same problem. I finally realized that you have to restart the VC service from the 'Adiministrative Tools -> Services" on the server to get rid of the problem.
That fixed all my error problems.

Thanks for the response Trevinom. Due to the issues we are having with Visual Cron, lack of support, and the instability of the engine (the service stops itself when it encounters an error and there is no notification of the shut down), we scrapped our implementation with the latest project and went back to SQL Agent.

Sorry to hear that drandles. We are getting to implement VC in our production environment. I hope I don't experience the problems you encountered. :(

Thanks for the heads-up though.

Thanks for the response Trevinom. Due to the issues we are having with Visual Cron, lack of support, and the instability of the engine (the service stops itself when it encounters an error and there is no notification of the shut down), we scrapped our implementation with the latest project and went back to SQL Agent.

Hi Derek,

what kind of "lack of support" are you talking about and what instability of the engine? These are things we have never heard of and are happy to follow up on whatever problems you may have.

---

Hi drandles

It is unfortunate that you feel let down by support but I really think there is obviously a misunderstanding here. From my own experience I really cannot praise henrik and support highly enough. As an independent systems integrator, I don't think I have come across another software product that offers such a responsive level of support for their customers. The product itself has evolved amazingly over the last 9 months mostly as a result of requests for additional functionality from customers.

Having gone through a detailed evaluation of similar automation products, most of which were very costly, we chose visual cron for a major print automation and erp integration project and both myself and my customer stand by our decision and are glad we did so. Visual cron will now feature as a key component in any integration project I work on in the future.

Perhaps, if you do reconsider your position, you could provide some more information about the version of VC you are using and the platform you are running on we can do what we can as a community to help you make the most of VC functionality, as every day I am amazed at the possibilities of this product and the support provided.

Cheers

Andy