[Solved] Cannot start Scheduler on Server 2019
Hi Guys
Migrated from our 2012R2 server across to 2019, and since then we are unable to install the Scheduler service. The scheduled fails to start noting an assmembly error:
Service cannot be started. System.TypeInitializationException: The type initializer for ‘Quartz.Impl.StdSchedulerFactory’ threw an exception. —> System.IO.FileLoadException: Could not load file or assembly ‘Common.Logging.Core, Version=106.3.1.0, Culture=neutral, PublicKeyToken=af08829b84f0328e’ or one of its dependencies. The located assembly’s manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) —> System.IO.FileLoadException: Could not load file or assembly ‘Common.Logging.Core, Version=3.4.1.0, Culture=neutral, PublicKeyToken=af08829b84f0328e’ or one of its dependencies. The located assembly’s manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
— End of inner exception stack trace —
at Quartz.Impl.StdSchedulerFactory..cctor()
— End of inner exception stack trace —
at Quartz.Impl.StdSchedulerFactory.ValidateConfiguration()
at Quartz.Impl.StdSchedulerFactory.Initialize(NameValueCollection props)
at CPService.C…
Equally, we could not upgrade the scheduler service on our 2012R2 box either
Any ideas?
Logged in to take a look and for some reason the updater did not update the config file for the scheduler. So the DLL’s referenced in the config file were pointing to the incorrect version for Common.Logging.Core.dll. I completely removed the scheduler files and just installed the CloudPanel Scheduler fresh to resolve it.
Hi Jacob
Its the latest – CloudPanel 3.2.0315
Cheers
@Jacob Dixon
Still broken. Just tried it again on the latest version, and getting the same error. Any ideas?
Please email me directly at jdixon@knowmoreit.com. I will have to connect and check it out.
- 5 Forums
- 716 Topics
- 3,649 Posts
- 1 Online
- 259 Members