Error in Publishing WSDL

Hi ,
I have designed an Enterprise Service in Enterprise Servcie Builder using CE 7.1 SR 3.
When i try to attemp to publish the WSDL file it throws and error -
====================================================================
= Root Exception ===================================================
====================================================================
Thrown:
com.sap.aii.utilxi.swing.framework.FrameworkException: Internal problem occurred
     at com.sap.aii.utilxi.swing.toolkit.ExceptionDialog.init(ExceptionDialog.java:124)
     at com.sap.aii.utilxi.swing.toolkit.ExceptionDialog.<init>(ExceptionDialog.java:96)
     at com.sap.aii.utilxi.swing.toolkit.IBMessages$1.run(IBMessages.java:319)
     at com.sap.aii.utilxi.misc.thread.ThreadPool.assureAWTEventQueueing(ThreadPool.java:84)
     at com.sap.aii.utilxi.misc.thread.ThreadPool.assureAWTEventQueueing(ThreadPool.java:67)
     at com.sap.aii.utilxi.swing.toolkit.IBMessages.showException(IBMessages.java:309)
     at com.sap.aii.utilxi.swing.toolkit.IBMessages.showException(IBMessages.java:299)
     at com.sap.aii.ib.gui.util.UIRunnable.handleException(UIRunnable.java:84)
     at com.sap.aii.ib.gui.util.UIRunnable$MainRunnable$1.run(UIRunnable.java:124)
     at java.awt.event.InvocationEvent.dispatch(Unknown Source)
     at java.awt.EventQueue.dispatchEvent(Unknown Source)
     at com.sap.aii.utilxi.swing.toolkit.Guitilities$EventProcessor.dispatchEvent(Guitilities.java:319)
     at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
     at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
     at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
     at java.awt.EventDispatchThread.run(Unknown Source)
*Caused by: java.rmi.RemoteException: javax.ejb.EJBException: Exception raised from invocation of public com.sap.aii.ibrep.core.esregistry.ServicesRegistryPublication* com.sap.aii.ibrep.server.esregistry.ServicesRegistryBean.publishServiceInterface(com.sap.aii.ib.bom.gen.XiReference) throws com.sap.aii.utilxi.misc.api.ResourceException,java.rmi.RemoteException,com.sap.aii.ib.core.uddi.RegistryClientException method on bean instance [email protected] for bean sap.com/com.sap.xi.repositoryxml|com.sap.xpi.ibrep.server.jarxml|ServicesRegistryBean; nested exception is: javax.ejb.EJBTransactionRolledbackException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance [email protected]1f for bean sap.com/tcesiuddisrproxyear*annotation|tcesiuddisrproxyejbm.jar*annotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Invalid Response code (404). Server <http://localhost:50100/ServicesRegistrySiService/ServicesRegistrySiPort> returned message <Not Found>.; nested exception is: javax.ejb.EJBException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance [email protected]1f for bean sap.com/tcesiuddisrproxyear*annotation|tcesiuddisrproxyejbm.jar*annotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Invalid Response code (404). Server <http://localhost:50100/ServicesRegistrySiService/ServicesRegistrySiPort> returned message <Not Found>.
javax.ejb.EJBTransactionRolledbackException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance [email protected]1f for bean sap.com/tcesiuddisrproxyear*annotation|tcesiuddisrproxyejbm.jarannotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Invalid Response code (404). Server <http://localhost:50100/ServicesRegistrySiService/ServicesRegistrySiPort> returned message <Not Found>.; nested exception is: javax.ejb.EJBException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance [email protected]1f for bean sap.com/tcesiuddisrproxyear*annotation|tcesiuddisrproxyejbm.jarannotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Invalid Response code (404).
Can anyone suggest the steps i shouls take to publish trhe servcie ssuccessfully.Or any suggestion / idea which i should try?
Thanks

hi,
you can try this thread:
No service definitions found In SR.
best regards,
v s

Similar Messages

Factory Instantiation Problem when publishing WSDL in Service Registry

