10-02-2012 07:07 AM
Hi,
We have a CPO 2.3.1 that refuses to connect to vCenter (see log extract at the end of the post).
We recently changed our vCenter server (part of an update to 5.1).
We tried following workarounds:
No change at all...
Would you have a clue on how to correct that?
Thank you.
Regards,
Pierre
||235|2012/10/02 15:46:21.667|6072||||WCF: <TraceRecord xmlns="http://schemas.microsoft.com/2004/10/E2ETraceEvent/TraceRecord" Severity="Error"><TraceIdentifier>http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.TraceHandledException.aspx</TraceIdentifier><Description>Handling an exception.</Description><AppDomain>Tidal.Automation.Server.exe</AppDomain><Exception><ExceptionType>Tidal.Scheduler.Common.Communications.CommunicationException, Tidal.Scheduler.Common, Version=2.3.0.0, Culture=neutral, PublicKeyToken=fba593b23cf207cd</ExceptionType><Message>The attempt to connect to (VMware vCenter Server (603)@VMware vCenter Server (603)) has failed due to following error: Failed to connect to VMware web service: Invalid keystore.</Message><StackTrace> at Tidal.Automation.Server.JavaAdapterBase.PerformServerAssistedOperation(ServerAssistedOperation operation, TargetConfiguration target, RuntimeUserConfiguration runtimeUser)
at Tidal.Automation.Server.JavaAdapterBase.PerformServerAssistedOperation(ServerAssistedOperation operation)
at Tidal.Automation.Engine.Core.Adapter.SuspendableAdapter.&lt;&gt;c__DisplayClass1c.&lt;PerformServerAssistedOperation&gt;b__1b(IAdapter adapter)
at Tidal.Automation.Engine.Core.AdapterLifecycleManager.PerformAdapterAction(Guid adapterId, AdapterAction action, Boolean haltingAction, Int32 remainingRetries)
at Tidal.Automation.Engine.Core.AdapterLifecycleManager.PerformAdapterAction(Guid adapterId, AdapterAction action, Boolean haltingAction)
at Tidal.Automation.Engine.Core.AdapterLifecycleManager.PerformAdapterAction(Guid adapterId, AdapterAction action)
at Tidal.Automation.Engine.Core.Adapter.SuspendableAdapter.PerformServerAssistedOperation(ServerAssistedOperation operation)
at Tidal.Automation.Engine.Core.AdapterSystem.PerformServerAssistedOperation(ServerAssistedOperation operation)
at Tidal.Automation.Server.WebService.AdapterService.PerformServerAssistedOperation(ServerAssistedOperation operation)
at SyncInvokePerformServerAssistedOperation(Object , Object[] , Object[] )
at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]&amp; outputs)
at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc&amp; rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc&amp; rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc&amp; rpc)
at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)</StackTrace><ExceptionString>Tidal.Scheduler.Common.Communications.CommunicationException: The attempt to connect to (VMware vCenter Server (603)@VMware vCenter Server (603)) has failed due to following error: Failed to connect to VMware web service: Invalid keystore.
at Tidal.Automation.Server.JavaAdapterBase.PerformServerAssistedOperation(ServerAssistedOperation operation, TargetConfiguration target, RuntimeUserConfiguration runtimeUser)
at Tidal.Automation.Server.JavaAdapterBase.PerformServerAssistedOperation(ServerAssistedOperation operation)
at Tidal.Automation.Engine.Core.Adapter.SuspendableAdapter.&lt;&gt;c__DisplayClass1c.&lt;PerformServerAssistedOperation&gt;b__1b(IAdapter adapter)
at Tidal.Automation.Engine.Core.AdapterLifecycleManager.PerformAdapterAction(Guid adapterId, AdapterAction action, Boolean haltingAction, Int32 remainingRetries)
at Tidal.Automation.Engine.Core.AdapterLifecycleManager.PerformAdapterAction(Guid adapterId, AdapterAction action, Boolean haltingAction)
at Tidal.Automation.Engine.Core.AdapterLifecycleManager.PerformAdapterAction(Guid adapterId, AdapterAction action)
at Tidal.Automation.Engine.Core.Adapter.SuspendableAdapter.PerformServerAssistedOperation(ServerAssistedOperation operation)
at Tidal.Automation.Engine.Core.AdapterSystem.PerformServerAssistedOperation(ServerAssistedOperation operation)
at Tidal.Automation.Server.WebService.AdapterService.PerformServerAssistedOperation(ServerAssistedOperation operation)
at SyncInvokePerformServerAssistedOperation(Object , Object[] , Object[] )
at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]&amp; outputs)
at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc&amp; rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc&amp; rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc&amp; rpc)
at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)</ExceptionString></Exception></TraceRecord>
||236|2012/10/02 15:46:21.667|6072||||An exception that was not of type RhapsodyException was caught while a webmethod call was being made. This exception has been caught and genericized.
||237|2012/10/02 15:46:21.667|6072||||EXCEPTION (Tidal.Scheduler.Common.Communications.CommunicationException): The attempt to connect to (VMware vCenter Server (603)@VMware vCenter Server (603)) has failed due to following error: Failed to connect to VMware web service: Invalid keystore.
Stack Trace: at Tidal.Automation.Server.JavaAdapterBase.PerformServerAssistedOperation(ServerAssistedOperation operation, TargetConfiguration target, RuntimeUserConfiguration runtimeUser)
at Tidal.Automation.Server.JavaAdapterBase.PerformServerAssistedOperation(ServerAssistedOperation operation)
at Tidal.Automation.Engine.Core.Adapter.SuspendableAdapter.<>c__DisplayClass1c.<PerformServerAssistedOperation>b__1b(IAdapter adapter)
at Tidal.Automation.Engine.Core.AdapterLifecycleManager.PerformAdapterAction(Guid adapterId, AdapterAction action, Boolean haltingAction, Int32 remainingRetries)
at Tidal.Automation.Engine.Core.AdapterLifecycleManager.PerformAdapterAction(Guid adapterId, AdapterAction action, Boolean haltingAction)
at Tidal.Automation.Engine.Core.AdapterLifecycleManager.PerformAdapterAction(Guid adapterId, AdapterAction action)
at Tidal.Automation.Engine.Core.Adapter.SuspendableAdapter.PerformServerAssistedOperation(ServerAssistedOperation operation)
at Tidal.Automation.Engine.Core.AdapterSystem.PerformServerAssistedOperation(ServerAssistedOperation operation)
at Tidal.Automation.Server.WebService.AdapterService.PerformServerAssistedOperation(ServerAssistedOperation operation)
at SyncInvokePerformServerAssistedOperation(Object , Object[] , Object[] )
at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)
at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)
Solved! Go to Solution.
10-02-2012 07:13 AM
You have an invalid keystore file because the HTTPS certification has changed. You need to delete the old keystore file and restart the CPO server and then reconnect/run something against vCenter.
There is also a possibility for Adatper Host Framework/java issues that I have seen commonly.
If you need more help, you'll need to open a TAC case with your services contract please. We normally try to not troubleshoot logs on the forums.
-Shaun Roberts
CIAC/CPO Support Team Lead
10-02-2012 07:13 AM
You have an invalid keystore file because the HTTPS certification has changed. You need to delete the old keystore file and restart the CPO server and then reconnect/run something against vCenter.
There is also a possibility for Adatper Host Framework/java issues that I have seen commonly.
If you need more help, you'll need to open a TAC case with your services contract please. We normally try to not troubleshoot logs on the forums.
-Shaun Roberts
CIAC/CPO Support Team Lead
10-02-2012 07:28 AM
Thank you Shaun and sorry for the logs...
By the way, if someone needs to do that in the future, the keystore is located at
Regards,
Pierre
10-02-2012 07:30 AM
Pierre,
No need to apologize, just FYI
Yes, the keystore is located in the services directory of your install directory of CPO. Should be file vmwareservice.keystore
-shaun
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