use the CRM_SOCM_SERVICE_REPORT but you must configure the sequence of the transaction type in sm34, SOCMC_COPY.

Dear Experts,

We're struck with error during the Solution Manager SP upgrade (SP14) using SUM (Software Update Manager).

Error "java.lang.NullPointerException: while trying to invoke the method java.lang.Process.destroy() of a null object returned from com.sap.sdt.tools.proc.OsProcess.getProcessObject()." occurred during Execution phase step "Deploy SDM".

Please find below the Error log:

<!--LOGHEADER[START]/-->

<!--HELP[Manual modification of the header may cause parsing problem!]/-->

<!--LOGGINGVERSION[2.0.7.1006]/-->

<!--NAME[F:\SUM\SUM\sdt\log\SUM\DEPLOY-SDM_12.LOG]/-->

<!--PATTERN[DEPLOY-SDM_12.LOG]/-->

<!--FORMATTER[com.sap.tc.logging.TraceFormatter(%d [%6s]: %m)]/-->

<!--ENCODING[UTF8]/-->

<!--LOGHEADER[END]/-->

Dec 14, 2015 10:31:32 PM [Info  ]: Number of source deployed components detected from components provider: 27

Dec 14, 2015 10:31:32 PM [Info  ]: Number of source deployed components detected from components provider: 27

Dec 14, 2015 10:31:32 PM [Info  ]: DeployController release is 7.10. Component version rule UPDATE_LOWER_ONLY will be used.

Dec 14, 2015 10:31:32 PM [Info  ]: Deploy version rule has been set to updateLowerOrChanged in file F:\SUM\SUM\sdt\param\jspm_config.txt.

Dec 14, 2015 10:31:32 PM [Info  ]: Deploy error strategy has been set to stop in file F:\SUM\SUM\sdt\param\jspm_config.txt.

Dec 14, 2015 10:31:32 PM [Info  ]: Deployment prerequisite check error strategy has been set to stop in file F:\SUM\SUM\sdt\param\jspm_config.txt.

Dec 14, 2015 10:31:32 PM [Info  ]: Undeploy error strategy has been set to skipDepending in file F:\SUM\SUM\sdt\param\jspm_config.txt.

Dec 14, 2015 10:31:32 PM [Info  ]: Undeploy dependency rule has been set to stop in file F:\SUM\SUM\sdt\param\jspm_config.txt.

Dec 14, 2015 10:31:32 PM [Info  ]: Deploy timeout has been set to 7200 seconds in file F:\SUM\SUM\sdt\param\jspm_config.txt.

Dec 14, 2015 10:31:32 PM [Info  ]: Start parsing deployment order definition file F:\SUM\SUM\sdt\config\dodf.xml.

Dec 14, 2015 10:31:32 PM [Info  ]: File F:\SUM\SUM\sdt\config\dodf.xml is parsed and relative deployment data model is extracted.

Dec 14, 2015 10:31:32 PM [Info  ]: Start parsing deployment order definition file F:\SUM\SUM\sdt\config\dodfNonsupportedDCType.xml.

Dec 14, 2015 10:31:32 PM [Info  ]: File F:\SUM\SUM\sdt\config\dodfNonsupportedDCType.xml is parsed and relative deployment data model is extracted.

Dec 14, 2015 10:31:32 PM [Info  ]: Number of source deployed components detected from components provider: 27

Dec 14, 2015 10:31:32 PM [Info  ]: Updating SDM...

Dec 14, 2015 10:31:32 PM [Info  ]: Unpacking F:/SUM/SolMan_Patches/SDMKIT17_0-10006657.JAR to folder F:/SUM/SUM/sdt/tmp/unpack_SDMKit...

Dec 14, 2015 10:31:32 PM [Info  ]: File F:\SUM\SUM\sdt\tmp\unpack_SDMKit has been deleted.

Dec 14, 2015 10:31:32 PM [Info  ]: Directory F:\SUM\SUM\sdt\tmp\unpack_SDMKit has been created.

Dec 14, 2015 10:31:32 PM [Info  ]: Stopping SDM server...