I have installed SOA Suite 10.1.3.1 and OSR 10.1.3. and am trying to publish a WSDL for a new business created as admin. This causes an UDDI error, though:
"Invalid WSDL location! WSDLException: faultCode=CONFIGURATION_ERROR: Problem instantiating factory implementation.: oracle.j2ee.ws.wsdl.factory.WSDLFactoryImpl."
I checked the jars in {oracle.home}/j2ee and couldn't find WSDLFactoryImpl in any of these. It is contained in orawsdl.jar under jdeveloper and bpel, though.
Anyone seeing the same problem or are you guys able to use the OSR and publish services ? Hints on how to patch the OSR classpath ? (I am running it as standalone within OC4J).
cheers,
Diego

yes, I do have one tip:
..don't install in the "home" instance. Well, to be more precise, don't install in the same instance as your BPEL PM and ESB - which by default is the "home" instance.
You have to create a new instance (e.g. "registry") for your OSR, see "Integrating Oracle BPEL Process Manager with the Oracle Application Server Service Registry", page 2-32, step 6 in the "Oracle BPEL Process Manager Administrator's Guide".
Maybe also have a read in
Re: Anyone successfully installed SOA [Advanced] & Service Registry 10.1.3.1 ?
good luck :-)
Message was edited by:
Diego Tognola

How to Publish WSDL in BSR

Hi,
I am installed AIA FP 2.2.1 so BSR is automatically installed with it. Afterwards i installed OSR 10.1.3.1. As per the AIA docs i have changed bsrConfig.properties to point to OSR registry.
registry.url=http://myAPPServer/registry
I was to publish WSDL using bsrPublish.bat file (bsrPublish <WSDLURL> WSDL). The script is executed successfully with no error, but i am neither seeing any information in BSR nor in OSR of the published WSDL.
Any idea how we can find published WSDL in BSR/OSR?
Thanks
Neeraj

Hi Neeraj,
Please check bsraccess.log (under AIA_HOME/infrastructure/BSR/bin) to see if an error has occured.
Paste the content if needed.

Error while publishing enterprise service from ES builder.

Hi Friends
I am not able to publish my service from ES builder. I am getting this error after publishing.
Please let me know if anyone has faced similar problem and has solution for it.
Thanks
-Mitesh
This is the error log generated.
javax.ejb.EJBException: Exception raised from invocation of public com.sap.aii.ibrep.core.esregistry.ServicesRegistryPublication com.sap.aii.ibrep.server.esregistry.ServicesRegistryBean.publishServiceInterface(com.sap.aii.ib.bom.gen.XiReference) throws com.sap.aii.utilxi.misc.api.ResourceException,java.rmi.RemoteException,com.sap.aii.ib.core.uddi.RegistryClientException method on bean instance com.sap.aii.ibrep.server.esregistry.ServicesRegistryBean@c8c9bc for bean sap.com/com.sap.xi.repositoryxml|com.sap.xpi.ibrep.server.jarxml|ServicesRegistryBean; nested exception is: javax.ejb.EJBTransactionRolledbackException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance [email protected] for bean sap.com/tcesiuddisrproxyear*annotation|tcesiuddisrproxyejbm.jarannotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details.; nested exception is: javax.ejb.EJBException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance [email protected] for bean sap.com/tcesiuddisrproxy~earannotation|tcesiuddisrproxyejbm.jar*annotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. javax.ejb.EJBTransactionRolledbackException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance [email protected] for bean sap.com/tcesiuddisrproxyearannotation|tcesiuddisrproxy~ejbm.jarannotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details.; nested exception is: javax.ejb.EJBException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance [email protected] for bean sap.com/tcesiuddisrproxyear*annotation|tcesiuddisrproxyejbm.jarannotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. javax.ejb.EJBException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance [email protected] for bean sap.com/tcesiuddisrproxy~earannotation|tcesiuddisrproxyejbm.jar*annotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:159) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEISyncMethod(WSInvocationHandler.java:118) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEIMethod(WSInvocationHandler.java:84) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invoke(WSInvocationHandler.java:65) at $Proxy1507_10002.publishPhysicalSystems(Unknown Source) at com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(ServicesRegistryProxyFacade.java:339) at sun.reflect.GeneratedMethodAccessor1785_10002.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43) 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:71) 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:38) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) 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:21) 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:16) 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:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy61_10002.publishPhysicalSystems(Unknown Source) at com.sap.aii.ib.server.uddi.RegistryClientDelegateProvider$EjbRegistryClient.publishPhysicalSystems(RegistryClientDelegateProvider.java:389) at com.sap.aii.ibrep.server.esregistry.ServicesRegistryBean.publishPhysicalSystem(ServicesRegistryBean.java:303) at com.sap.aii.ibrep.server.esregistry.ServicesRegistryBean.publishServiceInterface(ServicesRegistryBean.java:172) at sun.reflect.GeneratedMethodAccessor1787_10002.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43) 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:71) 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:38) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) 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:21) 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:16) 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:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy2658_10002.publishServiceInterface(Unknown Source) at sun.reflect.GeneratedMethodAccessor1786_10002.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.rmi_p4.P4DynamicSkeleton.dispatch(P4DynamicSkeleton.java:234) at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351) at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70) at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62) at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37) at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:872) at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53) at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58) at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108) at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304) Caused by: com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:1035) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:699) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:672) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:153) ... 65 more Caused by: java.lang.NullPointerException at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.ContentTypeImpl.init(ContentTypeImpl.java:40) at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.ContentTypeImpl.<init>(ContentTypeImpl.java:36) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.handleSOAPResponseMessage(SOAPTransportBinding.java:459) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:953) ... 68 more javax.ejb.EJBException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance [email protected] for bean sap.com/tcesiuddisrproxyearannotation|tcesiuddisrproxy~ejbm.jarannotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:72) 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:71) 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:38) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) 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:21) 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:16) 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:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy61_10002.publishPhysicalSystems(Unknown Source) at com.sap.aii.ib.server.uddi.RegistryClientDelegateProvider$EjbRegistryClient.publishPhysicalSystems(RegistryClientDelegateProvider.java:389) at com.sap.aii.ibrep.server.esregistry.ServicesRegistryBean.publishPhysicalSystem(ServicesRegistryBean.java:303) at com.sap.aii.ibrep.server.esregistry.ServicesRegistryBean.publishServiceInterface(ServicesRegistryBean.java:172) at sun.reflect.GeneratedMethodAccessor1787_10002.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43) 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:71) 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:38) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) 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:21) 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:16) 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:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy2658_10002.publishServiceInterface(Unknown Source) at sun.reflect.GeneratedMethodAccessor1786_10002.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.rmi_p4.P4DynamicSkeleton.dispatch(P4DynamicSkeleton.java:234) at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351) at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70) at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62) at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37) at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:872) at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53) at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58) at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108) at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304) Caused by: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:159) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEISyncMethod(WSInvocationHandler.java:118) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEIMethod(WSInvocationHandler.java:84) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invoke(WSInvocationHandler.java:65) at $Proxy1507_10002.publishPhysicalSystems(Unknown Source) at com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(ServicesRegistryProxyFacade.java:339) at sun.reflect.GeneratedMethodAccessor1785_10002.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43) ... 56 more Caused by: com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:1035) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:699) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:672) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:153) ... 65 more Caused by: java.lang.NullPointerException at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.ContentTypeImpl.init(ContentTypeImpl.java:40) at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.ContentTypeImpl.<init>(ContentTypeImpl.java:36) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.handleSOAPResponseMessage(SOAPTransportBinding.java:459) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:953) ... 68 more javax.ejb.EJBTransactionRolledbackException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance [email protected] for bean sap.com/tcesiuddisrproxyear*annotation|tcesiuddisrproxyejbm.jarannotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details.; nested exception is: javax.ejb.EJBException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance [email protected] for bean sap.com/tcesiuddisrproxy~earannotation|tcesiuddisrproxyejbm.jar*annotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. at com.sap.engine.services.ejb3.runtime.impl.TransactionAttributeHandler$Required.error(TransactionAttributeHandler.java:307) at com.sap.engine.services.ejb3.runtime.impl.TransactionAttributeHandler$TransactionAttributeErrorsHandler.error(TransactionAttributeHandler.java:130) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:40) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) 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:21) 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:16) 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:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy61_10002.publishPhysicalSystems(Unknown Source) at com.sap.aii.ib.server.uddi.RegistryClientDelegateProvider$EjbRegistryClient.publishPhysicalSystems(RegistryClientDelegateProvider.java:389) at com.sap.aii.ibrep.server.esregistry.ServicesRegistryBean.publishPhysicalSystem(ServicesRegistryBean.java:303) at com.sap.aii.ibrep.server.esregistry.ServicesRegistryBean.publishServiceInterface(ServicesRegistryBean.java:172) at sun.reflect.GeneratedMethodAccessor1787_10002.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43) 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:71) 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:38) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) 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:21) 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:16) 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:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy2658_10002.publishServiceInterface(Unknown Source) at sun.reflect.GeneratedMethodAccessor1786_10002.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.rmi_p4.P4DynamicSkeleton.dispatch(P4DynamicSkeleton.java:234) at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351) at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70) at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62) at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37) at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:872) at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53) at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58) at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108) at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304) Caused by: javax.ejb.EJBException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance [email protected] for bean sap.com/tcesiuddisrproxyearannotation|tcesiuddisrproxy~ejbm.jarannotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:72) 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:71) 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:38) ... 50 more Caused by: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:159) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEISyncMethod(WSInvocationHandler.java:118) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEIMethod(WSInvocationHandler.java:84) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invoke(WSInvocationHandler.java:65) at $Proxy1507_10002.publishPhysicalSystems(Unknown Source) at com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(ServicesRegistryProxyFacade.java:339) at sun.reflect.GeneratedMethodAccessor1785_10002.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43) ... 56 more Caused by: com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:1035) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:699) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:672) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:153) ... 65 more Caused by: java.lang.NullPointerException at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.ContentTypeImpl.init(ContentTypeImpl.java:40) at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.ContentTypeImpl.<init>(ContentTypeImpl.java:36) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.handleSOAPResponseMessage(SOAPTransportBinding.java:459) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:953) ... 68 more javax.ejb.EJBException: Exception raised from invocation of public com.sap.aii.ibrep.core.esregistry.ServicesRegistryPublication com.sap.aii.ibrep.server.esregistry.ServicesRegistryBean.publishServiceInterface(com.sap.aii.ib.bom.gen.XiReference) throws com.sap.aii.utilxi.misc.api.ResourceException,java.rmi.RemoteException,com.sap.aii.ib.core.uddi.RegistryClientException method on bean instance com.sap.aii.ibrep.server.esregistry.ServicesRegistryBean@c8c9bc for bean sap.com/com.sap.xi.repositoryxml|com.sap.xpi.ibrep.server.jarxml|ServicesRegistryBean; nested exception is: javax.ejb.EJBTransactionRolledbackException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance [email protected] for bean sap.com/tcesiuddisrproxyear*annotation|tcesiuddisrproxyejbm.jarannotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details.; nested exception is: javax.ejb.EJBException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance [email protected] for bean sap.com/tcesiuddisrproxy~earannotation|tcesiuddisrproxyejbm.jar*annotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:72) 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:71) 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:38) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) 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:21) 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:16) 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:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy2658_10002.publishServiceInterface(Unknown Source) at sun.reflect.GeneratedMethodAccessor1786_10002.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.rmi_p4.P4DynamicSkeleton.dispatch(P4DynamicSkeleton.java:234) at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351) at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70) at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62) at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37) at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:872) at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53) at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58) at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108) at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304) Caused by: javax.ejb.EJBTransactionRolledbackException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance [email protected] for bean sap.com/tcesiuddisrproxyearannotation|tcesiuddisrproxy~ejbm.jarannotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details.; nested exception is: javax.ejb.EJBException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance [email protected] for bean sap.com/tcesiuddisrproxyear*annotation|tcesiuddisrproxyejbm.jarannotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. at com.sap.engine.services.ejb3.runtime.impl.TransactionAttributeHandler$Required.error(TransactionAttributeHandler.java:307) at com.sap.engine.services.ejb3.runtime.impl.TransactionAttributeHandler$TransactionAttributeErrorsHandler.error(TransactionAttributeHandler.java:130) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:40) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) 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:21) 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:16) 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:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy61_10002.publishPhysicalSystems(Unknown Source) at com.sap.aii.ib.server.uddi.RegistryClientDelegateProvider$EjbRegistryClient.publishPhysicalSystems(RegistryClientDelegateProvider.java:389) at com.sap.aii.ibrep.server.esregistry.ServicesRegistryBean.publishPhysicalSystem(ServicesRegistryBean.java:303) at com.sap.aii.ibrep.server.esregistry.ServicesRegistryBean.publishServiceInterface(ServicesRegistryBean.java:172) at sun.reflect.GeneratedMethodAccessor1787_10002.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43) ... 31 more Caused by: javax.ejb.EJBException: Exception raised from invocation of public java.util.List com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(java.util.List) throws com.sap.esi.uddi.sr.api.ws.PublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault1,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault12,com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishPhysicalSystemsFault123 method on bean instance [email protected] for bean sap.com/tcesiuddisrproxy~earannotation|tcesiuddisrproxy~ejbm.jar*annotation|ServicesRegistryProxyFacade; nested exception is: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:72) 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:71) 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:38) ... 50 more Caused by: javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:159) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEISyncMethod(WSInvocationHandler.java:118) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEIMethod(WSInvocationHandler.java:84) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invoke(WSInvocationHandler.java:65) at $Proxy1507_10002.publishPhysicalSystems(Unknown Source) at com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishPhysicalSystems(ServicesRegistryProxyFacade.java:339) at sun.reflect.GeneratedMethodAccessor1785_10002.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43) ... 56 more Caused by: com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details. at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:1035) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:699) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:672) at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:153) ... 65 more Caused by: java.lang.NullPointerException at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.ContentTypeImpl.init(ContentTypeImpl.java:40) at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.ContentTypeImpl.<init>(ContentTypeImpl.java:36) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.handleSOAPResponseMessage(SOAPTransportBinding.java:459) at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:953) ... 68 more

