<div>Thank you all for the attention to my problem.</div>
<div> I already had accomplished all the suggestions made. It seems as though when the sde: or sde:sqlserver: is added to the front of the instance name the security is circumvented. If I add either one. and then go to login I can type in "any" username/password combination and I don't get an error. It returns to the connection screen and shows the datastore empty. If I remove the sde: then "ANY" combination of the correct username/password returns an error: "The specified credentials ar not valid or the provider is unable to establish a connection". </div>
<div>As I said placing sde:sqlserver: in the instance name causes a successful login (every time) but the datastore is not populated. If I type in my datastore name and hit connect I get an error message dialog from map. "failed to open fdo connection, failed to open ArcSDE connection, the file path des not exist, or it is too long (> 512 chars), or has invalid characters. (-269). I have seen this and noticed that the datastore name cannot have a - (dash) in it. Could this apply to the machine name also? Our IT dept has the computer name set to domain-assetnumber. Mine being Hiland-FPS93M1.</div>
<div>Thanks again for any help provided.</div>
<div>Brad<br><br></div>
<div class="gmail_quote">On Mon, May 3, 2010 at 8:10 PM, Jackie Ng <span dir="ltr"><<a href="mailto:jumpinjackie@gmail.com">jumpinjackie@gmail.com</a>></span> wrote:<br>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote"><br>The ArcSDE provider doesn't do direct connections, it goes through the<br>official ESRI SDE API.<br>
<br>There was talk about a direct connect ArcSDE provider, but AFAIK this only<br>works with Oracle and I haven't heard much more about this provider since.<br><br>- Jackie<br><font color="#888888">--<br>View this message in context: <a href="http://osgeo-org.1803224.n2.nabble.com/arcsde-connection-tp5000154p5001172.html" target="_blank">http://osgeo-org.1803224.n2.nabble.com/arcsde-connection-tp5000154p5001172.html</a><br>
Sent from the FDO Users mailing list archive at Nabble.com.<br>_______________________________________________<br>fdo-users mailing list<br><a href="mailto:fdo-users@lists.osgeo.org">fdo-users@lists.osgeo.org</a><br><a href="http://lists.osgeo.org/mailman/listinfo/fdo-users" target="_blank">http://lists.osgeo.org/mailman/listinfo/fdo-users</a><br>
<br></font></blockquote></div>
<p>Brad,</p>
<p>Have you seen the help here which provides the connection syntax for the<br>ESRI direct SDK connection?</p>
<p><a href="http://trac.osgeo.org/fdo/wiki/FdoArcSDEDirectConnect">http://trac.osgeo.org/fdo/wiki/FdoArcSDEDirectConnect</a></p>
<p><br>As far as the non-SDK provider (arguably poorly named with "Direct" in the<br>name) it only connects to SDE stores in Oracle. See<br><a href="http://trac.osgeo.org/fdo/wiki/FDORfc42">http://trac.osgeo.org/fdo/wiki/FDORfc42</a> for details though the algorithms<br>
and logic would be transportable to the SQLServer provider if funded.</p>
<p>--<br>View this message in context: <a href="http://osgeo-org.1803224.n2.nabble.com/arcsde-connection-tp5000154p5002138.html">http://osgeo-org.1803224.n2.nabble.com/arcsde-connection-tp5000154p5002138.html</a></p>
<div>- Show quoted text -<br>Sent from the FDO Users mailing list archive at Nabble.com.<br>_______________________________________________<br>fdo-users mailing list<br><a href="mailto:fdo-users@lists.osgeo.org">fdo-users@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/fdo-users">http://lists.osgeo.org/mailman/listinfo/fdo-users</a><br></div>
<div> </div>
<div>Hi Brad,</div>
<div>For direct connect to SQL 2008, set the server name for the server running SQL 2008 and use an instance name of:<br> sde:sqlserver:<servername>\instancename</div>
<div>Note that for direct connect, you need the sde direct connect libraries. Put the following dll's into your fdo bin directory (assuming that you are using sde 9.3):<br> gsrvrsql93.dll , sdesqlsrvr93.dll , xerces-c_2_7.dll , icuuc22.dll , and icudt22l.dll</div>
<div>Thanks,<br>Orest.</div>