Failed initializing the External Content Library with id adam

Question

While trying to expand any publication in CME, I am getting following error:

Failed initializing the External Content Library with id adam. One or more errors occurred. There was an error reading from the pipe: The pipe has been ended. (109, 0x6d). The read operation failed, see inner exception. There was an error reading from the pipe: The pipe has been ended. (109, 0x6d). There was an error reading from the pipe: The pipe has been ended. (109, 0x6d).

StackTrace Information Details: at Tridion.ExternalContentLibrary.DomainModel.MountPoint.GetStubSchemaId(Int32 publicationId) at Tridion.ExternalContentLibrary.DomainModel.UserContext.InitializeMountPoints(IEnumerable1 eclUris) at Tridion.ExternalContentLibrary.DomainModel.UserContext.GetMountPoints(Int32 publicationId) at Tridion.ExternalContentLibrary.Service.EclService2012.GetList(String parentItemId, Int32 pageIndex, EclItemTypes itemTypes, IEnumerable1 basedOnSchema) at SyncInvokeGetList(Object , Object[] , Object[] ) at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs) at Tridion.ExternalContentLibrary.Service.TransactionSupportInvoker.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)

Is there any configuration that I am missing due to which I am getting this error?

Please note, I tried connecting to multiple Adam servers however getting the same error.

Answer 1

I have recently done ADAM integration, i was able to get the content etc without any issue. Please validate your ExternalContentLibary.xml file for following

 <MountPoint type="AdamProvider" version="*" id="Adam" rootItemName="Adam">
            <StubFolders>
                <StubFolder id="tcm:18-527-2" />
            </StubFolders>
            <PrivilegedUserName>domain\username</PrivilegedUserName>
        </MountPoint>

you can also refer this link (Login required) for additional details.

Answer 2

The problem in my case was missing permission to the CM certificate for MTS User and Network Service account. After adding those permissions the connector started working without any issues.