Error While Loggin in Solution Manager 3.2

Hello there!!
I have HP-UX, Oracle 9i,Sol MAn 3.2
I have installed Sol Man3.2 on my Dev Server under instance SM1 and system number 00
now when i add this system on my SAP Logon
and click on the logon button
i get error as connection refused.
details error is mentioned below.
I have started the Instance SM1 and it is showing instance started.
Component:NI
Release:640
Version:37
Module: nixxi_r.cpp
Line:8716
Method: NiPConnect2
return Code -10
System Call: SiPeekPendConn
Error No 10061
Error text WSAECONNREFUSED: Connection refused
kindly help
saurabh

Hi Saurabh,
sorry, I am not able to support you in finding the cause for the connection problem.
Anyway, my recommendation:
- Delete the SolMan 3.2 installation
- Install Solman 4.0
- Apply all Support Packages
- perform the configuration on 4.0 according the IMG
Configuring SolMan 3.2 is wasted time, if it has not been used in the past. SolMan 4.0 supports implementation / upgrade from/to SAP ERP 2004.
An upgrade in the future costs much more time and money, then to reinstall 4.0 now.
Deleting SolMan 3.2 and reinstall SolMan 4.0, this will only 2 extra days. Upgrade takes about 4-10 days.
Best regards,
Ruediger Stoecker
Message was edited by: Ruediger Stoecker
Spelling mistakes corrected, more information on days.

Similar Messages

I got errors while installation of solution manager 4.0 sr2

I faced the errors below while installing Solution Manager 4.0 sr2.
How can I solve these problems?
Thanks.
ERROR 2007-03-13 17:30:12
FSL-00001 System call failed. Error 13 (Permission denied) in execution of system call 'openU' with parameter (/opt/cdler/CD2/IM_HPUX_PARISC/COMMON/INSTALL/JDBCCONNECT.JAR, O_RDONLY), line (368) in file (syuxcfile.cpp).
ERROR 2007-03-13 17:30:12
FSL-02015 Node /opt/cdler/CD2/IM_HPUX_PARISC/COMMON/INSTALL/JDBCCONNECT.JAR does not exist.
ERROR 2007-03-13 17:30:12
MUT-03025 Caught ESyException in Modulecall: ESAPinstException: error text undefined.
ERROR 2007-03-13 17:30:12
FCO-00011 The step copyScripts with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_Unpack|ind|ind|ind|ind|8|0|copyScripts was executed with status ERROR .

Hello Cemil,
The errors you are recieving are most likely user or permissions
related.
Can you please verify that there are 777 permissions on the
installation directories? Also are you installing as User Root?
Are you installing from an NFS Mount or network drive? If so it could be
possible that the user does not have enough permissions on this. If
so I recommend copying the installation files to a local directory and
retrying the installation from there.
Best regards,
Dolores

Error while upgrading to Solution Manager EHP1 from 3.2

Hi All,
I am trying to upgrade the solution manager3.2 to EHP1.
OS: Linux RHEL 4
DB: Oracle 10.2.0.2
I am in the Prepare phase.....
When I try to run the JPREPARE command( /dump/smrtest/SMR_UP/51036444/JPREPARE) I get the following error message
An unrecoverable error has occured:
Could not execute dialog SelectModulDialog. See previous messages.
Input output exception while processing dialog SelectModulDialog. See previous messages.
Could not send dialog message. See previous messages.
Could not bind to port 6240.
java.net.BindException: Address already in use
Can anyone help asap?

> I am in the Prepare phase.....
> When I try to run the JPREPARE command( /dump/smrtest/SMR_UP/51036444/JPREPARE) I get the following error message
You have a Java instance installed on 3.2?
> An unrecoverable error has occured:
>
> Could not execute dialog SelectModulDialog. See previous messages.
> Input output exception while processing dialog SelectModulDialog. See previous messages.
> Could not send dialog message. See previous messages.
> Could not bind to port 6240.
> java.net.BindException: Address already in use
Read the documentation about SAPJup - you have to change the default port (because most likely your ABAP part uses that one).
Markus

Error in Import Java Dump phase while installing SAP solution Manager 7.1

