why do I get "Server library could not be loaded (-324)" in map3d 2014?
Works fine in 2012 and now i can not connect to our Arcsde.
win 7- 64bit
Arcsde 10.0
copied proper .dll's
I am lost, please help
Likely you are experiencing this trouble because of changes made to the direct connect libraries in the 2013 (and 2014) FDO Providers. For this issue, this article was published.
The fastest and easiest option I'd suggest for you is to install & configure the 2015 release of Map or Civil to make this same connection.
Please let us know what your results are after this, or let me know if you need to look at other options. Thanks!
So I installed 2015 civil/map, and I still get the same error that I had in 2014!!! I copied the .dll files I needed and now I have a library error. I have no clue why this is being so difficult!!! I am going to stick with 2012C3D now. This is terrible!!
Hi Mike,
Thanks for reporting back on that. I'm really not sure why you that is happening in your case based on everything that you have told me to this point.
The only other thing I can think of to suggest is, since you are on 10.0, use the ESRI tools to upgrade the geodatabase (if you haven't done so already). This will open up the schema and data to access from non-ArcObjects processes. What that means for you is that you will then be able to connect to your data using the base FDO Provider in Map (SQL Server Spatial or Oracle) rather than having to use the "Add ArcSDE Connection".
Ok, I will work with our GIS department and see if we can resolve this. In the mean time I am going to continue using 2012. And I am also keeping my department on 2012. Everything works in 2012 as of now. It’s very frustrating that we can’t have a simple upgrade.
If we have to change from ArcSDE to cad FDO it’s not worth changing to 2014 or 2015. We have way to many dwg's connected using ARCSDE.
In reviewing all of your comments to this point, one thing wasn't clear to me. Are you testing 2014&2015 on a separate machine? Or is 2012 also installed (and working) on the same machine where it fails in 2014&2015?
And if these are different machines, by chance is the machine running 2012 32-bit, and the machine running 2014&2015 64-bit?
Just to make sure that we have the story straight...
I am running 64-bit. It is the same computer that 2012 is loaded on as well.
Win7 ent, 64-bit.
We have the 64-bit dll that we used for 2012 which works.
Perhaps this may help: