SMD Error in managed system type PI 7.1 EHP1 Step Logical Ports error

Hi people,
Solution Manager Ehp1 7.0 SPS24
I am currently runnig the wizard setup for managed System, everything is fine but when I run for PI 7.1 I get the following error:
Fri Sep 10 20:29:48 2010 Logical Ports A failure occured while creating the logical port for JAVA XI : PORT_NOT_CREATED
Step Logical Ports Details
A failure occured while creating the logical port for JAVA XI : PORT_NOT_CREATED
!! Exception : PORT_NOT_CREATED
Exceptions
com.sap.mw.jco.JCO$AbapException: (126) PORT_NOT_CREATED: PORT_NOT_CREATED
at com.sap.mw.jco.MiddlewareJRfc$Client.execute(MiddlewareJRfc.java:1511)
at com.sap.mw.jco.JCO$Client.execute(JCO.java:3980)
at com.sap.mw.jco.JCO$Client.execute(JCO.java:3514)
at com.sap.sup.admin.setup.SolManRfcAdapter.createXIlogicalPort(SolManRfcAdapter.java:185)
at com.sap.sup.admin.setup.SetupStep.runExec(SetupStep.java:427)
at com.sap.sup.admin.setup.SetupStep.execute(SetupStep.java:335)
at com.sap.smd.agent.plugins.remotesetup.SapInstance.setup(SapInstance.java:549)
at com.sap.sup.admin.setup.SapCluster.setup(SapCluster.java:1695)
at com.sap.sup.admin.setup.SapCluster.access$000(SapCluster.java:35)
at com.sap.sup.admin.setup.SapCluster$SetupRunner.run(SapCluster.java:1965)
at java.lang.Thread.run(Thread.java:534)
Any ideas?
Thanks in advance

Hi everyone,
Thanks everyone.
Guilherme, finally I understand what really happens. "Refresh" is not working properly in the Setup Wizard.
First I have done what I can:
System    Type      Managed Products                    Product Instances
DPI           ABAP     SAP Netweaver PI 7.1               Application Server ABAP (I could not select PI at the same time)
DPI           JAVA     SAP Netweaver PI 7.1               Application Server Java + Process Integration
But, when I refresh the browser Internet Explorer appears the following:
System    Type      Managed Products                    Product Instances
DPI           ABAP     SAP Netweaver PI 7.1               Application Server ABAP + Process Integration
DPI           JAVA     SAP Netweaver PI 7.1               Application Server Java + Process Integration
And then I do not get the error anymore. (I have to repeat step 2 in the wizard "Check Prerequisites for Diagnostics)
And If I run transaction SMSY, I can see how PI is mantained since the wizard refresh SMSY.
Product Instance Selection tab:
Application Server ABAP (Flag selected: relevant)
Process Integration (Flag selected: Also Installed, Technical System[ DPI, Java])
Application Server Java (Flag selected: relevant, Technical System[ DPI, Java])
So, if I use this configuration in the SMSY, when I run "solman_setup", configuring DPI (My PI7.1), when I run "Configure Diagnostics", the wizard shows ABAP + PI as expected.
Thanks a lot Guilherme!!

Similar Messages

PI 7.1 EHP1 Step Logical Ports error

Hello,
I got the below error when in ran the managed system configuration for PI 7.1 EHP1 system.
Our solman is on SP22
Step Logical Ports Details
A failure occured while creating the logical port for JAVA XI : An exception occurred that was not caught.
!! Exception : An exception occurred that was not caught.
Exceptions
com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: An exception occurred that was not caught.
at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:516)
at com.sap.mw.jco.MiddlewareJRfc$Client.execute(MiddlewareJRfc.java:1514)
at com.sap.mw.jco.JCO$Client.execute(JCO.java:3980)
at com.sap.mw.jco.JCO$Client.execute(JCO.java:3514)
at com.sap.sup.admin.setup.SolManRfcAdapter.createXIlogicalPort(SolManRfcAdapter.java:185)
at com.sap.sup.admin.setup.SetupStep.runExec(SetupStep.java:427)
at com.sap.sup.admin.setup.SetupStep.execute(SetupStep.java:335)
at com.sap.smd.agent.plugins.remotesetup.SapInstance.setup(SapInstance.java:549)
at com.sap.sup.admin.setup.SapCluster.setup(SapCluster.java:1695)
at com.sap.sup.admin.setup.SapCluster.access$000(SapCluster.java:35)
at com.sap.sup.admin.setup.SapCluster$SetupRunner.run(SapCluster.java:1965)
at java.lang.Thread.run(Thread.java:534)
EW Report for PI system is only 9 pages ,may be the above error is causing it.
Please help us to solve it
Thanks,
Srini

Hi Balbinot,
Thanks for your reply.
1. SMD_RFC user is not locked (in Solman).
2. According to note 1008474 in Visual Administrator of Solman CTC System Properties ,I found that the BACKEND_CLIENT property is having "001" as value (001 is our BW client) but the regular client is 201 .Should the value be 201 or 001 ????
And TTJAVA_HOME is having /usr/j2sdk1.4.2_13 but our java home is /usr/jdk/instances/j2sdk1.4.2_18 should i go ahead and change this one as well?
3.E2E_WS_CONN_LOG_PORT_CREATION does not exist in PI 7.1 system ,should this be run in Solution manager ?
Please help me to solve this issue?
Thanks,
Srini K

Error in Managed System Configuration - Sol Man 7.1

Dear Experts,
Whle configuring using solman_setup, I am getting below mentioned error in Managed System Configuaration:
Cannot retrieve CIM Instances from CIM Class 'SAP_DiagnosticsRelevantSoftwareFeature'!
Cannot retrieve all CIM Instances from CIM class name 'SAP_TechnicalScenario' via LMDB Mass Access API!
Cannot retrieve all CIM Instances from CIM class name 'SAP_DatabaseSystem' via LMDB Mass Access API!
Any suggestions??
Regards
Vivek

Hi Paul ,
Thanks for the note that you provided.
I am reconfiguring the LMDB and conteny Sync... The refresh will take 15-16 hours.. I am just waiting for the
sync to be finished. Let's see what is in the store for me
Keeping my fingers crossed untill then.
Regards
Vivek

Logical port error (WS_LOGICAL_PORT) when consuming WS in PI