Hi,
While installing SAP solution manager 7.1 I am getting the below error during the phase "Import Java Dump".
An error occurred while processing option SAP Solution Manager 7.1 > SAP Systems > MS SQL Server > Central System > Central System( Last error reported by the step : Execution of JLoad tool 'C:\j2sdk1.4.2_17-x64\bin\java.exe -classpath "C:\Program Files\sapinst_instdir\SOLMAN71\SYSTEM\MSS\CENTRAL\AS\install\sharedlib\launcher.jar" -showversion -Xmx1024m com.sap.engine.offline.OfflineToolStart com.sap.inst.jload.Jload "C:/Program Files/sapinst_instdir/SOLMAN71/SYSTEM/MSS/CENTRAL/AS/install/lib/iaik_jce.jar;C:/Program Files/sapinst_instdir/SOLMAN71/SYSTEM/MSS/CENTRAL/AS/install/sharedlib;D:/usr/sap/SPT/SYS/exe/uc/NTAMD64/mssjdbc/sqljdbc.jar" -sec SPT,jdbc/pool/SPT,
smn/sapmnt/SPT/SYS/global/security/data/SecStore.properties,
smn/sapmnt/SPT/SYS/global/security/data/SecStore.key -dataDir "D:/SAP SOLMAN/Java Components/51040039\DATA_UNITS\SOLMAN_JAVA_EXPORT_JDMP" -job "C:\Program Files\sapinst_instdir\SOLMAN71\SYSTEM\MSS\CENTRAL\AS\IMPORT.XML" -log jload.log' aborts with return code 1. SOLUTION: Check 'jload.log' and 'C:/Program Files/sapinst_instdir/SOLMAN71/SYSTEM/MSS/CENTRAL/AS/jload.java.log' for more information.
JLOAD.JAVA log details below
java version "1.4.2_17"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_17-b06)
Java HotSpot(TM) 64-Bit Server VM (build 1.4.2_17-b06, mixed mode)
Jload R 7.12 V 0 A 0
Jload -sec SPT,jdbc/pool/SPT,
smn/sapmnt/SPT/SYS/global/security/data/SecStore.properties,
smn/sapmnt/SPT/SYS/global/security/data/SecStore.key -dataDir D:/SAP SOLMAN/Java Components/51040039\DATA_UNITS\SOLMAN_JAVA_EXPORT_JDMP -job C:\Program Files\sapinst_instdir\SOLMAN71\SYSTEM\MSS\CENTRAL\AS\IMPORT.XML -log jload.log
Connecting to database
Couldn't connect to DB
com.sap.inst.common.exception.DBConnectionException: com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host has failed. java.net.ConnectException: Connection refused: connect
     at com.sap.inst.common.db.DBConnection.connect(DBConnection.java:157)
     at com.sap.inst.jload.Jload.main(Jload.java:222)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host has failed. java.net.ConnectException: Connection refused: connect
     at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(Unknown Source)
     at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(Unknown Source)
     at com.microsoft.sqlserver.jdbc.SQLServerConnection.loginWithoutFailover(Unknown Source)
     at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(Unknown Source)
     at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(Unknown Source)
     at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:215)
     at com.sap.sql.connect.OpenSQLDataSourceImpl.createConnection(OpenSQLDataSourceImpl.java:522)
     at com.sap.sql.connect.OpenSQLDataSourceImpl.getConnection(OpenSQLDataSourceImpl.java:276)
     at com.sap.inst.common.db.DBConnection.connectViaSecureStore(DBConnection.java:111)
     at com.sap.inst.common.db.DBConnection.connect(DBConnection.java:151)
     ... 6 more
An error occured during execution. Please consult SAP note 942766 for first steps on troubleshooting the problem.
I have gone thru with the notes and it didn't help me much.
I have used J2SDK 1.4.2_17 nad JCE_Policy-1.4.2 files.
Please let me know where IO went wrong.
Thanks in advance.
Sai

Hi,
1. Did you select java path (Export CD/DVD) while intsallation? Check once again.
2. Add JAVA_HOME = Java path in environment variable.
3. What is the exact error, you got it, post error here.
Regards,
Srini Nookala

Error in RFC & to Solution Manager System

Hi,
Error in RFC & to Solution Manager System
can anyone tells me why this error occurs???
With regards
kulwinder

FYI
We have just had same issue thaat in certain scenarios with RFC communication BACK to Solution Manager from Satellite system we got the error. We resolved this by looking at the RFC user used in the BACK connection (i.e. SOLMAN<SID>) on the Solution Manager and changing the user type from communications.
Hope this helps someone else, I spent ages digging around for an answer to such a simple fix
Paul

Error while invoking bean "presentation manager":