Hi ,
try to change the ServiceRegistry Logical Port
In NetWeaver Administrator under SOA Management _Business Administration _Web Services Administration
Client Proxy Name: ServicesRegistrySi
Authentication: User name/password
Role: SERVICES_REGISTRY_READ_WRITE
Should help u out

Failed to commit objects to server. Error while publishing reports from BW

Hi,
I am getting below error while publishing reports from BW to BO.
"0000000001 Unable to commit the changes to Enterprise. Reason: Failed to commit objects to server : #Duplicate object name in the same folder."
Anyone having any solution for this. Thanks in advance.

Hi Amit
It would be great if you could add a little info about how you solved this issue. Others might run into similar situations - I just did:-(
Thank you:-)

Error while reading wsdl file

I created and deployed a BPEL process with a JMS adapter and DB adapter.
I have tested this and it works fine.
After a few days, I try to open the project and the BPEL process, and click on the DB
adapter and it throws an exception on the designer :
"Error while reading wsdl file ... (wsdl file name) NULL Exception"
This is hard to debug as the exception does not provide any info, NULL.
This has happened several times for my project. The next time the JMS adapter hit the
same exception while opening on designer. This one I notice happened after I imported
a new schema file (xsd) into the BPEL process.
Only way around that I have for this currently is to delete and recreate the adapters, which as time
consuming as I have to re-create and re-assign a lot of the activities.
Has anyone encountered this and is there a way to fix this without deleting/recreating the adapters ?
Thanks.

I experienced the same issue and found the cause and a workaround;
"Error while reading wsdl file …. Exception: null"
http://www.petervannes.nl/files/b7c08911ce3cde3677e2182bbc5f032a-47.php
Edited by: 944333 on Jul 3, 2012 10:24 PM

Error while writing wsdl file

Hi,
i' m working on jdeveloper 10.1.3.1.0 and when i want to add a partner link to my BPEL project i get 'error while writing wsdl file' 'exception null' error then i couldn't create file.
so how can i solve this problem?
HELP:)

Once the wrapper procedure is created by the adapter, the adapter does a second search to obtain the information about the wrapper (i.e. parameters, their data types, etc.). What's likely happening here is that the wrapper is getting created, but the adapter can't find it. The XSD is based on the wrapper, so if it can't be found, then no XSD can be generated. Try removing the existing wrapper package or choose that option in the wizard when it generates a new one.

Error in loading wsdl file

Hi I am getting the following error while calling a service in BPEL.
Error while reading wsdl file
http://afsmlnx07.onerheem.com:7105/soa-infra/services/default/validationForCC/getStatusByCC?WSDL.Exception:WSDLException:faultCODE=OTHER_ERROR:Failed to read WSDL from http://afsmlnx07.onerheem.com:7105/soa-infra/services/default/validationForCC/getStatusByCC?WSDL:HTTP connection error code is 503.
Will you people help me regarding this?

