Com.sap.ip.me.api.sync.SyncException: EXCEPTION_INFO_CODE=7

Hi everybody,
My user and password are correct but I am trying to connect on my WAS with the following URL :
http://frgauns008:50800/meSync/servlet/meSync?sysid=qm0&login=jeletellier&password=jerome&client=120&language=fr&acknowledge=X&~test=true&
I get :
&WAF_SYNC&EXCEPTION_INFO_CODE=7&&WAF_SYNC&STATUS=&Execution Time= & HeaderType = MEREPLICATION &MORE_PACKAGES_WAITING = &
instead of the correct answer.
My user has the following autorizations object with * value :
S_ME_SYNC ;S_MILCLADM;S_MI_ADMCO;S_MI_ALERT
S_MI_CCMS;S_MI_MGMT;S_RFC;S_TCODE;
S_DATASET
Any idea ? Best regards Jérôme

Hello Jerome,
EXCEPTION_INFO_CODE=7 indicates a problem with Service user. You would have maintained the service user and password in the property file (<system name>.props) in the Visual Administrator. Kindly check whether the service user credentials mentioned here are correct. Unless you business demands, you may also do away with the service user i.e, remove the user from the property file.
Hope this helps.
Best Regards
Sivakumar

Similar Messages

SMARTSYNC : com.sap.ip.me.smartsync.sync.InboundTransformException

Hi experts,
when i sync applications via smartsync i get this errormessage:
"SMARTSYNC :com.sap.ip.me.smartsync.sync.InboundTransformException: Not wellformed nor collapsed xml".
I get this message for each syncbo from MAM 2.0 and also for the syncbo from the MDK-Sample application.
Can anyone help me?
GenericSync applications are working fine.
Clients: MI2.5 SP12P1, MI Server 2.5 SP11.
Regards.
Frank Brackmann

Hi Frank,
That SAP Note is specific to the error you are having but it also assumes that your system is uptodate with other required Notes and thats why it lists them. I am quite positive that if you apply the notes successfully your error will go away. I say this from experience, I have had so many errors but thankfully the SAP MI team have created the solutions that have fixed them. Everytime I do get an error of some sort I check to make sure that my System is uptodate with all upgrades/notes/patches. If it is, then I would start an OSS note. Luckily for you a note is readily available.
Oh one more thing Frank, I am using MI 2.5 sp13 client and server and its a major upgrade. I recommend you upgrade to sp13 soon it will resolve most if not all of your problems. The performance is way better, plus the new API's even though they are not documented well yet are definately much better than pre-sp13 .
-wael

Cannot find the class file for com.sap.portal.services.api.connectorgateway

Hi,
I was trying the "How to BI JAVA SDK in a Portal iView and get the following error.
The project was not built since its classpath is incomplete. Cannot find the class file for com.sap.portal.services.api.connectorgateway.IConnectorGatewayService. Fix the classpath and try rebuilding this project.
I have the following in my portalapp.xml file
<property name="SharingReference" value="com.sap.portal.ivs.connectorservice"/>
and i have also added the jar file "com.sap.portal.ivs.connectorservice_api" in the set of lib's
Has some faced a similar issue? or can someone suggest how I could possibly resolve this.
Thanks,
Smitha

Hi Smitha:
My webdynpro dc was build failed for "This compilation unit indirectly references the missing type com.sap.engine.services.webservices.espbase.client.dynamic.content.GenericObject (typically some required class file is referencing a type outside the classpath)".
How should i do? Thank you!

Package com.sap.ip.me.api.logging and com.sap.ip.me.api.user not found.

I don't have
com.sap.ip.me.api.logging
and
com.sap.ip.me.api.user
packages in me2lib.jar (and none of the jars in the lib folder of the SAPMobileEngine folder).
Any ideas as to where these are ?

I don't think you can use ME2.1 Client with MI2.5 Server. At least they have different login protocol, and maybe different synchronization protocol as well.
The library MEg.jar, that I have inspected for the missing libraries, is a part of MI25 SP09. I heartily advise you to migrate your application to MI.
Cheers,
Todor