Hi,
BPEL PM version : 10.1.2.0.2
Scenario : I have a Process1 which tries to access Another Process Process2. Process1 has a PL for a Webservice (WS1) whose end point is Process2's endpoint.
For architectural reason's I need to keep both the processes independent and that's the only way I can call Process2 as I've no control of Process1 and can not modify it except changing the endPoint location for WS1.
First question will this work ? If no then is there another way of doing this ?
If yes then I'm seeing the error message posted below.
Please advice.
<2007-03-08 08:29:30,019> <ERROR> <default.collaxa.cube> <BaseCubeSessionBean::logError> Error while invoking bean "presentation manager": HTML form size is larger than the preset limit: 70
java.lang.IllegalStateException: HTML form size is larger than the preset limit: 70
     at com.collaxa.cube.xml.xsd.xerces.HtmlFormHelper.incInputCount(HtmlFormHelper.java:46)
     at com.collaxa.cube.xml.xsd.xerces.HtmlFormHelper.writeSchemaType(HtmlFormHelper.java:109)
     at com.collaxa.cube.xml.xsd.xerces.HtmlFormHelper.writeElementSimpleType(HtmlFormHelper.java:232)
     at com.collaxa.cube.xml.xsd.xerces.SchemaToForm.writeForm(SchemaToForm.java:137)
     at com.collaxa.cube.xml.xsd.xerces.SchemaToForm.writeChildElementsFromElementDecl(SchemaToForm.java:374)
     at com.collaxa.cube.xml.xsd.xerces.SchemaToForm.writeForm(SchemaToForm.java:165)
     at com.collaxa.cube.xml.xsd.xerces.SchemaToForm.writeChildElementsFromElementDecl(SchemaToForm.java:374)
     at com.collaxa.cube.xml.xsd.xerces.SchemaToForm.writeForm(SchemaToForm.java:165)
     at com.collaxa.cube.xml.xsd.xerces.SchemaToForm.writeChildElementsFromElementDecl(SchemaToForm.java:374)
     at com.collaxa.cube.xml.xsd.xerces.SchemaToForm.writeForm(SchemaToForm.java:165)
     at com.collaxa.cube.xml.xsd.xerces.SchemaToForm.writeChildElementsFromElementDecl(SchemaToForm.java:374)
     at com.collaxa.cube.xml.xsd.xerces.SchemaToForm.writeForm(SchemaToForm.java:165)
     at com.collaxa.cube.xml.xsd.xerces.SchemaToForm.writeChildElementsFromElementDecl(SchemaToForm.java:374)
     at com.collaxa.cube.xml.xsd.xerces.SchemaToForm.writeForm(SchemaToForm.java:165)
     at com.collaxa.cube.xml.xsd.xerces.SchemaToForm.writeChildElementsFromElementDecl(SchemaToForm.java:374)
     at com.collaxa.cube.xml.xsd.xerces.SchemaToForm.writeForm(SchemaToForm.java:165)
     at com.collaxa.cube.xml.xsd.xerces.SchemaToForm.writeChildElementsFromElementDecl(SchemaToForm.java:374)
     at com.collaxa.cube.xml.xsd.xerces.SchemaToForm.writeForm(SchemaToForm.java:165)
     at com.collaxa.cube.xml.xsd.xerces.SchemaToForm.generateForm(SchemaToForm.java:104)
     at com.collaxa.cube.xml.xsd.xerces.WSDLFormHandler.writeForm(WSDLFormHandler.java:138)
     at com.collaxa.cube.xml.xsd.xerces.WSDLFormHandler.writeForm(WSDLFormHandler.java:92)
     at com.collaxa.cube.xml.xsd.xerces.WSDLFormHandler.write(WSDLFormHandler.java:76)
     at com.collaxa.cube.ejb.impl.PresentationManagerBean.getInitiateFormContent(PresentationManagerBean.java:66)
     at IPresentationManagerBean_StatelessSessionBeanWrapper62.getInitiateFormContent(IPresentationManagerBean_StatelessSessionBeanWrapper62.java:81)
     at com.oracle.bpel.client.BPELProcessHandle.getInitiateFormContent(BPELProcessHandle.java:383)
     at ngInitiateForm.jspService(_ngInitiateForm.java:243)
     at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:56)
     at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:350)
     at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:509)
     at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:413)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:824)
     at com.evermind.server.http.ServletRequestDispatcher.include(ServletRequestDispatcher.java:121)
     at com.evermind.server.http.EvermindPageContext.include(EvermindPageContext.java:267)
     at displayProcess.jspService(_displayProcess.java:806)
     at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:56)
     at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:350)
     at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:509)
     at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:413)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:824)
     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:330)
     at com.evermind.server.http.ServletRequestDispatcher.forward(ServletRequestDispatcher.java:222)
     at com.collaxa.cube.fe.DomainFilter.doFilter(DomainFilter.java:152)
     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:663)
     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:330)
     at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:830)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:285)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:126)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)
     at java.lang.Thread.run(Thread.java:534)

