03-05-2013 10:25 AM
TEO 2.3.5 SAP adpater Pre-requisite Error
Trying to setup an SAP ABAP connection. Satisfied the pre-requisite of SAP NCO sapnco30dotnet40P_7-20007348, still get the following error while checking the pre-requisite.
Unable to check for prerequisites:
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
This is what I see in the logs-
/StackTrace><ExceptionString>System.ServiceModel.CommunicationObjectAbortedException: The communication object, System.ServiceModel.Channels.TransportReplyChannelAcceptor+TransportReplyChannel, cannot be used for communication because it has been Aborted.</ExceptionString></Exception></TraceRecord>
||735|2013/03/01 07:33:30.028|2084|PoolThread:57|||WCF: System.ServiceModel Error: 131075 :
||736|2013/03/01 07:33:30.029|2084|PoolThread:57|||WCF: <TraceRecord xmlns="
http://schemas.microsoft.com/2004/10/E2ETraceEvent/TraceRecord
" Severity="Error"><TraceIdentifier>http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.ThrowingException.aspx</TraceIdentifier><Description>Throwing an exception.</Description><AppDomain>Tidal.Automation.Server.exe</AppDomain><Source>System.ServiceModel.Channels.TransportReplyChannelAcceptor+TransportReplyChannel/59871390</Source><Exception><ExceptionType>System.ServiceModel.CommunicationObjectAbortedException, System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</ExceptionType><Message>The communication object, System.ServiceModel.Channels.TransportReplyChannelAcceptor+TransportReplyChannel, cannot be used for communication because it has been Aborted.</Message><StackTrace> at System.ServiceModel.Channels.InputQueueChannel`1.EndDequeue(IAsyncResult result, TDisposable&amp; item)
at System.ServiceModel.Dispatcher.ErrorHandlingReceiver.EndTryReceive(IAsyncResult result, RequestContext&amp; requestContext)
at System.ServiceModel.Dispatcher.ChannelHandler.EndTryReceive(IAsyncResult result, RequestContext&amp; requestContext)
at System.ServiceModel.Dispatcher.ChannelHandler.AsyncMessagePump(IAsyncResult result)
at System.Runtime.Fx.AsyncThunk.UnhandledExceptionFrame(IAsyncResult result)
at System.Runtime.AsyncResult.Complete(Boolean completedSynchronously)
at System.Runtime.InputQueue`1.AsyncQueueReader.Set(Item item)
at System.Runtime.InputQueue`1.Shutdown(Func`1 pendingExceptionGenerator)
at System.ServiceModel.Channels.CommunicationObject.Abort()
at System.ServiceModel.Dispatcher.ListenerHandler.AbortChannels()
at System.ServiceModel.Dispatcher.ListenerHandler.OnAbort()
at System.ServiceModel.Channels.CommunicationObject.Abort()
at System.ServiceModel.Dispatcher.ChannelDispatcher.OnAbort()
at System.ServiceModel.Channels.CommunicationObject.Abort()
at System.ServiceModel.ServiceHostBase.OnAbort()
at System.ServiceModel.Channels.CommunicationObject.Abort()
at Tidal.Automation.Server.WebService.WCFHost.StopServiceHost(Object state)
at Tidal.Automation.Common.ThreadPool.OuterWaitCallBack(Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()
</StackTrace><ExceptionString>System.ServiceModel.CommunicationObjectAbortedException: The communication object, System.ServiceModel.Channels.TransportReplyChannelAcceptor+TransportReplyChannel, cannot be used for communication because it has been Aborted.</ExceptionString></Exception></TraceRecord>
||737|2013/03/01 07:33:30.164|2508|MainEngineThread|||Encountered an exception while attempting to kill adapter SAP Solution Manager Adapter (95151695-aacc-4310-af5f-c38abfcea384). Proceeding.
||738|2013/03/01 07:33:30.164|2508|MainEngineThread|||EXCEPTION (Tidal.Automation.Common.Product.RhapsodyException): An attempt was made to stop the adapter named 95151695-aacc-4310-af5f-c38abfcea384 but it appears to have never been started.
Stack Trace: at Tidal.Automation.Engine.Core.AdapterStarter.KillAdapter(Guid adapterId)
at Tidal.Automation.Engine.Core.AdapterLifecycleManager.DisableAdapterStartups()
||739|2013/03/01 07:33:30.165|2508|MainEngineThread|||Encountered an exception while attempting to kill adapter SAP ABAP Adapter (cf6f0f84-a364-4105-b11f-0fef62873b37). Proceeding.
||740|2013/03/01 07:33:30.165|2508|MainEngineThread|||EXCEPTION (Tidal.Automation.Common.Product.RhapsodyException): An attempt was made to stop the adapter named cf6f0f84-a364-4105-b11f-0fef62873b37 but it appears to have never been started.
Stack Trace: at Tidal.Automation.Engine.Core.AdapterStarter.KillAdapter(Guid adapterId)
at Tidal.Automation.Engine.Core.AdapterLifecycleManager.DisableAdapterStartups()
||741|2013/03/01 07:33:30.221|2508|MainEngineThread|||Encountered an exception while attempting to kill adapter SAP Solution Manager Adapter (95151695-aacc-4310-af5f-c38abfcea384). Proceeding.
||742|2013/03/01 07:33:30.221|2508|MainEngineThread|||EXCEPTION (Tidal.Automation.Common.Product.RhapsodyException): An attempt was made to stop the adapter named 95151695-aacc-4310-af5f-c38abfcea384 but it appears to have never been started.
Stack Trace: at Tidal.Automation.Engine.Core.AdapterStarter.KillAdapter(Guid adapterId)
at Tidal.Automation.Engine.Core.AdapterLifecycleManager.DisableAdapterStartups()
||743|2013/03/01 07:33:30.222|2508|MainEngineThread|||Encountered an exception while attempting to kill adapter SAP ABAP Adapter (cf6f0f84-a364-4105-b11f-0fef62873b37). Proceeding.
||744|2013/03/01 07:33:30.222|2508|MainEngineThread|||EXCEPTION (Tidal.Automation.Common.Product.RhapsodyException): An attempt was made to stop the adapter named cf6f0f84-a364-4105-b11f-0fef62873b37 but it appears to have never been started.
Stack Trace: at Tidal.Automation.Engine.Core.AdapterStarter.KillAdapter(Guid adapterId)
at Tidal.Automation.Engine.Core.AdapterLifecycleManager.DisableAdapterStartups()
03-05-2013 10:30 AM
The log snippets are not enough to diagnose this issue.
This should be escalated to development through TAC, with a complete set of diagnostic logs from the product.
03-05-2013 10:31 AM
Please open a TAC case. They can not only get you past the missing prerequisite, but also raise the issue on the bad prerequisite detection error which you are seeing so we can get it fixed in the product.
03-05-2013 10:34 AM
I will open a TAC case for sure but this is in my test environment (a sandbox type replicating the cusotmer env) not a customer instance though.
03-05-2013 10:39 AM
That's fine. TAC does provide support for internal teams for IAC, PO, and CP. Instructions are here: https://supportforums.cisco.com/thread/2108189
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide