2349168 - ACTool - BOE and Tomcat SLD configuration steps fails with error: SLD Connect information are inconsistent, please execute this script to create a correct one | SAP Knowledge Base Article

SAP Knowledge Base Article - Preview

2349168 - ACTool - BOE and Tomcat SLD configuration steps fails with error: SLD Connect information are inconsistent, please execute this script to create a correct one

Symptom

When running the ACTool from note 2137275 to configure a BOE or a Tomcat system in the SAP Solution Manager for Root Cause Analysis, the following steps fail with error 'SLD Connect information are inconsistent, please execute this script to create a correct one'.

  • Step: BOE - BI 4.0 Note 1653689 Step 6.1 - Enable SLD support for BO cluster
  • Step: Tomcat Wiki Step 5 (BI 4.0 Note 1653689 Step 6.2) - Install and run SLD Data Supplier

The log error is found in the ACTool log, the examples are below:

  • Step BOE - BI 4.0 Note 1653689 Step 6.1 - Enable SLD support for BO cluster
2099/06/11 09:48:53.670000|==| | |30248|   1| |||||||||||||||console output:---------- BOE - BI 4.0 Note 1653689 Step 6.1 - Enable SLD support for BO cluster ----------
2099/06/11 09:48:53.686000|==| | |30248|   1| |||||||||||||||Could not find the property key 'boe.home'. Please check whether it is mandatory.
2099/06/11 09:48:53.723000|==| | |30248|   1| |||||||||||||||readRegistry Exec reg query "HKEY_LOCAL_MACHINE\SOFTWARE\SAP BusinessObjects\Suite XI 4.0\Installer\Aurora" /v "path" successfully.
2099/06/11 09:48:53.725000|==| | |30248|   1| |||||||||||||||Detect BI 4.0 Server installed on D:\Program Files\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\

2099/06/11 09:48:53.749000|==| | |30248|   1| |||||||||||||||readRegistry Exec reg query "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\SAPHostExec" /v "ImagePath" successfully.
2099/06/11 09:48:53.755000|<<| | |30248|   1| |||||||||||||||Getting StreamGobbler result
2099/06/11 09:48:53.781000|<<| | |30248|   1| |||||||||||||||Mon   09:48:53 2016 SLD Registration Program [7.20.5]  (Mar 29 2014) [Non-Unicode]
2099/06/11 09:48:53.782000|<<| | |30248|   1| |||||||||||||||Mon   09:48:53 2016 Getting connect data from configuration file 'connect.key'
2099/06/11 09:48:53.782000|<<| | |30248|   1| |||||||||||||||Mon   09:48:53 2016 Using destination file 'connect.key'.
2099/06/11 09:48:53.783000|<<| | |30248|   1| |||||||||||||||Mon   09:48:53 2016 No key file 'connect.key.key' used.
2099/06/11 09:48:53.783000|<<| | |30248|   1| |||||||||||||||Mon   09:48:53 2016 Use encryted destination file 'connect.key' as data source
2099/06/11 09:48:53.818000|<<| | |30248|   1| |||||||||||||||Mon   09:48:53 2016 This is the secured information stored in file: 'connect.key'
2099/06/11 09:48:53.819000|<<| | |30248|   1| |||||||||||||||Mon   09:48:53 2016 host_param=<sld_host>
2099/06/11 09:48:53.819000|<<| | |30248|   1| |||||||||||||||Mon   09:48:53 2016 https_param=n
2099/06/11 09:48:53.819000|<<| | |30248|   1| |||||||||||||||Mon   09:48:53 2016 port_param=<sld_port>
2099/06/11 09:48:53.820000|<<| | |30248|   1| |||||||||||||||Mon   09:48:53 2016 user_param=slddsuser
2099/06/11 09:48:53.820000|<<| | |30248|   1| |||||||||||||||Getting StreamGobbler result finished
2099/06/11 09:48:53.821000|==| | |30248|   1| |||||||||||||||exec(...) Exec "C:\Program Files\SAP\hostctrl\exe\sldreg" -showconnect connect.key successfully.
2099/06/11 09:48:53.824000|==| | |30248|   1| |||||||||||||||console output:[DEBUG] Output>>This is the secured information stored in file: 'connect.key'
Mon   09:48:53 2016 host_param=<sld_host>
Mon   09:48:53 2016 https_param=n
Mon   09:48:53 2016 port_param=<sld_port>
Mon   09:48:53 2016 user_param=slddsuser

2099/06/11 09:48:53.827000|==| | |30248|   1| |||||||||||||||console output:[DEBUG] This is the secured information stored in file: 'connect.key'
                host_param=<sld_host>
                https_param=n
                port_param=<sld_port>
                user_param=slddsuser