Dec 14, 2015 10:31:32 PM [Info  ]: AS Java process ID 135 has been started.

Dec 14, 2015 10:31:32 PM [Info  ]:   Command line: F:\usr\sap\SID\DVEBMGS00\exe\sapjvm_5\bin\java.exe -Xmx900M -Djava.ext.dir=F:/usr/sap/SID/DVEBMGS00/SDM/program/lib;F:/usr/sap/SID/DVEBMGS00/exe/sapjvm_5/jre/lib/ext -cp . -jar F:\usr\sap\SID\DVEBMGS00\SDM\program\bin\SDM.jar shutdown Sdmguiport=50018 sdmHome=F:/usr/sap/SID/DVEBMGS00/SDM/program logfile=F:\SUM\SUM\sdt\log\SUM\OperateSDM_23.LOG

Dec 14, 2015 10:31:32 PM [Info  ]:   Standard out: F:\SUM\SUM\sdt\log\SUM\OPERATESDM_12.OUT

Dec 14, 2015 10:31:32 PM [Info  ]: Deployment message for component SAP_JAVASL :

Dec 14, 2015 10:31:32 PM [Error ]: The following problem has occurred during step execution: java.lang.NullPointerException: while trying to invoke the method java.lang.Process.destroy() of a null object returned from com.sap.sdt.tools.proc.OsProcess.getProcessObject().

Any ideas, please?

Thanks & best regards,

Sreenu

Hi Shilpi,

Thanks for reply.

Please see this.

Hi Expert,

We are using Solman 7.1 SP10.

Status changes occurred by the Solman batch user to knock it back to To Be Tested.

Change Document is normal change.

Please see the screenshot and advice it why this happened

Regards,

Abhinash

Have you restarted the instance?

No I have not found the resolution yet. 

Hi Saravanan, Can you check the e2emai.log file? Also See if SAP note helps here 2142276 - Grey Metrics in System Monitoring after Agent JVM upgrade Kind regards, Roland

Hi IMRAN,

This kind of issue occurs either because the agent cannot reach the EM host, therefore you have to try a telnet from the managed system to the EM host and port.

Besides that, if the EM is overloaded, the agent may not be able to connect, check the Enterprise Manager performance using the tool attached to KBA 2156320. It will provide recommendations in case any adjustment is necessary.

If the issue persists, attach file jvm_smdagent.out .

Kind regards,

Daniel.

Yeah sunil, i already done as per the Note. But, same error result.

Dear Daniel,

Thanks for your reply,

Please  Suggest which port need to be open form  managed system?

Willy interscope Ip adress:10.1.66.189 port no:6001

Please find the attached snap shot OF WILLY INTERSCOPE PORT details , log of JVM_SMDAGENT.OUT  and EM_PERFLOG ANALYZER snap shot below

JVM_SMDAGENT.OUT:

