APAR status
Closed as program error.
Error description
ABSTRACT: Times are incorrect by 2 hours with Windows XP SP3.... ....... ................................................................ ...... Environment: Client OS and level: XP SP3 Server OS and level: 2003 SP2 Database and level: Oracle 10g Scenario: All of our client machines are running Windows XP with a mixture of SP2 and SP3. When XP SP3 is installed all times within SmarTeam are ahead by two hours. 1) For example the system clock reads 13:21 2) Perform an update operation in SmarTeam on any object 3) If the client has SP3 installed the modified time will be '15:21' 4) If the client has SP2 installed the modified time will read '13:21' 5) We have tried the operation on a XP SP2 machine, everything is correct. The same machine is then upgraded to XP SP3 and the sameoperation performed. The time is incorrect. This issue was originally identified on R17SP8 but XP SP3 was not supported by SmarTeam. The problem was also only identified to occur during British Summer Time (March - October), this has not been confirmed in R19 yet, For recreating this problem I was using following procedure: 1. install ST foundation, ST editor and demo environment on XP ( virtual machine). 2. create a word document and add it to SmarTeam 3. check the timestamp of the added doc and compare with system time 4. install XP SP3 5. repeat step 2 and step 3 --> no problem detected. system time and creation date are ok 6. change time zone in XP to GMT (Dublin, London) 7. repeat step 2 and step 3 --> creation date in ST is 2 hrs ahead compared to system tim e.
Local fix
Problem summary
ABSTRACT: Times are incorrect by 2 hours with Windows XP SP3........... ................................................................ ...... Environment: Client OS and level: XP SP3 Server OS and level: 2003 SP2 Database and level: Oracle 10g Scenario: All of our client machines are running Windows XP with a mixture of SP2 and SP3. When XP SP3 is installed all times within SmarTeam are ahead by two hours. 1) For example the system clock reads 13:21 2) Perform an update operation in SmarTeam on any object 3) If the client has SP3 installed the modified time will be '15:21' 4) If the client has SP2 installed the modified time will read '13:21' 5) We have tried the operation on a XP SP2 machine, everything is correct. The same machine is then upgraded to XP SP3 and the sameoperation performed. The time is incorrect. This issue was originally identified on R17SP8 but XP SP3 was not supported by SmarTeam. The problem was also only identified to occur during British Summer Time (March - October), this has not been confirmed in R19 yet, For recreating this problem I was using following procedure: 1. install ST foundation, ST editor and demo environment on XP (virtual machine). 2. create a word document and add it to SmarTeam 3. check the timestamp of the added doc and compare with system time 4. install XP SP3 5. repeat step 2 and step 3 --> no problem detected. system time and creation date are ok 6. change time zone in XP to GMT (Dublin, London) 7. repeat step 2 and step 3 --> creation date in ST is 2 hrs ahead compared to system time.
Problem conclusion
NOTE THAT THIS PROBLEM WILL ALSO BE FIXED ON V5R20 SP1. Additional Closure Information: Time stamp within SmarTeam is synchronized with system time. Fixed in V5R20SP1.
Temporary fix
Comments
APAR Information
APAR number
HD89952
Reported component name
SMARTEAM NT>XP
Reported component ID
569199970
Reported release
519
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-10-22
Closed date
2011-05-26
Last modified date
2011-05-26
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
SMARTEAM NT>XP
Fixed component ID
569199970
Applicable component levels
R520 PSN
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS2S3T","label":"ENOVIA SmarTeam V5"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"519","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
26 May 2011