Problem with SAP Management console

[abdul_hakim]

Hi

I am starting my SAP Server from SAP Management console( ECC6.0 IDES Version).

I am able to login into my system but after few minutes the server color is changing from Green to Yellow and I am not able to continue using my system. What could be the problem? How to resolve the same?

Thanks.

Abdul Hakim

[Former Member · Accepted solution]

Hi,

Please check the services are running.

Check if tns listener is running.

Check dev_w0 for errors.

Regards

Abhishek

[abdul_hakim · Accepted solution]

Hi Abhishek,

Thanks for the reply.I am not a BASIS Person so i cannot understand your terminologies.

What i can say is all the servies( including WP(Stopped),MS & DP all in yellow color).

When i check the syslog in MMC it is saying Unable to connect to OS.

Regards,

Abdul Hakim

[Former Member · Accepted solution]

Hi,

Just paste the log from file dev_w0 from the path /usr/sap/<SID>/DVEBMGS<SYSNO>/work folder so that we can check for the error and suggest.

Also, try to execute the command R3trans -d from command prompt and send us the output.

Regards,

Sharath

[JPReyes · Accepted solution]

Can you please post the errors on the developer trace?

/usr/sap/<sid>/<instance>/work/dev_w0

Regards

Juan

[Former Member · Accepted solution]

Hi,

You can find dev_w0 log file under "<drive>:\usr\sap\<SID>\DVEBMGS<NO>\work" directory.

Just past the content here...

Check all database and SAP services are started and set in "Automatic" mode.

Right Click on "My Computer" ==> Select "Manage" ==> Explore "Services and Applications" ==> Select "Services"

At right side you will see all Windows Services..

Just check if database and SAP services are started.

Regards.

Rajesh Narkhede

[p330068 · Accepted solution]

Hi Abdul,

Check the JAVA_HOME and databse services.

Hope it helps

Regards

Arun

[former_member184158]

I have the same problem ???

---------------------------------------------------

trc file: "dev_w0", trc level: 1, release: "720"

---------------------------------------------------

*

*  ACTIVE TRACE LEVEL           1

*  ACTIVE TRACE COMPONENTS      all, MJ

*

M sysno      00

M sid        NSP

M systemid   562 (PC with Windows NT)

M relno      7200

M patchlevel 0

M patchno    214

M intno      20020600

M make       multithreaded, Unicode, 64 bit, optimized

M profile    \\Ibo-PC\sapmnt\NSP\SYS\profile\NSP_DVEBMGS00_Ibo-PC

M pid        2972

M

