Hello

One of my servers has had repeatedly service crashes, about any 45 minutes, starting suddenly the other day. Now I had to set service to recover at crash, to not have production interrupted too much.

This is the event log entries:
Faulting application name: VisualCronService.exe, version: 7.0.5.14362, time stamp: 0x52331302
Faulting module name: clr.dll, version: 4.0.30319.18052, time stamp: 0x5173c114
Exception code: 0xc00000fd
Fault offset: 0x00000000000cba4f
Faulting process id: 0x524
Faulting application start time: 0x01cecc22ee6c659e
Faulting application path: C:\Program Files (x86)\VisualCron\VisualCronService.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Report Id: aa7f4e91-381c-11e3-a9af-005056b63e65


An upgrade to 7.0.6 did not help. I saw another poster complaining about crashes realted to automatic update, and this could be the same problem. Before upgrading to 7.0.6 it could seem to be related to the auto upgrade box on the screen, but an upgrade did not make any differnce.

😠 😕

Hi Svei,

please send log_serverDATE.txt to support@visualcron.com.

---

I have the same thing happening on a server running 2003 server and VC ver 7.04, service crashes a few times a day.

Below is from the event logs.

Application: VisualCronService.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
Stack:
at VisualCronAPI.ImpersonationClass.LoadUserProfile(IntPtr, PROFILEINFO ByRef)
at VisualCronAPI.ImpersonationClass.Impersonate(System.String, System.String, System.String, Boolean, Boolean, Boolean, Boolean, Boolean, Boolean, LOGON_TYPE, LOGON_PROVIDER)
at VisualCronAPI.ImpersonationClass.Impersonate(VisualCron.NetworkCredentialClass)
at VisualCronService.EventFileClass.JGIPIGFJDLNNJLOENBHPCOIFDLPEHLECCKFN(System.String, System.String, System.IO.WatcherChangeTypes)
at VisualCronService.EventFileClass.KINOILFOJDOKONONDDCGMMFEGJALPHDBFGGJ(System.Object, System.IO.FileSystemEventArgs)
at System.IO.FileSystemWatcher.OnCreated(System.IO.FileSystemEventArgs)
at System.IO.FileSystemWatcher.NotifyFileSystemEventArgs(Int32, System.String)
at System.IO.FileSystemWatcher.CompletionStatusChanged(UInt32, UInt32, System.Threading.NativeOverlapped*)
at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32, UInt32, System.Threading.NativeOverlapped*)

I have the same thing happening on a server running 2003 server and VC ver 7.04, service crashes a few times a day.

Below is from the event logs.

Application: VisualCronService.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
Stack:
at VisualCronAPI.ImpersonationClass.LoadUserProfile(IntPtr, PROFILEINFO ByRef)
at VisualCronAPI.ImpersonationClass.Impersonate(System.String, System.String, System.String, Boolean, Boolean, Boolean, Boolean, Boolean, Boolean, LOGON_TYPE, LOGON_PROVIDER)
at VisualCronAPI.ImpersonationClass.Impersonate(VisualCron.NetworkCredentialClass)
at VisualCronService.EventFileClass.JGIPIGFJDLNNJLOENBHPCOIFDLPEHLECCKFN(System.String, System.String, System.IO.WatcherChangeTypes)
at VisualCronService.EventFileClass.KINOILFOJDOKONONDDCGMMFEGJALPHDBFGGJ(System.Object, System.IO.FileSystemEventArgs)
at System.IO.FileSystemWatcher.OnCreated(System.IO.FileSystemEventArgs)
at System.IO.FileSystemWatcher.NotifyFileSystemEventArgs(Int32, System.String)
at System.IO.FileSystemWatcher.CompletionStatusChanged(UInt32, UInt32, System.Threading.NativeOverlapped*)
at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32, UInt32, System.Threading.NativeOverlapped*)

The fix for this is easy. Find the Credential that you use in the File Trigger. The edit it and uncheck "Local logon".

---

Henrik,

I will give this a try. Can you tell me why the "Local Login" should not be checked for the file triggers?

And why does it crash the service? Is this going to be fixed in an update?

Henrik,

I will give this a try. Can you tell me why the "Local Login" should not be checked for the file triggers?

And why does it crash the service? Is this going to be fixed in an update?

We have not found yet. We have seen it on some systems. But if you are trying to gain access to network folder you should not use "Local logon". And if it is a local folder you probably not need "Local logon" for this Task.

---

Henrik,

This seems to have fixed the issue, can you give me a scenario that you would use the local login check box?

Foreground processes maybe?

Yes, here are some scenarios;

1. you want to Execute a process as a certain user
2. you want to copy from a user locked folder

---