[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | SQL/Services Forum |
| Notice: | kits(3) ft info(7) QAR access (8) SPR access (10) |
| Moderator: | SQLSRV::MAVRIS |
|
| Created: | Thu Oct 13 1988 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 2214 |
| Total number of notes: | 8586 |
2175.0. "another DRVCNDHDLERR" by M5::PTAKEO () Mon Mar 24 1997 16:36
Hi,
I have a customer who got a error %SQLSRV-F-DRVCNDHDLERR
with %SYSTEM-F-ACCVIO. The sql server shutdown after this error.
Please, someone know what error is? I've seen the note 1980, but
I'm not sure if it's the same error. My customer is running
SQLSRV V6.1-0 with RDB V6.1-03 on Alpha Server - OpenVMS V6.2-1H2
Thanks a lot...Pedro
========== sqlsrv.log =======================
0324 0858502677290 Process termination for PID 000077B5
0324 0858502687055 %SQLSRV-S-COM_FORCEX, Idle Timer Expired
0324 0858502687055 BIO 6649 DIO 4427 Flts 3096
0324 0858502696820 Connect 0 00:06:00.90 CPU 0 00:00:17.06
0324 0858502696820 Log File SYS$SYSDEVICE:[SQLSRV$SERVER]C54000_SS_MRI_0011.
LOG
0324 0900276085695 Process termination for PID 00006E43
0324 0900276593475 %SQLSRV-S-COM_FORCEX, Idle Timer Expired
0324 0900276603240 BIO 657 DIO 449 Flts 2222
0324 0900276603240 Connect 0 00:00:49.78 CPU 0 00:00:02.27
0324 0900276603240 Log File SYS$SYSDEVICE:[SQLSRV$SERVER]C54000_SS_MRI_0013.
LOG
0324 0901134538385 %SQLSRV-F-DRVCNDHDLERR, Condition handler error
0324 0901134684860 %SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual
address=7EE79670, PC=0003B7C4, PS=0000001B
SM33 job terminated at 24-MAR-1997 09:01:19.43
Accounting information:
Buffered I/O count: 24823 Peak working set size: 2720
Direct I/O count: 610 Peak page file size: 38928
Page faults: 2095 Mounted volumes: 0
Charged CPU time: 0 00:00:04.23 Elapsed time: 0 01:16:45.31
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2175.1 | Looks like a new one to me | SQLSRV::MAVRIS | Sue Mavris - [email protected] | Fri Mar 28 1997 09:48 | 10 |
| Hi Pedro,
This isn't a problem I've seen before. It looks like the comm server
signalled an exception and that the condition handler that's trying to log
the exception access violated. Does this happen often? Any chance you can
get the customer to upgrade to 6.0 eco02? The code that accvioed in the
condition handler is the same in the eco, but maybe the exception that caused
the condition handler to be invoked is different.
Sue
|
| 2175.2 | Thanks... | M5::PTAKEO | | Thu Apr 10 1997 09:05 | 8 |
| Hi Sue,
Thanks a lot for your help and information. My customer has upgraded
to eco02 and everthing is working fine.
Pedro
|