"Corbu" theme is not supported for this application

[Former Member]

We are encounter error "Corbu" theme is not supported for this application when we open our MSS/ESS NWBC web client. We had recently upgraded to note #1946911 SAP NWBC ABAP runtime patch 35 as per recommendation from our earlywatch but we are getting the error now on all of our pages. I have checked the note #1681286 which does not tell us much about the situation. We are running EHP5 Basis support pack SAPKB70213 and I have tried upgrading our ITS to version 7.21 and our SAPCRYPTOLIB to patch 8425. If anyone can help resolve this issue, it would be much appreciated!

[Former Member · Accepted solution]

What application are you getting the error for? Can you share a screenshot? It is the AS ABAP kernel that needs to be upgraded to 7.21 in order to have Corbu support in ITS.

[Former Member · Accepted solution]

This is the error we are receiving when accessing our ESS/MSS through web NWBC. Our ABAP kernel is currently running 7.21 and we have upgraded our web dispatcher kernel to 7.21 with the error still coming up.

[Former Member · Accepted solution]

The problem here is your NetWeaver version, which is 7.02. Corbu requires 7.03 SP04 or higher.

[Former Member · Accepted solution]

We're not sure why SAP delivered this patch in their Early Watch alerts if it isn't compatible with our system when we applied the patch through SNOTE and the program said it was good. Is there a way to disable this error and go back to the tradeshow theme?

[Former Member · Accepted solution]

You can use the NWBC configuration table NWBC_CFG, set NAME = THEME_NAME and VALUE = sap_tradeshow to force SAP Tradeshow instead of SAP Corbu.

[Former Member · Accepted solution]

You wouldn't happen to know the procedure for this? My ABAP people are at a loss. lol

[Former Member · Accepted solution]

Hi Connie,

Just go to SE16N and input the NWBC_CFG table. You can edit directly from there.

Input the value similar to this.

[Former Member · Accepted solution]

Thank you to everyone who helped me resolve this issue! If anyone needs to reference this in the future, there is note #1963267 that has the information to resolve this issue.