Hi All, We have a 4D v14.4 application running as server/client on Window 2012/R2. We have a separate Microsoft SQL application running on a similar box/OS. The SQL application needs to connect to the 4D application via 64 bit ODBC and pull data. The driver is installed on the 4D box with a published DSN. The SQL application can see the ODBC connection and often connect. However it also often gets an error stating “the server closed the connection.” It appears to fail the first connection attempt then succeed on the next attempt only to fail again on the third attempt and so on, back and forth. After several cycles like this our SQL application actually crashes and we need to re-boot the box before launching it again successfully. Unfortunately we can’t use the 32 bit ODBC driver because the SQL application does not support it…
Anyone have any thought on how to resolve this issue? Is there a setting within the OS or on the 4D server that might help? Any hint or suggestion is welcome! Thanks, Kirk ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
