I have a strange situation that I have recreated on multiple WebIntelligence servers. I would like to see if anyone can confirm or contradict what I have found. Technical support says theirs is working fine.
In the Time Zone tab of the date/time properties of the NT server (running IIS 4.0 and WebI 2.0), if the “automatically adjust clock for daylight savings time” box is checked I get some time errors. The time on the server is correct and it doesn’t change regardless of the “daylight savings time” box because we are no longer in daylight savings time.
For WebI documents everything works fine. However for 4.1 documents exported to the repository the time is off by ONE hour in the corporate documents listing. So for example if I export a 4.1 document at 9:00 AM and then go to WebI, login, and refresh the corporate documents listing the time says 8:00 AM. If I uncheck the “daylight savings time” box on the server, logout of WebI (this is required), log back in and refresh the corporate documents list the time is now correct at 9:00 AM! I can toggle this back and forth to recreate the situation and I have done it on two different servers.
Greg,
It’s funny that you mention the 1 hour thing. I have my environment set up and no matter what time a user send a document to the doc agent in 4.11- it is 1 hour different in their console, yet when I look directly at the doc agent scheduled time, it is exactly (correct time). Is this a known bug ? laurenf@bellatlantic.net
“Mills, S. Greg” wrote:
I have a strange situation that I have recreated on multiple WebIntelligence servers. I would like to see if anyone can confirm or contradict what I have found. Technical support says theirs is working fine.
In the Time Zone tab of the date/time properties of the NT server (running IIS 4.0 and WebI 2.0), if the “automatically adjust clock for daylight savings time” box is checked I get some time errors. The time on the server is correct and it doesn’t change regardless of the “daylight savings time” box because we are no longer in daylight savings time.
For WebI documents everything works fine. However for 4.1 documents exported to the repository the time is off by ONE hour in the corporate documents listing. So for example if I export a 4.1 document at 9:00 AM and then go to WebI, login, and refresh the corporate documents listing the time says 8:00 AM. If I uncheck the “daylight savings time” box on the server, logout of WebI (this is required), log back in and refresh the corporate documents list the time is now correct at 9:00 AM! I can toggle this back and forth to recreate the situation and I have done it on two different servers.
I’m not currently using WebI, but do have one suggestion that might help.
WindowsNT and Windows95 do not handle time and time changes the same way. If you’re always seeing the correct time on an NT machine, and seeing conflicting results from 95 workstations, it might be Microsoft to blame, and not Business Objects. If the time is varying from NT workstation to NT workstation, make sure that they have been setup in the same timezone. I recently read an excerpt from a Microsoft Knowledge Base article on this topic, (I don’t have the article number) but that would be another place to look.
In the Time Zone tab of the date/time properties of the NT server (running IIS 4.0 and WebI 2.0), if the “automatically adjust clock for daylight savings time” box is checked I get some time errors. The time on the server is correct and it doesn’t change regardless of the “daylight savings time” box because we are no longer in daylight savings time.
For WebI documents everything works fine. However for 4.1 documents exported to the repository the time is off by ONE hour in the corporate documents listing. So for example if I export a 4.1 document at 9:00 AM and then go to WebI, login, and refresh the corporate documents listing the time says 8:00 AM. If I uncheck the “daylight savings time” box on the server, logout of WebI (this is required), log back in and refresh the corporate documents list the time is now correct at 9:00 AM! I can toggle this back and forth to recreate the situation and I have done it on two different servers.