DHCP Service errors in Publisher
We have thousand of the same DHCP Service errors below on the Publisher, but the DHCP service is disbled. Don't know if that is a bug in Window 2000. It is running on OS 2000.2.7sr8. Thanks.
Event ID: 1008 Source: Perflib
The Open Procedure for service "DHCPServer" in DLL "C:\WINNT\system32\perfctrs.dll" failed. Performance data for this service will not be available. Status code returned is data DWORD 0.
Hi Binh,
Have a look at this thread from January of this year. The excellent answers from Aaron and Steven from Cisco systems address this exact problem.
http://forum.cisco.com/eforum/servlet/NetProf?page=netprof&forum=IP%20Communications%20and%20Video&topic=IP%20Telephony&CommCmd=MB%3Fcmd%3Dpass_through%26location%3Doutline%40%5E1%40%40.1dda5362/2#selected_message
Hope this helps!
Rob
Please remember to rate helpful posts..........
Similar Messages
-
WCF Service hosted in Azure Cloud Service errors after published
I have a project with several WCF services (mix of REST and SOAP). The project has been running On-Prem for 6 months without an issue. We are moving this to Azure but have run into an issue that will prevent us from going live.
The project uses Autofac for it's IOC. We are gonig to host this in a Cloud Service in Azure. Everything appears to work correctly when running locally in the Azure Emulator however once we deploy using the Cloud Service project, everything builds
and deploys correctly, but we receive the following error when trying to access a service.
Server Error in '/' Application.
Value cannot be null. Parameter name: key
Description:
An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the
code. Exception Details: System.ArgumentNullException: Value cannot be null. Parameter name: key
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using
the exception stack trace below.
Stack Trace:
[ArgumentNullException: Value cannot be null.
Parameter name: key]
System.ThrowHelper.ThrowArgumentNullException(ExceptionArgument argument) +48
System.Collections.Generic.Dictionary`2.FindEntry(TKey key) +38
System.Collections.Generic.Dictionary`2.TryGetValue(TKey key, TValue& value) +20
System.ServiceModel.Dispatcher.WebHttpDispatchOperationSelector..ctor(ServiceEndpoint endpoint) +2459
System.ServiceModel.Description.WebHttpBehavior.GetOperationSelector(ServiceEndpoint endpoint) +125
System.ServiceModel.Description.WebHttpBehavior.ApplyDispatchBehavior(ServiceEndpoint endpoint, EndpointDispatcher endpointDispatcher) +1955
System.ServiceModel.Description.DispatcherBuilder.InitializeServiceHost(ServiceDescription description, ServiceHostBase serviceHost) +4245
System.ServiceModel.ServiceHostBase.InitializeRuntime() +119
System.ServiceModel.ServiceHostBase.OnOpen(TimeSpan timeout) +45
System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout) +553
System.ServiceModel.HostingManager.ActivateService(ServiceActivationInfo serviceActivationInfo, EventTraceActivity eventTraceActivity) +350
System.ServiceModel.HostingManager.EnsureServiceAvailable(String normalizedVirtualPath, EventTraceActivity eventTraceActivity) +1614
[ServiceActivationException: The service '/Event/Calendar' cannot be activated due to an exception during compilation. The exception message is: Value cannot be null.
Parameter name: key.]
System.Runtime.AsyncResult.End(IAsyncResult result) +925
System.ServiceModel.Activation.HostedHttpRequestAsyncResult.End(IAsyncResult result) +528
System.ServiceModel.Activation.AspNetRouteServiceHttpHandler.EndProcessRequest(IAsyncResult result) +107
System.Web.CallHandlerExecutionStep.OnAsyncHandlerCompletion(IAsyncResult ar) +151
It appears that it's having an issue with the service configuration endpoint. That is registered through Autofac WCF integration using the OOTB RouteTable here:
RouteTable.Routes.Add(new ServiceRoute("Event/Calendar", new AutofacWebServiceHostFactory(), typeof(CalendarSvc)));
All of this works fine in IIS and the local Azure emulator, but once deployed to the cloud service is where we get an issue.I don't know Autofac. What is it doing? If you use a normal WCF REST service, or ASP.NET Web API, do you see the same issue? If it does work, you may want to post a question on Autofac's forum:
https://github.com/autofac/Autofac/issues. -
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 moreHi ,
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 -
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 -
The DHCP Service failed to see a directory server for authorization error
Hi Experts,
"The DHCP Service failed to see a directory server for authorization error"
I have DHCP Server installed on the same server where Active directory is installed its a domain controller, when I see the event logs I saw the above error.
This alert comes a number of times, just after the error
"The DHCP/BINL service on the local machine, belonging to the Windows Administrative domain eg.com.pk, has determined that it is authorized to start. It is servicing clients now."
Please somebody suggest some solution for this.
TechSpec90Two questios:
Is the server a domain controller?
And, according to this, "The DHCP/BINL service on the local machine, belonging to the Windows Administrative domain eg.com.pk, has determined that it is authorized to start. It is servicing clients now", the service eventually do start, yes?
Best Regards,
Jesper Vindum, Denmark
Systems Administrator
Help the forum: Monitor(alert) your threads and vote helpful replies or mark them as answer, if it helps solving your problem. -
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 -
Report on Journals, SQL reporting service error
Hi Experts, I have one issue on BPC MS 5.1 "Reports on Journal" issue. When trying to run the report on journals, the pop-up web base screen returning "SQL Reporting Service Error". Going to check the SQL reporting services configuration, all the services are green beside the two optional configurations - "Sharepoint Integration" and "Encryption Keys", and going to webadmin tasks - publish reports, all the items have been build and published. Any clue?
Thanks
ThomasThanks Sorin, I have no access to the SQL currently, I will get the info ASAP with our basis. By the way, when I run the report from BPC server side, the extra msg came out(not only : Error Msg: Reporting Services Error)
Error Msg: Reporting Services Error
The item '/XXXAPPset/JEF_LEGALAPP_ByUser' cannot be found. (rsItemNotFound)
Is this mean something missing when system trying to build the report? since I can't find the Journal report format when I open the link "Http://domain/reports"
Thanks and Regards,
Thomas -
How can I make DHCP Service automatically assign IP addresses?
We decided on using OS X Server's DHCP service rather than depend on our router to dole out IPs. Here's the size and shape of our local subnet:
Range: 192.168.0.0 to 192.168.7.255
Mask: 255.255.248.0
Router: 192.168.1.1
DNS: ....etc...
We're trying to have the DHCP block managed as 192.168.2.0 through 192.168.2.255. Maybe I'm missing something, but shouldn't DHCP automatiScally assign IPs in that range every time someone plugs in a computer? Right now we're having to enter MAC + IP static maps manually into Server Admin, which is a major pain. How can we fix that so it becomes automatic?
Here's how DHCP service is set on our quad-Ethernet Xserve Xeon. en0 / en1 / en2 / en3 are all set up the same, but only en0 is checked:
GENERAL:
Subnet Name: Our LAN (en0)
Starting IP Address: 192.168.2.0
Ending IP Address: 192.168.2.255
Subnet Mask: 255.255.248.0
Network Interface: en0
Router: 192.168.1.1
Lease Time: 4 hours
DNS Servers:
192.168.1.100.... etc.
Default Search Domain: ourdomain.private
LDAP:
Server Name: (blank)
Search Base: (blank)
Port: (Leave blank to use the default port)
[ ] LDAP over SSL
URL:
WINS:
WINS/NBNS Primary Server: 10.0.1.20
WINS/NBNS Secondary Server: 10.0.1.21
NBDD Server: 1.0.1.22
NBT Node Type: Not Set
NetBIOS Scope ID: (blank)
I'm stuck.... I thought all I'd have to do is define a suitable range, like the 256 addresses in the middle of our DHCP block, but it's not enough. Your help is certainly appreciated.
- BertThis morning I stumbled onto the solution (at least a partial solution). I noticed in /var/log/system.log that there were warnings to the effect of "Hey -- you've got disabled DHCP ports that have conflicting ranges with your enabled DHCP port." Previously, I hadn't thought this was a major error, but when I deleted the three disabled ports from DHCP (en1, en2, and en3) and restarted DHCP then everything started working correctly. Hosts that were previously not getting IP addresses assigned because they weren't listed in Static Maps are now getting addresses.
The log entries looked basically like this:
Apr 19 09:54:38 myserver servermgrd[50]: servermgr_dhcp:bootp config:Error:Subnets 'My LAN (en2)' and 'My LAN (en0)' have overlapping ranges: '1\
92.168.2.0-192.168.2.255' overlaps '192.168.2.0-192.168.2.255'
Apr 19 09:54:38 myserver servermgrd[50]: servermgr_dhcp:bootp config:Error:Subnets 'My LAN (en2)' and 'My LAN (en3)' have overlapping ranges: '1\
92.168.2.0-192.168.2.255' overlaps '192.168.2.0-192.168.2.255' - 'My LAN (en3)' is not active
Apr 19 09:54:38 myserver servermgrd[50]: servermgr_dhcp:bootp config:Error:Subnets 'My LAN (en2)' and 'My LAN (en1)' have overlapping ranges: '1\
92.168.2.0-192.168.2.255' overlaps '192.168.2.0-192.168.2.255' - 'My LAN (en1)' is not active
Apr 19 09:54:38 myserver servermgrd[50]: servermgr_dhcp:bootp config:Error:Subnets 'My LAN (en0)' and 'My LAN (en2)' have overlapping ranges: '1\
92.168.2.0-192.168.2.255' overlaps '192.168.2.0-192.168.2.255' - 'My LAN (en2)' is not active
Apr 19 09:54:38 myserver servermgrd[50]: servermgr_dhcp:bootp config:Error:Subnets 'My LAN (en0)' and 'My LAN (en3)' have overlapping ranges: '1\
92.168.2.0-192.168.2.255' overlaps '192.168.2.0-192.168.2.255' - 'My LAN (en3)' is not active
: and so on
The next problem I need to work through is why there's huge amounts of DHCP-related traffic in the logs. It's clogging up with stuff like this:
Apr 19 10:33:40 fannxfile bootpd[54475]: DHCP DISCOVER [en3]: 1,0:e:8:eb:47:90 <SipuraSPA>
Apr 19 10:33:40 fannxfile bootpd[54475]: replying to 192.168.2.44
Apr 19 10:33:40 fannxfile bootpd[54475]: OFFER sent <no hostname> 192.168.2.44 pktsize 303
Apr 19 10:33:40 fannxfile bootpd[54475]: service time 0.000404 seconds
Apr 19 10:33:40 fannxfile bootpd[54475]: DHCP DISCOVER [en0]: 1,0:e:8:eb:47:90 <SipuraSPA>
Apr 19 10:33:40 fannxfile bootpd[54475]: replying to 192.168.2.44
Apr 19 10:33:40 fannxfile bootpd[54475]: OFFER sent <no hostname> 192.168.2.44 pktsize 303
Apr 19 10:33:40 fannxfile bootpd[54475]: service time 0.000385 seconds
Apr 19 10:33:40 fannxfile bootpd[54475]: DHCP DISCOVER [en1]: 1,0:e:8:eb:47:90 <SipuraSPA>
Apr 19 10:33:40 fannxfile bootpd[54475]: replying to 192.168.2.44
Apr 19 10:33:40 fannxfile bootpd[54475]: OFFER sent <no hostname> 192.168.2.44 pktsize 303
Apr 19 10:33:40 fannxfile bootpd[54475]: service time 0.000363 seconds
Apr 19 10:33:40 fannxfile bootpd[54475]: DHCP REQUEST [en2]: 1,0:e:8:eb:47:90 <SipuraSPA>
Apr 19 10:33:40 fannxfile bootpd[54475]: replying to 192.168.2.44
Apr 19 10:33:40 fannxfile bootpd[54475]: ACK sent <no hostname> 192.168.2.44 pktsize 303
Apr 19 10:33:40 fannxfile bootpd[54475]: service time 0.000597 seconds
Apr 19 10:33:40 fannxfile bootpd[54475]: DHCP REQUEST [en3]: 1,0:e:8:eb:47:90 <SipuraSPA>
Apr 19 10:33:40 fannxfile bootpd[54475]: service time 0.000103 seconds
Apr 19 10:33:40 fannxfile bootpd[54475]: DHCP REQUEST [en0]: 1,0:e:8:eb:47:90 <SipuraSPA>
Apr 19 10:33:40 fannxfile bootpd[54475]: service time 0.000298 seconds
Apr 19 10:33:40 fannxfile bootpd[54475]: DHCP REQUEST [en1]: 1,0:e:8:eb:47:90 <SipuraSPA>
Apr 19 10:33:40 fannxfile bootpd[54475]: service time 0.000153 seconds
Apr 19 10:33:40 fannxfile bootpd[54475]: DHCP REQUEST [en2]: 1,0:e:8:eb:47:90 <SipuraSPA>
Apr 19 10:33:40 fannxfile bootpd[54475]: service time 0.000134 seconds
Apr 19 10:33:40 fannxfile bootpd[54475]: DHCP REQUEST [en3]: 1,0:e:8:eb:47:90 <SipuraSPA>
Apr 19 10:33:40 fannxfile bootpd[54475]: service time 0.000139 seconds
Apr 19 10:33:40 fannxfile bootpd[54475]: DHCP REQUEST [en0]: 1,0:e:8:eb:47:90 <SipuraSPA>
Apr 19 10:33:40 fannxfile bootpd[54475]: service time 0.000125 seconds
Apr 19 10:33:40 fannxfile bootpd[54475]: DHCP REQUEST [en1]: 1,0:e:8:eb:47:90 <SipuraSPA>
Apr 19 10:33:40 fannxfile bootpd[54475]: service time 0.000174 seconds
This is happening REALLY fast. Every second there's a block of log entries like the above. I don't get it because I've set the lease times to 4 hours. I'll reset the leases back to 12 hours, but I don't understand what's causing the rapid fire log entries.
Perhaps the smart thing to do at this point is to reboot the server.
To answer some of your specific questions:
Q: Have you tried specifying the range as 192.168.0.1 - 192.168.7.254 instead? Please don't take this the wrong way but is the service actually running?
A: Yes, definitely up and running. Hosts that are in the static map were getting addresses. After deleting the three disabled Ethernet ports with conflicting ranges, I'm also seeing hosts that have not been entered into static maps appearing with dynamic IP addresses, which is what we wanted.
Regarding the suggestion to set the network range to 192.168.0.1 - 192.168.7.254: That's the range the way it was originally set, but I thought what the range was supposed to be was the smaller block of addresses you wanted DHCP to draw from out of your total subnet. I may be wrong, but doesn't DHCP service already know your total network size from the network mask? [255.255.248.0 in our case] This implies that our subnet ranges from 192.168.0.0 to 192.168.7.255 (including base and broadcast addresses at both ends).
My thought was that the "Starting IIP Address" and "Ending IP Address" wanted to be the range of addresses in that that I wanted to use as a pool for DHCP. Hence 192.168.2.0 through 192.168.2.255. We have devices with static IP addresses on our network (servers, printers, and our VoIP phone system, mostly) on 192.168.0.xxx, 192.168.1.xxx and 192.168.3.xxx, and if DHCP doubly assigns addresses in these ranges to our workstations, then we're in big trouble.
Q: sudo serveradmin fullstatus dhcp
A: ...that produces the following output now following deletion of the DHCP ports with conflicting ranges:
fannxfile:log root# serveradmin fullstatus dhcp
dhcp:setStateVersion = 1
dhcp:servicePortsAreRestricted = "NO"
dhcp:numConfiguredStaticMaps = 43
dhcp:dhcpLeasesArray:arrayindex:0:timeLeft = 12201
dhcp:dhcpLeasesArray:arrayindex:0:clientID = ""
dhcp:dhcpLeasesArray:arrayindex:0:computerName = ""
dhcp:dhcpLeasesArray:arrayindex:0:macAddress = "00:1b:63:17:a3:bd"
dhcp:dhcpLeasesArray:arrayindex:0:ipAddress = "192.168.2.21"
dhcp:dhcpLeasesArray:arrayindex:1:timeLeft = 12168
dhcp:dhcpLeasesArray:arrayindex:1:clientID = ""
dhcp:dhcpLeasesArray:arrayindex:1:computerName = ""
dhcp:dhcpLeasesArray:arrayindex:1:macAddress = "00:1b:63:17:a3:bd"
dhcp:dhcpLeasesArray:arrayindex:1:ipAddress = "192.168.2.9"
dhcp:state = "RUNNING"
dhcp:logPaths:systemLog = "/var/log/system.log"
dhcp:backendVersion = "10.5"
dhcp:timeOfModification = "2009-04-19 10:05:46 -0700"
dhcp:numDHCPActiveClients = 2
dhcp:numDHCPLeases = 2
dhcp:timeOfSnapShot = "2009-04-19 10:43:09 -0700"
dhcp:timeServiceStarted = "2009-04-19 10:05:46 -0700"
dhcp:readWriteSettingsVersion = 1
dhcp:servicePortsRestrictionInfo = emptyarray
-- Bert Sierra -
BK AGENT SERVICE ERROR DOMAIN ERROR 6.
I was sent an .iba file from someone, when I went to publish and open the ibooks file I get that error. Never seen before any help?
BK AGENT SERVICE ERROR DOMAIN ERROR 6.Since publish from .iba and open from .ibooks require two totally different apps, which one was it that gave you the error? If iBooks, then on what device?
-
WorkFlow Error when publishing
Hello,
I am having errors publishing workflows. This was working and all of a sudden stopped. From the error message I am taking it as a permissions issue?
Here is the code it spits out:
System.InvalidOperationException: Operation failed with error System.UnauthorizedAccessException: Attempted to perform an unauthorized operation.
at Microsoft.SharePoint.SPAppPrincipalManager.GetManager(SPWeb web)
at Microsoft.SharePoint.WorkflowServices.SPWebWorkflowSecurityContext.EnsureAppPrincipal(SPWeb elevatedWeb)
at Microsoft.SharePoint.WorkflowServices.SPWebWorkflowSecurityContext.<SetupApplicationEcosystem>b__3()
at Microsoft.SharePoint.SPSecurity.<>c__DisplayClass5.<Run
Anyone have any thoughts? This happens with all sorts of workflows, even basic ones as shown in the above example!
Thanks,
WillHi,
For your issue, Re-register the workflow service using command:
Register-SPWorkflowService -SPSite 'https://myhost/mysite' -WorkflowHostUri 'https://workflowhost' -AllowOAuthHttp -Force
Reopened SharePoint Designer again and test again.
Here are similar posts, you can use as a reference:
https://social.technet.microsoft.com/Forums/en-US/61b2cfad-355d-4a43-8dd6-7d6813cd1b2f/sharepointdesigner-error-when-publishing-a-workflow?forum=sharepointcustomizationprevious
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,
Lisa Chen
Lisa Chen
TechNet Community Support -
Exception caught if error is raised in Service Error Handler
Can any one help me on this? Im not able to understand the funda for the behaviour?
Proxy Service A calls proxy service B using Publish action. In proxyservice B - service error handler, Im raising an error with customised message. Proxy service B routes to another proxy service C which routes to Business service.
If my business service gives me timed out , error is handled at Proxy service C error handler , and again Proxy Service B error handler is invoked. Here my code stops where Im raising the error.
When I raise error in Service Handler where it is being caught?
Thank you in advance.
Regards,
VyshnaviHi Vyshnavi,
There are four levels where you may define an Error Handler and it will catch errors related to this level only. If it could not handle any error reached to it, it will propagate the error to the higher level error handler. All errors which can not be handled at lower levels, System Error Handler, handles those.
To know more about this, please refer -
http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/userguide/modelingmessageflow.html#wp1040161
http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/userguide/modelingmessageflow.html#wp1128288
Regards,
Anuj -
Error when Publish data to passive cache
Hi,
I am using active-passive push replication. When I add data to active cache, the data added to cache but get the below error during publish data to passive cache.
011-03-31 22:38:06.014/291.473 Oracle Coherence GE 3.6.1.0 <Error> (thread=Proxy:ExtendTcpProxyService:TcpAcceptor, member=1): Failed to publish EntryOperation{siteName=site1, clusterName=Cluster1, cacheName=dist-contact-cache, operation=Insert, publishableEntry=PublishableEntry{key=Binary(length=12, value=0x154E094D65656E616B736869), value=Binary(length=88, value=0x12813A15A90F00004E094D65656E61
6B736869014E07506C6F74203137024E074368656E6E6169034E0954616D696C4E616475044E06363030303432401A155B014E0524737263244E0E73697465312D436C757374657231), originalValue=Binary(length=0, value=0x)}} to Cache dist-contact-cache because of
(Wrapped) java.io.StreamCorruptedException: invalid type: 78 Class:com.oracle.coherence.patterns.pushreplication.publishers.cache.AbstractCachePublisher
2011-03-31 22:38:06.014/291.473 Oracle Coherence GE 3.6.1.0 <D5> (thread=Proxy:ExtendTcpProxyService:TcpAcceptor, member=1): An exception occurred while processing a InvocationRequest for Service=Proxy:ExtendTcpProxyService:TcpAcceptor: (Wrapped: Failed to publish a batch with the publisher [Active Publisher] on cache[dist-contact-cache]) java.lang.IllegalStateException: Attempted to publish to cache dist-contact-cache
Here is my coherence cache config xml file
!DOCTYPE cache-config SYSTEM "cache-config.dtd">
<cache-config xmlns:sync="class:com.oracle.coherence.patterns.pushreplication.configuration.PushReplicationNamespaceContentHandler">
<caching-schemes>
<sync:provider pof-enabled="true">
<sync:coherence-provider />
</sync:provider>
<caching-scheme-mapping>
<cache-mapping>
<cache-name>dist-contact-cache</cache-name>
<scheme-name>distributed-scheme-with-publishing-cachestore</scheme-name>
<sync:publisher>
<sync:publisher-name>Active Publisher</sync:publisher-name>
<sync:publisher-scheme>
<sync:remote-cluster-publisher-scheme>
<sync:remote-invocation-service-name>remote-site2</sync:remote-invocation-service-name>
<sync:remote-publisher-scheme>
<sync:local-cache-publisher-scheme>
<sync:target-cache-name>dist-contact-cache</sync:target-cache-name>
</sync:local-cache-publisher-scheme>
</sync:remote-publisher-scheme>
<sync:autostart>true</sync:autostart>
</sync:remote-cluster-publisher-scheme>
</sync:publisher-scheme>
</sync:publisher>
</cache-mapping>
</caching-scheme-mapping>
<proxy-scheme>
<service-name>ExtendTcpProxyService</service-name>
<thread-count>5</thread-count>
<acceptor-config>
<tcp-acceptor>
<local-address>
<address>localhost</address>
<port>9099</port>
</local-address>
</tcp-acceptor>
</acceptor-config>
<autostart>true</autostart>
</proxy-scheme>
<remote-invocation-scheme>
<service-name>remote-site2</service-name>
<initiator-config>
<tcp-initiator>
<remote-addresses>
<socket-address>
<address>localhost</address>
<port>5000</port>
</socket-address>
</remote-addresses>
<connect-timeout>2s</connect-timeout>
</tcp-initiator>
<outgoing-message-handler>
<request-timeout>5s</request-timeout>
</outgoing-message-handler>
</initiator-config>
<serializer>
<class-name>com.tangosol.io.pof.ConfigurablePofContext</class-name>
</serializer>
</remote-invocation-scheme>
</caching-schemes>
</cache-config>Please find below for active and passive server start command, log files.
Thanks.
Active server start command
java -server -showversion -Xms128m -Xmx128m -Dtangosol.coherence.ttl=0 -Dtangosol.coherence.cacheconfig=active-cache-config.xml
-Dtangosol.coherence.cluster="Cluster1" -Dtangosol.coherence.site="site1" -Dtangosol.coherence.clusteraddress="224.3.6.2"
-Dtangosol.coherence.clusterport="3001" -Dtangosol.pof.config=pof-config.xml -cp "config;lib\custom-types.jar;lib\coherence.jar;lib/coherence-common-1.7.3.20019.jar;lib/coherence-pushreplicationpattern-3.0.3.20019.jar;lib/coherence-messagingpattern-2.7.3.20019.jar;" com.tangosol.net.DefaultCacheServer
Passive server start command
java -server -showversion -Xms128m -Xmx128m -Dtangosol.coherence.ttl=0 -Dtangosol.coherence.cacheconfig=passive-cache-config.xml
-Dtangosol.coherence.cluster="Cluster2" -Dtangosol.coherence.site="site2" -Dtangosol.coherence.clusteraddress="224.3.6.3"
-Dtangosol.coherence.clusterport="3003" -Dtangosol.pof.config=pof-config.xml -cp "config;lib\custom-types.jar;
lib\coherence.jar;lib/coherence-common-1.7.3.20019.jar;lib/coherence-pushreplicationpattern-3.0.3.20019.jar;
lib/coherence-messagingpattern-2.7.3.20019.jar;" com.tangosol.net.DefaultCacheServer
Active Server log
<Error> (thread=PublishingService:Thread-3, member=1): Failed to publish the range MessageTracker{MsgId{40-1} } of messages for subscription SubscriptionIdentifier{destinationIdentifier=Identifier{dist-contact-cache}, subscriberIdentifier=Identifier{Active Publisher}} with publisher com.oracle.coherence.patterns.pushreplication.publishers.RemoteClusterPublisher@423d4f Class:com.oracle.coherence.patterns.pushreplication.providers.coherence.CoherencePublishingService
2011-04-01 20:23:20.172/65.972 Oracle Coherence GE 3.6.1.0 <Info> (thread=PublishingService:Thread-3, member=1): Publisher Exception was as follows Class:com.oracle.coherence.patterns.pushreplication.providers.coherence.CoherencePublishingService
(Wrapped: Failed to publish a batch with the publisher [Active Publisher] on cache [dist-contact-cache]) java.lang.IllegalStateException: Attempted to publish t
o cache dist-contact-cache
at com.tangosol.util.Base.ensureRuntimeException(Base.java:293)
at com.oracle.coherence.patterns.pushreplication.publishers.RemoteClusterPublisher$RemotePublishingAgent.run(RemoteClusterPublisher.java:348)
at com.tangosol.coherence.component.net.extend.proxy.serviceProxy.InvocationServiceProxy.query(InvocationServiceProxy.CDB:6)
at com.tangosol.coherence.component.net.extend.messageFactory.InvocationServiceFactory$InvocationRequest.onRun(InvocationServiceFactory.CDB:12)
at com.tangosol.coherence.component.net.extend.message.Request.run(Request.CDB:4)
at com.tangosol.coherence.component.net.extend.proxy.serviceProxy.InvocationServiceProxy.onMessage(InvocationServiceProxy.CDB:9)
at com.tangosol.coherence.component.net.extend.Channel.execute(Channel.CDB:39)
at com.tangosol.coherence.component.net.extend.Channel.receive(Channel.CDB:26)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Peer.onNotify(Peer.CDB:96)
at com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:42)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.IllegalStateException: Attempted to publish to cache dist-contact-cache
at com.oracle.coherence.patterns.pushreplication.publishers.cache.AbstractCachePublisher.publishBatch(AbstractCachePublisher.java:163)
at com.oracle.coherence.patterns.pushreplication.publishers.RemoteClusterPublisher$RemotePublishingAgent.run(RemoteClusterPublisher.java:343)
... 9 more
Caused by: (Wrapped) java.io.StreamCorruptedException: invalid type: 78
at com.tangosol.util.ExternalizableHelper.fromBinary(ExternalizableHelper.java:266)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.PartitionedService$ConverterKeyToBinary.convert(PartitionedService.CDB:16)
at com.tangosol.util.ConverterCollections$ConverterInvocableMap.invoke(ConverterCollections.java:2156)
at com.tangosol.util.ConverterCollections$ConverterNamedCache.invoke(ConverterCollections.java:2622)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.partitionedService.PartitionedCache$ViewMap.invoke(PartitionedCache.CDB:11)
at com.tangosol.coherence.component.util.SafeNamedCache.invoke(SafeNamedCache.CDB:1)
at com.oracle.coherence.patterns.pushreplication.publishers.cache.AbstractCachePublisher.publishBatch(AbstractCachePublisher.java:142)
... 10 moreCaused by: java.io.StreamCorruptedException: invalid type: 78
at com.tangosol.util.ExternalizableHelper.readObjectInternal(ExternalizableHelper.java:2266)
at com.tangosol.util.ExternalizableHelper.readObject(ExternalizableHelper.java:2254)
at com.tangosol.io.DefaultSerializer.deserialize(DefaultSerializer.java:74)
at com.tangosol.util.ExternalizableHelper.deserializeInternal(ExternalizableHelper.java:2708)
at com.tangosol.util.ExternalizableHelper.fromBinary(ExternalizableHelper.java:262)
... 16 more
Passive Server log
2011-04-01 20:23:20.141/56.925 Oracle Coherence GE 3.6.1.0 <Error> (thread=Proxy:ExtendTcpProxyService:TcpAcceptor, member=1): Failed to publish EntryOperation{siteName=site1, clusterName=Cluster1, cacheName=dist-contact-cache, operation=Insert, publishableEntry=PublishableEntry{key=Binary(length=12, value=0x154E094D65656E616B736869), value=Binary(length=88, value=0x12813A15A90F00004E094D65656E616
B736869014E07506C6F74203137024E074368656E6E6169034E0954616D696C4E616475044E06363030303432401A155B014E0524737263244E0E73697465312D436C757374657231), originalValue=Binary(length=0, value=0x)}} to Cache dist-contact-cache because of (Wrapped) java.io.StreamCorruptedException: invalid type: 78 Class:com.oracle.coherence.patterns.pushreplication.publishers.cache.AbstractCachePublisher2011-04-01 20:23:20.141/56.925 Oracle Coherence GE 3.6.1.0 <D5> (thread=Proxy:ExtendTcpProxyService:TcpAcceptor, member=1): An exception occurred while processing a InvocationRequest for Service=Proxy:ExtendTcpProxyService:TcpAcceptor: (Wrapped: Failed to publish a batch with the publisher [Active Publisher] on cache [
dist-contact-cache]) java.lang.IllegalStateException: Attempted to publish to cache dist-contact-cache
at com.tangosol.util.Base.ensureRuntimeException(Base.java:293)
at com.oracle.coherence.patterns.pushreplication.publishers.RemoteClusterPublisher$RemotePublishingAgent.run(RemoteClusterPublisher.java:348)
at com.tangosol.coherence.component.net.extend.proxy.serviceProxy.InvocationServiceProxy.query(InvocationServiceProxy.CDB:6)
at com.tangosol.coherence.component.net.extend.messageFactory.InvocationServiceFactory$InvocationRequest.onRun(InvocationServiceFactory.CDB:12)
at com.tangosol.coherence.component.net.extend.message.Request.run(Request.CDB:4)
at com.tangosol.coherence.component.net.extend.proxy.serviceProxy.InvocationServiceProxy.onMessage(InvocationServiceProxy.CDB:9)
at com.tangosol.coherence.component.net.extend.Channel.execute(Channel.CDB:39)
at com.tangosol.coherence.component.net.extend.Channel.receive(Channel.CDB:26)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Peer.onNotify(Peer.CDB:96)
at com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:42)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.IllegalStateException: Attempted to publish to cache dist-contact-cache
at com.oracle.coherence.patterns.pushreplication.publishers.cache.AbstractCachePublisher.publishBatch(AbstractCachePublisher.java:163)
at com.oracle.coherence.patterns.pushreplication.publishers.RemoteClusterPublisher$RemotePublishingAgent.run(RemoteClusterPublisher.java:343)
... 9 more
Caused by: (Wrapped) java.io.StreamCorruptedException: invalid type: 78
at com.tangosol.util.ExternalizableHelper.fromBinary(ExternalizableHelper.java:266)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.PartitionedService$ConverterKeyToBinary.convert(PartitionedService.CDB:16)
at com.tangosol.util.ConverterCollections$ConverterInvocableMap.invoke(ConverterCollections.java:2156)
at com.tangosol.util.ConverterCollections$ConverterNamedCache.invoke(ConverterCollections.java:2622)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.partitionedService.PartitionedCache$ViewMap.invoke(PartitionedCache.CDB:11)
at com.tangosol.coherence.component.util.SafeNamedCache.invoke(SafeNamedCache.CDB:1)
at com.oracle.coherence.patterns.pushreplication.publishers.cache.AbstractCachePublisher.publishBatch(AbstractCachePublisher.java:142)
... 10 more
Caused by: java.io.StreamCorruptedException: invalid type: 78
at com.tangosol.util.ExternalizableHelper.readObjectInternal(ExternalizableHelper.java:2266)
at com.tangosol.util.ExternalizableHelper.readObject(ExternalizableHelper.java:2254)
at com.tangosol.io.DefaultSerializer.deserialize(DefaultSerializer.java:74)
at com.tangosol.util.ExternalizableHelper.deserializeInternal(ExternalizableHelper.java:2708)
at com.tangosol.util.ExternalizableHelper.fromBinary(ExternalizableHelper.java:262)
... 16 more -
Server 2012 R2 DHCP authentication error (1046-DHCP)
Hello all, here is my story, hope someone can help me solve it.
Goal :
Getting the DHCP running on windows server 2012 R2
Current situation :
We have two different domains in one forest (domain-A & domain-B).
Domain-A has several w2k8r2 servers. In Domain-A we have two server 2008 R2 domain controllers (serverA1 & serverA2). On both servers the DHCP rule is installed and running.
Domain-B has several w2k8r2 servers. In Domain-B we have two server 2008 R2 domain controllers. Both servers don’t have DHCP server role !
We installed 2 w2k12R2 servers (server-b1 & server-b2) in domain-B and promoted to domain controller. We installed the DHCP server role on server-b1 & server-b2 configured the failover. The domain function lever is still w2k8r2.
The change :
In domain-A we unauthorized the DHCP server-A1 & server-A2 and deleted the DHCP server role.
Restarted server–A1 & server-A2 and checked if the DHCP server role is removed.
In domain-B we restarted server-B1 & server-B2. We authorized the DHCP on server-B1 & server-B2.
The error :
The DHCP didn’t go online, it gives the following error message in the event viewer (this is the only error message about the DHCP server)
Eventid 1046, DHCP-Server
The DHCP/BINL service on the local machine, belonging to the Windows Administrative domain Domain-B, has determined that it is not authorized to start.
It has stopped servicing clients. The following are some possible reasons for this:
This machine is part of a directory service enterprise and is not authorized in the same domain.
(See help on the DHCP Service Management Tool for additional information).
This machine cannot reach its directory service enterprise and it has encountered another DHCP service on the network belonging to
a directory service enterprise on which the local machine is not authorized.
Some unexpected network error occurred.
Tried solutions :
1) checked the local network settings, the dns server is the one in the old forest (domain-A) this is correct !
2) Checked with adsiedit.msc if there was still an entry that was looking at server-A1 & server-A2. Nothing found. 3) I unauthorized the 2 new servers (server-b1 and server-b2) I installed a new w2k12R2 server in domain-A1, installed the dhcp server role
only. Tried to authorizes the dhcp server but the exact same error.
looking forward to all the ideas, and the solution
J
Design is the TechnologyHi,
According to your description, when we installed a new windows server 2012 r2 in the domain A and only installed the DHCP role, the authorization was still not success. So please check if the unauthorized and authorized process was success. To verify if
the DHCP servers have been authorized, please try to run netsh dhcp show server
command, then we can see the DHCP server which was authorized. And you mentioned that you have checked with ADSIEdit to see if there was an entry. Yes, we can make full use of ADSIEdit. If a DHCP server was authorized successfully, there must be an
entry about the DHCP server in the ADSIEdit. So please check if there are some entries in the ADSIEdit of all your DCs in the domain. Ensure that only one entry about this new windows server 2012 r2 in the ADSIEdit.
If there are different in the several DCs, please try to use AD replication to make the data consistent.
And we must log on the server as an administrator to complete this operation.
To check the entry, please follow steps below,
1. Start adsiedit.msc.
2. Open the Configuration container.
3. Expand Services.
4. Expand Net Services.
Best Regards,
Tina -
Distribution Service: "Error occurred while loading an article."
Hi,
I am finishing a folio with 53 articles.
While uploading to Distribution Service I have got this message more than 20 times:
Every time after this message I need to start the publishing process again. The articles already send pass very soon and than it slows down and after one or two new articles the error occurs again.
So it took me 4 hours to publish a folio with about 140 MB!
This could not be a problem of my internet connection. It is very fast and absolutly stable.
What is the reason for this?
Thanks for your help.
AlmuteHi,
after it worked 2 hours ago very fine - now it is stopping after a few articles again!
Am 11.12.2011 um 16:26 schrieb Klaasjan Tukker:
Re: Distribution Service: "Error occurred while loading an article."
created by Klaasjan Tukker in Digital Publishing Suite - View the full discussion
the seattle team has been working on this for the past couple of hours, things should be working. please check. if not, send me a PM.
klaasjan tukker
adobe
Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/4077368#4077368
To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/4077368#4077368. In the Actions box on the right, click the Stop Email Notifications link.
Start a new discussion in Digital Publishing Suite by email or at Adobe Forums
For more information about maintaining your forum email notifications please go to http://forums.adobe.com/message/2936746#2936746.
Best regards
Almute Kraus
...........exclam.................................
email [email protected]
fon +49.211.938899.30
fax +49.211.938899.39
mail helmut kraus
leuchtenberger kirchweg 46a
40489 düsseldorf
germany
......... www.exclam.de .......................... -
The DHCP service failed to see a directory server for authorization.
We have two DHCP servers hosted on Hyper-V.
But after shutdown activity at our DC, the servers gave an usual issue.
"The DHCP service failed to see a directory server for authorization."
We have rebooted number of time before getting this server into production but it never gave such kind of error.
Also this time the local DC was shutdown.
Please suggest the necessary steps to be taken.Hi,
The authorized DHCP server contacts a domain controller every 60 min to detect/redetect his status. Maybe your DHCP has tried to reach the DC which was offline thus throwing that error. Are you still having issues with DHCP server servicing clients?
Once the server talks to a DC and checks that his authorized the service will start leasing IPs to clients.
http://technet.microsoft.com/en-us/library/cc754493.aspx
http://technet.microsoft.com/en-us/library/cc781697(v=ws.10).aspx
Regards,
Calin
Maybe you are looking for
-
Z77A-GD65 power issue/bad system board?
Looking for advice. I am afraid its a bad board, but some symptoms point at power which also makes no sense. This is what the WHOLE system should look like. MSI Z77A-GD65 system board Intel 3770K 3.5Ghz Anted Kuhler H20 620 G.Skills RipJaws 16GB 1600
-
This is going to sound stupid but HELLLPPP ME. :(
so, my computer got that trojan virus and my mother decided to pretty much refresh my whole computer by using some anti-virus download which deleted everything that the computer did not come with, this included my itunes and all the music that was in
-
Change a category name in numbers
I am trying to set up the personel budget and want to change or add category names. I cannot do this, would anyone know how? Some of the names there are of no use to me and do not fit my needs, thanks
-
Merging two iPhoto Libraries from two different MACs
Can I blend together two iPhoto libraries? I have a library on another MAC and would love to move it to my laptop merging with the existing iPhoto. How I can do that? I just afraid to overwrite the original library.
-
Setting up OracleXE as SQL Server Linked server
I have recently installed OracleXE locally following the standard installation instructions. On the same machine I also have a local instance of SQL Server. I want to set OracleXE as a linked server to the Instance of SQL Server. Can any provide me w