Jump to content
Sign in to follow this  
Chuck

ESS Not Working under Server 12

Recommended Posts

After much Googling, I got a FileMaker 12 system to connect to a MySQL database and created a shadow table in FileMaker for one of the MySQL tables, but when I try to serve the file, after being prompted for data source credentials, I'm greeted with the following message:

"ODBC Error: [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application"

This when logging onto the served file from the same machine or a remote machine on both Windows and Mac OS X.

Details:

The server is running Windows 7 Ultimate and is 64-bit. I installed the 32-bit MySQL ODBC Connector 5.1.11. I added a System DSN C:\Windows\SysWOW64\odbcad32.exe rather than the default control panel for doing so. I launched FileMaker Pro Advanced 12, opened the FileMaker file, added the external ODBC data source and successfully created a shadow table pointing to the MySQL table. I deleted unneeded fields, and have a layout that successfully shows the data in a table view. Everything works as hoped for at this point.

On the very same machine I'm running FileMaker Server 12. Launching the FileMaker Server Admin Console I click "Upload a database," select the file that I just opened and upload it. It's being served successfully.

Now, launching FileMaker Pro Advanced again, File>Open Remote, select server from Local Hosts, select the file I just uploaded, click Open, enter my credentials for the file, and this is where things go wrong. Instead of opening successfully, I get a dialog prompting me to enter my ODBC data source credentials (didn't come up when I opened the file locally rather than through the server). I enter the credentials accurately and get that ODBC error message I quoted above.

So, what am I doing wrong? The end goal here is to be able to have the ODBC driver on the server allowing access to the MySQL tables from systems that don't have the ODBC driver. Am I on the right track with this?

Thanks,

Chuck

Share this post


Link to post
Share on other sites

Reading between the lines you appear to be trying to do this all in one machine?

Try running FMP on another machine. You do not need to install the ODBC driver on the FM client machine as it should be inheriting the ODBC connections through FMServer.

Share this post


Link to post
Share on other sites

I tried this on two machines. One is the server, running Windows 7 Ultimate with FileMaker Server 12 and FileMaker Pro Advanced 12. The other is a Mac running Lion with FileMaker Pro Advanced 12. When opening a local file on the desktop, I have no problem. When serving the exact same file and opening it in either the FileMaker client on the server itself or opening it in the FileMaker client on my Mac, I get exactly the same error.

Note that an experiment with a virtual machine on my Mac (using VirtualBox) with Windows 7 Ultimate (running as a 32-bit machine) did not have this problem. The server with the problem is running a virtual machine (running VMWare, I believe) also running Windows 7 Ultimate, but as a 64-bit machine.

Thanks,

Chuck

Share this post


Link to post
Share on other sites

I got this solved, but aren't exactly what I did differently than I had before. Basically I installed the 64-bit version of the ODBC driver, created a DSN with it in the odbcad.exe in System32 and used that new data source for the shadow table rather than the 32-bit data source. I'm almost sure I had tried that before without success, but, well, it's working now, so I won't complain. :)

Thanks,

Chuck

Share this post


Link to post
Share on other sites

And I just remembered FMS is 64bit, but FMP is still 32bit.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Who Viewed the Topic

    1 member has viewed this topic:
    AlesD 
×

Important Information

By using this site, you agree to our Terms of Use.