Hi Karl, Thanks for the information. We are actually using Meridio version 5.2 (as I see compatibility matrix, MCF has been tested with version 4.1 and 5.0) Actually we don't have development resources within our team for those kind of purposes yet but that's good to know that might be required.
Regards Kambiz ________________________________ From: Karl Wright <[email protected]> To: "[email protected]" <[email protected]>; Kambiz Niktabar <[email protected]> Sent: Monday, November 3, 2014 3:25 PM Subject: Re: Error while creating Meridio authority connection Hi Kambiz, There are a number of possibilities. I'll list them in order of likelihood. (1) The Meridio API might have changed, so that the WSDLs and XSDs we compile against might need to be updated. What version of Meridio are you working with? (2) It's possible that the plugin would need to be recompiled for the version of Meridio you are using. Unfortunately, we do not have the source for that plugin. The source was owed to MetaCarta as part of their contract with Meridio at the time, but Meridio refused to provide it nonetheless, and all attempts to get hold of it failed, especially after Meridio was bought by Autonomy. If you have the ability to develop against Meridio in a Windows environment, it is likely not that difficult to recreate the service on your own, and contribute it back to the MCF project. The immediate error is definitely not caused by (2), so I'd look into version incompatibility first. Karl On Mon, Nov 3, 2014 at 9:12 AM, Kambiz Niktabar <[email protected]> wrote: Hello, > > >I tried setting up MCF for indexing Meridio. I already installed MetaCartaWebService on Meridio web servers and It seems working fine, but creation of Meridio authority connection fails and I got the following error message. By looking at the MCF debug log, I noticed that it uses LoginUnifiedWithClientWorkstation method to authenticate against Meridio DMWS and that’s where it’s failing. Did I miss any configuration somewhere? > >Threw exception: 'Remote procedure exception: Server was unable to process request. ---> 23000#The object you attempted to access or update does not exist. The object may have been deleted by another user. Refresh the current view and try again. Meridio System: Server1 ##System.Web.Services.Protocols.SoapException: API Error 23000: The object you attempted to access or update does not exist. at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at Meridio.Web.Services.DM.MeridioSOAP.MeridioSOAP.ReqAuthenticate(ReqAuthenticateType ReqAuthenticate1) at Meridio.Web.Services.DM.Libraries.DMConnectionLib.loginUnified(String strClientWorkstation) at Meridio.Web.Services.DM.MeridioDM.LoginUnified(String clientWorkstation) ---> API Error 23000: The object you attempted to access or update does not exist.' > > >Regards > >Kambiz Niktabar > >