Hi,
check whether proxy settings are unchecked or not.
In Jdev Tools/Preferences/Web Browser and Proxy.
That should be unchecked.
Regards
PavanKumar.M

"Error in loading WSDL file" --- Adaptive Webservice Model

Hi All,
I have been using Deprecated web service model. But now my application is moving to Test. So in order not to change the URL of the webservice model in the Test, i tried with the Adaptive webservice model. But when i try to import the model its saying " Error in loading WSDL file. Check the error log for more details." Please help me out in this.
Thanks in advance,
Pranesh.

Hi Pranesh,
Please refer to this thread for similar issue and check the log file for NWDS for more details
Error in loading the WSDL file. Check the error log for more details
Hope it helps
Regards
Arun

404 error when publishing to FTP server.

I'm getting the 404 error when publishing my iWeb site to my FTP server. Please help.
It says I have a good connection and publishes but then I get the error when I "Click to go to the site." I've read where I have to upload the file to my server but with the file index_html. Do I rename my iWeb file, domain, to index_html?

I'm getting the 404 error when publishing my iWeb site to my FTP server. Please help.
It says I have a good connection and publishes but then I get the error when I "Click to go to the site."
A 404 errors means the file is not on the server.
Checking the connection is just testing the FTP connection.
I've read where I have to upload the file to my server but with the file index_html. Do I rename my iWeb file, domain, to index_html?
Do I rename my iWeb file, domain, to index_html?
No, you don't. The domain file is where iWeb stores its assets. It stays on your computer. It has no meaning outside it. iWeb publishes the index.html file and all the other files.
Read this : The concept of iWeb Sites
So if your pages do not load, check for their presence on the server.

Error in publishing crystal report

In /crystal/rptadmin I am getting this error when publishing crystal reports
<report name> [<technical name>]
0000000004 Item 1 was not found in the collection.
Has anyone experienced the same error before?

