Advanced Server 7 ODBC error - [DataDirect][ODBC SequeLink driver][SequeLink Client]TCP/IP error, connection refused

Advanced Server 7 ODBC error - [DataDirect][ODBC SequeLink driver][SequeLink Client]TCP/IP error, connection refused

Post by Sterling L » Mon, 13 Sep 2004 03:34:45


I have installed a FileMaker Server 7 with the Advanced Server license.

In FileMaker Server Admin, under Action, Properties, Clients for my server
under the Enable Client Services tab, Allow ODBC and JDBC connections is
checked. I have nothing listed in the FileMaker Web Publishing Engine
section.

Although I do have both the xDBC.fmx and the xDBC Support Folder copied to
my FileMaker Server 7\Extensions\Plugins director, under FileMaker Server
Admin under the Server Plug-Ins panel, nothing is listed (should it be?)

The problem is, when I try to actually create a datasource, in this case on
the local machine, I get the following error when I try to test a
connection:

[DataDirect][ODBC SequeLink driver][SequeLink Client]TCP/IP error,
connection refused

The SequeLink Server Host is set to localhost

SequeLink Server Port is 2399

If I click on the dots, I get the same error, but I tried putting in my
database name under Server Data Source, to no effect. Same error.

Server is Windows 2003 Enterprise Edition with all latest Microsoft Updates.

Any suggestions for troubleshooting? Does anyone have the above
configuration working correctly?



- Sterling Ledet

Sterling Ledet & Associates, Inc.

Adobe, Macromedia, Quark and Apple traiing

http://www.yqcomputer.com/
 
 
 

Advanced Server 7 ODBC error - [DataDirect][ODBC SequeLink driver][SequeLink Client]TCP/IP error, connection refused

Post by Sterling L » Mon, 13 Sep 2004 08:50:37

I figured out the answer to this question.

What I hadn't done was in the shared database opened it in FileMaker 7
Developer and turned on ODBC access for that specific database under
Edt>Sharing>ODBC/JDBC. So although my Advanced Server was set up correctly,
it didn't have any databases that were actually set to be shared via ODBC.

Just posting so that others who run across this will have a ready answer.

- Sterling Ledet



on
Updates.