ZDATE_ILLEGAL_LOCTIME occurring in specific time

[Former Member]

Hi All,

ABAP Dumps ZDATE_ILLEGAL_LOCTIME are occurring in PI system in specific time regularly.

I have went for OS reboot for both Application and DB Server and then make sure that DB and Application servers has same time stamp and then started SAP and DB services. But still we are facing these dumps regularly in particular time and later these dumps are not repeating in the day.

We had same issues earlier to other Systems. Reboot of the servers has fixed but now it doesn't fixed the issue.

From the dump analysis, I could see the Source is trex system and Patrol is the user responsible for all the dumps. But I am not understanding what actually being carried with user Patrol from trex system. Please see the below details from dump.

Please advise, how can I check this issue.

Application server... "XXXXXXXX"

Network address...... "XXXXXXXX"

Operating system..... "Windows NT"

Release.............. "6.1"

Hardware type........ "2x AMD64 Level"

Character length.... 16 Bits

Pointer length....... 64 Bits

Work process number.. 7

Shortdump setting.... "full"

Database server... "XXXXXXXXX"

Database type..... "MSSQL"

Database name..... "PIP"

Database user ID.. "pip"

Terminal.......... "Trex "

Char.set.... "C"

SAP kernel....... 720

created (date)... "Oct 10 2014 16:47:53"

create on........ "NT 5.2 3790 S x86 MS VC++ 14.00"

Database version. "SQL_Server_9.00 "

[Sriram2009]

Hi Reddy.

You have to check the time zone & Time settings in OS & server Bios level.Kindly refer the SAP KBA

2017092 - ZDATE_ILLEGAL_LOCTIME or ZDATE_LARGE_TIME_DIFF in VMWare environments.

Regards

SS

[Former Member]

Hi Sriram,

Thank You.

I have checked the time zone and time settings, everything seems to be fine.

Can you please let me know how can I check it from server bios level?

But I have the problem with only one user(PATROL) and here source is external server. But how come if the user calling the external system that results in change in application and DB server?

I referred the KBA you have provided where it is recommending NTP. In my server already I could see that NTP server. Please refer below screenshot,

Please advise.

Regards,

Satyardha

[Sriram2009]

Hi Reddy.

1.  You can refer the SCN wiki link to check time settings

Timezone changes best practices - Basis Corner - SCN Wiki

2. Could you share the full dumps as text format attachement?

Regards

SS

[Former Member]

Hi Sriram,

Sorry, I am unable to attach the document here. Please find the dump details below,

Short text

    The local time of the application server is not correct.

What happened?

    Error in the SAP kernel

    The current ABAP program "????????????????????????????????????????" had to be

     terminated because the

    ABAP processor detected an internal system error.

What can you do?

    Please make a note of the actions and input which caused the error.

    -

    To resolve the problem, contact your

    SAP system administrator.

    Using transaction ST22 for ABAP dump analysis you can see and

    administrate termination messages and retain them for longer periods.

Error analysis

    The ABAP interpreter always determines the local time relative to the

  database time. To do so, it obtains both the time of the application

  server and that of the database at regular intervals. The times must

  meet specific plausibility criteria - for example, the time of the time

  stamp obtained second cannot be earlier than that of the time stamp

  obtained first.

  In this case, the plausibility criteria for the local time of the

  application server were not met.

  Earlier time stamp: "See former similar dump: Fri Jan 22 23:40:59 2016#"

  Later time stamp: "See former similar dump: Fri Jan 22 23:37:59 2016#"

w to correct the error

  It is possible that the time of the application server was set forward

  or back in the running system.

  Ensure that the times and time zones of the application server and

  database server match and restart the system.

stem environment

  SAP Release..... 711

  SAP Basis Level. 0013

  Application server... "PERSON"

  Network address...... "199.11.43.00"

  Operating system..... "Windows NT"

   Release.............. "6.1"

   Hardware type........ "2x AMD64 Level"

   Character length.... 16 Bits

   Pointer length....... 64 Bits

   Work process number.. 7

   Shortdump setting.... "full"

   Database server... "PETR"

   Database type..... "MSSQL"

   Database name..... "PIP"

   Database user ID.. "pip"

   Terminal.......... "douglas"

   Char.set.... "C"

   SAP kernel....... 720

   created (date)... "Oct 10 2014 16:47:53"

   create on........ "NT 5.2 3790 S x86 MS VC++ 14.00"

   Database version. "SQL_Server_9.00 "

   Patch level. 700

   Patch text.. " "

   Database............. "MSSQL 9.00.2047 or higher"

   SAP database version. 720

   Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows

    NT 6.0, Windows NT 6.1, Windows NT 6.2, Windows NT 6.3"

   Memory consumption

   Roll.... 0

   EM...... 4189792

   Heap.... 0

   Page.... 0

   MM Used. 760016

   MM Free. 3427104

