Skip to main content
May 8, 2008
Question

MX 7 / SQL 7.0 Conflicts

  • May 8, 2008
  • 3 replies
  • 617 views
We are running Cold Fusion MX 7.0.2 on a Windows 2003 server. We are having problems with the HTTP service on this server shutting down. A re-boot fixes the problem but then it fails again in about a week.
The data sources for our web sites are stored in SQL Server 7. Does anyone know if there are problems using the SQL 7 ODBC driver provided with MX 7?
This topic has been closed for replies.

3 replies

Inspiring
May 20, 2008
Quokka644 wrote:
> I would like to try a JDBC connection. It appears a need to download a JDBC
> driver for SQL Server 7.0 but I can't seem to find one. I see them for SQL
> Server 200 & 2005 but not version 7.0.

The SQL 2000 driver should work for SQL 7.

Jochem


--
Jochem van Dieten
Adobe Community Expert for ColdFusion
Participant
June 23, 2008
Hi Jochem,

we're having the same problems with CFMX6 and 7.

Trying to use the JDBC-driver in CFMX6 gives us an error telling us we need to use MSSQL2000 or above.

Any ideas where we can get a JDBC-driver for SQL7?

Sebastiaan Naafs - van Dijk
May 20, 2008
Jochem,

Thank you for your expertise.

I would like to try a JDBC connection. It appears a need to download a JDBC driver for SQL Server 7.0 but I can't seem to find one. I see them for SQL Server 200 & 2005 but not version 7.0.

Inspiring
May 8, 2008
quote:

Originally posted by: Quokka644
We are running Cold Fusion MX 7.0.2 on a Windows 2003 server. We are having problems with the HTTP service on this server shutting down. A re-boot fixes the problem but then it fails again in about a week.
The data sources for our web sites are stored in SQL Server 7. Does anyone know if there are problems using the SQL 7 ODBC driver provided with MX 7?


I have a couple of questions:

1. What do you mean by HTTP service? The ColdFusion MX 7 Application Server, the World Wide Web Publishing Service, the HTTP SSL service, or something else?

2. What makes you think that your problem is related to database connectivity? I'm not saying it isn't possible I'm just trying to get more information.

3. Is there a reason to use ODBC rather then the JDBC drivers bundled with ColdFusion? JDBC is generally regarded as the preferred method for database connectivity.

4. What JVM are you using?



Thing to try:

1. Verify that you have the latest service pack and patches for Windows and ColdFusion 7.

2. If you believe that ODBC is the culprit try using the SQL Server driver bundled with ColdFusion.

3. Check your Windows and CF logs for any relevant messages.




Troubleshooting DataDirect SequeLink ODBC service issues
http://www.adobe.com/go/tn_18800
May 15, 2008
To answer your questions (sorry for the delay).

1) HTTP basic web page serving fails. After a long wait we get a Jrun error message. We also get message from our hosting company that states "Monitors that are down include: HTTP / Monitors that are up include: Ping,SMTP".

2) When we tried to shut off the Cold Fusion services, the Cold Fusion MX ODBC service refused to respond to a Stop command.

3) No specific reason other than habit. We have been using ODBC connections to databases since we started using Cold Fusion 9 years ago.

4) Regarding JVM - I'm not sure of the specific information you need. Here is the virtual path - D:/Programs/CFusionMX7/runtime/jre. We have a max Heap size of 512MB. This is the Class Path - -Dcoldfusion.classPath={application.home}/../lib/updates,{application.home}/../lib,{application.home}/../gateway/lib/,{application.home}/../wwwroot/WEB-INF/cfform/jars These are JVM arguments - -server -Dsun.io.useCanonCaches=false -XX:MaxPermSize=128m -Dcoldfusion.rootDir={application.home}/../ -Dcoldfusion.libPath={application.home}/../lib .

Regarding service packs - we are using Windows 2003 R2 Standard Edition Service Pack 2. We are using Cold Fusion MX Version - 7,0,2,142559 / OS Version - 5.2 .

We have checked the Event viewer logs as well as various Cold Fusion logs, however, we can't seem to pin down a common re-occurring message at the same times as the failures.