Hi All,
I am trying to integrate simple Currency Conversion Web Service witm my ECC program.
Program displays two fields in the selection screen (Currency From and Currency To)
WS is: http://www.webservicex.com/ws/WSDetails.aspx?WSID=10&CATID=2
The scenario is as below:
Proxy (Z-PROGRAM ) <-sync-> PI <-sync-> WS (Currency Convertor)
Looks like ABAP Proxy is done ok.
PI configuration also looks ok as I am trying it in IB's Test Configuration tool - all steps are 'Green / Passed'
Based on WSDL 3 interfaces were generated:
CurrencyConvertorHttpPost
CurrencyConvertorHttpGet
CurrencyConvertorSoap
I am using Soap one... along with WS Communication Channel
CC has configuren itself based on WSDL likn provided,
Technical Transport Settings were set to:
Target Host:               www.webservicex.net
Service Name / Port:     -1
URL Access Path:          /CurrencyConvertor.asmx
Transport Binding:          SOAP 1.1 Using HTTP
Why am I getting logical port error?
Error while determining logical port Cannot find logical port for agreement EAC1E5CF03FD3B2C827ADDECA2EA6B26 and interface urn:webservicex:com:test:currencyrates.CurrencyConvertorSoap
I searched the web for error message and I found obsolete logical port configuration using LPCONFIG, and also some 'new' approach with SOAMANAGER LogPort configuraton
(When I try to do this as suggested in [document |http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b04408cc-f10e-2c10-b5b7-af11026b2393?QuickLink=index&overridelayout=true]
then I cannot see my newly created services on the list)
... but is this the right track to follow?
Should I run Logical Port configuration in PI?
I would appreciate your comments on this.
Regards,
bob.

Hello,
Why am I getting logical port error?
Error while determining logical port Cannot find logical port for agreement EAC1E5CF03FD3B2C827ADDECA2EA6B26 and interface urn:webservicex:com:test:currencyrates.CurrencyConvertorSoap
WS Adapter is used for those that are using WS-RM (Webservice-Reliable Messaging)...See this blog
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b00bbb77-75bc-2a10-6b9a-a6f8161515a6, but I think for now this is limited to SAP-to-SAP connections. That is why in your error it is searching for a logical port (ABAP Proxy).
You should be using the SOAP Receiver Adapter instead.
Hope this helps,
Mark

SMD Installation Error in Managed Systems

We are installing SMD 7.11 in all our managed systems running on Aix 6.1, we are able to install in all the systems except one, which gives the error at the below step.
SAPVM.log
$ cat SAPVM.log
SAPCAR: processing archive /sapinst_sm/smd/SMD711_01_IM_AIX_PPC64/COMMON/INSTALL/SAPVM.SAR (version 2.01)
x sapjvm_5
x sapjvm_5/jre
x sapjvm_5/jre/bin
x sapjvm_5/jre/bin/java
x sapjvm_5/jre/bin/keytool
x sapjvm_5/jre/bin/policytool
x sapjvm_5/jre/bin/kinit
x sapjvm_5/jre/bin/klist
x sapjvm_5/jre/bin/ktab
x sapjvm_5/jre/bin/rmiregistry
x sapjvm_5/jre/bin/rmid
x sapjvm_5/jre/bin/tnameserv
x sapjvm_5/jre/bin/orbd
x sapjvm_5/jre/bin/servertool
x sapjvm_5/jre/bin/unpack200
x sapjvm_5/jre/bin/pack200
x sapjvm_5/jre/lib
x sapjvm_5/jre/lib/applet
x sapjvm_5/jre/lib/ppc64
x sapjvm_5/jre/lib/ppc64/server
x sapjvm_5/jre/lib/ppc64/server/libjvm.so
SAPCAR: checksum error in sapjvm_5/jre/lib/ppc64/server/libjvm.so (error 12). No such file or directory
$
sapinst_dev.log
INFO       2011-11-21 13:46:11.588
           CJSlibModule::writeInfo_impl()
Output of /tmp/sapinst_exe.13631492.1321899048/SAPCAR -x -v -i -f /sapinst_sm/smd/SMD711_01_IM_AIX_PPC64/COMMON/INSTALL/SAPVM.SAR, sapjvm_5:
SAPCAR: processing archive /sapinst_sm/smd/SMD711_01_IM_AIX_PPC64/COMMON/INSTALL/SAPVM.SAR (version 2.01)
x sapjvm_5
x sapjvm_5/jre
x sapjvm_5/jre/bin
x sapjvm_5/jre/bin/java
x sapjvm_5/jre/bin/keytool
x sapjvm_5/jre/bin/policytool
x sapjvm_5/jre/bin/kinit
x sapjvm_5/jre/bin/klist
x sapjvm_5/jre/bin/ktab
x sapjvm_5/jre/bin/rmiregistry
x sapjvm_5/jre/bin/rmid
x sapjvm_5/jre/bin/tnameserv
x sapjvm_5/jre/bin/orbd
x sapjvm_5/jre/bin/servertool
x sapjvm_5/jre/bin/unpack200
x sapjvm_5/jre/bin/pack200
x sapjvm_5/jre/lib
x sapjvm_5/jre/lib/applet
x sapjvm_5/jre/lib/ppc64
x sapjvm_5/jre/lib/ppc64/server
x sapjvm_5/jre/lib/ppc64/server/libjvm.so
SAPCAR: checksum error in sapjvm_5/jre/lib/ppc64/server/libjvm.so (error 12). No such file or directory
TRACE      2011-11-21 13:46:11.590
FSPath(/tmp/sapinst_exe.13631492.1321899048/SAPCAR) done
TRACE      2011-11-21 13:46:11.590
ChildApplication(/tmp/sapinst_exe.13631492.1321899048/SAPCAR).getReturnCode(true)
TRACE      2011-11-21 13:46:11.591 [syuxctask.cpp:560]
           CUnixProcessManager::waitpid(pid_t pid, int * pStatus, int options)
           lib=syslib module=syslib