Resolve Error:NoClassDefFoundError: com/sap/workflow/engine/api/IWorkflow

Hi,
I want Create Task in UWL using web dynpro coding .
i have done some coding using UWL APIs.
when i run the application i will get an error   java.lang.NoClassDefFoundError: com/sap/workflow/engine/api/IWorkflow
i think i want to give a some web dynpro references but now i have given reference like
Library reference =tckmcbc.uwl~api
Sharing reference = PORTAL:sap.com/com.sap.portal.usermapping
but i nedd to give some other reference? or how to resolve this error.
Regards,
BOOPATHI.M

HI ,
My Code is :
IWDClientUser clientUser = null;
     IUser creator = null;
     clientUser = WDClientUser.getCurrentUser();
     creator = clientUser.getSAPUser();
     IJWFPortalService service = (IJWFPortalService) PortalRuntime.getRuntimeResources().getService(IJWFPortalService.KEY);
     IWorkflow eWF = service.getWorkflowEngineJMS();
     Hashtable taskCtxt = new Hashtable();
     taskCtxt.put("_wfitemtype_","uwl.notification.erp.fyi");
     if(wdContext.currentVnCreateTaskElement().getVaDescription()!=null)
          taskCtxt.put("_wfdescription_",wdContext.currentVnCreateTaskElement().getVaDescription());// "mydescription");
     else
          wdComponentAPI.getMessageManager().raiseException("Please enter the Description",true);
     taskCtxt.put("_wfpriority_",wdContext.currentContextElement().getCaPriority());//new Integer (0));
     if(wdContext.currentVnCreateTaskElement().getVaAssignedUser()!=null)
     taskCtxt.put("_wftaskassignees_",wdContext.currentVnCreateTaskElement().getVaAssignedUser());//"administrator");
     else
     wdComponentAPI.getMessageManager().raiseException("Please enter the User",true);
     taskCtxt.put("_wftemplatename_","QuickTask");
     taskCtxt.put("_wfduedate_", dateTime);
     Hashtable appCtxt = new Hashtable();
     appCtxt.put("mysystem", "SAP_LocalSystem");
     appCtxt.put("mylaunchcontext", "uwl");
     appCtxt.put("myappcontext", "test");
    if(wdContext.currentVnCreateTaskElement().getVaTitle()!=null)
    eWF.createTask(wdContext.currentVnCreateTaskElement().getVaTitle(), creator, taskCtxt,appCtxt);
Regards,
Boopathi M

Com.sap.tc.buildplugin.api.IPluginBuildInfo.getDcNameWithVendor()Ljava/lang

Hello,
I was working with Webdynpro last Friday without any problems and today (Tuesday) when I try to build any of my DC Projects I am getting the follwing error:
com.sap.tc.buildplugin.api.IPluginBuildInfo.getDcNameWithVendor()Ljava/lang/String
Any idea what can be happening? I have not changed anything since last time I build something.
Best Regards,
Diego.

Hello
Kindly advice how you solved the problem.
Tx.
Kind Regards
Ramamoorthy D

Location of com.sap.aii.mapping.api on PI 7.1.

Hello,
just tried to extract the above mentioned jar. file for development of java mappings on my local machine. I can find the jar on XI 3.0 in j2ee\cluster\server0\apps\sap.com\com.sap.xi.services (as also described in some tutorials) however in release 7.1. it does not seem to be there. Has the path structure changed in the new release and where can I find the standard libraries on 7.1.?
Thank you for your information.

Hi Florian,
Please see the path mentioned in this wiki:
https://wiki.sdn.sap.com/wiki/display/XI/Where%20to%20get%20the%20libraries%20for%20XI%20development
Regards,
---Satish

Deployable cannot be retrieved from FILE_PROVIDER , stopping. Cause:com.sap.conn.jco.JCoException: (103) JCO_ERROR_LOGON_FAILURE: Name or password is incorrect

Hi All,
After two years of CTS+ working without issue, in the last fortnight JCO_ERROR_LOGON_FAILURE has occurred. I have reviewed all the configuration in document http://scn.sap.com/doc/DOC-30177, and it all looks fine. The user configured also checks out fine as well. The user id that is causing all the trouble is CTS_<SID>. We chose this option so we could determine which user in case of future issues. We have two development paths, Project and BAU. So at anyone time transports that have started in the BAU development system will need to be imported into the Project development system (using transport express) and vice versa. Attached is the security authentication log from the system showing authentication failure. I have also checked the transport routes defined for the business systems in the SLD and these look fine as well. Roles assigned to the user are SAP_CTS_PLUS,
SAP_J2EE_ADMIN, SAP_XI_CMS_SERV_USER, SAP_XI_CONFIGURATOR, SAP_XI_DEVELOPER, Z_CTS_PLUS_ADDITIONAL. I have also checked the permissions on the file at the operating system level.
Any suggestions/advice gratefully received as this really has me scratching my head.
Log:
!REPOSITORY_ERROR_CHECK_STACKTRACE!
[EXCEPTION]
com.sap.conn.jco.JCoException: (103) JCO_ERROR_LOGON_FAILURE: Name or password is incorrect (repeat logon) on DXI mshost strsap31
at com.sap.conn.jco.rt.MiddlewareJavaRfc.generateJCoException(MiddlewareJavaRfc.java:662)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcClient.connect(MiddlewareJavaRfc.java:1364)
at com.sap.conn.jco.rt.ClientConnection.connect(ClientConnection.java:731)
at com.sap.conn.jco.rt.PoolingFactory.init(PoolingFactory.java:103)
at com.sap.conn.jco.rt.ConnectionManager.createFactory(ConnectionManager.java:293)
at com.sap.conn.jco.rt.DefaultConnectionManager.createFactory(DefaultConnectionManager.java:46)
at com.sap.conn.jco.rt.ConnectionManager.getFactory(ConnectionManager.java:262)
at com.sap.conn.jco.rt.RfcDestination.initialize(RfcDestination.java:509)
at com.sap.conn.jco.rt.RfcDestination.getSystemID(RfcDestination.java:533)
at com.sap.conn.jco.rt.RepositoryManager.getRepository(RepositoryManager.java:30)
at com.sap.conn.jco.rt.RfcDestination.getRepository(RfcDestination.java:603)
at com.sap.conn.jco.rt.RfcDestination.getRepository(RfcDestination.java:27)
at com.sap.cts.jco.tms.TmsJCoAdapter.initializeJCo(TmsJCoAdapter.java:76)
at com.sap.cts.jco.tms.TmsJCoAdapter.<init>(TmsJCoAdapter.java:57)
at com.sap.cts.jco.EpsFileReader.<init>(EpsFileReader.java:76)
at com.sap.cts.jco.EpsFileReaderController.doImport(EpsFileReaderController.java:90)
at com.sap.cts.core.ImportManager.execImport(ImportManager.java:102)
at com.sap.cts.ejb.DeployBean.execImport(DeployBean.java:170)
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:597)
at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:47)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:47)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:37)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:21)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_MethodRetry.invoke(Interceptors_MethodRetry.java:46)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:25)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:17)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:138)
at com.sap.engine.services.ejb3.webservice.impl.DefaultImplementationContainer.invokeMethod(DefaultImplementationContainer.java:204)
at com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.process0(RuntimeProcessingEnvironment.java:710)
at com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.preProcess(RuntimeProcessingEnvironment.java:662)
at com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.process(RuntimeProcessingEnvironment.java:322)
at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPostWOLogging(ServletDispatcherImpl.java:199)
at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:65)
at com.sap.engine.services.webservices.servlet.SoapServlet.doPost(SoapServlet.java:61)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:38)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:457)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)
at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:276)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)
at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
Caused by: RfcException: [null]
message: Name or password is incorrect (repeat logon) on DXI mshost strsap31
Return code: RFC_SYS_EXCEPTION(3)
error group: 103
key: RFC_ERROR_LOGON_FAILURE
at com.sap.conn.rfc.api.RfcApi.RfcOpen(RfcApi.java:219)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcClient.connect(MiddlewareJavaRfc.java:1331)
... 87 more
Caused by: RfcException: [DXI|strsap31]
message: Name or password is incorrect (repeat logon)
Return code: RFC_SYS_EXCEPTION(3)
error group: 104
key: RFC_ERROR_SYSTEM_FAILURE
Exception raised by DXI|strsap31
at com.sap.conn.rfc.engine.RfcIoOpenCntl.RfcReceive(RfcIoOpenCntl.java:2034)
at com.sap.conn.rfc.api.RfcApi.RfcOpen(RfcApi.java:187)
... 88 more
Caused by: com.sap.conn.rfc.exceptions.RfcGetException: Name or password is incorrect (repeat logon)
at com.sap.conn.rfc.engine.RfcImp.ab_rfcerror(RfcImp.java:1157)
at com.sap.conn.rfc.engine.RfcGet.rfcget_run(RfcGet.java:131)
at com.sap.conn.rfc.engine.RfcGet.ab_rfcget(RfcGet.java:23)
at com.sap.conn.rfc.engine.RfcRcv.ab_rfcreceive(RfcRcv.java:33)
at com.sap.conn.rfc.engine.RfcIoOpenCntl.RfcReceive(RfcIoOpenCntl.java:1981)
... 89 more

