Getting exception from scheduled task

[packetloss]

Hopefully this is something simple to figure out. When I run (1.1.3 but same thing happened with the previous versions as well (1.0 - current) manually everything works fine every time. It downloads the listings and loads it into WMC and I have a full 20 days of guide data.

However, whenever the scheduled task runs (on Windows 7) I get the following exceptions:

Log Name: Application
Source: .NET Runtime
Date: 3/5/2017 3:02:02 AM
Event ID: 1026
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: htpc
Description:
Application: epg123.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: Newtonsoft.Json.JsonReaderException
Stack:
at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.Deserialize(Newtonsoft.Json.JsonReader, System.Type, Boolean)
at Newtonsoft.Json.JsonSerializer.DeserializeInternal(Newtonsoft.Json.JsonReader, System.Type)
at Newtonsoft.Json.JsonConvert.DeserializeObject(System.String, System.Type, Newtonsoft.Json.JsonSerializerSettings)
at Newtonsoft.Json.JsonConvert.DeserializeObject[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]](System.String, Newtonsoft.Json.JsonSerializerSettings)
at epg123.sdApi.SdApi.sdGetRequestResponse(METHODS, System.String, System.Object, Boolean)
at epg123.sdApi.SdApi.sdGetScheduleMd5s(epg123.sdApi.sdScheduleRequest[])
at epg123.sdJson2mxf.getMd5ScheduleEntries(System.String[], Int32)
at epg123.sdJson2mxf.getAllScheduleEntryMd5s(Int32)
at epg123.sdJson2mxf..ctor(epg123.epgConfig)
at epg123.Program.Main(System.String[])

[garyan2]

I'm not quite sure where this one is coming from. It certainly can't be from epg123.sdApi.SdApi.sdGetRequestResponse(METHODS, System.String, System.Object, Boolean) since everything there is in a try/catch. Is there anything in the trace.log file?

[packetloss]

I think I discovered the problem. I had a folder with v 1.0xx in it and another folder with 1.1.x in it and even though I set up the scheduled job from 1.1.x it was referencing the 1.0.x exe. Once I deleted that folder and rescheduled the job everything seems to run fine.