Running Unity 4.1(1). Servers all changed over correctly. Voicemail time stamps still 1 hour behind. Running Server 2000 on Unity servers, Exchange 2003 on Windows 2003 server. Outlook Web Access showing correct time stamps.
Logging in to the TUI, prompt is an hour behind.
What did I miss?
Solved! Go to Solution.
I was able to get this to work by manually disabling in time zone to do not update automatically on both exchange server and unity.
Just finished testing successfully and voicemail timestamps are correct. Hope this helps
So you just disabled the auto DST update under date & time in Windows?
Were your clocks OK prior to doing this?
I'll try this Monday and see what happens.
This did seem to take care of the time stamps but the event logs are now off by an hour.
Edit - Event log corrected itself.
Has anyone else seen this DST problem yet?
Updating the clocks manually seems to break something along the way.
First Unity box unregistered its ports with our Call Manager and went into failover mode.
I wonder if the clocks are trying to sync with our domain controllers which are correct.
I put everything back to auto and the correct time. The prompts are an hour behind but at least it all works.
Did you install the JRE Time Zone Update in addition to the Windows update?
Unity 4.2 also has ES59 that needs installed.
Unity 4.1(1) also has additional updates:
These instructions are for patching the time zone information used by the Unity Inbox in Unity 4.1(1) only if 4.1(1)ES34 is also present.
Pre-requisite: This update applies if the following two conditions on your Unity system are true:
1) Unity 4.1(1) is installed
2) Unity 4.1(1) ES34 is present
To determine if Unity 4.1(1) ES34 is installed, run the Gather Unity System Information (GUSI) tools from Tools Depot.
The report generated will list the Engineering Specials (ES) present on your system
If your Unity system does not meet the two pre-requisites above, do not proceed with this Engineering Special (ES) as it does not apply to your system.
Step 1: Open the Services MMC (type "services.msc" from Start -> Run) and stop the Tomcat service
Step 2: Make a backup of the following file found in path
Current File Name: TimeZoneData.properties
New File Name: TimeZoneData.properties.org
Step 3: In the folder containing this ReadMe.txt, copy the file TimeZoneData.properties to path
Step 4: Open the Services MMC (type "services.msc" from Start -> Run) and start the Tomcat service
Yes, the JRE Time Zone Update WAS applied to both of our Unity boxes in addition to the Windows patch.
The ES patch was NOT installed as we didn't meet the pre-requisite to install it. We don't have ES34 installed:
Unity Install Information:
Unity server name = UNITY1
Unity version = 4.1(1.0)
No Engineering Specials installed
Logging diagnostics and data files to= d:\CommServer\Logs\
Total capacity (megs)= 67142.93
Megs free= 50797.2
% free space= 75.66
UMR repository location= d:\CommServer\UnityMTA\
Total capacity (megs)= 67142.93
Megs free= 50797.2
% free space= 75.66
Cisco Unity TSP version = 8.0(2)
CSAgent = -not installed-
Switch 1 = IPCM1
Switch 2 = Not installed
Ports configured = 72
Default recording codec = 8K Mu-Law
TUI Languages loaded = ENU
Default TUI Language = ENU
GUI Languages loaded = ENU
Default GUI Language = ENU
Default TTS Language = ENU
TTS Default Engine =
Standard Unity conversation in use
Did you try running the JRE update again to make sure it says it was installed?
To verify the update was successful, issue the same command:
"X:\CommServer\cscoserv\Java2SDK\jre\bin\java -jar tzupdater.jar -u -v"
and verify the returned text contains this statement:
"You have the same version as the embedded one."
Is this a Unified or VM only installation?
I did when it was installed last week and just did it again to verify.
I get "You have the same version as the embedded one." on both servers.
This is a Unified installation but being used as VM only. In other words we have a separate Exchange 2003 server running but are only using it for voice mails.
Wow...really running out of options!
Did you run Microsoft's TZEDIT just to verify the time zone was correctly edited?
Did you try stopping and restarting the Tomcat service?
just got off with cisco tac, and they suggested (altho there are no notes about it) that the Unity box needs to be reloaded, and possible exchange server for the dst patches to take effect.
obviously can't do that in the middle of the day, so will update later if that solves it.
the server correctly rolls to DST, but tac said that rebooting seems to be the trick..
windows.. when in doubt.. reboot.
per cisco tac, jre is only for the pca interface.. would have nothing to do with time stamping on msg's,thats between exchange and unity.
I'm off to the reboot fairy tonight. see if that solves the issue.
I've rebooted Unity a few times today with no effect.
Have not rebooted Exchange server though. Will give it a try tonight also.
Wish my Cisco equipment updated as easy as my Microsoft systems did.
Nice of TAC to keep us updated!
Certain Windows systems are showing the wrong time even though the DST patch has been applied to the system: Simply change the time zone to some other time zone manually on the affected system, apply it, and then change it back to the correct time zone.
Here are some details on this:
I did have this happen on all my Win2000 boxes. Just unchecking the 'Auto apply DST' box, applying the change, and then checking the 'Auto apply DST' box fixes it.
Wonder if this has to happen from now on though?
I am running 4.2(1) for a client, the server not in production yet, so no worries here about the DST changes. I had applied ES59 and JRE updates as required last week. I tested over the weekend, changed the time to 1.59 am and the time did change succesfully to 3.00 am. So I was hoping things should work properly on Monday. I see on Monday that the time never changed properly at all over the weekend. The server clock and timestamps were an hour off. I had to manually change the time on the server today..
if you haven't already, you may want to visit the field notices for Unity and Connection noted in this post:
Rebooting the Exchange message store did not do a darn thing to the time stamps. They are still an hour behind.
The only thing we have not applied was the Exchange patch described in the link above. I'm reluctant to apply it due to the fact that messages may stop flowing.
Has anyone applied this Microsoft Exchange patch and if so did you run into any problems with Unity?
I'll give this a try. Sounds as if the key is to shut down Unity (not the entire server) and change the time zone. Just rebooting doesn't work since Unity is starting with the server.
Unity 4.2.1. Server is set for no auto DST.
Time sone is set for Arizona. Time stamps in Exchange for left messages show correct time. Phones show correct time. TUI readback of messages are an hour off. Will try rebooting server.
Has anyone gotten this issue resolved. I didn't have this problem going into Tuesday, however now I do. My Unity VM's are 1 hour behind, but the system clock is fine.
The easiest fix providing you have applied the DST patches to the OS is (at least for me):
1. On your Unity server stop Unity but don't shutdown the entire server.
2. Once Unity has stopped, go to the date / time control panel applet and change your time zone to something different. CLICK APPLY.
3. In the same applet, change your timezone back to your normal time zone. CLICK OK.
4. Start Unity.
Do the same on the failover if you have one.
Hope this helps.
I thought I had heard that the Exchange patch from MS did not work as well as they thought it would. I have been hearing rumbles about Outlook not working right for appointments.
If you have failover running with Unity, I think that if the Primary's time is different than the failover server, the SQL database will come off it's rocker for replication cause a failover trigger to happen. This drops the TSP ports and may trigger the "flipping" failover from primary to secondary and vice versa.