[fdo-users] Use of ArcSDE SDK Direct

Orest Halustchak orest.halustchak at autodesk.com
Thu Nov 18 14:19:57 EST 2010

Hi Crispin,

In addition to gsrvrora10g93.dll, I think you also need to include sdeora10gsrvr93.dll, xerces-c_2_7.dll, icuuc22.dll, and icudt22l.dll. The "Server library could not be loaded" message is coming from one of the ESRI dll's when it can't find one of the other libraries.

Regarding the comment about some clients might not enable the connection using direct connect, my guess is that it's saying that the client needs to look at the instance parameter to notice that a direct connect is requested or not, but that should be handled by the provider and I'm not sure what other issue there might be here.


-----Original Message-----
From: fdo-users-bounces at lists.osgeo.org [mailto:fdo-users-bounces at lists.osgeo.org] On Behalf Of Crispin_at_1Spatial
Sent: Thursday, November 18, 2010 8:43 AM
To: fdo-users at lists.osgeo.org
Subject: [fdo-users] Use of ArcSDE SDK Direct


We have a site with a preferred connection to ArcSDE via the ESRI direct
method/DLLs described here:

However, I have the following issues that I wonder if anyone (Mr Fortin?)
could help with.
I am using either FDO 3.4 or 3.5 on a PC with Oracle client installed.

Having copied in "sde.dll" and "gsrvrora10g93.dll" to match the SDE server
the provider is not happy connecting until other DLLs (the normal ARC client
ones) are in place.
"The ArcSDE runtime was not found (module sde91.dll)"

There is a cryptic message in the wiki that says "Some clients might not
enable the connection using direct connect mode because of the order of
connection parameters input" but then does not explicitly specify the order
of the parameters in the connection string.
I suspect that this is causing the other connection method to be imposed -
is this right?

Until I have the whole of the ArcSDE for Oracle client is installed I get an
"SDEHOME" error implying there are additional dependencies not found and
then the cryptic "Server library could not be loaded (-324)"

Connecting with FDO 3.5 throws the following in Windows - "... entry point
?ignorableWhitespace at SAXParser ... could not be located ... "  (see attached
file of error image)

Any help appreciated,


View this message in context: http://osgeo-org.1803224.n2.nabble.com/Use-of-ArcSDE-SDK-Direct-tp5751663p5751663.html
Sent from the FDO Users mailing list archive at Nabble.com.
fdo-users mailing list
fdo-users at lists.osgeo.org

More information about the fdo-users mailing list