Question
CF 7.0.2 ODBC Server crashed unexpectedly
hi
We moved from an older Dual PIII box under Win2k to a Dual Xeon under Win2k3.
First step was to move Sybase ASA 9.0.2.33xx dbs from the old box to the new, leaving ColdFusion 6.1 MX on the old box connecting through ODBC. This workd flawlessly for weeks.
Yesterday I also moved the front end (coldfusion 6.1 to cf 7.0.2) to the new box
Now, we get problems like this in the Sybase ASA server log
---
I. 09/27 09:49:14. Disconnecting shared memory client, process id not found
I. 09/27 09:49:14. Disconnected SharedMemory client's AppInfo: HOST=MINDPOWER-4;OS=Windows 2003 Build 3790 Service Pack 1;PID=0x1a4c;THREAD=0xefc;EXE=C:\CFusionMX7\db\slserver54\bin\swsoc.exe;VERSION=9.0.2.3370;API=ODBC;TIMEZONEADJUSTMENT=120
I. 09/27 09:50:36. Disconnecting shared memory client, process id not found
I. 09/27 09:50:36. Disconnected SharedMemory client's AppInfo: HOST=MINDPOWER-4;OS=Windows 2003 Build 3790 Service Pack 1;PID=0x193c;THREAD=0x9ac;EXE=C:\CFusionMX7\db\slserver54\bin\swsoc.exe;VERSION=9.0.2.3370;API=ODBC;TIMEZONEADJUSTMENT=120
I. 09/27 09:50:36. Disconnecting shared memory client, process id not found
I. 09/27 09:50:36. Disconnected SharedMemory client's AppInfo: HOST=MINDPOWER-4;OS=Windows 2003 Build 3790 Service Pack 1;PID=0x193c;THREAD=0xf48;EXE=C:\CFusionMX7\db\slserver54\bin\swsoc.exe;VERSION=9.0.2.3370;API=ODBC;TIMEZONEADJUSTMENT=120
---
and of course the errors logged in CF as
---
- Error Executing Database Query. [Macromedia][SequeLink JDBC Driver]TCP/IP error, connection reset by peer. <br>The error occurred on line 64.
- Error Executing Database Query. [Macromedia][SequeLink JDBC Driver]TCP/IP error, connection refused. <br>The error occurred on line 96.
[Macromedia][SequeLink JDBC Driver]TCP/IP error, connection reset by peer.
ErrorCode HY000
Message Error Executing Database Query.
- Error Executing Database Query. [Macromedia][SequeLink JDBC Driver]Network problem, session aborted due to internal error in remote procedure call, connection closed. <br>The error occurred on line 96.
---
The Event Viewer of the Win2k3 box showed lots of those in the System Log
---
Type Error, Event ID 7031
The ColdFusion MX 7 ODBC Server service terminated unexpectedly. It has done this 8 time(s).
or
Type Warning, Event ID 7039
A service process other than the one launched by the Service Control Manager connected when starting the ColdFusion MX 7 ODBC Server service. The Service Control Manager launched process 3720 and process 7752 connected instead.
Note that if this service is configured to start under a debugger, this behavior is expected.
Of course, we don't have debugging
---
In the application log, there are errors like this:
---
The description for Event ID ( 0 ) in Source ( ColdFusion MX 7 ODBC Server ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: ColdFusion MX 7 ODBC Server@LOCALHOST,ErrorCode=3004,ErrorMessage=sched.swschd.1756.Internal error, an unexpected exception was detected..
The description for Event ID ( 0 ) in Source ( ColdFusion MX 7 ODBC Server ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: ColdFusion MX 7 ODBC Server@LOCALHOST,ErrorCode=3001,ErrorMessage=srvc.swsrvcdb.3268.Internal error, memory allocation failed.,ClientHost=127.0.0.1,Session=2.
The description for Event ID ( 0 ) in Source ( ColdFusion MX 7 ODBC Server ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: ColdFusion MX 7 ODBC Server@LOCALHOST,ErrorCode=3003,ErrorMessage=ssp.swsrvssp.3551.Internal error, invalid request received from the client application.,ClientHost=127.0.0.1,Session=2.
The description for Event ID ( 0 ) in Source ( ColdFusion MX 7 ODBC Server ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: ColdFusion MX 7 ODBC Server@LOCALHOST,ErrorCode=3004,ErrorMessage=sched.swschd.1756.Internal error, an unexpected exception was detected..
---
Of course, the application stalls as well and our users are upset.
We staged that new box and found no problems, not with ASA. With CF 7, we had several isuses, some of them are still not quite clear.
Now that we wanted to go productive, those errors occur.
Note that the ODBC settings for those DSNs allowed both connections, Shared Mem and TCP/UP localhost, because cf is now on the same machine like the db.
My question now is: Where should I try to find the error ... on ASA or CF7 side?
Any hints welcome!
Thanks
Martin
We moved from an older Dual PIII box under Win2k to a Dual Xeon under Win2k3.
First step was to move Sybase ASA 9.0.2.33xx dbs from the old box to the new, leaving ColdFusion 6.1 MX on the old box connecting through ODBC. This workd flawlessly for weeks.
Yesterday I also moved the front end (coldfusion 6.1 to cf 7.0.2) to the new box
Now, we get problems like this in the Sybase ASA server log
---
I. 09/27 09:49:14. Disconnecting shared memory client, process id not found
I. 09/27 09:49:14. Disconnected SharedMemory client's AppInfo: HOST=MINDPOWER-4;OS=Windows 2003 Build 3790 Service Pack 1;PID=0x1a4c;THREAD=0xefc;EXE=C:\CFusionMX7\db\slserver54\bin\swsoc.exe;VERSION=9.0.2.3370;API=ODBC;TIMEZONEADJUSTMENT=120
I. 09/27 09:50:36. Disconnecting shared memory client, process id not found
I. 09/27 09:50:36. Disconnected SharedMemory client's AppInfo: HOST=MINDPOWER-4;OS=Windows 2003 Build 3790 Service Pack 1;PID=0x193c;THREAD=0x9ac;EXE=C:\CFusionMX7\db\slserver54\bin\swsoc.exe;VERSION=9.0.2.3370;API=ODBC;TIMEZONEADJUSTMENT=120
I. 09/27 09:50:36. Disconnecting shared memory client, process id not found
I. 09/27 09:50:36. Disconnected SharedMemory client's AppInfo: HOST=MINDPOWER-4;OS=Windows 2003 Build 3790 Service Pack 1;PID=0x193c;THREAD=0xf48;EXE=C:\CFusionMX7\db\slserver54\bin\swsoc.exe;VERSION=9.0.2.3370;API=ODBC;TIMEZONEADJUSTMENT=120
---
and of course the errors logged in CF as
---
- Error Executing Database Query. [Macromedia][SequeLink JDBC Driver]TCP/IP error, connection reset by peer. <br>The error occurred on line 64.
- Error Executing Database Query. [Macromedia][SequeLink JDBC Driver]TCP/IP error, connection refused. <br>The error occurred on line 96.
[Macromedia][SequeLink JDBC Driver]TCP/IP error, connection reset by peer.
ErrorCode HY000
Message Error Executing Database Query.
- Error Executing Database Query. [Macromedia][SequeLink JDBC Driver]Network problem, session aborted due to internal error in remote procedure call, connection closed. <br>The error occurred on line 96.
---
The Event Viewer of the Win2k3 box showed lots of those in the System Log
---
Type Error, Event ID 7031
The ColdFusion MX 7 ODBC Server service terminated unexpectedly. It has done this 8 time(s).
or
Type Warning, Event ID 7039
A service process other than the one launched by the Service Control Manager connected when starting the ColdFusion MX 7 ODBC Server service. The Service Control Manager launched process 3720 and process 7752 connected instead.
Note that if this service is configured to start under a debugger, this behavior is expected.
Of course, we don't have debugging
---
In the application log, there are errors like this:
---
The description for Event ID ( 0 ) in Source ( ColdFusion MX 7 ODBC Server ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: ColdFusion MX 7 ODBC Server@LOCALHOST,ErrorCode=3004,ErrorMessage=sched.swschd.1756.Internal error, an unexpected exception was detected..
The description for Event ID ( 0 ) in Source ( ColdFusion MX 7 ODBC Server ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: ColdFusion MX 7 ODBC Server@LOCALHOST,ErrorCode=3001,ErrorMessage=srvc.swsrvcdb.3268.Internal error, memory allocation failed.,ClientHost=127.0.0.1,Session=2.
The description for Event ID ( 0 ) in Source ( ColdFusion MX 7 ODBC Server ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: ColdFusion MX 7 ODBC Server@LOCALHOST,ErrorCode=3003,ErrorMessage=ssp.swsrvssp.3551.Internal error, invalid request received from the client application.,ClientHost=127.0.0.1,Session=2.
The description for Event ID ( 0 ) in Source ( ColdFusion MX 7 ODBC Server ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: ColdFusion MX 7 ODBC Server@LOCALHOST,ErrorCode=3004,ErrorMessage=sched.swschd.1756.Internal error, an unexpected exception was detected..
---
Of course, the application stalls as well and our users are upset.
We staged that new box and found no problems, not with ASA. With CF 7, we had several isuses, some of them are still not quite clear.
Now that we wanted to go productive, those errors occur.
Note that the ODBC settings for those DSNs allowed both connections, Shared Mem and TCP/UP localhost, because cf is now on the same machine like the db.
My question now is: Where should I try to find the error ... on ASA or CF7 side?
Any hints welcome!
Thanks
Martin