Just to let you know, I encountered a similar problem when upgrading from 4.9.2 to 4.9.3 on a test server (Windows Server 2003, R2, SP2) which was resolved by uninstalling 4.9.2 and a fresh install of 4.9.3 rather than an upgrade to the new version.
The method not found was a little different:
'Int32 VisualCron.FileEventClass.get_Interval()'
Then the following lines were:
at rHorOBa26hO3qVhtla1.0GlNgdar5hYRWBQJPaN.T5nl1O6v7()
at rHorOBa26hO3qVhtla1.0GlNgdar5hYRWBQJPaN.6mjNCGEaIb()
at iD5Ndca31y3rNl5RXiG.ExyyNOak9Ia3Tm0ehMc.rOQmsMp0g()
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
It kept trying to restart the server ("starting restarter"), and would get the recurring error after "loading jobs".
The errors started when trying to create a new job shortly after the upgrade to test the file triggers in this version (there were not existing jobs with file triggers on that server.)
We have some production servers to upgrade to the new version, that do have jobs with existing file triggers. Is this likely to recur unless we do a new install on each of them, or is there a fix that should allow an upgrade?
Edited by user
2008-06-18T10:07:56Z
|
Reason: Not specified