M  kernel runs with dp version 134000(ext=119000) (@(#) DPLIB-INT-VERSION-134000-UC)

M  length of sys_adm_ext is 588 bytes

M  ***LOG Q0Q=> tskh_init, WPStart (Workp. 0 2972) [dpxxdisp.c   1377]

I  MtxInit: 30000 0 0

M  DpSysAdmExtCreate: ABAP is active

M  DpSysAdmExtCreate: VMC (JAVA VM in WP) is not active

M  DpIPCInit2: read dp-profile-values from sys_adm_ext

M  DpShMCreate: sizeof(wp_adm) 31696 (2264)

M  DpShMCreate: sizeof(tm_adm) 5517056 (27448)

M  DpShMCreate: sizeof(wp_ca_adm) 64000 (64)

M  DpShMCreate: sizeof(appc_ca_adm) 64000 (64)

M  DpCommTableSize: max/headSize/ftSize/tableSize=500/16/1384064/1384080

M  DpShMCreate: sizeof(comm_adm) 1384080 (2744)

M  DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0

M  DpShMCreate: sizeof(slock_adm) 0 (296)

M  DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0

M  DpShMCreate: sizeof(file_adm) 0 (80)

M  DpShMCreate: sizeof(vmc_adm) 0 (2152)

M  DpShMCreate: sizeof(wall_adm) (41664/42896/64/192)

M  DpShMCreate: sizeof(gw_adm) 48

M  DpShMCreate: sizeof(j2ee_adm) 3952

M  DpShMCreate: SHM_DP_ADM_KEY (addr: 000000000F9A0050, size: 7163600)

M  DpShMCreate: allocated sys_adm at 000000000F9A0060

M  DpShMCreate: allocated wp_adm_list at 000000000F9A3070

M  DpShMCreate: allocated wp_adm at 000000000F9A3260

M  DpShMCreate: allocated tm_adm_list at 000000000F9AAE40

M  DpShMCreate: allocated tm_adm at 000000000F9AAE90

M  DpShMCreate: allocated wp_ca_adm at 000000000FEEDDA0

M  DpShMCreate: allocated appc_ca_adm at 000000000FEFD7B0

M  DpShMCreate: allocated comm_adm at 000000000FF0D1C0

M  DpShMCreate: system runs without slock table

M  DpShMCreate: system runs without file table

M  DpShMCreate: allocated vmc_adm_list at 000000001005F060

M  DpShMCreate: system runs without vmc_adm

M  DpShMCreate: allocated gw_adm at 000000001005F110

M  DpShMCreate: allocated j2ee_adm at 000000001005F150

M  DpShMCreate: allocated ca_info at 00000000100600D0

M  DpShMCreate: allocated wall_adm at 0000000010060160

M  DpCommAttachTable: attached comm table (header=000000000FF0D1C0/ft=000000000FF0D1D0)

M  DpRqQInit: use protect_queue / slots_per_queue 0 / 2001 from sys_adm

M  rdisp/queue_size_check_value :  -> on,50,30,40,500,50,500,80

X  EmInit: MmSetImplementation( 2 ).

X  MM global diagnostic options set: 0

X  <ES> client 0 initializing ....

X  <ES> EsILock: use spinlock for locking

X  Using implementation view

X  <EsNT> Using memory model view.

M  <EsNT> Memory Reset disabled as NT default

X  ES initialized.

X  mm.dump: set maximum dump mem to 96 MB

M  DpVmcSetActive: set vmc state DP_VMC_NOT_ACTIVE

M  ThStart: taskhandler started

M  rdisp/thsend_mode : -1 -> 0

M  ThInit: initializing DIA work process W0

M 

M Thu May 29 07:17:58 2014

M  ThInit: running on host Ibo-PC

M  calling db_connect ...

B  Loading DB library 'C:\usr\sap\NSP\DVEBMGS00\exe\dbsdbslib.dll' ...

B  Library 'C:\usr\sap\NSP\DVEBMGS00\exe\dbsdbslib.dll' loaded

B  Version of 'C:\usr\sap\NSP\DVEBMGS00\exe\dbsdbslib.dll' is "720.00", patchlevel (0.212)

C 

C  DBSDBSLIB : version 720.00, patch 0.212 (Make PL 0.214)

C  MAXDB shared library (dbsdbslib) patchlevels (last 10)

C    (0.212) Call TH callback after cancel (note 1692560)

C    (0.210) Init length of tablename for describe (note 1678130)

C    (0.200) Take care of warnings during database connect (note 1600066)

C    (0.117) Define a primary key on the temp tables for R3szchk (note 1606260)

C    (0.114) Support of MaxDB 7.8 and 7.9 (note 1653058)

C    (0.103) Close all lob locators at end of the transaction (note 1626591)

C    (0.101) Fix for unknown table __TABLE_SIZES_ (R3szchk) (note 1619504)

C    (0.098) Use filesystem counter for R3szchk (note 1606260)

C    (0.092) Secondary connection to HANA (note 1481256)

C    (0.089) UPDSTAT with SAPSYSTEMNAME longer as 3 characters (note 1584921)

C 

C 

C  Loading SQLDBC client runtime ...

C 

C Thu May 29 07:18:00 2014

C  SQLDBC Module  : C:\sapdb\clients\NSP\pgm\libSQLDBC77.dll

C 

C Thu May 29 07:18:01 2014

C  SQLDBC SDK     : SQLDBC.H  7.8.2    BUILD 028-121-245-008

C  SQLDBC Runtime : libSQLDBC 7.8.2    BUILD 028-121-245-008

C  SQLDBC client runtime is MaxDB 7.8.2.028 CL 245008

C  SQLDBC supports new DECIMAL interface : 1

C  SQLDBC supports VARIABLE INPUT data   : 1

C  SQLDBC supports VARIABLE OUTPUT data  : 1

C  SQLDBC supports Multiple Streams      : 1

C  SQLDBC supports LOB LOCATOR KEEPALIVE : 1

C  SQLDBC supports LOB LOCATOR COPY      : 1

C  SQLDBC supports BULK SELECT with LOBS : 1

C  SQLDBC supports BATCH STREAM          : 1

C  INFO : SQLOPT= -I 0 -t 0 -S SAPR3

C  Try to connect (DEFAULT) on connection 0 ...

C  Attach to SAP DB : Kernel    7.8.02   Build 028-121-245-008

C  Database release is SAP DB 7.8.02.028

C  INFO : Database 'NSP' instance is running on 'ibo-pc'

C  DB supports UPSERT SQL syntax : 1

C  DB supports new EXPAND syntax : 1

C  DB supports LOB locators      : 1

C  DB uses MVCC support          : 0

C  DB max. input host variables  : 2000

C  DB max. statement length      : 65535

C  UPSERT is disabled for : WBCROSSGT

C  INFO : SAP DB Packet_Size = 131072

C  INFO : SAP DB Min_Reply_Size = 4096

C  INFO : SAP DB Comm_Size = 126976

C  INFO : DBSL buffer size = 126976

C  INFO : SAP DB MaxLocks = 300000

C  INFO : Connect to DB as 'SAPNSP'

C  Command info enabled

C  Now I'm connected to MaxDB

C  00: ibo-pc-NSP, since=20140529071801, ABAP= <unknown> (0)

B  Connection 0 opened (DBSL handle 0)

C  INFO : SAP RELEASE (DB) = 702

M  ThInit: db_connect o.k.

M  ICT: exclude compression: *.zip,*.rar,*.arj,*.z,*.gz,*.tar,*.lzh,*.cab,*.hqx,*.ace,*.jar,*.ear,*.war,*.css,*.pdf,*.gzip,*.uue,*.bz2,*.iso,*.sda,*.sar,*.gif,*.png,*.swc,*.swf

[former_member126060]

Hello Abdul,

Regarding the dispatcher staying in yellow status, please proceed as follows:

Could you please, try to register the R/3 MMC Snap-in again using: regsvr32 sapmmc.dll. Refer to SAP note 354595 for further information.

patch the MMC dll's from the marketplace. Database independent section.

Dll's are in /system32 folder.

Delete any sapstartsrv.exe.tmp in the exe directories.may need to stop service to do this.

Make sure sapstartsrv.exe and sapstartsrv.exe.new are at same patch level and modification date and time in the ct_run directory. (for example \usr\sap\<SID>\SYS\exe\uc\NTAMD64)

If not delete sapstartsrv.exe.new and copy sapstartsrv.exe to sapstartsrv.exe.new in order for both files to be

identical including the 'last modification' date

Copy sapstartsrv.exe and sapstartsrv.exe.new to all the exe directories to make sure they are at same patch level modification date and time.

Try again following steps :

> extract kernel again

> registerd the service from command prompt with sapstartsrv -t

1. Stop the SAP service

2. Open a command prompt

3. Go to kernel directory

4. call 'sapstartsrv.exe -t' from the command line

5. Confirm

the dialog window

6. Start the service again

> Start service again

> register the R/3 MMC Snap-in again using:

regsvr32 sapmmc.dll.

Best Regards

Niraj