Dispatcher is in Yellow color after Kernel Upgrade.

[Former Member]

Hello Experts,

I have Problem with the Dispatcher ie,. after Upgrading Kernel in ECC6.0 the Dispatcher is in Yellow color and there is no Information about Dialog Workprocess. Could any one Please help me with the Good solution to Fix this Problem and Make the Dispatcher from Yellow to Green.

Regards,

Pavan.

[Former Member]

Even we have got the same , it was the reason because if it is ABAP+JAVA stack , the app may be running but all the server process of JAVA has to be started , even if one of the server is nt started or in starting , dispatcher will be in Yellow colour.

[Former Member]

If you're on windows, copy the new sapstartsrv.exe from the new kernel directory to C:\windows\system32 and restart your instance.  Just had to do this over the weekend.

Chris

[Former Member]

Christopher,

copying sapstartsrv.exe to windows\system32 will not help at all to get the yellow state fixed.

The purpose of the sapstartsrv.exe in the system32 directory is just to provide the COM-Interfaceof sapstartsrv at a central place, nothing else.

This interface normally does not change at all. So there is no update needed in system32.

See my last reply about the Yellow State after updating the kernel.

regards

Peter

[Former Member]

Peter,

While I understand that your reply will work, as I stated, I just used my solution over the weekend.

Perhaps the situation was a little different, but my solution solved my issue Saturday.

Chris

[Former Member]

sopying sapstartsrv worked also for me

and that could be the only reason if server is running

[Former Member]

Is this Peter DArnell Simon LSU graduate??

[Former Member]

Peter -

While I'm not 100% why it was the case, doing what Chris suggested helped us.  The windows\system32\sapstartsrv.exe was significantly out of date with the one in the updated kernel folder.  After replacing that sapstartsrv.exe with updated one in the kernel folder and restarting the instance, we went from yellow to green but perhaps we are an anomoly.

[Former Member]

>> windows\system32\sapstartsrv.exe was significantly out of date

can you please be more precise on this?

Which version was in system32 and which one was used as service executable.

Last question: which SAPMMC version is used in this system?

Thank you

Peter

[Former Member]

The windows\system32\sapstartsrv.exe was from a previous kernel and was not automatically updated after updating the kernel in the \usr\sap\SID\SYS\exe\uc\NTAMD64 folder.  I believe the version of the MMC is irrelevant in this case but it was Management Console 3.0 -  Version 6.1 (The one that comes with Server 2008 R2 Enterprise)

[isaias_freitas]

Hello Peter,

I would say that an old version of the sapstartsrv at the system32 could actually be causing the issue.

@Steve, I agree that the MMC version would not be the issue.

@Pavan, some people suggested to reinstall the service. This can help as well. Here are the detailed steps to do that (SAP must be down!):

1) Logon with the "<sid>adm" user;

2) Double click at the "sapstartsrv.exe" from the "instance/exe"

   folder;

3) Select "Uninstall Service + Unregister COM Interface";

4) Specify the SID and System Number, and click ok;

5) Double click at the "sapstartsrv.exe" again;

6) Select "Install Service + Register COM Interface + Start Serv";

7) Specify the SID and System Number (NR);

😎 Specify the instance profile (use the "browse" button);

9) Specify the user as "domain\SAPService<SID>";

10) Specify the password for that user;

11) Select to use the environment of the "domain\<sid>adm" user;

12) Click OK.

Regards,

Isaías

[Former Member]

yes,

I also assume that the wrong sapstartsrv.exe is registered as service executable.

But before recreating the service I would like to crosscheck that:

just open a command box and run following command:

sc.exe qc SAP<SID>_<nr>.

Have a look a BINARY_PATH_NAME.

If it is pointing to windows\system32\sapstartsrv.exe then it is the wrong one.

The executable from the instance/exe directory (DVEBMGS01, D01...) has to be used.