Child process 22151394 returned 12
TRACE      2011-11-21 13:46:11.592
FSPath(/tmp/sapinst_exe.13631492.1321899048/SAPCAR) done
TRACE      2011-11-21 13:46:11.592
ChildApplication(/tmp/sapinst_exe.13631492.1321899048/SAPCAR).getReturnCode() done: 12
TRACE      2011-11-21 13:46:11.593
FSPath(/tmp/sapinst_exe.13631492.1321899048/SAPCAR) done
TRACE      2011-11-21 13:46:11.594
ChildApplication(/tmp/sapinst_exe.13631492.1321899048/SAPCAR).getStatus()
TRACE      2011-11-21 13:46:11.595
FSPath(/tmp/sapinst_exe.13631492.1321899048/SAPCAR) done
TRACE      2011-11-21 13:46:11.595
ChildApplication(/tmp/sapinst_exe.13631492.1321899048/SAPCAR).getStatus() done: TST_FINISHED
TRACE      2011-11-21 13:46:11.596
FSPath(/tmp/sapinst_exe.13631492.1321899048/SAPCAR) done
TRACE      2011-11-21 13:46:11.596
Returncode of /tmp/sapinst_exe.13631492.1321899048/SAPCAR: 12
TRACE      2011-11-21 13:46:11.597
FSPath(/tmp/sapinst_exe.13631492.1321899048/SAPCAR) done
ERROR      2011-11-21 13:46:11.598
           CJSlibModule::writeError_impl()
MUT-03011 Execution of the command "/tmp/sapinst_exe.13631492.1321899048/SAPCAR -x -v -i -f /sapinst_sm/smd/SMD711_01_IM_AIX_PPC64/COMMON/INSTALL/SAPVM.SAR, sapjvm_5" finished with return code 12. Output:
SAPCAR: processing archive /sapinst_sm/smd/SMD711_01_IM_AIX_PPC64/COMMON/INSTALL/SAPVM.SAR (version 2.01)
x sapjvm_5
x sapjvm_5/jre
x sapjvm_5/jre/bin
x sapjvm_5/jre/bin/java
x sapjvm_5/jre/bin/keytool
x sapjvm_5/jre/bin/policytool
x sapjvm_5/jre/bin/kinit
x sapjvm_5/jre/bin/klist
x sapjvm_5/jre/bin/ktab
x sapjvm_5/jre/bin/rmiregistry
x sapjvm_5/jre/bin/rmid
x sapjvm_5/jre/bin/tnameserv
x sapjvm_5/jre/bin/orbd
x sapjvm_5/jre/bin/servertool
x sapjvm_5/jre/bin/unpack200
x sapjvm_5/jre/bin/pack200
x sapjvm_5/jre/lib
x sapjvm_5/jre/lib/applet
x sapjvm_5/jre/lib/ppc64
x sapjvm_5/jre/lib/ppc64/server
x sapjvm_5/jre/lib/ppc64/server/libjvm.so
SAPCAR: checksum error in sapjvm_5/jre/lib/ppc64/server/libjvm.so (error 12). No such file or directory
TRACE      2011-11-21 13:46:11.599 [iaxxejsbas.hpp:413]
           handleException<ESAPinstJSError>()
Converting exception into JS Exception EJSException.
The logInquirerOutStepError-NW_DiagnosticsAgent-ind-ind-ind-ind-0-0-NW_DiagnosticsAgent_GetSid-ind-ind-ind-ind-1-0-NW_getJavaHome-ind-ind-ind-ind-4-0.xml says are below
$ cat logInquirerOutStepError-NW_DiagnosticsAgent-ind-ind-ind-ind-0-0-NW_DiagnosticsAgent_GetSid-ind-ind-ind-ind-1-0-NW_getJavaHome-ind-ind-ind-ind-4-0.xml
<?xml version="1.0" encoding="utf-8"?>
<stepMessages componentTyp="NW_getJavaHome|ind|ind|ind|ind" componentInstance="|NW_DiagnosticsAgent|ind|ind|ind|ind|0|0|NW_DiagnosticsAgent_GetSid|ind|ind|ind|ind|1|0|NW_getJavaHome|ind|ind|ind|ind|4|0" step="unpackSAPJVM">
<configuration>
<property name="CPUCount">16</property>
<property name="CPUFamily">IBM6000</property>
<property name="INSTPARA_DB">IND</property>
<property name="INSTPARA_PRODUCT">NetWeaver</property>
<property name="INSTPARA_PRODUCT_VERSION">06</property>
<property name="INSTPARA_START_DIR">/tmp/sapinst_instdir/SMD_NW711/INSTALL/STANDALONE/SMD/INST</property>
<property name="OSType">AIX_64</property>
<property name="OSUname">AIX palatine 1 6 00F65A064C00</property>
<property name="OSVersion"></property>
<property name="RamSize">20480</property>
<property name="RealOSBits">64</property>
<property name="SAPInst ABI version">712</property>
<property name="SAPInst latest changelist">1068035</property>
<property name="SAPInst used source locations">/bas/710_REL/src</property>
<property name="SAPInst version of used kernel">710_REL</property>
<property name="SwapSize">20480</property>
</configuration>
<firstErrorMessage>
<message type="error" timestamp="2011-11-21 13:46:11.992">Could not get value for property .</message>
</firstErrorMessage>
<lastErrorMessage>
<message type="error" timestamp="2011-11-21 13:46:11.992">Could not get value for property .</message>
</lastErrorMessage>
<messageStack>
<message type="trace" timestamp="2011-11-21 13:46:11.990"> Call block:CallBackInCaseOfAnErrorDuringStepExecution     function:CallTheLogInquirer is validator: true</message>
<message type="warning" timestamp="2011-11-21 13:46:11.992">Could not get property IDs of the JavaScript object.</message>
<message type="error" timestamp="2011-11-21 13:46:11.992">Could not get value for property .</message>
<message type="trace" timestamp="2011-11-21 13:46:12.97">Target node does not exists and (mode & ISyNode::MISSING) ==> I will copy/move.</message>
<message type="trace" timestamp="2011-11-21 13:46:12.97">Moved /tmp/sapinst_instdir/SMD_NW711/INSTALL/STANDALONE/SMD/INST/logInquirerOutStepError-NW_DiagnosticsAgent-ind-ind-ind-ind-0-0-NW_DiagnosticsAgent_GetSid-ind-ind-ind-ind-1-0-NW_getJavaHome-ind-ind-ind-ind-4-0.xml to /tmp/sapinst_instdir/SMD_NW711/INSTALL/STANDALONE/SMD/INST/logInquirerOutStepError-NW_DiagnosticsAgent-ind-ind-ind-ind-0-0-NW_DiagnosticsAgent_GetSid-ind-ind-ind-ind-1-0-NW_getJavaHome-ind-ind-ind-ind-4-0.1.xml</message>
<message type="trace" timestamp="2011-11-21 13:46:12.142">A child process has been started. Pid = 22151402</message>
<message type="trace" timestamp="2011-11-21 13:46:12.215">Child process 22151402 returned 0 </message>
<message type="trace" timestamp="2011-11-21 13:46:12.244">A child process has been started. Pid = 22151404</message>
<message type="trace" timestamp="2011-11-21 13:46:12.327">Child process 22151404 returned 255 </message>
<message type="warning" timestamp="2011-11-21 13:46:12.328">Could not run /usr/sbin/lsattr -l aio0 -E -O successfully. Either the return code was != 0 or the process terminated abnormally.</message>
<message type="trace" timestamp="2011-11-21 13:46:12.358">A child process has been started. Pid = 22151406</message>
<message type="trace" timestamp="2011-11-21 13:46:12.457">Child process 22151406 returned 0 </message>
</messageStack>
</stepMessages>
$
Has anyone faced this issue?
Regards

