Registration

Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
http://scn.sap.com
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata

Introduction

 

Support Desk Tool reads and checks the system configuration from BW Java portal and BW ABAP side.
In some cases it indicates some inconsistencies in the environment setup and reports it as RED error flag:

 

That page collects symptoms and tries to help to resolve them . In case the problem is not in the list and the tool does not include useful steps to resolve it, we recommend to report it to SAP Support for further investigations.

How to use Support Desk Tool:

Open Support Desk Tool URL: http(s)://<j2ee_server>:<j2ee_port>/irj/servlet/prt/portal/prtroot/com.sap.ip.bi.supportdesk.default
Press the reload button to refresh current sytem settings.

 List of known symptoms.

Symptom 1

Port '8000' of WAS Hostname (<j2ee_server>:<j2ee_port>) is not identical with HTTP Port '8101' of WebAS ABAP system. HTTP Port of Message Server (profile parameter ms/http_port) is retrieved from ABAP system. Port '8000' is properly HTTP Port of Application Server.

Port '8000' of ITS Hostname (<j2ee_server>:<j2ee_port>) is not identical with HTTP Port '8101' of WebAS ABAP system. HTTP Port of Message Server (profile parameter ms/http_port) is retrieved from ABAP system. Port '8000' is properly HTTP Port of Application Server.

Resolution

Click for help.

  

Symptom 2

RED    Web Template Validation failed due Java to ABAP communication problem (return code:ERSBOLAP018)

Resolution

Depending on the symptom there are two possible SAP Notes:
1573365 - Sporadic communication error in BEx Web 7.X
1656517 - RSBOLAP018 error while saving or executing a template in WAD


Symptom 3

RED   The system flagged as BI Mastersystem 'SAP_BW' does not have an alias named 'POACLNT800'

Resolution

When finding this error, it means that the BW system which is connected on the portal has not an alias defined. Go to your portal <http/https>://<j2ee_server>:<j2ee_port>/irj/portal -> "System Administration" -> "System Configuration" -> "System Landscape" -> "SAP_BW" -> “Display" -> "System Aliases" place the tool suggestion (in our example POACLNT800 into field “Alias Name” and click “Add”. This alias must also be defined as default. Save the changes. The red mark is gone.

 

Symptom 4

Error: First RFC call failed, config not loaded. Check the System landscape configuration.

Resolution

SAP Note: 1903392 - Error: First RFC call failed, config not loaded

 

Symptom 5

Webdynpro JCO destination WD_ALV_METADATA_DEST does not exist. Planning modeller will not work.
Webdynpro JCO destination WD_ALV_MODELDATA_DEST does not exist. Planning modeller will not work.
Webdynpro JCO destination BI_METADATA does not exist. Planning modeller will not work.
Webdynpro JCO destination BI_MODELDATA does not exist. Planning modeller will not work.

Resolution

SAP Note: 919850 - Problems with the planning modeler and the planning wizard

 

Symptom 6

User/Password combination of JCo RFC Provider is not valid
User of JCo RFC Provider is empty
Password of JCo RFC Provider is empty

Resolution

Click for help.

Symptom 7

RED    Error while determining user mapping for DDIC user.

Resolution

Click for help.

 

  • No labels