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.


ErikC
  •  ErikC
  • Paid support Topic Starter
2010-09-09T11:15:26Z
I have a job which runs in queue mode.

I have an other job with a few 'run job' tasks running this job.

I got an error doing this:


Server version: 5.5.5.28661 - (2009-03-03)
Protocol: 5.1.3
OS: Windows2003


System.NullReferenceException: Object reference not set to an instance of an object.
   at OBOKIIHBDBPMCFALPGECCIFHCDJPEDKODDGK.GHAMFGCEDFOEIDCMEENNAFIOCECPBDKLJMLG.KCNEAGBIECJPPHEIOEECJGLJEMGKOIJJMDOF(JobClass& , TriggerClass , TriggerResultCloneClass )
   at OBOKIIHBDBPMCFALPGECCIFHCDJPEDKODDGK.GHAMFGCEDFOEIDCMEENNAFIOCECPBDKLJMLG.CDNOOLGEPGBGGJAMMEDFMIIMLGEDLDMDDNGK(JobClass& , TriggerClass , Boolean , TriggerResultCloneClass , JobClass )
   at OBOKIIHBDBPMCFALPGECCIFHCDJPEDKODDGK.CBPMOIAKMKCNPCNCCLDABHKDCFAMOELCEBAP.AJJPAOPPMKGOGDNPAABOMEODMMKBOBEPBLLP()
   at OBOKIIHBDBPMCFALPGECCIFHCDJPEDKODDGK.CBPMOIAKMKCNPCNCCLDABHKDCFAMOELCEBAP.Run()
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()


The client hung AND the server service stopped.

I really didn't like the service stopped....

Regards,
Erik
Uses Visualcron since 2006.
Sponsor
Forum information
Support
2010-09-09T14:35:42Z
Perhaps it is referencing to a Job that does not longer exist?

Is it possible to export the settings and let us test to run that particular Job - then we will find the exact reason right away.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
ErikC
  •  ErikC
  • Paid support Topic Starter
2010-09-09T16:02:20Z
I will give you the steps to reproduce the issue in 5.6.7-2:

- Make two jobs.
- In the 1st you check the 'Put in queue'
- The 2nd has two Run Job tasks and they will run the 1st job

Start the 2nd. It will run and you can't stop it anymore.

Edit the 1st task in the 2nd job and remove the checkbox: 'Run synchronous'

Run the 2nd job again.

I played a little and there is the error:


9/9/2010 3:31:49 PM	Err	An unhandled error has occured (please send the information below to support@visualcron.com): 

Server version: 5.6.7.21485 - (2009-09-02)
Protocol: 5.6.2
OS: Windows2003


System.NullReferenceException: Object reference not set to an instance of an object.
   at OBOKIIHBDBPMCFALPGECCIFHCDJPEDKODDGK.GHAMFGCEDFOEIDCMEENNAFIOCECPBDKLJMLG.KCNEAGBIECJPPHEIOEECJGLJEMGKOIJJMDOF(JobClass& , TriggerClass , TriggerResultCloneClass )
   at OBOKIIHBDBPMCFALPGECCIFHCDJPEDKODDGK.GHAMFGCEDFOEIDCMEENNAFIOCECPBDKLJMLG.CDNOOLGEPGBGGJAMMEDFMIIMLGEDLDMDDNGK(JobClass& , TriggerClass , Boolean , TriggerResultCloneClass , JobClass , Boolean )
   at OBOKIIHBDBPMCFALPGECCIFHCDJPEDKODDGK.CBPMOIAKMKCNPCNCCLDABHKDCFAMOELCEBAP.AJJPAOPPMKGOGDNPAABOMEODMMKBOBEPBLLP()
   at OBOKIIHBDBPMCFALPGECCIFHCDJPEDKODDGK.CBPMOIAKMKCNPCNCCLDABHKDCFAMOELCEBAP.Run()
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()



Regards
Erik
Uses Visualcron since 2006.
ErikC
  •  ErikC
  • Paid support Topic Starter
2010-09-10T08:22:21Z
An addition to above:

If you remove one task from the 2nd job, so only having 1 run job task it works fine.
The job Result and Status of the 2nd job will stay on 'Running' though, even when the 2nd job (with only one run job task) finishes.
Uses Visualcron since 2006.
Support
2010-09-10T12:25:08Z
Thanks for your testing. We believe we have fixed the issue.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
ErikC
  •  ErikC
  • Paid support Topic Starter
2010-09-10T15:06:21Z
Fixed in 5.6.8, thanks! 😍

Regards,
Erik
Uses Visualcron since 2006.
buzzlightyear
2011-02-21T12:02:33Z
I'm experiencing a similar or related problem. The last task of the 1st job starts the 2nd job. The 2nd job only executes the 1st task, the other tasks are not completed due to Conditions on them. It seems that because the 2nd job don't run all of its tasks, it is not seen as having completed, so the last task of the 1st job says Running, even though the 2nd job has completed and has a Waiting status.

EDIT: Forgot to add, I'm running 5.6.9.
Scroll to Top