Hello Donna,
in this case I recommend to post to the [dedicated SAP Integration Kit|BusinessObjects Integration Kits; forum.
That forum is monitored by qualified technicians and you will get a faster response there.
Also, all SAP queries remain in one place and thus can be easily searched in one place.
Best regards
Falk

Error while importing WSDL file created in JDeveloper inside BS

Hi All,
I am facing error while importing WSDL of the DBAdapter service created using JDeveloper inside my business service in OSB.
The error in OSB is 'The Resource Mapped Does not exist'

Which version of OSB are you using? You need to upload schema (.xsd) files as well. WSDL has references to that schema(s) but they are not uploaded hence this error. On sbconsole, if you click on a WSDL name to see it, a button comes with name "Edit References". Click that to point to the xsd's you uploaded.
Regards,
Anuj

Getting error while publishing workflow using SP designer for SharePoint 2013

Hi,
I am try to setup Workflow manager for our sharepoint applications.
WF manager set ran without any issue.
I registered the SPWorkflow service which succeeded as well. The Workflow service application shows "Workflow is connected"
I am creating a workflow using sharepoint designer using my credential (not Service account). I am able to save it but while publishing, its prompting with an error.
The error says "Errors were found while compiling the workflow.The workflow files were saved but cannot run." Clicking advanced button show
"Microsoft.SharePoint.SPException: We're sorry, we weren't able to complete the operation, please try again in a few minutes. If you see this message repeatedly, contact your administrator.
at Microsoft.SharePoint.SPScaleOutDatabaseMap.CreateSqlSession(ISPScaleOutDatabaseMapProvider mapProvider, Byte[] compositeKey, Guid forceRefreshVersion, Guid& version)
at Microsoft.SharePoint.SPScaleOutDatabaseCommandExecutor.Execute(ExecuteDelegate operation, ISPScaleOutDatabaseMapProvider mapProvide"
Any help would be highly appreciated
Thanks,

Hi,
According to your post, my understanding is that you got error while publishing workflow using SharePoint designer for SharePoint 2013.
Please check whether the Central Admin > Manage Service Application-> “App Management Service” is started.
Please check whether the “Configure service application associations”, ”App Management Service” is already associated.
Then please check whether the “Manage Services on server” and the “App Management Service” is started.
In addition, please try to re-register Workflow Service.
If the issues still exists, please follow the steps in the
Steps to Verify that Server Is Correctly Set Up. After you verified that the server is correctly set up, follow the steps in the
Steps to Troubleshoot Workflow Management Service and
Troubleshooting the Service Bus for Windows Server then retry your action related to publishing workflows
More information:
http://wp.ahcheng.com/2013/03/23/error-were-found-when-compiling-the-workflow-the-workflow-files-were-saved-but-cannot-be-run/
http://sp2013.pro/2013/04/solution-errors-were-found-when-compiling-the-workflow-the-workflow-files-were-saved-but-cannot-be-run-cannot-set-unknown-member/
Best Regards,
Linda Li
Linda Li
TechNet Community Support

Error while loading WSDL File in Eclipse

Hi Experts
We are getting the following Error while Loading WSDL File in Eclipse.
IWAB0399E Error in generating Java from WSDL: WSDLException (at /wsdl:definitions/wsdl:portType/wsp:Policy): faultCode=INVALID_WSDL: Encountered unexpected element 'Policy'.:
Please advice how to resolve it.
Regards
Prashant

It seems that your WSDL is not well defined, you need to test your wsdl via WS-I compliance in order to check if the wsdl is well created, you can do this via soapui, just create a new project, import the wsdl file or set the URL, left click in the project and select check WS-I compliance, this tool will test your wsdl and gives you a detailed report of what might be the problem.

Error in publishing endpoint in service registry

Hey,
I am gettin the following error while publishing the service registry.
10160A save request exceeded the quantitylimits for a given structure type. #Number of Business Entities exceeds your limit 1(2).
This is with respect to the endpoint. The endpoint is also not published when I checked it in the service registry of PI.
regards,
Milan.

Hi Milan,
Open your UDDI client->Select Publish->Select Retrieve My Business
check if you are able to add more than one Business entity.
You find out all the Business entities present in the UDDI, Take their keys (UDDI Keys)
then go to Publish->Select Retrieve My Business
create business entity with the key you have obtained before and then delete that, It will delete the the business entity and then try to publish the your service with end point.
Thanks,
Sunil Singh

Error in Publishing WSDL

Similar Messages

Maybe you are looking for