AgentLauncherLogger [debug]: run
AgentLauncherLogger [debug]: ***********************************************************************
AgentLauncherLogger [debug]: * LoadBalanceRestricted=false
AgentLauncherLogger [debug]: * P4ClassLoad=P4Connection
AgentLauncherLogger [debug]: * SAPDBHOST=
AgentLauncherLogger [debug]: * SAPINFO=DA4_95_smdagent
AgentLauncherLogger [debug]: * SAPJStartVersion=721, patch 402, changelist 1562712, hpia64, optu (EXT) (Mar  9 2015, 04:39:10)
AgentLauncherLogger [debug]: *  SAPMYNAME=pcbe6ci_DA4_95
AgentLauncherLogger [debug]: * SAPSTARTUP=1
AgentLauncherLogger [debug]: * SAPSYSTEM=95
AgentLauncherLogger [debug]: * SAPSYSTEMNAME=DA4
AgentLauncherLogger [debug]: * application.home=/usr/sap/DA4/SMDA95/exe
AgentLauncherLogger [debug]: * com.sap.vm.codeline=61_REL
AgentLauncherLogger [debug]: * com.sap.vm.compressedoops=true
AgentLauncherLogger [debug]: * com.sap.vm.profilingserver=true
AgentLauncherLogger [debug]: * com.sap.vm.type=opt
AgentLauncherLogger [debug]: *  com.sap.vm.version=10
AgentLauncherLogger [debug]: * env.class.path=
AgentLauncherLogger [debug]: * file.encoding=ISO8859-1
AgentLauncherLogger [debug]: * file.encoding.pkg=sun.io
AgentLauncherLogger [debug]: * file.separator=/
AgentLauncherLogger [debug]: * j2ee.dbhost=
AgentLauncherLogger [debug]: * java.awt.graphicsenv=sun.awt.X11GraphicsEnvironment
AgentLauncherLogger [debug]: * java.awt.printerjob=sun.print.PSPrinterJob
AgentLauncherLogger [debug]: * java.class.path=/usr/sap/DA4/SMDA95/exe/jstart71.jar:/usr/sap/DA4/SMDA95/exe/sapjvm_6/lib/jvmx.jar:/usr/sap/DA4/SMDA95/exe/sapjvm_6/lib/jvmx_tools.jar:/usr/sap/DA4/SMDA95/exe/jre/lib/iqlib.jar:/usr/sap/DA4/SMDA95/exe/sapjvm_6/lib/tools.jar:lib/iaik/iaik_jce.jar:lib/iaik/iaik_jsse.jar:lib/iaik/iaik_smime.jar:lib/iaik/iaik_ssl.jar:lib/iaik/w3c_http.jar:../exe/jstartupapi.jar:../exe/jstartupimpl.jar:lib/patch_7.10.13.0.20150224225905/launcher/smdagentlauncher.jar:../exe/jperflib.jar
AgentLauncherLogger [debug]: * java.class.version=50.0
AgentLauncherLogger [debug]: * java.endorsed.dirs=/usr/sap/DA4/SMDA95/exe/sapjvm_6/jre/lib/endorsed
AgentLauncherLogger [debug]: * java.ext.dirs=/usr/sap/DA4/SMDA95/exe/sapjvm_6/jre/lib/ext-sap:/usr/sap/DA4/SMDA95/exe/sapjvm_6/jre/lib/ext
AgentLauncherLogger [debug]: *  java.home=/usr/sap/DA4/SMDA95/exe/sapjvm_6/jre
AgentLauncherLogger [debug]: * java.io.tmpdir=/var/tmp/
AgentLauncherLogger [debug]: * java.library.path=/usr/sap/DA4/SMDA95/exe/sapjvm_6/jre/lib/ia64/server:/usr/sap/DA4/SMDA95/exe/sapjvm_6/jre/lib/ia64:/usr/sap/DA4/SMDA95/j2ee/os_libs:/usr/sap/DA4/SMDA95/exe
AgentLauncherLogger [debug]: * java.runtime.name=Java(TM) SE Runtime Environment
AgentLauncherLogger [debug]: * java.runtime.version=6.1.076
AgentLauncherLogger [debug]: * java.specification.name=Java Platform API Specification
AgentLauncherLogger [debug]: * java.specification.vendor=Sun Microsystems Inc.
AgentLauncherLogger [debug]: * java.specification.version=1.6
AgentLauncherLogger [debug]: * java.vendor=SAP AG
AgentLauncherLogger [debug]: *  java.vendor.url=http://www.sap.com/
AgentLauncherLogger [debug]: * java.vendor.url.bug=http://service.sap.com/support
AgentLauncherLogger [debug]: * java.version=1.6.0_95
AgentLauncherLogger [debug]: * java.vm.compressedOopsMode=32-bits Oops
AgentLauncherLogger [debug]: * java.vm.info=Apr 23 2015 13:48:20 - 61_REL - optU - hpux ia64 - 6 - bas2:239155 (mixed mode)
AgentLauncherLogger [debug]: * java.vm.name=SAP Java Server VM
AgentLauncherLogger [debug]: * java.vm.specification.name=Java Virtual Machine Specification
AgentLauncherLogger [debug]: * java.vm.specification.vendor=Sun Microsystems Inc.
AgentLauncherLogger [debug]: * java.vm.specification.version=1.0
AgentLauncherLogger [debug]: * java.vm.vendor=SAP AG
AgentLauncherLogger [debug]: * java.vm.version=6.1.076 25.45-b02
AgentLauncherLogger [debug]: * jstartup.debuggable=yes
AgentLauncherLogger [debug]: * jstartup.mode=JSTART
AgentLauncherLogger [debug]: * jstartup.ownHardwareId=F0831984652
AgentLauncherLogger [debug]: * jstartup.ownProcessId=17339
AgentLauncherLogger [debug]: * jstartup.whoami=java
AgentLauncherLogger [debug]: * line.separator=

AgentLauncherLogger [debug]: * os.arch=ia64
AgentLauncherLogger [debug]: * os.name=HP-UX
AgentLauncherLogger [debug]: * os.version=B.11.31
AgentLauncherLogger [debug]: * path.separator=:
AgentLauncherLogger [debug]: * sun.arch.data.model=64
AgentLauncherLogger [debug]: * sun.boot.class.path=/usr/sap/DA4/SMDA95/exe/sapjvm_6/jre/lib/sapjvm-alt-rt.jar:/usr/sap/DA4/SMDA95/exe/sapjvm_6/jre/lib/resources.jar:/usr/sap/DA4/SMDA95/exe/sapjvm_6/jre/lib/rt.jar:/usr/sap/DA4/SMDA95/exe/sapjvm_6/jre/lib/sunrsasign.jar:/usr/sap/DA4/SMDA95/exe/sapjvm_6/jre/lib/jsse.jar:/usr/sap/DA4/SMDA95/exe/sapjvm_6/jre/lib/jce.jar:/usr/sap/DA4/SMDA95/exe/sapjvm_6/jre/lib/charsets.jar:/usr/sap/DA4/SMDA95/exe/sapjvm_6/jre/lib/jfr.jar:/usr/sap/DA4/SMDA95/exe/sapjvm_6/jre/classes
AgentLauncherLogger [debug]: * sun.boot.library.path=/usr/sap/DA4/SMDA95/exe/sapjvm_6/jre/lib/ia64
AgentLauncherLogger [debug]: * sun.cds.enableSharedLookupCache=false
AgentLauncherLogger [debug]: * sun.cpu.endian=big
AgentLauncherLogger [debug]: * sun.cpu.isalist=
AgentLauncherLogger [debug]: * sun.io.unicode.encoding=UnicodeBig
AgentLauncherLogger [debug]: * sun.java.launcher=jstart
AgentLauncherLogger [debug]: * sun.jnu.encoding=ISO8859-1
AgentLauncherLogger [debug]: * sun.management.compiler=HotSpot 64-Bit Tiered Compilers
AgentLauncherLogger [debug]: * sun.os.patch.level=unknown
AgentLauncherLogger [debug]: * sys.global.dir=/usr/sap/DA4/SYS/global
AgentLauncherLogger [debug]: * user.country=US
AgentLauncherLogger [debug]: * user.dir=/usr/sap/DA4/SMDA95/SMDAgent
AgentLauncherLogger [debug]: * user.home=/home/da4adm
AgentLauncherLogger [debug]: * user.language=en
AgentLauncherLogger [debug]: * user.name=da4adm
AgentLauncherLogger [debug]: * user.timezone=
AgentLauncherLogger [debug]: ***********************************************************************
AgentLauncherLogger [info]: Running SMD Agent ...
adding Provider IAIK...

