DST Problems

[twix79]

We applied the latest SP6 to the MSS and the Microsoft changes to the MAS, but are having some issues this morning. The system clocks all show the proper time, but when reviewing messages the time in the header is an hour earlier. Interestingly the subscriber activity log shows the proper time as well as the time stamp on the a Notify Me message. We are on 2.0.1, SP6 version 32.7. I have a call out to Avaya, but was wondering if anyone else had similar issues?

 

[ChuckRCT]

I haven't had a chance to test it out, but I did have a couple customers that didn't load SP6 32.7 where I was changing the time manually. They also had the TZEdit utility loaded on the Windows 2000 Server. The time.bat file when run from the MAS to synch with the MSS was not working correctly. It would add an additional hour. I had to uncheck the "automatic adjusment for DST" field to get the time.bat file to work correctly. I'm not sure if this is related to your problem but maybe the TZEdit is affecting your system?

Chuck
RCT Technologies

 

[twix79]

I'm not sure if that is the case or not right now. All of the system clocks agree with the right time, it is just the timestamp associated with the header. My initial response from Avaya was that it is a wide-spread problem and high level management is involved in finding the resolution. It sounds like they have been pretty overwhelmed with calls, so I haven't received any additional feedback beyond that yet. I will update this post if I receive any news.

 

[twix79]

This appears to function different for Audix versus Aria. I left a message in a mailbox and checked with an Audix COS. The header was an hour off. I changed the COS for that mailbox to Aria, worked perfectly. Changed back to Audix and it showed up an hour off again.

Not much for new updates from Avaya yet...just that they have several Tier 4 engineers working on case with development.

 

[twix79]

New update...since the problem appeared to be only related to Audix, I decided to look at IIS. Stopping and restarting all of the IIS services fixed this issue for me on all of my servers.

So, the necessary steps are:

MSS - Apply SP6 (version 32.7)
MAS - Run tzedit.exe (including steps j & k in Control Panel)
MAS - Stop and start IIS services