Thank you Ken
We have got enough space under /tmp, the issue is resolved after a reboot of the server, we rebooted the server and then started the same installation it worked.
Now again, when I try to install the hostagent, it gives me the below error:
INFO       2011-11-23 09:10:51.414 [syuxcaccmg.cpp:305]
           bool CSyAccountMgtImpl::isExisting(ISyAccountMgt::eAccountType accountType, iastring sName)
           lib=syslib module=syslib
Account 206 already exists.
INFO       2011-11-23 09:10:51.416 [syuxcaccmg.cpp:305]
           bool CSyAccountMgtImpl::isExisting(ISyAccountMgt::eAccountType accountType, iastring sName)
           lib=syslib module=syslib
Account sapinst already exists.
WARNING    2011-11-23 09:10:51.427 [syuxcgroup.cpp:146]
           <anonymous namespace>::for_each_user lib=syslib module=syslib
System call failed. Error 3 (No such process) in execution of system call 'getpwent' with parameter (), line (143) in file (syuxcgroup.cpp), stack trace: iaxxejsctl.cpp: 272: EJS_ControllerImpl::executeScript()
iaxxejsbas.hpp: 450: EJS_Base::dispatchFunctionCall()
iaxxejsexp.cpp: 178: EJS_Installer::invokeModuleCall()
syxxbuser.cpp: 242: *** syslib entry point CSyUser::isMember(const iastring & 'sapinst') const ***
syuxcuser.cpp: 664: bool CSyUserImpl::isMember(const iastring & sName) const
syuxcgroup.cpp: 404: PSyAccountIterator CSyGroupImpl('212')::getMembers() const
syuxcgroup.cpp: 102: <anonymous namespace>::for_each_user
INFO       2011-11-23 09:10:51.439 [syuxcaccmg.cpp:237]
           bool CSyAccountMgtImpl::isExisting(ISyAccountMgt::eAccountType accountType, iastring sName)
           lib=syslib module=syslib
Account sapadm already exists.
INFO       2011-11-23 09:10:51.449 [syuxcaccmg.cpp:305]
           bool CSyAccountMgtImpl::isExisting(ISyAccountMgt::eAccountType accountType, iastring sName)
           lib=syslib module=syslib
Account 206 already exists.
INFO       2011-11-23 09:10:53.189 [syuxcpath.cpp:371]
           CSyPath::createFile() lib=syslib module=syslib
Creating file /tmp/sapinst_instdir/SMD_NW711/LM/INST/services.SAPtmp.
WARNING[E] 2011-11-23 09:10:54.72 [syxxc_services_entry.cpp:286]
           CSyServicesEntryParser::parsePort() const lib=syslib module=syslib
FSL-03009 Unexpected token in /etc/services entry 'x11                  6000-6063/tcp # X Window System' at line 7633, column 7: Conversion of port number string to integer failed.
WARNING[E] 2011-11-23 09:10:54.73 [syxxc_services_entry.cpp:286]
           CSyServicesEntryParser::parsePort() const lib=syslib module=syslib
FSL-03009 Unexpected token in /etc/services entry 'x11                  6000-6063/udp # X Window System' at line 7634, column 7: Conversion of port number string to integer failed.
WARNING[E] 2011-11-23 09:10:54.91 [syxxc_services_entry.cpp:286]
           CSyServicesEntryParser::parsePort() const lib=syslib module=syslib
FSL-03009 Unexpected token in /etc/services entry 'ircu                        6665-6669/tcp   # IRCU' at line 7809, column 7: Conversion of port number string to integer failed.
WARNING[E] 2011-11-23 09:10:54.91 [syxxc_services_entry.cpp:286]
           CSyServicesEntryParser::parsePort() const lib=syslib module=syslib
FSL-03009 Unexpected token in /etc/services entry 'ircu                        6665-6669/udp   # IRCU' at line 7810, column 7: Conversion of port number string to integer failed.
INFO       2011-11-23 09:10:54.521 [syuxccuren.cpp:1068]
INFO       2011-11-23 09:11:36.615
           CJSlibModule::writeInfo_impl()
Output of /tmp/sapinst_exe.10617084.1322057387/SAPCAR -x -v -i -R ./hostagent -f /sapinst_sm/smd/SMD711_K_UI_AIX_PPC64/DBINDEP/SAPHOSTAGENT.SAR,:
SAPCAR: processing archive /sapinst_sm/smd/SMD711_K_UI_AIX_PPC64/DBINDEP/SAPHOSTAGENT.SAR (version 2.01)
x hostagent.lst
x hostagent.mf
x hostexecstart
x installsapinit.sh
x ldappasswd
x ldapreg
x librfccm.o
WARNING[E] 2011-11-23 09:11:36.632
           CJSlibModule::writeError_impl()
MUT-03010 Execution of the command "/tmp/sapinst_exe.10617084.1322057387/SAPCAR -x -v -i -R ./hostagent -f /sapinst_sm/smd/SMD711_K_UI_AIX_PPC64/DBINDEP/SAPHOSTAGENT.SAR," finished with status TST_ERROR.
WARNING[E] 2011-11-23 09:11:36.647
           CJSlibModule::writeError_impl()