Java version number: 1.6.0_95
Java compiler: null
Java vendor-specific string: SAP AG
Java vendor URL: http://www.sap.com/
Java installation directory: /usr/sap/DA4/SMDA95/exe/sapjvm_6/jre
Java class format version number: 50.0
Java class path: /usr/sap/DA4/SMDA95/exe/jstart71.jar:/usr/sap/DA4/SMDA95/exe/sapjvm_6/lib/jvmx.jar:/usr/sap/DA4/SMDA95/exe/sapjvm_6/lib/jvmx_tools.jar:/usr/sap/DA4/SMDA95/exe/jre/lib/iqlib.jar:/usr/sap/DA4/SMDA95/exe/sapjvm_6/lib/tools.jar:lib/iaik/iaik_jce.jar:lib/iaik/iaik_jsse.jar:lib/iaik/iaik_smime.jar:lib/iaik/iaik_ssl.jar:lib/iaik/w3c_http.jar:../exe/jstartupapi.jar:../exe/jstartupimpl.jar:lib/patch_7.10.13.0.20150224225905/launcher/smdagentlauncher.jar:../exe/jperflib.jar
Operating system name: HP-UX
Operating system architecture: ia64
Operating system version: B.11.31

Installed security providers providers:

Provider 1: IAIK  version: 3.1810000000000005
Provider 2: SUN  version: 1.6
Provider 3: SunRsaSign  version: 1.5
Provider 4: SunJSSE  version: 1.6
Provider 5: SunJCE  version: 1.6
Provider 6: SunJGSS  version: 1.0
Provider 7: SunSASL  version: 1.5
Provider 8: XMLDSig  version: 1.0
Provider 9: SunPCSC  version: 1.6
[ms://10.1.66.189:8102/P4] Agent ready.
12/15/15 11:56:00 PM IST [INFO] [IntroscopeAgent] Introscope Agent Release 8.2.4.0 (Build 476771)
12/15/15 11:56:00 PM IST [INFO] [IntroscopeAgent] Using Java VM version "SAP Java Server VM 1.6.0_95" from SAP AG
12/15/15 11:56:00 PM IST [INFO] [IntroscopeAgent] Trying to load agent profile based on system property "com.wily.introscope.agentProfile"
12/15/15 11:56:00 PM IST [INFO] [IntroscopeAgent] Trying to load file from /usr/sap/DA4/SMDA95/SMDAgent/applications.config/com.sap.smd.agent.application.wilyhost/IntroscopeSapAgent.profile
12/15/15 11:56:00 PM IST [INFO] [IntroscopeAgent] Loaded file from /usr/sap/DA4/SMDA95/SMDAgent/applications.config/com.sap.smd.agent.application.wilyhost/IntroscopeSapAgent.profile
12/15/15 11:56:00 PM IST [INFO] [IntroscopeAgent] Agent Metric Aging is turned off
12/15/15 11:56:00 PM IST [INFO] [IntroscopeAgent] Agent Metric Aging: property introscope.agent.metricAging.heartbeatInterval is set to 1800
12/15/15 11:56:00 PM IST [INFO] [IntroscopeAgent] Agent Metric Aging: property introscope.agent.metricAging.dataChunk is set to 500
12/15/15 11:56:00 PM IST [INFO] [IntroscopeAgent] Agent Metric Aging: property introscope.agent.metricAging.numberTimeslices is set to 3000
12/15/15 11:56:00 PM IST [INFO] [IntroscopeAgent] Looking for agent profile property "introscope.agent.extensions.directory" to locate the extensions directory.
12/15/15 11:56:00 PM IST [INFO] [IntroscopeAgent] The agent extensions directory /usr/sap/DA4/SMDA95/SMDAgent/applications.config/com.sap.smd.agent.application.wilyhost/ext was successfully located
12/15/15 11:56:00 PM IST [INFO] [IntroscopeAgent] Introscope Agent startup complete.                 
12/15/15 11:56:00 PM IST [INFO] [IntroscopeAgent] The Agent will attempt to determine its name.
12/15/15 11:56:00 PM IST [INFO] [IntroscopeAgent] Using the Agent name "SAP HostAgent SMDA95" based on the value of the System Property "com.wily.introscope.agent.agentName".
12/15/15 11:56:00 PM IST [INFO] [IntroscopeAgent] Initial agent name set to SAP HostAgent SMDA95
12/15/15 11:56:00 PM IST [INFO] [IntroscopeAgent] Started Error Reporting service
12/15/15 11:56:00 PM IST [INFO] [IntroscopeAgent.Isengard] Initiating connection attempts to the Introscope Enterprise Manager.
12/15/15 11:56:00 PM IST [INFO] [IntroscopeAgent.Isengard] The Agent reconnection delay is set to 15 second(s).
12/15/15 11:56:00 PM IST [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at utclsm:6001,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory (1).
Initialization done.
12/15/15 11:56:10 PM IST [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at utclsm:6001,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory (2).
12/15/15 11:56:20 PM IST [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at utclsm:6001,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory (3).
12/15/15 11:56:30 PM IST [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at utclsm:6001,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory (4).
12/15/15 11:56:40 PM IST [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at utclsm:6001,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory (5).
12/15/15 11:56:50 PM IST [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at utclsm:6001,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory (6).
12/15/15 11:57:00 PM IST [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at utclsm:6001,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory (7).
12/15/15 11:57:10 PM IST [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at utclsm:6001,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory (8).
12/15/15 11:57:20 PM IST [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at utclsm:6001,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory (9).
12/15/15 11:57:30 PM IST [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at utclsm:6001,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory (10).
12/15/15 11:57:30 PM IST [INFO] [IntroscopeAgent.ConnectionThread] The Agent will continue to attempt to connect to Introscope Enterprise Manager. Further failures will not be logged.

EM PERFLOG ANALYZER

Kindly advise,

Regards,

IMRAN.

Hi IMRAN,

Please increase the EM heap memory as recommended by the tool and restart the EM.

Please also try a telnet from your managed system host to host "utclsm"  port 6001. If it does not work, then the Introscope Host Adapter can't connect either due to a network issue, you have to make sure that name "utclsm" can be resolved correctly in your network.

Make sure you perform the test using the host name "utclsm" and not the direct IP, it has to be tested exactly as shown in the logs.

After you do this, restart the SMD Agent and check in the EM webview / workstation if the respective host is shown.

Kind regards,

Daniel.

Hello All,

The ACP file 'ST========710' is now released.
Please create a new MOPZ transaction and the issue should be resovled.

Sorry for any inconvenience caused.

Kind regards,
Gordon Goh
SAP Product Support

The OBJID is the object id to retrieve the document from the content server which is defined by SOLARCONTENTDB in transaction OAC0. It is a content repository.

In solar02 - click on URL under document attributes and it will show the direct URL link to access the physical document. You can paste it in browser to retrieve the document. It has the object id in the URL.

How long did you wait, it can take some time as the message suggest.

Also check the S- user has proper authorizations in marketplace.

OK I found out what the cause was.  Seemed very odd that is was saying this error for ALL java systems including Solman which is running on Windows.

Turns out that the service user running solman really didn't have access to the directory C:Windows\Temp.  A bit misleading but hey corrected it.

Thanks

Craig

I was referring to SPRO settings in SolMan

Regards,

AD

Hi All,

Sorry it's me again, could have posted this in the other thread but you usually get told off for that sort of thing so here is another!

For each of my JAVA Stack systems Solman included I am seeing this error :-

Exception while accessing Web Service - cause: Service call exception; nested exception is:

java.net.ConnectException: Connection refused (port 53000 to address 127.0.0.1 (localhost))

For the extracts for CONFIGURATION (WEB SERVICE) except for production java stacks which don't show the port or address in the error.

Exception while accessing Web Service - cause: Service call exception; nested exception is:

java.net.ConnectException: Connection refused: connect

Any ideas what is causing this and how do I resolve?

Thanks

Craig

Hello Imtiaz,

I have been trying to complete this particular phase from 1 day. Moreover, every time when i execute it i waited for more than 30 mins.

I am using the administrator s-user id.

Regards

Praveen

Hi

On ITSM system how can i display the login ID (shich in GUI/SU01) of every business partner on My data page or when we click on

the name of the creator of Incident/Service .

no issue if will display both but we need to show the login I. i know all are available on BUT000 table

but how to show. please see my snapshot

Thanks

Can you still check by login to marketplace to see you can add one SP for the system to download basket.

Can you check system logs and traces, does it report any connection failure.