So visual cron seems to crash on us every couple of days causing our jobs not to run. On inspection of event log I found the following VC error:


*****************************
An unhandled error has occured (please send the information below to support@visualcron.com):

Server version: 5.5.0.17433 - (2009-12-22)
Protocol: 5.1.3
OS: Windows2003


System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
at System.String.InternalCopy(String str)
at System.Text.StringBuilder.ToString()
at OBOKIIHBDBPMCFALPGECCIFHCDJPEDKODDGK.CCEDIKOJOACMABGAIHHOHPJCDMJPDMLJKHNK.EPOGAFJJMELOGIDDGJOALGAMEFGJNONOALDC()
at OBOKIIHBDBPMCFALPGECCIFHCDJPEDKODDGK.CCEDIKOJOACMABGAIHHOHPJCDMJPDMLJKHNK.FPDFJBKIDPGOHFPMFHLFLCAEFAPNIPNIICAI()
at OBOKIIHBDBPMCFALPGECCIFHCDJPEDKODDGK.OIBJEFOGNEPACHAMDIDCNAGMMCNHOOEINEMF.Dispose(Boolean )
at OBOKIIHBDBPMCFALPGECCIFHCDJPEDKODDGK.OIBJEFOGNEPACHAMDIDCNAGMMCNHOOEINEMF.Dispose()
at OBOKIIHBDBPMCFALPGECCIFHCDJPEDKODDGK.OIBJEFOGNEPACHAMDIDCNAGMMCNHOOEINEMF.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()

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

**************************


The job i believe that is causing the failure downloads a file from an FTP then reads the file to verify it is there. The file is fairly large (600MB) however we have plenty available memory (over 2gb avail, 4GB total) and our other usage is low.

Does VC have a cap on the amount of memory it can use when storing the standard output? and if so is there a suggestion on another way i can verify the file was downloaded sucessful and is not corrupted?

jonathan.

Hi Jonathan,

could you please try the same with version 5.5.5.?

---

ok will need to install it after hours though. the error happens with the job at 8pm so i should have the results for you tomorrow.

thanks Henrik!

Hey Henrik,

We installed 5.5 and it was working fine for a while but failed again last night with the same error. Any ideas?

Jonathan.

Do you have the log file from the crash with 5.5.5. We see that this problem is handled in 5.5.5. (but not 5.5.0) so we would like to see the full error from 5.5.5.

In this case we are talking about the size of the output of a Task. Do you really need to read the file to verify it is there? Even though we handle this it will still throw an error because memory usage is too big. Use a Condition instead to verify that the file is there.

---