User id missing in client 000

What jar for com.sap.aii.mapping is

Dear
i am testing with blow blog.
/people/pooja.pandey/blog/2005/06/27/xslt-mapping-with-java-enhancement-for-beginners
in this blog, java program use the following;
import com.sap.aii.mapping.api.AbstractTrace;
import com.sap.aii.mapping.api.StreamTransformationConstants;
what .jar file name is?
i could not find com.sap.aii.mapping on eclipse.
thanks
Denis

Denis,
You need the <b>aii_map_api.jar</b> file for this.
You will get this in the following location on your XI server,
<b>j2ee\cluster\server0\apps\sap.com\com.sap.xi.services</b>
Upload the Jar, in your Project Build Path.
Regards,
Bhavesh

Java mapping how to use com.sap.tc.logging

Hi I would like to know how to use logging within a java mapping.
I know i have to use theese classes : Location, Category, ConsoleLog but i dont know how.
1) How to load the P1, P2, P3 and P4 tags in the Error tag of the SOAP header watched in SXMB_MONI
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">STREAM_TRANSFORMATION_EX</SAP:Code>
<SAP:P1>SwissMedical/Interfaces/IFI002/LiquidacionMapping~</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Java mapping of application triggered an exception</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
2) How to load and activate log in the DIAGNOSTIC tag of the SOAP Header.
- <SAP:Diagnostic xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:TraceLevel>Information</SAP:TraceLevel>
<SAP:Logging>Off</SAP:Logging>
</SAP:Diagnostic>
Thanks!!

As already suggested, you can display custom messages using AbstractTrace.
trace = (AbstractTrace)param.get( StreamTransformationConstants.MAPPING_TRACE );
trace.addInfo("G1-CYCLE is missing");
For more on coding front refer:
http://help.sap.com/javadocs/NW04/current/pi/com/sap/aii/mapping/api/StreamTransformation.html
To get this trace seen in MONI, set parameter TRACE_LEVEL in SXMB_ADM to 2.

Call to messaging system failed: com.sap.aii.af.ra.ms.api.DeliveryException

hello
I am running an interface RFC2WS sync and recieve this message in the RFC. the message does not get out of the XI and rich the target (WS).
the XI been upgraded lately, and I think this might be the cuase to the problem, becuase the interface been worked before, and still working in PROD environment as is.
what could be the problem and how can I start investigate it to find the problem?
this is what the SAP recieves
call to messaging system failed: com.sap.aii.af.ra.ms.api.DeliveryException
Thanks
Kfir

Hi Kfir,
just check in RWB, in component monitoring, the status of integration server and adapter engine.......if it is red, then ask your basis guys to remove that error................just check your comm channels, i think your comm channels are in error, if they are just edit them, save and activate them again..........i think then your this issue will be resolved.'
Regards,
Rajeev Gupta

