Unsolved
This post is more than 5 years old
1 Message
0
2560
.NET Wrapper for Centera 3.3 SDK
Hello together,
i would like to know if there is a .NET Wrapper for the 3.3 SDK available?
Or should the .NET Wrapper 3.2P5 work also with the 3.3 SDK?
In my tests the 3.2P5 SDK and the .NET Wrappper for 3.2P5 works.
But with the 3.3 SDK the 3.2P5 Wrapper throws an error at the point where it tries to open the pool.
"Unable to load DLL 'FPLibrary.dll': The application could not be startet, because the application configuration is not correct. To solve this problem you should reinstall the application. (Exception from HRESULT: 0x800736B1)"
I also tried to add the dlls to a directory that is also in the system PATH variable. Same error.
I would appreciate to get assistance...
Greetings
Markus
rlearn
6 Posts
0
September 27th, 2012 10:00
Hi Markus
I have just now started trying to upgrade to 3.3 SDK and encounter the same problem you reported here. Did you get any answer to it outside of this thread. Can you help?
Regards
Rajesh
mckeown_paul
409 Posts
0
October 3rd, 2012 05:00
At first I couldn't get this to work either but I managed to get it to work by forcing the build of the wrapper and the code calling it to 32bit. My environment has the 32bit sdk libs installed. I'll change my laptop to 64 bit and let you know how I got on
Saldana1
1 Message
0
October 5th, 2012 12:00
Dear.
Today I am presenting the same problem I have compiled the SDK wrapper libraries with version 3.3.718.0 and when starting the application I get the error "Unable to load DLL 'FPLibrary.dll': Could not start the application because its configuration is incorrect. Reinstalling the application may fix this problem. (Exception from HRESULT: 0x800736B1) "
On my computer running windows 7 32 bit no error, this happens when I run it on windows server 2003 32 bit
SDK compilation was done with visual studio 2008.
I hope you can help with this problem.
regards
rlearn
6 Posts
0
October 5th, 2012 19:00
I tried with Windows 2003 and SDK 3.3 and initially encountered the problem with FPLibrary.dll. The application configuration is incorrect because there is some runtime dependency that is not resolved. I would prefer EMC to ship the manifest file with the dll or at least document the dependencies upfront to avoid this time wasted.
I managed to have it working with installing a particular version of Microsoft runtime update - http://www.microsoft.com/en-us/download/details.aspx?id=26347
as mentioned in https://community.emc.com/message/675984#675984. This solved the problem.