Another thing I want to mention is if I run my process2 independently it works fine. So my guess is that the way I'm calling Process2 from Process1 maynot be correct. I'm not even sure if this thing will actually work or not.
Process1 has a webservice that has http binding to call an outside servlet. I need to have another layer in between (Process2) that will call the Outside servlet. So it's Process1 calling Process2 and Process2 calling the outside servlet.
My hands are tied that I can't change the webservice in Process1 or modify Process1 directly (I don't own this and it's shipped as standard functionality) which calls the servlet and has http binding. How can I call Process2 from the same binding and what endpoint should I use for my process ?
Any help is highly appreciated.
Thanks,
Megha

Error while starting the OIM managed server in oracle VM

Hi ,
I am getting the following error , while starting the OIM managed server in Oracle VM.
<Jun 14, 2012 4:45:38 AM EDT> <Error> <org.quartz.impl.jdbcjobstore.JobStoreCMT> <BEA-000000> <MisfireHandler: Error handling misfires: Unexpected runtime exception: null
org.quartz.JobPersistenceException: Unexpected runtime exception: null [See nested exception: java.lang.NullPointerException]
at org.quartz.impl.jdbcjobstore.JobStoreSupport.doRecoverMisfires(JobStoreSupport.java:3042)
at org.quartz.impl.jdbcjobstore.JobStoreSupport$MisfireHandler.manage(JobStoreSupport.java:3789)
at org.quartz.impl.jdbcjobstore.JobStoreSupport$MisfireHandler.run(JobStoreSupport.java:3809)
Caused By: java.lang.NullPointerException
at org.quartz.SimpleTrigger.computeNumTimesFiredBetween(SimpleTrigger.java:800)
at org.quartz.SimpleTrigger.updateAfterMisfire(SimpleTrigger.java:514)
at org.quartz.impl.jdbcjobstore.JobStoreSupport.doUpdateOfMisfiredTrigger(JobStoreSupport.java:944)
at org.quartz.impl.jdbcjobstore.JobStoreSupport.recoverMisfiredJobs(JobStoreSupport.java:898)
at org.quartz.impl.jdbcjobstore.JobStoreSupport.doRecoverMisfires(JobStoreSupport.java:3029)
at org.quartz.impl.jdbcjobstore.JobStoreSupport$MisfireHandler.manage(JobStoreSupport.java:3789)
at org.quartz.impl.jdbcjobstore.JobStoreSupport$MisfireHandler.run(JobStoreSupport.java:3809)
>
How to resolve this issue.Any one please suggest me , i am in a big trouble ...
Thanks in advance ..
-Deena.

Hi P.k,
The table QRTZ92_TRIGGERS is there in the database.But while trying to run this command (UPDATE QRTZ92_TRIGGERS set NEXT_FIRE_TIME=1 where NEXT_FIRE_TIME < 0)in database i am getting the table or view does not exist.
What is GTC resource?
OIM version - 11.1.1.5.0.
-Deena.

Error while invoking bean "domain manager": Error deploying BPEL suitcase.

