So I'm trying to get FM Server 7 Advanced (v3) to serve up some data via ODBC.

I've installed the ODBC drivers, and they're enabled according to "fmsadmin list plugins". I've set the permissions under extended privilages on one of my DB's to allow access via xDBC.

The server is running, and the "Allow Access via JDBC/ODBC" is checked.

When attempting to connect via DataDirect 32-BIT SequeLink 5.4, I get this result:

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

To ensure that I have a clue how ODBC works, I had a local copy of FM 7 Pro host a database with ODBC, and was able to set up the sharing correctly so I could pull the data into other apps. I just can't seem to get FM Server 7 Advanced to actually share the data.

Something I have looked into - since everyone says that port 2399 is where the connection needs to happen, I did a port scan on my XServe and found that it wasn't open. Although the Firewall is completly turned off, I suspect that because I'm not seeing an active open service there, that tells me that it's not actually running an ODBC server, and that's why it's causing the TCP/IP connection error listed above.

Has ANYONE gotten FM 7 Server Advanced on Mac OS X to serve ODBC data? If so, HOW?

So I'm trying to get FM Server 7 Advanced (v3) to serve up some data via ODBC.

I've installed the ODBC drivers, and they're enabled according to "fmsadmin list plugins". I've set the permissions under extended privilages on one of my DB's to allow access via xDBC.

The server is running, and the "Allow Access via JDBC/ODBC" is checked.

When attempting to connect via DataDirect 32-BIT SequeLink 5.4, I get this result:

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

To ensure that I have a clue how ODBC works, I had a local copy of FM 7 Pro host a database with ODBC, and was able to set up the sharing correctly so I could pull the data into other apps. I just can't seem to get FM Server 7 Advanced to actually share the data.

Something I have looked into - since everyone says that port 2399 is where the connection needs to happen, I did a port scan on my XServe and found that it wasn't open. Although the Firewall is completly turned off, I suspect that because I'm not seeing an active open service there, that tells me that it's not actually running an ODBC server, and that's why it's causing the TCP/IP connection error listed above.

Has ANYONE gotten FM 7 Server Advanced on Mac OS X to serve ODBC data? If so, HOW?

So I'm trying to get FM Server 7 Advanced (v3) to serve up some data via ODBC.

I've installed the ODBC drivers, and they're enabled according to "fmsadmin list plugins". I've set the permissions under extended privilages on one of my DB's to allow access via xDBC.

The server is running, and the "Allow Access via JDBC/ODBC" is checked.

When attempting to connect via DataDirect 32-BIT SequeLink 5.4, I get this result:

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

To ensure that I have a clue how ODBC works, I had a local copy of FM 7 Pro host a database with ODBC, and was able to set up the sharing correctly so I could pull the data into other apps. I just can't seem to get FM Server 7 Advanced to actually share the data.

Something I have looked into - since everyone says that port 2399 is where the connection needs to happen, I did a port scan on my XServe and found that it wasn't open. Although the Firewall is completly turned off, I suspect that because I'm not seeing an active open service there, that tells me that it's not actually running an ODBC server, and that's why it's causing the TCP/IP connection error listed above.

Has ANYONE gotten FM 7 Server Advanced on Mac OS X to serve ODBC data? If so, HOW?

Do you have the latest update for the ODBC driver? I believe it is a separate download that you need to install. We experienced the same issue and after installing the update for ODBC, it started working for us.

This was on a windows platform so it may be the same thing you are experiencing but maybe not.

HTH,

John

Do you have the latest update for the ODBC driver? I believe it is a separate download that you need to install. We experienced the same issue and after installing the update for ODBC, it started working for us.

This was on a windows platform so it may be the same thing you are experiencing but maybe not.

HTH,

John

Do you have the latest update for the ODBC driver? I believe it is a separate download that you need to install. We experienced the same issue and after installing the update for ODBC, it started working for us.

This was on a windows platform so it may be the same thing you are experiencing but maybe not.

HTH,

John

I have downloaded the latest ODBC driver (the first available for Mac) and installed it. It doesn't seem to have helped.

I have downloaded the latest ODBC driver (the first available for Mac) and installed it. It doesn't seem to have helped.

I have downloaded the latest ODBC driver (the first available for Mac) and installed it. It doesn't seem to have helped.

Do you have the ODBC connection setup correctly? You are using the server's IP address and not its machine name? We did so much tinkering with the server & different settings & reinstalls that I am not totally convinced that the ODBC update fixed it. I never got a solid answer from FMP tech support on why this would be happening. They kept telling me to see if there was a 2399 port open and if it wasn't open, then it was a problem with our firewall. It wasn't a problem with the firewall so I don't think they really know what is happening. I think it is still a bug.

Sorry I couldn't be any help,

John

Do you have the ODBC connection setup correctly? You are using the server's IP address and not its machine name? We did so much tinkering with the server & different settings & reinstalls that I am not totally convinced that the ODBC update fixed it. I never got a solid answer from FMP tech support on why this would be happening. They kept telling me to see if there was a 2399 port open and if it wasn't open, then it was a problem with our firewall. It wasn't a problem with the firewall so I don't think they really know what is happening. I think it is still a bug.

Sorry I couldn't be any help,

John

Do you have the ODBC connection setup correctly? You are using the server's IP address and not its machine name? We did so much tinkering with the server & different settings & reinstalls that I am not totally convinced that the ODBC update fixed it. I never got a solid answer from FMP tech support on why this would be happening. They kept telling me to see if there was a 2399 port open and if it wasn't open, then it was a problem with our firewall. It wasn't a problem with the firewall so I don't think they really know what is happening. I think it is still a bug.

Sorry I couldn't be any help,

John

I am using the server's IP address - the machine name isn't going to do much good because it's not on the same network.

Thanks for posting though - and I resubmit my query - has ANYONE gotten FMSA7v3 to serve ODBC data?

I am using the server's IP address - the machine name isn't going to do much good because it's not on the same network.

Thanks for posting though - and I resubmit my query - has ANYONE gotten FMSA7v3 to serve ODBC data?

I am using the server's IP address - the machine name isn't going to do much good because it's not on the same network.

Thanks for posting though - and I resubmit my query - has ANYONE gotten FMSA7v3 to serve ODBC data?

I'm getting the same error. Has anyone gotten this to work?

I'm getting the same error. Has anyone gotten this to work?

I'm getting the same error. Has anyone gotten this to work?

Same problem for my own... If anyone has an idea, it's welcome !

Well, I have solved the problem, for my own...

And it was really a stupid mistake !

When I set up ODBC/JDBC right on my database with FMPro, I used a Mac user which didn't have write permission on the file. FMP hadn't returned any error, but my changes weren't saved !

So don't forget to :

- allow JDBC access to your files (you need to close your files on the server before doing that)

- check the user which opens the file to change JDBC right has write permissions to the file...

Regards,

ElDiablo

Why JDBC rights when you're using ODBC???

I had the same thing....now it works locally...haven't tested it on the server....do we need Server Advanced for a local workgroup environment???

cheers,

MAcb