MUT-03010 Execution of the command "/tmp/sapinst_exe.10617084.1322057387/SAPCAR -x -v -i -R ./hostagent -f /sapinst_sm/smd/SMD711_K_UI_AIX_PPC64/DBINDEP/SAPHOSTAGENT.SAR," finished with status TST_ERROR.
WARNING    2011-11-23 09:11:36.887 [syixcsyinf.cpp:572]
           <anonymous-namespace>::runLsattr lib=syslib module=syslib
Could not run /usr/sbin/lsattr -l aio0 -E -O successfully. Either the return code was != 0 or the process terminated abnormally.
ERROR      2011-11-23 09:11:37.26 [sixxcstepexecute.cpp:969]
FCO-00011 The step unpack with step key |NW_SAPHostAgent|ind|ind|ind|ind|0|0|unpack was executed with status ERROR .
WARNING    2011-11-23 09:11:37.106 [iaxxejshlp.cpp:150]
Could not get property IDs of the JavaScript object.
ERROR      2011-11-23 09:11:37.107 [iaxxejsctl.cpp:492]
FJS-00010 Could not get value for property .
WARNING    2011-11-23 09:11:37.400 [syixcsyinf.cpp:572]
           <anonymous-namespace>::runLsattr lib=syslib module=syslib
Could not run /usr/sbin/lsattr -l aio0 -E -O successfully. Either the return code was != 0 or the process terminated abnormally.
Any idea on the above error?

Error during Managed system setup "Wilyhost Agent" type

