Access violation in ntdll.dll Microsoft SQL ODBC driver

[rmcshane]

When I try to do a Load ODBC log in Log Analyer I get and Error Source: syssrcsql. Error: Access violation at address 7C82F350 in module 'ntdll.dll'. Write address 00000008.

I then get a second pop up box titles Log Analyzer Access Violation 7c82F350 in module 'ntdll.dll'. Write of address 00000008

The OS is Microsoft Windows Server 2003 Standard Enterprises Service Pack 1. According to Microsoft web siter I am current on patches. ODBC driver is Version 200.86.1830.00 File SQLSRV32.dll. I am accessing a Microsoft SQL 2000 server. Log Analyzer is version 5.02

When I run Log Analyzer from a seperate system running XP Pro, I get a slightly different error. SOurce: testit. Access violation at address 7C91010 in module 'ntdll.dll'. Read of address 00000018

HOSTMON has no problem writing to the same SQL database.

It also fails when clicking the Test button on ODBC logs Manager.

In all cases the ODBC driver is attaching as the user sa.

I have tweaked the fetch parameter mentioned in previous psots in the mostmon.ini, but that had no affect.

[KS-Soft]

I found a lot of articles about similar problem with ODBC driver but most of them relates to old versions. Unfortunately I did not find anything specific to version 200.86.1830.00 or any information that could explain this error Log Analyzer uses just several usual ODBC functions that are used by most ODBC programs...

Also I tried to find iformation about error source: syssrcsql. But did not find anything at all. Are you sure "syssrcsql" is spelled correctly?

Regards
Alex

[rmcshane]

In your reply you refernce syssrcsql. That is the name of the ODBC source. I am goignt o attempt to build a frech Windows 2003 server with nothing else on it and see if that might resolve the issue.

[jjackowski]

I'm having the exact problem, so did formatting and redoing the whole server solve this issue ?

Thanks,

Jakub

[KS-Soft]

Rebuild will not help you. There is bug in new ODBC Manager. We implemented some workaround in version 5.64.
Quote from the manual

Log Analyzer: Bug in new versions of Microsoft ODBC Manager (odbc32.dll version 4.00.6304.00, 4.00.6305.00 and may be some other) may lead to access violation error and memory leakage. If you experience such problem, install new Log Analyzer and add 2 lines into logsman.ini file:
[Misc]
ReleaseHDBC=0
This will eliminate access violation error. Unfortunatelly we have not found a way to avoid memory leakage. Hopefully Microsoft will fix this problem in next versions.

If you have posibility to use old ODBC Manager, use old manager and old Windows. As usually we recommend Windows 2000...

Regards
Alex

[jjackowski]

Thanks Alex !

I'm testing it still with version 5.64 beta. Thanks for the update i'll check it out

[KS-Soft]

5.64 Beta? Then you don't need update, just add those 2 lines into logsman.ini file and restart Log Analyzer

Regards
Alex

[jjackowski]

I know.. but then the memory leakage will still occur ? I'm guessing so..

[KS-Soft]

Yes