My issue is the following, when I use wsa adressing in my bpel process such as:
xmlns:ns2="http://schemas.xmlsoap.org/ws/2003/03/addressing"
and create a variable based on this schema
<variable name="partnerReference" element="ns2:EndpointReference"/>
I can compile and generate the jar file. But when I deploy this file in my console I get the following error:
Module     oracle.soa.bpel.system
Host     brux0304
Host IP Address     10.18.80.129
User     weblogic
Thread ID     [ACTIVE].ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'
Message     Error while invoking bean "domain manager": Error deploying BPEL suitcase.
Supplemental Detail     error while attempting to deploy the BPEL component file "/soa/oracle/Middleware/user_projects/domains/base_domain/servers/soa_server1/dc/soa_f7fc611b-51eb-4910-a671-d2bb5c5c31d0"; the exception reported is: java.lang.Exception: BPEL 1.1 compilation failed
This error contained an exception thrown by the underlying deployment module.
Verify the exception trace in the log (with logging level set to debug mode).
ORABPEL-05250
Error deploying BPEL suitcase.
error while attempting to deploy the BPEL component file "/soa/oracle/Middleware/user_projects/domains/base_domain/servers/soa_server1/dc/soa_f7fc611b-51eb-4910-a671-d2bb5c5c31d0"; the exception reported is: java.lang.Exception: BPEL 1.1 compilation failed
This error contained an exception thrown by the underlying deployment module.
Verify the exception trace in the log (with logging level set to debug mode).
at com.collaxa.cube.engine.deployment.DeploymentManager.deployComponent(DeploymentManager.java:197)
at com.collaxa.cube.ejb.impl.CubeServerManagerBean._deployOrLoadComponent(CubeServerManagerBean.java:820)
at com.collaxa.cube.ejb.impl.CubeServerManagerBean.deployComponent(CubeServerManagerBean.java:119)
at com.collaxa.cube.ejb.impl.bpel.BPELServerManagerBean.deployComponent(BPELServerManagerBean.java:88)
at sun.reflect.GeneratedMethodAccessor844.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
at com.bea.core.repackaged.springframework.jee.intercept.MethodInvocationInvocationContext.proceed(MethodInvocationInvocationContext.java:104)
at oracle.security.jps.ee.ejb.JpsAbsInterceptor$1.run(JpsAbsInterceptor.java:94)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413)
at oracle.security.jps.ee.ejb.JpsAbsInterceptor.runJaasMode(JpsAbsInterceptor.java:81)
at oracle.security.jps.ee.ejb.JpsAbsInterceptor.intercept(JpsAbsInterceptor.java:112)
at oracle.security.jps.ee.ejb.JpsInterceptor.intercept(JpsInterceptor.java:105)
at sun.reflect.GeneratedMethodAccessor843.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310)
at com.bea.core.repackaged.springframework.jee.intercept.JeeInterceptorInterceptor.invoke(JeeInterceptorInterceptor.java:69)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.jee.spi.MethodInvocationVisitorImpl.visit(MethodInvocationVisitorImpl.java:37)
at weblogic.ejb.container.injection.EnvironmentInterceptorCallbackImpl.callback(EnvironmentInterceptorCallbackImpl.java:54)
at com.bea.core.repackaged.springframework.jee.spi.EnvironmentInterceptor.invoke(EnvironmentInterceptor.java:50)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at $Proxy281.deployComponent(Unknown Source)
at com.collaxa.cube.ejb.impl.bpel.BPELServerManagerBean_bp05wg_ICubeServerManagerLocalBeanImpl.__WL_invoke(Unknown Source)
at weblogic.ejb.container.internal.SessionLocalMethodInvoker.invoke(SessionLocalMethodInvoker.java:39)
at com.collaxa.cube.ejb.impl.bpel.BPELServerManagerBean_bp05wg_ICubeServerManagerLocalBeanImpl.deployComponent(Unknown Source)
at oracle.fabric.CubeServiceEngine.load(CubeServiceEngine.java:886)
at oracle.fabric.CubeServiceEngine.load(CubeServiceEngine.java:128)
at oracle.integration.platform.blocks.deploy.CompositeDeploymentConnection.deployComponents(CompositeDeploymentConnection.java:242)
at oracle.integration.platform.blocks.deploy.CompositeDeploymentConnection.deploy(CompositeDeploymentConnection.java:93)
at oracle.integration.platform.blocks.deploy.CompositeDeploymentManagerImpl.initDeployment(CompositeDeploymentManagerImpl.java:149)
at oracle.integration.platform.blocks.deploy.CompositeDeploymentManagerImpl.load(CompositeDeploymentManagerImpl.java:62)
at sun.reflect.GeneratedMethodAccessor18895.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
at oracle.integration.platform.blocks.deploy.DeploymentEventPublisher.invoke(DeploymentEventPublisher.java:68)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at $Proxy309.load(Unknown Source)
at oracle.integration.platform.blocks.deploy.StandaloneCompositeDeploymentCoordinatorImpl.coordinateCompositeRedeploy(StandaloneCompositeDeploymentCoordinatorImpl.java:95)
at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.overwriteExistingComposite(BaseDeployProcessor.java:398)
at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deploySARs(BaseDeployProcessor.java:229)
at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.java:161)
at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.java:109)
at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doRedeploy(DeployProcessor.java:101)
at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.process(DeployProcessor.java:81)
at oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerServlet.doPostInsideLoggingSession(CompositeDeployerServlet.java:221)
at oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerServlet.doPost(CompositeDeployerServlet.java:124)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:821)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:27)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413)
at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:94)
at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:161)
at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413)
at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:94)
at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:161)
at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:136)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3715)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
When I remove the namespace and variable it works.
What should be causing that?
Regards,
Luciana