Hello All,
Managed system setup finished with one error. Iam using this for selfmonitoring (solman itself as managed system)
Error msg as follows.
0 Wilyhost Agent(s) from host inbbssun02 are connected to the EM.
Wilyhost Agent configuration finished without errors, but on Enterprise Manager (TDCTBI.india.tcs.com:6001) no Wilyhost Agent was detected from host inbbssun02. Please check the log file jvm_smdagent.out whether the Wilyhost Agent could connect to the Enterprise Manager. If the Enterprise Manager configuration has been changed recently please restart the SMD Agent on OS level.
I checked jvm_SMDAgent.out. and log as follows.
/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Introscope Agent Release 8.0.2.0 (Build 470970)
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Using Java VM version "Java HotSpot(TM) 64-Bit Server VM 1.4.2_20-rev" from S
un Microsystems Inc.
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Trying to load agent profile based on system property "com.wily.introscope.ag
entProfile"
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Trying to load file from /usr/sap/SMD/J98/SMDAgent/applications.config/com.sa
p.smd.agent.application.wilyhost/IntroscopeSapAgent.profile
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Loaded file from /usr/sap/SMD/J98/SMDAgent/applications.config/com.sap.smd.ag
ent.application.wilyhost/IntroscopeSapAgent.profile
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Agent Metric Aging is turned off
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Agent Metric Aging: property introscope.agent.metricAging.heartbeatInterval i
s set to 1800
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Agent Metric Aging: property introscope.agent.metricAging.dataChunk is set to
500
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Agent Metric Aging: property introscope.agent.metricAging.numberTimeslices is
set to 3000
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Looking for agent profile property "introscope.agent.extensions.directory" to
locate the extensions directory.
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] The agent extensions directory /usr/sap/SMD/J98/SMDAgent/applications.config/
com.sap.smd.agent.application.wilyhost/ext was successfully located
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Introscope Agent startup complete.
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] The Agent will attempt to determine its name.
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Using the Agent name "SAP HostAgent J98" based on the value of the System Pro
perty "com.wily.introscope.agent.agentName".
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent] Initial agent name set to SAP HostAgent J98
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent.Isengard] Initiating connection attempts to the Introscope Enterprise Manager.
1/06/10 02:55:29 PM IST [INFO] [IntroscopeAgent.Isengard] The Agent reconnection delay is set to 15 second(s).
1/06/10 02:55:30 PM IST [INFO] [IntroscopeAgent] Started Error Reporting service
[p4://inbbssun02:50004] Agent ready.
1/06/10 02:55:34 PM IST [INFO] [IntroscopeAgent.IsengardServerConnectionManager] Connected Agent to the Introscope Enterprise
Manager at TDCTBI.india.tcs.com:6001,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory. Host = "inbbssun02", Proce
ss = "SAP HostAgent Process", Agent Name = "SAP HostAgent J98".
Is there any seperate setting for wilyhost agent connection to EM ?
Regards,
Shyam

I have restarted the agent at OS level and it appears in the Agent Admin page.
I then re-ran the Managed System Config for this system and receive the same error.
I have looked at the jvm_smdagent.out file on the wilyhost and found the following errors
1/11/10 05:37:02 AM CET [INFO] [IntroscopeAgent] Looking for agent profile property "introscope.agent.extensions.directory" to locate the extensions directory.
1/11/10 05:37:02 AM CET [INFO] [IntroscopeAgent] The agent extension property "introscope.agent.extensions.directory" is not set. No extensions will be loaded.
1/11/10 05:37:02 AM CET [INFO] [IntroscopeAgent] Introscope Agent startup complete.
1/19/10 12:34:08 PM CET [WARN] [IntroscopeAgent.IsengardServerConnectionManager] The Introscope Agent is sending data to the Introscope Enterprise Manager too slowly. Keeping the connection alive.
The agent on the solution manager box is version 7.0 and the version od the agent on the PI box is 7.11
Regards
Stephen

Configuration Check Error in Managed System Configuration

Hi dear experts,
I come across a problem as the screenshot shows blew:
I check some relevant information, but no issues found:
1.
DEWDFLSSC5062:/usr/sap/hostctrl/exe # ./saphostexec -status
saphostexec running (pid = 7094)
sapstartsrv running (pid = 7097)
10:46:34 24.06.2014 LOG: Using PerfDir (DIR_PERF) = /usr/sap/tmp
saposcol running (pid = 7130)
DEWDFLSSC5062:/usr/sap/hostctrl/exe # cat host_profile
SAPSYSTEMNAME = SAP
SAPSYSTEM = 99
service/porttypes = SAPHostControl SAPOscol SAPCCMS
DIR_LIBRARY = /usr/sap/hostctrl/exe
DIR_EXECUTABLE = /usr/sap/hostctrl/exe
DIR_PROFILE = /usr/sap/hostctrl/exe
DIR_GLOBAL = /usr/sap/hostctrl/exe
DIR_INSTANCE = /usr/sap/hostctrl/exe
DIR_HOME = /usr/sap/hostctrl/work
service/admin_users = daaadm
service/logfile_000 = /tmp/s
service/logfile_001 = /usr/sap/DAA/SMDA97/SMDAgent/log/smdagent_trace*.trc
service/logfile_002 = /usr/sap/DAA/SMDA97/SMDAgent/log/smdagent_trace.*.trc
service/logfile_003 = /usr/sap/DAA/SMDA97/SMDAgent/log/smdagent_trace.trc
And the version of hostagent is up-to-date.
2.The URL
- http://<SMDhost>:1128/SAPOscol/?wsdl
- http://<SMDhost>:1128/SAPHostControl/?wsdl
can be accessed.
3.The step 3 in managed systems configuration is executed successfully.
4.I have even uninstalled and re-installed the SMD and hostagent, and change the alert_timeout parameter in T-code DMD, but the issue insisted.
5.Only a few SMDs in my landscape, so I think the parameter MaxThreadCount, InitialThreadCount, MinThreadCount should be no problem.
Now I have no idea how to proceed, please give me some advice, thank you in advance.
Best Regards,
Pany Pan

Hi Pany
Kindly check the below two sapnote
1935653 - Error "A timeout occured during the execution of the OS Command Console" when performing a Managed System Configuration - Solution Manager 7.1
1865122 - Solution Manager 7.10 Configuration Check errors : "A timeout occured during the execution of the OS Command Console" "An unexpected error occured"
Moreover , you need to check/verify/maintain the parameter in configtool
ThreadManager -> MaxThreadCount
Total number of Diagnostics Agents * 2 + 50
1250
ThreadManager -> InitialThreadCount
Total number of Diagnostics Agents * 1.5
900
ThreadManager -> MinThreadCount
Total number of Diagnostics Agents
600
ConnectionManipulator -> maxSoTimeOutConnections
Total number of Diagnostics Agents * 1.35
810
ConnectionManipulator -> MaxParallelUsers
Total number of Diagnostics Agents + 50
650
In Diagnostics Agent Troubleshooting - SAP Solution Manager Setup - SCN Wiki
guide check the section Required Solution Manager Java Stack Settings (Scalability)
I face the same issue , which got resolved by maintaining the above parameters, maxthreadCount,
minthreadcount , maxSoTimeOutConnections.
With Regards
Ashutosh Chaturvedi

Error in Managed system configuration.

Hi Folks,
In Solman 7.1 i am configuring my Java system in managed system configuration on the last phase of configuration which is "Check Configuration" i got the below error...
Can any one guide me on this....
I installed the Diagnostic agent as well as willy inter scope.
Regards,
Anil.

check the note which describes your problem
1776959 - Solution Manager 7.1 Manged System configuration. Error: Timezone from managed system could not be retrieved: Timezone of J2EE Engine (GMT+01:00) does not match the timezone of the diagnostics agent (Europe/Berlin)
Resolution
Open the instance.properties file of the J2EE Engine on the managed system
Locate the parameter "-Duser.timezone=" and its value
If the -Duser.timezone is not set the JVM uses GMT
Set the -Duser.timezone parameter in the JVM of the SMD Agent. If there was no "-Duser.timezone in the J2EE's instance.properties file use the timezone that was indicated in the error message e.g. GMT+01:00 (from the above error message, this might differ on your environment) To do this:
Locate the smd.properties file (for newer agents the files is called: smdagent.properties)
The path is: .../usr/sap/<DiagnosticAgentSID>/SMDA<SYSNumber>/SMDAgent/smdagent.properties
The -Duser.timezone= parameter of the Diagnostics Agent and the SAP J2EE engine need to be set to the same timezone. That means the string needs to be the same for both parameters
e.g.
If the -Duser.timezone= parameter of the J2EE engine is set to -Duser.timezone="GMT+01:00"
set the Diagnostics Agent parameter to:
smdagent.javaParameters=-DP4ClassLoad=P4Connection -Xmx256m -Xms256m -Duser.timezone="GMT+01:00"
Restart the Agent
Re-run the "Configuration Check" in the "Managed System Configuration"
Please make sure that the time zone configuration is correct according to the SAP recommendations: http://wiki.sdn.sap.com/wiki/display/Basis/Timezone+changes+best+practices

SOLMAN_SETUP Wizard - Error on Managed System Configuration

Hi all,
I've installed SAP Solution Manager 7.0 EHP1 (Stack 19) on linux-oracle.
After I start the configuration with SOLMAN_SETUP tcode.
The "Initial Configuration" and the "Basic Configuration" phases are termined with success.
In the third phase "Managed System Configuration", I try to connect itself on client 001 but when I try to generate the RFC Connection I received an error message on wizard when the system create the "Back RFC Destination". If I check this RFC on SM59 tcode it works!!!! I don't understand why I received the error message during the wizard.
Then on "Check Prerequisites" I execute the "Diagnostic Prerequisites" phase and I received 2 error messages:
a) The Introscope Enterprise Manager configuration cannot be loaded. Details:
java.sql.SQLException: All configured Enterprise Managers are offline - check configuration. at com.sap.sup.admin.wily.jdbc.EMOverview.getQueryEMgrs(EMOverview.java:251) at com.sap.sup.admin.wily.jdbc.EMOverview.populateAgentCache(EMOverview.java:415) at com.sap.sup.admin.wily.jdbc.EMOverview.checkAgentCache(EMOverview.java:461) at com.sap.sup.admin.wily.jdbc.EMOverview.getAllEMgrs(EMOverview.java:220) at com.sap.sup.admin.selfcheck.checks.wily.em.EmJdbcCheck.process(EmJdbcCheck.java:32) at com.sap.sup.admin.selfcheck.fwk.check.AbstractCheck.processImpl(AbstractCheck.java:165) at sun.reflect.GeneratedMethodAccessor342.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:62) at java.lang.reflect.Method.invoke(Method.java:391) at com.sap.smd.server.exec.asio.AsioInvocationHandler$1.call(AsioInvocationHandler.java:87) at com.sap.smd.server.util.concurrent.FutureResult$1.run(FutureResult.java:90) at com.sap.smd.server.exec.asio.AsioInvocationHandler$AsioRunner.run(AsioInvocationHandler.java:274) at com.sap.smd.server.exec.TaskRunner.run(TaskRunner.java:45) at com.sap.smd.server.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:781) at java.lang.Thread.run(Thread.java:770)
b) The RFC Read Destination is not available for connection to Satellite System (RC=2). Details:
Please check SAP Note 1106900
I find The RFC Read Destination on SM59 tcode and it works if I try to "Connection Test".
Could you please help me to check the two errors??
Thanks in advanced
Moreno

