Troubleshoot ODBC-connection

[Jonas Eriksson]

Hi!

I lost my ODBC-connection. Very confusing. The ODBC-client driver SequeLink says error 2306 "TCP/IP Error, connection refused" (on localhost, port 2399). Found a suggestion in the DataDirect-helpfiles to run netstat -a to see if the server is listening on port 2399, its not. Is it the xDBC plugin that has stopped to work? ODBC is allowed in FMSA admin.

Everything else works fine, including WPE.

ODBC has been running fine on our Win2000Server for months until last friday when we had to take the PDC (Win2003SBS) offline a short while to make more space on the system partition (for that reason we moved the mailserver-files to another partition). Cannot see why that should affect our FMSA odbc-functions, can you?

Greatful for any suggestions!

[Leb i Sol]

PDC is probably also a Master Browser....which is where your name resolution and browing would come in play....the only connetion would be if your files are not stored on the same machine as the ODBC is created.

In other words if your odbc had a path to DB such as ServerNameFMfiles it probably has issues resolving it.

Better way would be setting up a share as above and then mounting a drive letter to that share/path and then using a login script that would kill the path and recreate it on login. This was if there are issues you will be notifed in login script vs. discovering it when using FM.

Don't know much about SequeLink but perhaps you can post more...

All the best!

[Jonas Eriksson]

Thank you for your thoughts, but the files and the odbcclient are on the same computer (at least until its been tested ok).

I am still searching for answers, but I am a little stuck, so meantime I am rewriting my code to use the WPE instead of ODBC.

[James22]

I know this won't help you but I have a question since you are more advanced than I am. I have created a test data base to try out the odbc link. I get the same error as you do. Somehow DataDirect's sequelink thinks I am accessing a server where everything is on my own computer [localhost]. Do you use a Sequel Manager?

I will eventually connect my app to a pda.

James

[Jonas Eriksson]

Hi!

Perhaps we have the exact same problem. I've tried connecting to FM on the same computer (localhost) to FMPro, and to FMSA.

Why do you believe that Sequelink think you're accessing a server? If you're using localhost (or 127.0.0.1) it speaks to the port 2399 on the local computer.

If you write [netstat -a] in your commandprompt do you se something listening on port 2399? You should, but I dont.

[Jonas Eriksson]

Now I've left ODBC for WPE, XML & XSLT. But it would still be of interest to startup the ODBC for some use in the future.

[Leb i Sol]

An old follow up...

I noticed that you have XP...1st thing I would look is the Sp2 = Firewall and then checking the ports with netstat -a.

Also consider getting this utility:

http://www.download.com/3000-2085-10062969.html

Now whenever ur using ref. to machine as "localhost" or 127.0.0.1 you can sometimes run into problems as it is loopback IP not a 'true' accessible IP by anyone else on the LAN/WAN other than the machine you are on.

If you are having issues accessing data through ODBC on your own machine then definetly look towards XP-firewalls or failed port start-ups.

If you are testing ODBC --> to servershare

then it can be many things:

-depending on your network(s) and subnets and routers etc.....won't go into this unless you share more specs.

-try refering to your machine (or the host) based on your LAN IP

eg. 192.168.1.15FM_DBS

note: many ISP with 1 public IP will assign it to your machine NOT the router/modem that you sit behind. In this case you need to do some work on the router...

sorry if it is an overkill but it never hurts to go over 'assumed facts'.

All the best!

[HALBURN]

We are having the same problem. Have you had any luck getting your ODBC connection to work again?

I am running FileMaker Server 8 Advanced on Mac OSX 10.4.6. About three weeks ago we started having trouble connecting from our UPS Worldship computer to the FM8A server via ODBC. I did a port scan from the server using the Apple Network Utility and sure enough I am no longer getting any response from port 2399.

I called FileMaker tech support and they pretty much blamed the problem on the computer and directed me to call Apple to try and solve the problem.

I currently do not have any firewalls active so there should not be anything blocking any ports. I assume that something in either the FileMaker Server software or the operating system must have gotten corrupted.

As a test I configured Timbuktu on the server to communicate on port 2399. I did a port scan and now the Apple Network Utility returns feedback as if port 2399 was responding. What's odd is that the port responds with a FileMaker feedback message not a Timbuktu response. After my test I set Timbuktu back to port 407 and did a rescan of the ports. Once again, no response from port 2399.

We installed FMS on a second test computer and our UPS Worldship computer can connect to it via ODBC. So the connection problem is definitely somewhere on our main FM8A server.

Can someone please tell me if there is a magic terminal command that I can use to try and zap port 2399 back to working properly?

Any suggestions on how to trouble shoot and solve this problem would be greatly appreciated.

[HALBURN]

I was able to solve our ODBC problem by deleting a corruption in the xDBC Support folder and reinstalling FMS8A.

Here is a detailed link to the fix:

http://worldsync.com/guide/trouble/odbc_jdbc_connection_refused.pdf