There seems to be some issue with partnerrole definition. Please check CreatePurchaseOrderListEbizProvABCSImplProcess.bpel(line 51): and CreatePurchaseOrderListEbizProvABCSImplProcess.bpel(line 617): role not found
as mentioned in the log.
Regards,
Narayana

Error in Installation of Solution Manager on Virtualbox centOS

Error in Installation of Solution Manager on Virtualbox centOS .
I tried as per the solution given in the error.
Please go through attachment for error and my /etc/hosts file.

Hi,
I guess you added the entry in /etc/hosts after you got the error.
That being true, stop and start your sapinst again. This will allow you to continue. The information is cached and the only way is to stop and start sapinst.
Cheers,
Amerjit

Error while Loggin inot VISUAL ADMIN-No login module succeeded.

Hi,
I am trying to login to the Visual Admin for the first time for my new Portal System (Quality).
But I am getting error while loggin in with Administrator user:-
com.sap.engine.services.security.exceptions.BaseLoginException: No login module succeeded.
The visual_administration.0.trc file shows the following:-
1.5 #C000AC117C1900010000000159CB59CB000455D3152A8478#1220264988408#com.sap.engine.services.adminadapter.gui.tasks.LoginTask##com.sap.engine.services.adminadapter.gui.tasks.LoginTask#######Thread[Thread-15,6,main]##0#0#Error#1#/System/Server/VisualAdministrationTool#Java###Error while trying to login to SBQEP: No login module succeeded.
[EXCEPTION]
#1#com.sap.engine.services.security.exceptions.BaseLoginException: No login module succeeded.
     at com.sap.engine.services.security.login.ModulesProcessAction.run(ModulesProcessAction.java:188)
     at java.security.AccessController.doPrivileged(AccessController.java:231)
     at com.sap.engine.services.security.login.FastLoginContext.login(FastLoginContext.java:181)
     at com.sap.engine.services.security.remoteimpl.login.RemoteLoginContextHelperImpl.login(RemoteLoginContextHelperImpl.java:72)
     at com.sap.engine.services.security.remoteimpl.login.RemoteLoginContextHelperImplp4_Skel.dispatch(RemoteLoginContextHelperImplp4_Skel.java:64)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(AccessController.java:207)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
predecessor system -
com.sap.engine.services.security.exceptions.BaseLoginException: No login module succeeded.
     at com.sap.engine.services.security.login.ModulesProcessAction.run(ModulesProcessAction.java:188)
     at java.security.AccessController.doPrivileged(AccessController.java:231)
     at com.sap.engine.services.security.login.FastLoginContext.login(FastLoginContext.java:181)
     at com.sap.engine.services.security.remoteimpl.login.RemoteLoginContextHelperImpl.login(RemoteLoginContextHelperImpl.java:72)
     at com.sap.engine.services.security.remoteimpl.login.RemoteLoginContextHelperImplp4_Skel.dispatch(RemoteLoginContextHelperImplp4_Skel.java:64)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(AccessController.java:207)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Have reffered SAP Note 957355 and performed the steps given in the note,but still the same error.
I am able to login to the PORTAL with the same Administrator user and password.
Pls suggest where could be the issue and how to process.
Regards,
Abhijeet

Problem solved. ... No, I have also an answer , perhaps it can help some other peoples.
As I said there is a note 957355. I create the entrys in offlineconfigtool, but nothing happens. So I checked the other entrys in the "configuration" node in "security" (the note 957355 treated the authentication entry)    , like "UME User Store" "ticket" and so on. I've taking another system and ckecked this entrys and compare it with my system. So I could restore the default entrys in all security nodes (for authentication). After an restart - voila, it workes.
greetings
ps.: hm, can I give some points for me?

Error While creating users in managed system.

Dear All,
I am configuring SAP Solution Manager 7.1. I am in stage of Managed System Configuration (for JAVA).
In step 6 Create user: While creating (System) user SM_COLL_<SID> I am getting error :
An error occurred while processing the UME command READ_USER from agent <hostname> : Server returned: 401 Unauthorized. Please check SMD agent application logs.
And for ABAP System,
SMDAGENT_XXX Technical User (in Managed System <SID> Client 000)
while creating user SMDAGENT_<SID> and SAPSUPPORT
I am getting error:
No CENTRAL nor DIALOG instance known for system <SID>
But in SM51 I can see Server Status Active.
and Users are not present.(Checked it through SU01)
I am not getting why this is happening.
Please help me regarding the same.
Thanks & Regards
Ajitabh

Hi,
I am pasting the SMD agent application logs:
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[SMDAgentAppLog]/>
<!PATTERN[SMDAgentApplication.log]/>
<!FORMATTER[com.sap.tc.logging.TraceFormatter(%d [%t] %10s %m)]/>
<!ENCODING[Cp1252]/>
<!FILESET[0, 10, 1000000]/>
<!PREVIOUSFILE[SMDAgentApplication.9.log]/>
<!NEXTFILE[SMDAgentApplication.1.log]/>
<!LOGHEADER[END]/>
Nov 29, 2011 2:02:09 PM [Thread[Connector,5,main]] Warning    com.sap.smd.wily.hostagent.mai.MaiAdapter - init: Introscope Host Adapter is not active, no Introscope metrics from MAI
Nov 29, 2011 2:21:01 PM [Thread[Thread-33,5,main]] Warning    com.sap.smd.wily.hostagent.mai.MaiAdapter - init: Introscope Host Adapter is not active, no Introscope metrics from MAI
Nov 29, 2011 2:38:31 PM [Thread[Thread-67,5,main]] Warning    com.sap.smd.wily.hostagent.mai.MaiAdapter - init: Introscope Host Adapter is not active, no Introscope metrics from MAI
Nov 30, 2011 1:26:19 PM [Thread[ExRun:OutsideDiscovery_1,5,OutsideDiscovery:ExecTG]] Path       Caught java.net.ConnectException: Connection refused: connect
     at java.net.PlainSocketImpl.socketConnect(Native Method)
     at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
     at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
     at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
     at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
     at java.net.Socket.connect(Socket.java:521)
     at com.sap.smd.agent.plugin.connectors.http.ConnectionExtendedImpl.openSocket(ConnectionExtendedImpl.java:2025)
     at com.sap.smd.agent.plugin.connectors.http.ConnectionExtendedImpl.open(ConnectionExtendedImpl.java:1398)
     at com.sap.smd.agent.plugin.connectors.http.ConnectionExtendedImpl.sendInternal(ConnectionExtendedImpl.java:1552)
     at com.sap.smd.agent.plugin.connectors.http.ConnectionExtendedImpl.send(ConnectionExtendedImpl.java:1483)
     at com.tssap.dtr.client.lib.protocol.requests.RequestBase.perform(RequestBase.java:570)
     at com.tssap.dtr.client.lib.protocol.requests.RequestBase.perform(RequestBase.java:693)
     at com.sap.smd.agent.plugin.connectors.http.HTTPConnectorService.performRequest(HTTPConnectorService.java:548)
     at com.sap.smd.agent.plugin.connectors.http.HTTPConnectorService.performRequest(HTTPConnectorService.java:673)
     at com.sap.smd.agent.plugin.connectors.http.HTTPConnectorService.performRequest(HTTPConnectorService.java:638)
     at com.sap.smd.agent.plugin.connectors.http.HTTPConnectorService.performRequest(HTTPConnectorService.java:624)
     at com.sap.smd.agent.plugin.connectors.webservice.SAPHostAgentTrustedConnectionConfigurator.setupTrustedConnection(SAPHostAgentTrustedConnectionConfigurator.java:81)
     at com.sap.smd.agent.plugin.connectors.webservice.WSConnectorFactory.configureLocalSAPHostAgentEndPoint(WSConnectorFactory.java:244)
     at com.sap.smd.agent.plugin.hostagent.check.HostAgentCheckService.getHostAgentVersion(HostAgentCheckService.java:105)
     at com.sap.smd.agent.plugins.dcc.util.WSProxyManager.checkSAPHostAgentVersion(WSProxyManager.java:287)
     at com.sap.smd.agent.plugins.dcc.util.WSProxyManager.initSAPHostControlWebServiceClient(WSProxyManager.java:112)
     at com.sap.smd.agent.plugins.dcc.util.WSProxyManager.getSAPHostControlProxy(WSProxyManager.java:75)
     at com.sap.smd.agent.plugins.dcc.job.PhysicalHostPushJob.run(PhysicalHostPushJob.java:195)
     at com.sap.smd.server.exec.TaskRunner.run(TaskRunner.java:46)
     at com.sap.smd.server.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:781)
     at java.lang.Thread.run(Thread.java:679)