Help in com.sap.aii.af.ra.ms.api.DeliveryException

Hi guys,
I'm doing a complex RFC to JDBC syncronous select scenario, In my BPM the sync send step is showing an error.
The message i'm getting in moni is
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
The scenario was working fine untill yesterday....Can anyone help me in this regard??
Thanks
Varun

hi varun,
was new patch applied to the system...?
check this for your reference
com.sap.aii.af.ra.ms.api.DeliveryException: Exception in method process ?
regards
Ramesh P

SR Log Error - | Message : com.sap.esi.uddi.sr.api.exceptions.SRException

Hi,
We are getting below errors in /nwa/logs. We have our PI (7.11) and Service Registry configured on the same server. And have out CE (7.2) system connected to this service registry. Does any one has similar experience? Please let me know if you have any solution for the same.
SR Log Error
| 11-Nov-11 14:10:45.568
| Method   : getClassificationSystems()
| Class    : com.sap.esi.uddi.sr.api.ws.ServicesRegistrySiImplBean
| ThreadID : 146
| Message : com.sap.esi.uddi.sr.api.exceptions.SRException: No classification system found for ID 'QName: Namespace= http://uddi.sap.com/classification; Name= ConfigurationFlags'
|
|       com.sap.esi.uddi.sr.impl.common.Utility.cs2srException(Utility.java:122)
|       com.sap.esi.uddi.sr.impl.ejb.ServicesRegistryBean.getClassificationSystems(ServicesRegistryBean.java:242)
|       sun.reflect.GeneratedMethodAccessor1325.invoke(Unknown Source)
|       sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
|       java.lang.reflect.Method.invoke(Method.java:585)
|       com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:46)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
|       com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
|       com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
|       com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38)
|       com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
|       com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
|       com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
|       com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
|       com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)
|       com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
|       $Proxy1087.getClassificationSystems(Unknown Source)
|       com.sap.esi.uddi.sr.api.ws.ServicesRegistrySiImplBean.getClassificationSystems(ServicesRegistrySiImplBean.java:456)
|       sun.reflect.GeneratedMethodAccessor1324.invoke(Unknown Source)
|       sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
|       java.lang.reflect.Method.invoke(Method.java:585)
|       com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:46)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
|       com.sap.engine.services.ejb3.runtime.impl.Interceptors_WS.invoke(Interceptors_WS.java:31)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
|       com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
|       com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
|       com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38)
|       com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
|       com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
|       com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
|       com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
|       com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)
|       com.sap.engine.services.ejb3.webservice.impl.DefaultImplementationContainer.invokeMethod(DefaultImplementationContainer.java:203)
|       com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.process0(RuntimeProcessingEnvironment.java:512)
|       com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.preProcess(RuntimeProcessingEnvironment.java:486)
|       com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.process(RuntimeProcessingEnvironment.java:256)
|       com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPostWOLogging(ServletDispatcherImpl.java:176)
|       com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPostWithLogging(ServletDispatcherImpl.java:112)
|       com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:70)
|       SoapServlet.doPost(SoapServlet.java:51)
|       javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
|       javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
|       com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:140)
|       com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:37)
|       com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:486)
|       com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:298)
|       com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:396)
|       com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:385)
|       com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48)
|       com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
|       com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:84)
|       com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
|       com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:245)
|       com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
|       com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78)
|       com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
|       com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
|       com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
|       com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
|       com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
|       com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
|       com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
|       com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
|       com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
|       com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
|       com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
|       com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:43)
|       com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
|       com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
|       com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)
|       com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
|       com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
|       com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:428)
|       com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:247)
|       com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)
|       com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)
|       com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)
|       com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
|

Hi,
Refer Error:Service Registyr Configuration PI 7.11
and http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/8071b1b8-3c5c-2e10-e7af-8cadbc49d711?QuickLink=index&overridelayout=true
Thanks,
Chandra

Publish of a Service over Service Registry - com.sap.esi.uddi.sr.api.exce