Some more info when I tried to run the setup wizard again.
Step Wilyhost Agent Details
Setup Exception: Empty or no Wily EM host retrieved from secured global config! Going on with "localhost".
Setup Exception: No Wily EM port was passed by SetupWizard! Going on with port 6001 instead.
Created destination XXX|hostname_xxx_01
Created action xxx -XXX AbapSystem
Created action xxx|hostname_xxx_01 - XXX|hostname_xxx_01 AbapInstance
Created 2 action(s).
Retrieving list of Enterprise Managers failed: All configured Enterprise Managers are offline - check configuration.
Exceptions
java.sql.SQLException: All configured Enterprise Managers are offline - check configuration.
at com.sap.sup.admin.wily.jdbc.EMOverview.getQueryEMgrs(EMOverview.java:251)
at com.sap.sup.admin.wily.jdbc.EMOverview.populateAgentCache(EMOverview.java:415)
at com.sap.sup.admin.wily.jdbc.EMOverview.checkAgentCache(EMOverview.java:461)
at com.sap.sup.admin.wily.jdbc.EMOverview.getAgentEMgrs(EMOverview.java:269)
at com.sap.sup.admin.wily.hostagent.Setup.emCanBeAccessed(Setup.java:440)
at com.sap.sup.admin.wily.hostagent.Setup.executeSetup(Setup.java:87)
at com.sap.sup.admin.setup.AppCfgTasks.configureEPAgent(AppCfgTasks.java:110)
at com.sap.sup.admin.setup.SetupStep.runExec(SetupStep.java:416)
at com.sap.sup.admin.setup.SetupStep.execute(SetupStep.java:328)
at com.sap.smd.agent.plugins.remotesetup.SapInstance.setup(SapInstance.java:545)
at com.sap.sup.admin.setup.SapCluster.setup(SapCluster.java:1680)
at com.sap.sup.admin.setup.SapCluster.access$000(SapCluster.java:35)
at com.sap.sup.admin.setup.SapCluster$SetupRunner.run(SapCluster.java:1950)
at java.lang.Thread.run(Thread.java:571)
hostname is the hostname of the system, i removed it.
xxx is the solution manager sid.

Solman_admin password changes results in errors during managed system setup

Hello all,
I am trying to get Solman 4.0 EHP 1 to work, but get numberous problems.
Currently I have 6 messages at SAP, but no solution yet.
Situation:
Solman 4.0
SAP_BASIS     701     0003
SAP_ABA     701     0003
ST-PI     2008_1_700     0000
PI_BASIS     701     0003
SAP_BW     701     0003
CRMUIF     500     0001
SAP_AP     700     0014
BBPCRM     500     0013
CPRXRPM     400     0014
BI_CONT     704     0002
ST     400     0019
ST-A/PI     01L_CRM570     0000
ST-ICO     150_700     0016
ST-SER     701_2008_2     0002
So, it is uptodate.
The problem:
Changing the solman_admin password results in errors during connecting a managed system.
In the inital setup the solman_admin is created with a pasword.
After the basic setup I setup some managed systems.
In the meantime I had to change the password of solman_admin
I am logged in with solman_admin and do solman_setup to setup the managed system.
During the setup a process tries to logon back to the solman using solman_admin and the incorrect password.
This is the logging:
Step SSO Details
Found SID for SSO ACL entry : MSD
Found login.ticket_client for SSO ACL entry : 000
The Read entry permission on TicketKeystore/SAPLogonTicketKeypair-cert was given to sap.com/tcwebadministratorsolmandiag/servlet_jsp/smd/root/WEB-INF/lib/SetupLib.jar
The TicketKeystore/SAPLogonTicketKeypair-cert was succesfully read (823 bytes)
A failure occured while connecting to ABAP stack on localhost sys=70 client=300 user=SOLMAN_ADMIN
!! Exception : Password logon no longer possible - too many failed attempts
A failure occured while importing ABAP SSO ticket certificate in ABAP stack
!! Exception : java.lang.NullPointerException
Java SSO ticket certificate of MSD was imported in ABAP PSE of kswv024.mob.local (client 300)
The Java SSO ticket certificate was successfully imported in ABAP System PSE, and the ACL updated accordingly (SID=MSD LoginTicketClient=000)
Anyone else has this problem?
gr
Sander

Just for clarification it's Solman 7.0 EHP1 correct?
Also you may want to unlock the following user:
localhost sys=70 client=300 user=SOLMAN_ADMIN
Then if you navigate (in solution manager) to TCode solman_workcenter -> "Root Cause Analysis" tab ->"Agent Administration" menu item on the left -> "Applications Configuration" tab -> under the Agent Applications - Configuration menu on the left select "com.sap.smd.agent.application.global.configuration" -> Change the "Scope" drop down in the frame to the right to the SMD agent that you are using for "localhost sys=70 client=300" -> Click the "edit" button to the right of the Scope drop down box -> now find the entry below that lists "SOLMAN_ADMIN" as the user and find the corresponding password entry and update it with the new password that you changed it to -> click save and try the managed setup again.
Hope this helps, please let me know and we can go from there.

Link SAP PI 7.3 to SolMan 7.1 - error during managed system configuration

All,
I installed my diagnostics agent twice with different options:
- Direct P4 connection via Java EE Dispatcher Node with port 5xx04
- P4 connection via SCS message server with port 81xx
In both cases I get an error during the managed system configuration of SAP PI 7.3: Remote error : Connection to P4 port of managed system failed.
I'm a bit confused with the step Enter System Parameters. In the Java parameters section, I can only enter port 39xx. if not, I get an error.
Also, I marked and unmarked the option concerning the ABAP user store, but the error persists.
Please advice.
Thanks a lot.

