Has anyone successfully applied these Daylight Savings Time (DST) patches yet....
1.) Windows Server 2003 DST Patches (from Microoft)
2.) BOE-XI (R2) MONTHLY HOT FIX 1
3.) BOE-XI (R2) CRITICAL HOT FIX 15
We are testing it on our DEV environment - and the Microsoft patch appears to break our page servers.
I'm dowloading the BOE-XI (R2) patches but they are taking hours (probably everyone had the same idea). My first couple of attempts at downloading the BOBJ patches delivered corrupted zip files.
Anyone done this successfully yet - patched the OS and the application...?
We are using Crystal Enterprise 10 on Windows 2000 Server and have applied the following patches in order listed:
Service Pack 6 10.0.101.8012 service pack
(this is the order that Business Objects recommends)
1. Common10win_en.exe v10.0.103.1544 weekly
2. CE10win_en.exe v10.0.101.1566 weekly
3. Viewers10win_en_200611.exe v10.0.104.5032 monthly
Also, all Microsoft TZ patches were previously applied to the server.
The effect on our environment after applying all patches for the OS and CE 10 is that ALL of the recurring jobs are now scheduled to run 1 hour later than originally scheduled.
We have the same problem. The report which has scheduled for 11am that has actually run on 12pm but the report runtime is 12. We have installed CE patch.
We did restart the server after applying the patches (and no we are not clustered).
One interesting thing is that the Microsoft OS patches we applied to the Windows 2000 Server/Professional machines did not work properly. We actually had to go into the Time Zone settings and change from our time zone to another time zone and back again for the fix to be applied properly.
My theory is that our production evironment ran with the psuedo-fixed OS and did not recognize that March 11 was the beginning of EDST. After we fixed the OS problem and restarted the server, the system now recognized ESDT properly but too late for all the scheduled jobs to be set for the proper time.
Still waiting to hear back from a tech at Business Objects to work on this issue.
We have rebooted the server. I have just scheduled one report and the report run time is current but the instance time from history is one hour behind. I guess Crystal Repository database did not update for some reason.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.