Hello
I try to publish a Service over the Service Registry UI but this results in a com.sap.esi.uddi.sr.api.exceptions.SRExceptionerror code: null detail message: java.lang.NullPointerException->java.lang.NullPointerException
Is the problem the schema import or the two address locations ?
We use ESR CE 7.1 SP3
Kind regards
Gerald Eder
The WSDL looks like :
<?xml version="1.0" encoding="utf-8" ?>
- <wsdl:definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="http://test.com/soa/" xmlns:i0="http://test.com/soa" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" targetNamespace="http://test.com/soa/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
<wsdl:import namespace="http://test.com/soa" location="http://pwwdev.test.com/Appl/Corp/Services/SOA/SOAServer/customerid.asmx?wsdl=wsdl1" />
- <wsdl:types>
- <s:schema targetNamespace="http://test.com/soa/">
<s:import schemaLocation="http://pwwdev.test.com/Appl/Corp/Services/SOA/SOAServer/customerid.asmx?schema=schema1" namespace="http://test.com/soa" />
</s:schema>
</wsdl:types>
- <wsdl:service name="CustomerID">
- <wsdl:port name="CustomerIDBinding" binding="i0:CustomerIDBinding">
<soap:address location="http://pwwdev.test.com/Appl/Corp/Services/SOA/SOAServer/customerid.asmx" />
</wsdl:port>
- <wsdl:port name="CustomerIDBinding1" binding="i0:CustomerIDBinding1">
<soap12:address location="http://pwwdev.test.com/Appl/Corp/Services/SOA/SOAServer/customerid.asmx" />
</wsdl:port>
</wsdl:service>
</wsdl:de

Hi Rajesh,
Many thanks for your prompt reply, however this note 1267817 was already applied before posting message.
B/W I have observed that in spite of the error the service published multiple times in the registry (perhaps each try to publish resulted a entry in SR).
Really crazy error, any other suggestion??
Regards, Immy.

Com.sap.esi.uddi.sr.api.exceptions.SRExceptionerror code: null detail messa

Dear All,
When we try to publish a Web Service using Service Registry, following error appears, even though my user has the roles UDDI_Admin and SERVICE_REGISTRY_READ_WRITE
com.sap.esi.uddi.sr.api.exceptions.SRExceptionerror code: null detail message: com.sap.esi.uddi.sr.impl.uddi.wsdl.validation.UDDIServerRemoteException: <Localization failed: ResourceBundle='com.sap.engine.services.webservices.wscm.validation.accessors.validation', ID='DISPOSITION_REPORT_UDDI_SERVER', Arguments: ['http://host:port/uddi/api/inquiry/', 'http://host:port/uddi/api/publish/', 'Fatal: A serious technical error has occurred while processing the request. ']> : Can't find bundle for base name com.sap.engine.services.webservices.wscm.validation.accessors.validation, locale en->com.sap.esi.uddi.sr.impl.uddi.wsdl.validation.UDDIServerRemoteException: <Localization failed: ResourceBundle='com.sap.engine.services.webservices.wscm.validation.accessors.validation', ID='DISPOSITION_REPORT_UDDI_SERVER', Arguments: ['http://host:port/uddi/api/inquiry/', 'http://host:port/uddi/api/publish/', 'Fatal: A serious technical error has occurred while processing the request. ']> : Can't find bundle for base name com.sap.engine.services.webservices.wscm.validation.accessors.validation, locale en->com.sap.esi.uddi.server.proxy.depl.v3.DispositionReport
Note: We have also configured the UDDI destination as described in sap help @ http://help.sap.com/saphelp_nwpi71/helpdata/en/45/c1ea61a1194432e10000000a155369/frameset.htm
Thanks in Advance,
Immy.

Hi Rajesh,
Many thanks for your prompt reply, however this note 1267817 was already applied before posting message.
B/W I have observed that in spite of the error the service published multiple times in the registry (perhaps each try to publish resulted a entry in SR).
Really crazy error, any other suggestion??
Regards, Immy.

Com.sap.ip.me.api.sync.SyncException: EXCEPTION_INFO_CODE=7

Similar Messages

Maybe you are looking for