08-31-2015 05:48 AM - edited 03-20-2019 08:42 PM
Hi,
Can anyone confirm whether is there any fix for this bug ?
03-02-2017 07:45 AM
I can tell you that the Workaround given ("Issue will go after the restart tomcat or the node itself"), does work...temporarily. We have had issues with this since upgrading to 10.5.2.13900-12 and have since restarted the tomcat service as well as the node itself. After each restart the time started to show correctly (using EST instead of UTC time) but then would randomly go back to UTC without any system changes. Sometimes it would be correct for a weekend, sometimes an entire 2 weeks. Currently trying to find what triggers the failure (going back to UTC) to see if it can be prevented. Might end up needing to just update system.
09-17-2017 10:53 PM - edited 09-17-2017 11:01 PM
I am performing this fix today. I shall revert with update.
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCuu63399/?reffering_site=dumpcr
Symptom: Server Time Displayed in UTC Format in BAT scheduler page. CCM ADMIN --> Bulk Administration --> Job Scheduler
Workaround: Issue will go after the restart tomcat or the node itself.
05-15-2018 08:16 AM
I've had the same problem. I preformed the suggested workaround. Update TMZ to something else, reboot...change back to TMZ desired and reboot again (publisher only). It fixed it for about 2 days!!
This creates a lot of headaches when scheduling BAT jobs. Anybody got a permanent fix other than an upgrade to 11.5?!?! TAC/Cisco...please write a .cop fix for this!!!!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide