XMLTV Reader Fails to Recognize Time Zone

[lastlegends]

I have been running a custom python script to parse / output an XMLTV file that I load into NPVR for TV listings (common free EPG grabbers often don't have my area and I don't want to pay a yearly fee for one). Everything was working fine until the time change last weekend. Now whenever I try to load my XMLTV listings it acts like everything is okay but if I check the log file it has literally thousands of lines saying:
2014-11-08 21:19:12.059 [ERROR][8] XMLTV EPG Reader - Unknown timezone: MDT

I checked the time zone on the Windows machine itself (in the registry and in the little time program on the start bar) and both say that the machine is in MST. The script I use to output the XMLTV file also accounts for daylight savings time changes and has the correct MST UTC offset (in numbers, not text). Running the validity checker provided by the XMLTV project on my XMLTV file says the only issue is with the channel IDs but that was never an issue in the past so that most likely isn't it. Typical programme entries in my XMLTV file look like:
<programme start="20141110180000 -0700" stop="20141110190000 -0700" channel="XXXXXX">

I have also tried rebooting the machine in question on the off chance that the NPVR setting never got updated after the time change.

Emptying the EPG and then updating it also did not solve the problem.

Attached is part of a log file demonstrating what I mean. It is also worth noting that I only have about 5 channels that I'm using the XMLTV listing for, despite the thousands of error messages in the log file.

Does anyone have any insights on this? I liked having the XMLTV guide as it gave more info about shows and it allowed me to get a variable time span of listings whereas the OTA listings don't always span 24 hours, making it hard to make sure programs scheduled for recording with auto-record feature.

[sub]

You'd probably need to supply a sample xmltv file.

[mvallevand]

Does it work with MST which started last weekend?

Martin

[lastlegends]

Well, in the course of answering the comments / questions you guys posed I seem to have stumbled upon the answer. It appears that even though the EPG updater was pointed to the correct file it was not correctly reading that file for whatever reason. When the issue began occurring it was also pointing to that file but was missing a specific channel from that file in the selection box. I simply went through and re-selected the channel I wanted when I discovered this. However, it appears if I re-select the file location and then choose my channel everything works perfectly.

[sub]

Ok, great.