Not solved: Topic: AccessViolation when my server prog close

[jschmied]

This old toppic is still not solved !!!

I use TOracleSession in a ISAPI DLL. When I close this prog, I obtain an AccessViolation at address 78463A33 in module 'ntdll.dll'.
The access violation happends inside the LogOff() procedure.
I have DOA 345 with Delphi 5 on Win2000 SP2.

 

[Marco Kalter]

Can you verify if this is a Net8 problem? Do you have any other Net8 or SQL*Net installations that you can try?

When do you LogOff in this DLL? Is this an explicit LogOff, or is it a result of the fact that object instances are freed?

If this happens implicitly, can you change this and explicitly LogOff? I'm thinking that maybe there is a problem with the finalization order of the units in this DLL.

------------------
Marco Kalter
Allround Automations

 

[jschmied]

This looks like a Problem with w2k SP2. I don't get the error when the application is running on NT4.
The same happends on a standalone-client too when a second oracle session in not in the main-thread. (The main thread has it's own session.) I stepped trough the code with a debugger and it happends within a explicit LogOff().

Oracle:
8.1.7
System:
w2k SP2 with most pre sp3 fixpacks

 

[MarkR]

You should also note that Borland does not certify that executables created with Delphi 5 will work under Win2k. Therefore, I would be somewhat hesitant to write for Win2k with Delphi 5.

They do certify executables created with Delphi 6 to run under Win2k.

 

[sparis]

I had the same problem when I used a TDataBase (BDE) with a TOracleSession in a same server prog. I resolved it by changing the order of the opening of these objects. I must open TDataBase before TOracleSession. If I don't do that, I have an AV.