This error happens always if the service definition is done by invoking sapstartsrv.exe without specifying the complete path to the executable (from withing windows Search Programs and Files or within a command box.

On Windows Server 2003 this will work fine - on Windows Server 2008 (R2) system32/sapstartsrv.exe will not work, because it has the wrong ACL on the executable,

kind regards

Peter

[Former Member]

If you have upgraded the kernel and restart the system, the first thing what is happening is, that the executables are replicated from the stage directory (..\sys\exe\uc\ntamd64) to the executable directory of the instance (...\DVEBMGS00\exe).

The replication is initiated with the old service executable (sapstartsrv.exe), the kerne starting after the replication is the new one.

Now it happened that the shared memory segments containing the internal ABAP Server information (kind of work processes, queue information....) is created by the new kernel and will be red with the old Service executable (which provides this information to MMC). If the size or structure of the shared memory segment has changed between the two versions the service can't interpret the internal information and therefor the color of the instance keeps yellow, when looking at the status immediately..

Within 5 Minutes after the system was started with a new kernel the service will restart itself without restarting the system. After this restart the color should automatically switch to green (because the service running has the same version than disp+work)..

regards

Peter

[Former Member]

HI,

please check the level of the kernel after ur upgrade .check all the services .can you please tell me what is ur platform and what is the version of database ?

[Former Member]

Please check disp+work version in both kernel path to make sure you have same version....also tell me wheather it is unicode or non-unicode.

[Former Member]

Hi Pavan,

Close all MMC instances, and stop SAP service. Or reboot the server.

Additionally, check the note 396309 - Dispatcher remains yellow, although the system is running

Best regards,

Orkun Gedik

[Former Member]

Thank you Orkun. i have done what you had mentioned. But im facing same problem. Dispatcher is still in Yellow color,

Unable to view Dialog work process Queue and Unable to View Database Hostname in the SAP MMC. (sap crm7.0)

Please help me with right Solution to fix the Problem. a soon as Possible.

Regards,

Pavan.

[Former Member]

>> Unable to view Dialog work process Queue and Unable to View Database Hostname in the SAP MMC. (sap crm7.0)

Are you facing with this problem on the additional application server? Or database server itself?

Best regards,

Orkun Gedik

[Former Member]

In the SAP MMC when we try to Right click on the Database. it should Display the Database HostName/ name Right!!!!!!!!!

but in my SAP MMC the Database Hostname/name is not displayed. only i can see ( -| ) this symbol when i right click on the Database and see.

And Second Point is Dispatcher is in yellow color and iam unable to View Dialog work Process queue information.

Can you please give me the solutions for the above Problems..

Thanks and Regards,

Pavan.

[Former Member]

In the SAP MMC when  we try to Right click on the Database. it should Display the Database HostName/ name  Right!!!!!!!!!
> 
>  but in my SAP MMC  the Database Hostname/name is not displayed. only  i can see  ( -|  )  this  symbol when i right click on the Database and see.
> 
>  And Second Point is  Dispatcher is in yellow color  and  iam unable to  View  Dialog work Process queue information.
> 
> Can you  please give me  the solutions for the above Problems..
> 
> 
> Thanks and Regards,
> 
> Pavan.

Hi,

Try to download latest SAP MMC on the SAP Marketplace.

Best regards,

Orkun Gedik

[former_member204746]

try this:

stop SAP

stop SAPMMC

stop and DISABLE SAP services. it must be disabled!

uncompress the kernel in another directory. I usually copy SAPCAR.EXE to SAPCAR_ERIC.EXE and use that copy such as:

SAPCAR_ERIC.exe -xvf BLAHBLAH.SAR

Then, copy the kernel.

Finally, restart everything and cross your fingers.

[nicholas_chang]

Hi,

you can follow Eric's way. If it still doesn't work, i normally solve these problem with belows:

1) reboot your server if possible, i believe your SAP MMC should works fine after this.

2) If option 1 is not feasible, run sapstartservice.exe to register your instance again. This should work.

Cheers,

Nicholas Chang

[former_member204746]

one more thing,

when you uncompressed your kernel, a file named SAPCAR.exe is part of it. if you use SAPCAR to uncompress the kernel file, if will uncompress all files from AAA to SAPCA... but not the rest from SAPCAR to ZZZ.

This is why I always use a copied or renamed SAPCAR executable.

This issue will cause the yellow status.

Also, if your SAPMMC is still opened, it wil ltry to re-open the SAP_SID_)) service over and over again. so, disabling it will make sure that it is not in use.

Try this and come back with results.

[Former Member]

how to register instance again

[Former Member]

run sapstartsrv from cmd and install service