ColdFusion MX 6.1: Hot fix to upgrade DataDirect Sequelink ODBC Server to version 5.4
ODBC access in Macromedia ColdFusion MX 6.1 is provided through the use of the DataDirect SequeLink Server software, which runs under the Windows services labeled ColdFusion MX ODBC Agent and ColdFusion MX ODBC Server. This TechNote explains how to upgrade a ColdFusion MX 6.1 SequeLink installation to SequeLink 5.4, which is the most current and stable version.
Note: ColdFusion MX 7 includes the 5.4 SequeLink server and doesn't require this upgrade.
Troubleshooting
Symptoms
SequeLink (the ODBC Server service) hangs or crashes under load.
Details
If restarting the ODBC Server service resolves the hang, use the following steps to determine if this is application-related or ODBC Server-related.
- Inspect /cfusionmx/db/slserver52/logging *.log and *.dmp for evidence of crashes. Examples are listed here.
Windows Event Log
The description for Event ID ( 0 ) in Source ( ColdFusion MX ODBC Server ) could not be found. It contains the following insertion string(s): ColdFusion MX ODBC Server@LOCALHOST,ErrorCode=3004,ErrorMessage=sched.swschd.1756.Internal error, an unexpected exception was detected..
SequeLink error
ColdFusion MX ODBC Server@LOCALHOST,ErrorCode=3004,ErrorMessage=sched.swschd.1756.Internal error, an unexpected exception was detected.
SequeLink .dmp file (if any)
Friday, July 02, 2004 12:30:58 PM ACCESS_VIOLATION
Stack Dump:
PC:1F8008F3-Seg:1;Off:0000F8F3-SearchStatusCode+8196
PC:1F8120F4-Seg:1;Off:000210F4-CursorLibTransact+3900
PC:1F7F40FA-Seg:1;Off:000030FA-MpHeapFree+910
PC:1F7F328F-Seg:1;Off:0000228F-SQLDriverConnectW+1B9
PC:00405335-Seg:1;Off:00004335 - Check the version of the ODBC driver and database. Possible problems include:
- Using an older Access (97) database can cause problems with newer drivers.
- Using Access 2000 databases but with older drivers (older than MDAC 2.6 SP2).
- Database not on repair schedule. Backup and repair the database often.
Error Executing Database Query.[MERANT][SequeLink JDBC Driver] TCP/IP error, connection reset by peer.
Installing the SequeLink 5.4 server to ColdFusion MX 6.1
Follow the directions below to upgrade an existing ColdFusionMX 6.1 installation with the 5.4 SequeLink server build .097.
- Determine the version of the SequeLink driver. If the overall driverpack version is 3.3 build 31 or higher, it will contain the 5.4 SequeLink driver. The 5.4 ODBC Server requires the 5.4 SequeLink driver.
set path=c:\cfusionmx\runtime\jre\bin;%path%
set classpath=c:\cfusionmx\lib\macromedia_drivers.jar;.;
java macromedia.jdbc.sqlserver.SQLServerDriver
should return:
[Macromedia][SQLServer JDBC Driver]Driver Version:3.3.31 (008841.005010.006327)
java macromedia.jdbc.sequelink.SequeLinkDriver
should return:
[DataDirect][SequeLink JDBC Driver]Driver Version:5.4.0038 - Download cfmx61_slserver54.zip (14MB).
- Place the downloaded ZIP file in cf_root/db/.
- Shut down the ColdFusion MX ODBC Server service in the Windows Services control panel.
- Save the existing configuration by doing the following:
- Create a directory inside cf_root/db/slserver52 and call it /Sequelink52 (so the version is clear)
- Rename the cf_root/db/slserver52 directory to /db/slserver52orig
- Expand the cfmx61_slserver54.zip (preserve folders ON).
The cf_root/db/slserver52/ directory name and structure needs to remain intact due to hardcoded registry entries even though the version will be 5.4.
Note: If ColdFusionMX was not installed on C:\CFusionMX, search and replace all paths contained in the swandm.ini, swcla.ini and slxperf.ini files undercf_root/db/slserver52/ to the correct ColdFusion MX installation path. - Start the ColdFusion MX ODBC Server service.
- Confirm the ODBC Server version by viewing thecf_root/db/slserver52/logging/ColdFusion MX ODBC Server*.log:
You should now see:
SLX ODBC Socket. Build 0097 - Re-submit each ODBC data source through the ColdFusion MX Administrator.
Each data source needs to be registered with SequeLink and submitting the data source in the ColdFusion administrator creates the necessary data source records in SequeLink's swandm.ini.
Note: The server is a non-unicode enabled server compatible with the current 6.1 installation.
Possible Errors:
Most errors that occur when restarting the service after upgrade are caused by path issues in the swandm.ini or other .ini files.
- Forgot to change path location in swcla.ini (or other INI files) to match ColdFusion MX root.
Error: [SequeLink error 6853] Failed to access configuration at C:\CFusionMX\db\slserver52\cfg\swandm.ini.
Solution: Edit and search/replace all occurances of paths to the correct location. - Forgot to change the paths in the INI files (non-standard ColdFusion MX root). Causes ColdFusion MX ODBC Agent to fail on startup.
The Event viewer shows:
The description for Event ID ( 0 ) in Source ( SequeLink ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: Failed start service ColdFusion MX ODBC Agent because the service is not properly registered.
Solution: Most likely, it's a pathing issue. The swandm.ini file is referencing a path such as \cfusionmx that doesn't correspond to your installation. If your system has a different location for the ColdFusion MX root, do a global search and replace in all the .ini files.
The upgrade is not successful until all ODBC Socket or MS Access data sources verify.
To revert the installation to SequeLink 5.2, rename the /dbslserver52orig directory back and re-submit all ODBC data sources used in applications.
Additional Information
- ColdFusion MX: Enabling debugging for DataDirect SequeLink Server ODBC Services (TechNote tn_19205)
- Troubleshooting DataDirect SequeLink ODBC service issues (TechNote tn_18800)
This content requires Flash
To view this content, JavaScript must be enabled, and you need the latest version of the Adobe Flash Player.
Download the free Flash Player now!