Nov 30, 2011 1:26:19 PM [Thread[ExRun:OutsideDiscovery_1,5,OutsideDiscovery:ExecTG]] Error      Pb:
[EXCEPTION]
java.rmi.RemoteException: Error to perform http request cause by java.io.IOException: Unable to open connection to host "FQDN:1128". The host is down or unavailable...; nested exception is:
     java.io.IOException: Unable to open connection to host "FQDN:1128". The host is down or unavailable.
Dec 2, 2011 4:56:53 PM [Thread[Thread-368,5,main]] Warning    [Setup]Step Id 1051 has no step description
Dec 2, 2011 4:56:53 PM [Thread[Thread-368,5,main]] Warning    [Setup]Step Id 1051 has no step description
Dec 2, 2011 5:02:05 PM [Thread[Thread-363,5,main]] Error      [Setup]Failed to get a soap response from http://FQDN:50000/spml/spmlservice
Dec 2, 2011 5:02:05 PM [Thread[Thread-363,5,main]] Error      [Setup]An error occured while processing the UME command READ_USER from agent HOSTNAME : Server returned: 401 Unauthorized
[EXCEPTION]
com.sap.sup.admin.xmlsoap.core.soap.NativeSOAPException: Server returned: 401 Unauthorized
Kindly help me out guys.
Thanks & Regards
Ajitabh

Error while Running Receiving Transaction Manager

Hi.,
We have 11..5.10.2 on AIX 5.3 intermeditley we are getting the below error for Receiving Transaction Manager. for temporary sloution we will restart the Receiving Transaction Manager is there any permanent solution for this.....?
we have two Receiving Transaction Manager process.
Error
"APP 00204: Concurrent manager encountered an error while running the spawned
concurrent program Receiving Transaction Manager: rcvoltm TM:Timeout"

Hello.
Have a look on MOS Doc ID 1071727.1
Octavio

Runtime Errors Raise Exception in Solution Manager

Hi Guru's,
While I try to excute the transaction solman_issue_mgnt in solution manager for issue tracking, runtime errors occurs.
Error analysis
    A RAISE statement in the program "CL_GUI_HTML_VIEWER============CP" raised the
     exception
    condition "CNHT_ERROR_PARAMETER".
    Since the exception was not intercepted by a superior
    program, processing was terminated.
Could anyone suggest me on this issue.
regards,
Guna

Hi Juan,
As per the note, everything was fine there. We have SAP_Basis 700 with SP16.
Earlier it was worked fine. Now only we are facing this issue while excuting the t-code solman_issue_mgmt.
regards,
Guna

Error when installing sap solution manager

Dear all,
When i am installing SAP solution manager (SAP SOLMAN 7.0 EHP1SR1 WINDOWS_X86_64), I meet the following error:
An error occurred while processing option SAP Solution Manager 7.0 EhP1 > SAP Systems > MS SQL Server > Central System > Central System( Last error reported by the step: ABAP processes of instance S01/DVEBMGS00 [ABAP: UNKNOWN] did not start after 10:30 minutes. Giving up.). You can now:
Choose Retry to repeat the current step.
Choose Log Files to get more information about the error.
Stop the option and continue with it later.
Log files are written to C:\Program Files/sapinst_instdir/SOLMAN/SYSTEM/MSS/CENTRAL/AS.
Do anyone meet the same error before? Please help...
Thanks.

I had a similar issue because the size of the pagiing file, after increase the size of paging file to 20Gb, I solved the issue in my system. The instance wasn't up because the size of paging file.

Error while opening MDM Data Manager

Hi,
We are getting the following error while trying to open Data manager on our repository.
"Error Initializing Attributes for table Taxonomy
Application will exit
Already exists"
mds Version 5.5.42.90
MDM DataManager Ver5.5.42.90
The repository loads without any errors. The server log file too doesnt show any errors.
Is there anyway to fix this?

Go to your MDM console, Login to repository and Unload repository first.
Then load with Update Indices.
This problem comes when you change anything in schema in console and then load repository with immediate option.
So always prefer to use update indices as accelator files will get updated and data comes from actual database.
If the problem still persists then Go again to console and check your repository for any fatal error. if errors come then repair repository and if not come then also repair.
Then load with update indices.
Hope it will help you.
BR,
Alok
Edited by: Alok Sharma on Feb 14, 2008 9:20 AM

Error While Loggin in Solution Manager 3.2

Similar Messages

Maybe you are looking for