cancel
Showing results for 
Search instead for 
Did you mean: 

START_CALL_SICK error in ECC 6.0

Former Member
0 Kudos

Hello Experts,

I applied SAPKD70036, SAPKA70020 & SAPKB70020 Patches in ECC 6.0 server and then we were frequently getting START_CALL_SICK error whenever we try to login as well as SICK Code shows this message

SAP System Check

CPU timers not synchronized. Check note 1036194.

Severe problems were detected during initial system check.Please, do not use that system before fixing these problems.

DETAILS of our Server:

System environment

SAP-Release 700

Application server... "saperp60p"

Network address...... "126.6.6.61"

Operating system..... "Windows NT"

Release.............. "5.2"

Hardware type........ "4x Intel 80686"

Character length.... 16 Bits

Pointer length....... 32 Bits

Work process number.. 0

Shortdump setting.... "full"

Database server... "SAPERP60P"

Database type..... "MSSQL"

Database name..... "SEP"

Database user ID.. "sep"

Terminal................. "rvyas"

Char.set.... "C"

SAP kernel....... 700

created (date)... "Oct 19 2009 02:03:09"

create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"

Database version. "SQL_Server_8.00 "

Patch level. 228

Patch text.. " "

Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"

SAP database version. 700

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

NT 6.0, Windows NT 6.1"

Memory consumption

Roll.... 8176

EM...... 2090448

Heap.... 0

Page.... 0

MM Used. 788320

MM Free. 1300608

Please lemme know the solution.

Thanks

Rhishabh

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi,

Check the below links.

[SQL Server timing values may be incorrect when you use utilities or technologies that change CPU frequencies|http://support.microsoft.com/kb/931279]

[A Windows Server 2003-based server may experience time-stamp counter drift if the server uses dual-core AMD Opteron processors or multiprocessor AMD Opteron processors|http://support.microsoft.com/kb/938448]

[Programs that use the QueryPerformanceCounter function may perform poorly in Windows Server 2000, in Windows Server 2003, and in Windows XP|http://support.microsoft.com/kb/895980]

Hope it helps.

Thanks,

Shambo

former_member185031
Active Contributor
0 Kudos

>>CPU timers not synchronized. Check note 1036194.

Have you gone through this note?

Regards,

Subhash

Former Member
0 Kudos

Hello ,

Yeah, I already gone through the Note but still I need to know the workaround or is there any way to by pass this error.

We'll apply the latest Driver but at this moment we want, Users can't see this ABAP Dump & they directly by passed to SAP Easy Screen/ Main Screen.

If is it possible then please lemme know. I'll really appreciate if you can suggest some Idea.

Thanks

Rhishabh

markus_doehr2
Active Contributor
0 Kudos

You can change your boot.ini and add "/usepmtimer" - as described in the mentioned note.

Markus