Hi Allam,
I checked the KBA and I think now, I have the correct HTTP port.
The error I now get is S:CL_DIAGSTP_MESSAGE:483
When I take the next step, Configure Automatically, I get this error during the Byte Code Adapter Installation phase when I open the Java URL stated in the navigation column:
DIAG_WILY_MSG:157:S - com.sap.smdagent.vmmanager.VMManagerP4Exception: com.sap.smdagent.plugins.connectors.p4.exceptions.P4AuthorizationException: Access is denied to SAP System sid: check the connection credentials.More details about the error in agent 'sappi' log file (SMDAgentApplication.X.log).; nested exception is:
com.sap.engine.services.security.exceptions.BaseLoginException: Error during authentication. For more information see the remote server traces.
Any idea?
Thanks.

SMD - Diagnostic Administration -- Managed Systems takes long time

Hi All,
On SMD administration URL , http://system:50000/smd ---> Diagnostics administration ---> Agent Administration --> managed systems takes very long time.
Sometimes it never ends and keep on going...
CPU utilization is also very high...
Have anyone encountered this issue ?
We are using Solman 7.00 on Solaris, DB is oracle.
Thanks!

Reply with ur System Technical Note,
find below DOCS for Solman System Technical Config,
https://websmp103.sap-ag.de/~sapdownload/011000358700000255562007E/Sizing_Guide_SM_70_SP15.pdf
https://websmp103.sap-ag.de/~form/sapnet?_FRAME=OBJECT&_HIER_KEY=501100035870000015092&_HIER_KEY=601100035870000179416&_HIER_KEY=601100035870000179443&_HIER_KEY=701100035871000457214&#HOME
Basically SMD is mostly dependant on J2ee Heap and Abap Configuration. Set up the required Heap and T-Code ST02 paramaters properly and call the SMD again.
Regards
Srikanth Mandalapu
Edited by: srikanth mandalapu on Oct 10, 2008 12:11 AM

Managed System SLM~ABAP is not configured (Step 10: Configuration Check)

When I try to spend the last procedure "Configuration Check" (item 10 - Managed System Configuration) I get here is only an error message
The definition of Technical System 'SLM~JAVA' is not correct: 'SLM~JAVA': Operating System 'Linux~2.6.32-358.23.2.' of Host 'sslm' must have at least one Software Component Version
'SLM~JAVA': Operating System 'Linux~2.6.32-358.23.2.' of Host 'sslm' must have at least one Software Component Version
Outside Discovery issue: refer to SAP Note 1611483
Managed systems setup | Managed System Definition Status (post setup) | SYSTEM =SLM~JAVA
What a way such settings: Managed systems setup | Managed System Definition Status?
I probably know only the tab SapSolution Manager: Configuration-> Managed system configuration-> Technical systems, but there make these settings is not possible.
How do I resolve this is "must have at least one Software Component Version"?
ps said note (1611483) has been done, but apparently no effect brought

Hi Michael,
Can you please check below :
Correct Software Component version is displayed in LMDB -> Host - > Tab Installed Software.
Managed System setup -> Assign Diagnostic agent -> Check SAP Host agents (to enusre agent is running)
You may restart both Diagnostic and Host agent and check again after few minutes if data is updated.
Additionally please check below SAP notes which might help resolve the issue :
1890035 - Error "Host 'hostname' must have at least one installed Technical system" during the step 'Check Prerequisites'
1799138 - Solution Manager configuration check returns "The definition of Technical System '{SID}~{STACK}' is not correct: '{SID}~{STACK}' : Operating System '{OSName}' of Host '{hostname}' must have at least one Software Component Version"
Hope this helps.
Thanks & Regards,
Nisha

Error on load: System.IO.IOException: The process cannot access the file : error in event viewer when users want to view documents from this third party deployed scan solution

Error on load: System.IO.IOException: The process cannot access the file
'\\server1\SCANSHARED\.pdf' because it is being used by another process.
   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy)
   at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy)
   at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share)
   at System.IO.File.WriteAllBytes(String path, Byte[] bytes)
   at abc.Scan.Layouts.ICC.Scan.View.Page_Load(Object sender, EventArgs e)
I faced this error in event viewer when users want to view documents from this third party deployed scan solution
here I have two WFS servers and they configured with load balancing in F5 .
when I enable both servers in F5 I receive this error messages in 2nd server,
when users want to view documents
adil

Do you have antiVirus installed on the sharepoint servers?
These folders may have to be excluded from antivirus scanning when you use file-level antivirus software in SharePoint. If these folders are not excluded, you may see unexpected behavior. For example, you may receive "access denied" error messages when files
are uploaded.
Please follow this KB and exclude the folders from Scanning.
http://support.microsoft.com/kb/952167
Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

Logical port error when accessing e-recruiting web pages

Hi,
We are trying to set up our e-recruiting 3.0 and web dispatcher systems. We were receiving an error in our e-recruiting system in transaction SM20 that states Logon Failed (Reason=34, Type=H). The user is SAPSYS for client 000. The system was attempting to log on to our web dispatcher system. SAP suggested creating an entry in SM30, table VUSREXTID, mapping the External ID to our web dispatcher system. This entry helped in that we are not receiving the above error message anymore. However, when we attempt to access the web pages we are receiving the error Name of logical port &lp_name& is invalid. Prior to adding this entry we were able to access the logon page by entering the following url using an external alias (ex. https://recruiting.mphi.org/internal). Recruiting.mphi.org is our web dispatcher system. We do not want our e-recruiting system to be accessible from the outside. We want everything to go through our web dispatcher. Has anyone had a similar issue setting these up?
Thanks!
Heather

Hello Heather,
I am no specialist in network infrastructure but i remember a customer setting up a web dispüatcher szenario. I also encountered this &lp_name& error from time to time during my work.
The error points towards damaged urls and the customer also encountered such problems when setting up the web dispatcher landscape. Sometimes the last parameter of the URL was ignored or lost. Sometimes the web dispatcher transformed the URL including the parameters. But as parameters are case sensitive transforming them to upper/lower result in errors as the system no longer recognizes them.
Perhaps you can check the URL with which the web dispatcher is calling the sap server to find out if it does any funny things w/ the links.
Best Regards
Roman Weise

SMD Error in managed system type PI 7.1 EHP1 Step Logical Ports error

Similar Messages

Maybe you are looking for