ser and Transaction

   Client.............. 001

   User................ "PATROL"

   Language Key........ "E"

   Transaction......... " "

   Transaction ID...... "2B61C1E5BB50F152ADDF005056B00039"

   EPP Whole Context-ID.... " "

   EPP Connection ID....... " "

   EPP Caller Counter...... 0

   Program............. "????????????????????????????????????????"

   Screen.............. " "

   Screen Line......... 0

   Debugger Active..... "none"

   Information on caller of Remote Function Call (RFC):

   System.............. "########"

   Installation Number. "##########"

   Database Release.... 720

   Kernel Release...... 720

Connection Type..... "E" (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)

Call Type........... "synchronous and non-transactional (emode 0, imode 0)"

Inbound TID.........." "

Inbound Queue Name..." "

Outbound TID........." "

Outbound Queue Name.." "

Client.............. "###"

User................ "############"

Transaction......... " "

Call Program........." "

Function Module..... "GET_SYSTEM_TIME_REMOTE"

Call Destination.... "MS_CONNECTJOBSpersimmon3601patrolB4DC4EBC8743EB6D25F36D58

D68F48957A0D135C001EN"

Source Server....... "DOUG"

Source IP Address... "199.22.2.09"

Additional information on RFC logon:

Trusted Relationship " "

Logon Return Code... 0

Trusted Return Code. 0

Note:

- For Releases < 4.0, information on the RFC caller not available.

- The installation number is available from caller Release > 700

[Sriram2009]

Hi Reddy,

Thanks for your information. Message is clear short text "The local time of the application server is not correct" You have to check the time zone (in Application server... "PERSON") & Time. Normally latest version of Windows OS by default time zone is -8 you have to set it your zone.

Regards

SS

[Former Member]

Hi Sriram,

From where I can check the default time zone is -8 and how can I make to my time zone? Please suggest.

And also from the dump, you would seen the Source is DOUG. What actually it referring to? Can you please explain what is being carried out at that part and because if this only user is getting dumps.

Please advise.

Regards,

Satyardha

[Former Member]

Hi Sriram,

Moreover I could see time zone is not defined for the user. Is this cause the issue?

Please advise.

Regards,

Satyardha

[Sriram2009]

Hi Reddy.

1. At OS level you can refer the link  http://www.windowsnetworking.com/articles-tutorials/windows-7/Configuring-Time-Windows-7-Win-2008-R2...

2 Is it a new SAP system?  When your are creating the new user id it will pop up the warning or error message about the time zone is not defined, Kindly refer the SAP Note point number 3 and SAP KBA

1375438 - Globalization Collection Note

2006897 - How to compare timezone settings between OS and application server with report TZCUSTHELP

Regards

SS

[Former Member]

Hi Sriram,

Thank You.

It is not a new system. From one month I was getting these dumps in specific time in a day.
When I checked at SAP, this is set GMTUK but when I check at OS, time zone is UTC

As I know UTC and GMTUK time zone is same. Correct me if I am wrong. Or this differnce causing the issue?

Please let me know.

[Sriram2009]

Hi Reddy.

I think you have to define either one of the settings set either utc or gmt and then check the dump

Regards

SS

[Former Member]

Hi,

We have an external sever which is used for alerts monitoring for all production System.

From that Sever, it calling through RFC's and thus resulting ZDATE dumps in PI prod. If in this case, does reboot of External sever resolve the issue?

Does any impact of Kernel resulting these dumps? If yes, could you please let me know

Thank You.

Regards,

Satyardha

[Sriram2009]

Hi Reddy.

1.  In your environment all the SAP servers are in the same or different location? If it is same you have to maintain the time zone and Time  same in all SAP server OS & SAP level. I don't think it should be kernel issue.

Could you check the all the SAP system time are synchronized? refer the SAP Note 2046718 - Time Synchronization on Windows

2. In the very first communication the dumps shows that terminal  " Trex" could you check the time zone settings...

3.  In the syslog it show's any error message?

Regards

SS