2099/06/11 09:48:53.829000|>>|E| |30248|   1| |||||||||||||||console output:[ERROR] <sld_host>!=<sld_host>
2099/06/11 09:48:53.830000|>>|E| |30248|   1| |||||||||||||||console output:[ERROR] <sld_port>!=<sld_port>
2099/06/11 09:48:53.831000|>>|E| |30248|   1| |||||||||||||||console output:[ERROR] slddsuser!=slddsuser
2099/06/11 09:48:53.832000|>>|E| |30248|   1| |||||||||||||||console output:[ERROR] SLD Connect information are inconsistent, please execute this script to create a correct one.
2099/06/11 09:48:53.833000|==| | |30248|   1| |||||||||||||||console output:Script 1.  BOE - BI 4.0 Note 1653689 Step 6.1 - Enable SLD support for BO cluster                        FAILED
  • Step: Tomcat Wiki Step 5 (BI 4.0 Note 1653689 Step 6.2) - Install and run SLD Data Supplier
||||console output:---------- Tomcat Wiki Step 5 (BI 4.0 Note 1653689 Step 6.2) - Install and run SLD Data Supplier ----------
2099/06/11 13:59:20.705000|==| | |24060|   1| |||||||||||||||console output:[INFO] Detect webapp folder sap.com~TomcatSLDDataSupplierWEB in D:\Program Files\SAP BusinessObjects\tomcat\webapps
2099/06/11 13:59:20.706000|==| | |24060|   1| |||||||||||||||console output:[INFO] Detect war filesap.com~TomcatSLDDataSupplierWEB.war in D:\Program Files\SAP BusinessObjects\tomcat\webapps
2099/06/11 13:59:20.708000|==| | |24060|   1| |||||||||||||||console output:[DEBUG] com.sap.sup.admin.sldsupplier.WORKING_DIR=D:/Program Files/SAP BusinessObjects/tomcat/webapps/sap.com~TomcatSLDDataSupplierWEB

2099/06/11 13:59:20.735000|==| | |24060|   1| |||||||||||||||readRegistry Exec reg query "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\SAPHostExec" /v "ImagePath" successfully.
2099/06/11 13:59:20.756000|<<| | |24060|   1| |||||||||||||||Getting StreamGobbler result
2099/06/11 13:59:20.910000|<<| | |24060|   1| |||||||||||||||Mon   13:59:20 2016 SLD Registration Program [7.20.5]  (Mar 29 2014) [Non-Unicode]
2099/06/11 13:59:20.910000|<<| | |24060|   1| |||||||||||||||Mon   13:59:20 2016 Getting connect data from configuration file 'connect.key'
2099/06/11 13:59:20.910000|<<| | |24060|   1| |||||||||||||||Mon   13:59:20 2016 Using destination file 'connect.key'.
2099/06/11 13:59:20.911000|<<| | |24060|   1| |||||||||||||||Mon   13:59:20 2016 No key file 'connect.key.key' used.
2099/06/11 13:59:20.911000|<<| | |24060|   1| |||||||||||||||Mon   13:59:20 2016 Use encryted destination file 'connect.key' as data source
2099/06/11 13:59:20.948000|<<| | |24060|   1| |||||||||||||||Mon   13:59:20 2016 This is the secured information stored in file: 'connect.key'
2099/06/11 13:59:20.948000|<<| | |24060|   1| |||||||||||||||Mon   13:59:20 2016 host_param=<sld_host>
2099/06/11 13:59:20.948000|<<| | |24060|   1| |||||||||||||||Mon   13:59:20 2016 https_param=n
2099/06/11 13:59:20.948000|<<| | |24060|   1| |||||||||||||||Mon   13:59:20 2016 port_param=<sld_port>
2099/06/11 13:59:20.949000|<<| | |24060|   1| |||||||||||||||Mon   13:59:20 2016 user_param=slddsuser
2099/06/11 13:59:20.949000|<<| | |24060|   1| |||||||||||||||Getting StreamGobbler result finished
2099/06/11 13:59:20.951000|==| | |24060|   1| |||||||||||||||exec(...) Exec "C:\Program Files\SAP\hostctrl\exe\sldreg" -showconnect connect.key successfully.
2099/06/11 13:59:20.953000|==| | |24060|   1| |||||||||||||||console output:[DEBUG] Output>>This is the secured information stored in file: 'connect.key'
Mon   13:59:20 2016 host_param=<sld_host>
Mon   13:59:20 2016 https_param=n
Mon   13:59:20 2016 port_param=<sld_port>
Mon   13:59:20 2016 user_param=slddsuser


2099/06/11 13:59:20.955000|==| | |24060|   1| |||||||||||||||console output:[DEBUG] This is the secured information stored in file: 'connect.key'
    host_param=<sld_host>
    https_param=n
    port_param=<sld_port>
    user_param=slddsuser

2099/06/11 13:59:20.956000|>>|E| |24060|   1| |||||||||||||||console output:[ERROR] SLD Connect settings are inconsistent, please execute this script to create a correct one.

2099/06/11 13:59:20.957000|==| | |24060|   1| |||||||||||||||console output:Script 16. Tomcat Wiki Step 5 (BI 4.0 Note 1653689 Step 6.2) - Install and run SLD Data Supplier                    FAILURE

 

 

 


Read more...

Environment

  • SAP Solution Manager 7.10
  • SAP Solution Manager Diagnostics

Product

SAP Solution Manager 7.1

Keywords

KBA , SV-SMG-INS-DIA , Configuration of Root Cause Analysis related infrastructure , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.