SQL server errors, and drops the database connection when running a query .
Version: Adaptive Server Enterprise/15.0/EBF 12783 GA/P/NT (IX86)/Windows 2000/ase150/2158/32-bit/OPT/Fri Aug 19 18:42:50 2005'; Running on Windows Server 2003.


The log file has:
00:00000:00021:2006/12/06 15:36:18.27 kernel SQL Server system exception (0xc0000005) generated by a storage access violation.
00:00000:00021:2006/12/06 15:36:18.27 kernel pc: 0x00E4E47F CgLavaUtils::CgTargetListExprs+ 0xc8 (0x2176FD74, 0x02FCEF40, 0x2171C0D4, 0x00000000)
00:00000:00021:2006/12/06 15:36:18.27 kernel pc: 0x00E4E47F CgLavaUtils::CgTargetListExprs+ 0xc8 (0x222A1E9C, 0x2176FD74, 0x00000001, 0x00000000)
00:00000:00021:2006/12/06 15:36:18.27 kernel pc: 0x00E54BD1 CgGenLava::CGConsDMLOp+ 0x3d1 (0x21B1A018, 0x00000001, 0x21B97000, 0x02FCF0B0)


and so on


The query uses a LEFT OUTER JOIN to a view. Using a JOIN instead of left outer prevents the error.

In case anyone else runs across this problem, 15.0.1 may have it fixed:
"An outer join query with an ON clause containing a join condition with
constants would stack trace"

which is actually what was happening in my query. Haven't tested it yet with
15.0.1, but hopefully this will fix the problem.


"M. Searer" <nospam (AT) nospam (DOT) com> wrote

SQL server errors, and drops the database connection when running a query .
Version: Adaptive Server Enterprise/15.0/EBF 12783 GA/P/NT (IX86)/Windows
2000/ase150/2158/32-bit/OPT/Fri Aug 19 18:42:50 2005'; Running on Windows
Server 2003.


The log file has:
00:00000:00021:2006/12/06 15:36:18.27 kernel SQL Server system exception
(0xc0000005) generated by a storage access violation.
00:00000:00021:2006/12/06 15:36:18.27 kernel pc: 0x00E4E47F
CgLavaUtils::CgTargetListExprs+ 0xc8 (0x2176FD74, 0x02FCEF40, 0x2171C0D4,
0x00000000)
00:00000:00021:2006/12/06 15:36:18.27 kernel pc: 0x00E4E47F
CgLavaUtils::CgTargetListExprs+ 0xc8 (0x222A1E9C, 0x2176FD74, 0x00000001,
0x00000000)
00:00000:00021:2006/12/06 15:36:18.27 kernel pc: 0x00E54BD1
CgGenLava::CGConsDMLOp+ 0x3d1 (0x21B1A018, 0x00000001, 0x21B97000, 0x02FCF0B0)

and so on


The query uses a LEFT OUTER JOIN to a view. Using a JOIN instead of left outer
prevents the error.

The EBF for 15.0.1 fixed it.


"M. Searer" <nospam (AT) nospam (DOT) com> wrote