We‘re successfully operating an EMC Centrea integration in our .NET WebApplication using the XAM SDK with the centera VIM-module for about 2 years. By then, we used a mix of the SDK-Dll’s to get the XAM interface working. Those are the dll’s we’re currently running (see also attachment):

SDK API:

FPCore.dll 4.0.710.0

fpos64.dll 3.2.286.0

fpparser.dll 3.2.48.0

FPStreams.dll 4.0.710.0

FPUtils.dll 4.0.710.0

pai_module 3.2.98.0

Xam.dll 1.0.115.0

Xam_toolkit.dll 1.0.115.0

Xamsdk.dll 1.0.0.0

centera_vim 1.0.115.0

But now EMC has announced the EOL for the XAM-Interface. So we would know migrate our customers to the SDK API using the .NET Wrapper. With that occasion, we also wanted to integrate a „proper“ version of the SDK-API. But in the official API we got different versions of the SDK-libraries:

SDK API 3.2 p5

FPCore.dll 3.2.705.0

fpos64.dll 3.2.285.0

fpparser.dll 3.2.48.0

FPStreams.dll   3.2.705.0

FPUtils.dll  3.2.705.0

FPXml.dll  3.2.705.0

pai_module 3.2.98.0

SDK API 3.3.718

FPCore.dll 3.3.718.0

fpos64.dll 3.3.292.0

fpparser.dll  3.3.5.0

FPStreams.dll  3.3.718.0

FPUtils.dll 3.3.718.0

FPXml.dll 3.3.718.0

pai_module 3.3.100.0

Using those libraries, the SDK API with the .NET Wrapper is working fine. But we’re not able to get the XAM Implementation to work as well (our goal is to migrate from one to the other API, so we can only use one set of libraries. In a second step we will the remove the XAM implementation. This is the error we got when we are trying to load the centera_vim library:

Seems like a method or property was not found in the FPUtils.dll provided with the latest “official” SDK API. My question is now, do you have a SDK-API that is working with both access methods? As you can see, back then I downloaded some SDK-libraries which have higher versions (for example FPUtils) as the official release?

Thanks for your help,

best regards,
Ivan Schnyder