cancel
Showing results for 
Search instead for 
Did you mean: 

*** WARNING => pfclock may be badly adjusted (7994)

Former Member
0 Kudos

Hi,

my second install appeared to work but I get these messages below when starting up and obviously I can't connect.

Any help appreciated.

Simon Farrell

C:\MiniWAS>REM =====================================================

C:\MiniWAS>REM Set the Environment for the DB Connect

C:\MiniWAS>REM =====================================================

C:\MiniWAS>set DBMS_TYPE=ada

C:\MiniWAS>set PATH=C:\sapdb\programs\bin;C:\sapdb\programs\pgm;C:\WINDOWS\syste

m32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\80

\Tools\Binn\;C:\sapdb\programs\bin;C:\sapdb\programs\pgm;C:\sapdb\programs\sap;C

:\MiniWAS;C:\sapdb\programs\bin;C:\sapdb\programs\bin;C:\sapdb\programs\sap;C:\s

apdb\programs\pgm

C:\MiniWAS>REM =====================================================

C:\MiniWAS>REM Start the Database (SAP-DB)

C:\MiniWAS>REM =====================================================

C:\MiniWAS>cmd /c strdbsBSP.cmd

C:\MiniWAS>set DBNAME=BSP

C:\MiniWAS>x_server

18641 ERROR: XSERVER is already running!

C:\MiniWAS>dbmcli -U c db_warm

OK

Database BSP successfully started !

C:\MiniWAS>REM =====================================================

C:\MiniWAS>REM Start SAP System

C:\MiniWAS>REM =====================================================

C:\MiniWAS>rem del pxastat

C:\MiniWAS>start /B msg_server.exe pf=BSP_D00.pfl

C:\MiniWAS>disp+work.exe break pf=BSP_D00.pfl

dp Ctrl-C enabled

.\SLOG00: No such file or directory

rslgwr1(20): rstrbopen cannot open pre-existing SysLog file.

maximum pfclock time: 4294sec (1)

adjust_clock: delta 155497

adjust_clock: delta 155479

      • WARNING => pfclock may be badly adjusted (155479)

gw Ctrl-C enabled

maximum pfclock time: 4294sec (1)

adjust_clock: delta 8305

dp Ctrl-C enabled

dp Ctrl-C enabled

dp Ctrl-C enabled

maximum pfclock time: 4294sec (1)

maximum pfclock time: 4294sec (1)

maximum pfclock time: 4294sec (1)

adjust_clock: delta 4862

***

      • work process W1 died => tskh_init: db_connect

***

      • work process W2 died => tskh_init: db_connect

***

      • work process W0 died => tskh_init: db_connect

adjust_clock: delta 7994

      • WARNING => pfclock may be badly adjusted (7994)

IcmHandleArgs: Illegal option break

      • ICM up and operational (pid: 1784) ***

***

      • DISPATCHER EMERGENCY SHUTDOWN => DpEnvCheck: no more work processes

Shutdown ICM server ....

      • ICM shutdown completed (pid: 1784) ***

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Simon,

To get the lates pathces,go to: service.sap.com/patches,

and then go to the respective application.

Let me know the R/3 version and the O.S anf DB details.

Rgs

vikas

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Simon,

Well..Check the environment variables of Oracle/DB both in my computer-properties-advanced-enivonment variables and in registry.

Please apply the latest Kernal patches.

Reply back.

rgs

vikas

Former Member
0 Kudos

Hi,

I checked in my computer and I have no environment variables set that relate to PFCLOCK. I did find two variables set from a previous Mini SAP install refering to database = SQL ! and path = c:\mbs.

I can now get into the system allthoug the response is terrible.

Do you have a link that I can use to find the latest patches etc

Many thanks

Many Thanks

Simon Farrell