access violation in module secur32.dll ?

Flo77 · Post by **Flo77** » Fri 21 Sep 2007 10:43

Hi,

on Windows Vista I get the error "access violation at adress ... in module secur32.dll" when I try to connect to a SQLServer 2005 Express database - the same procedure call works fine on Windows XP.
At design time the connection can be established (setting the TMSConnection property "Connected" to true)...

What can be the reason for this failure?

My SDAC version is 4.10.0.10 ...

Antaeus · Post by **Antaeus** » Fri 21 Sep 2007 12:29

Other users did not report us about such problems. Probably the problem is related to your environment.
What IDE do you use? Do you run either Delphi, or the final application in compatibility mode?

Flo77 · Post by **Flo77** » Mon 24 Sep 2007 07:05

My IDE is CodeGear C++ Builder 2007, it does not run in compatibility mode.

My application also does not run in compatibility mode (the descripted error occurs in both compatibility and normal mode), and has administrator rights.

The access violation occurs right when the connect statement of the TMSConnection is called, other statements before and after are executed wihout error.

Antaeus · Post by **Antaeus** » Mon 24 Sep 2007 08:08

Please describe in what application, and in what place of the application does the problem appear.
I've found one thread among MSDN Forums that may be related to this problem.

Flo77 · Post by **Flo77** » Mon 24 Sep 2007 08:55

This thread in MSDN Forums explains my problem ... sorry, I didn't find it by myself.

The problem obviously is with GetUserName() - which likely is called indirect as I don't have this statement in my application. So I'm not sure if this is a problem of SDAC...

The problem occurs right after the start of the application when the connection to the database is to be established ( in FormCreate() ).
What else do you need to know about my application (if ever this is a problem concerning SDAC)?

Flo77 · Post by **Flo77** » Mon 24 Sep 2007 10:54

Ok, what I did now was changing the position of the Connect() statement (no longer in WinMain() ) - with no effect. The error each time occurs when calling TMSConnection->Connect();

Here's the list of DLLs being loaded with the Connect() statement:

CLBCatQ.DLL
SQLOLEDB.dll
MSDART.DLL
MSDATL3.dll
OLEDB32.dll
WININET.dll
Normaliz.dll
OLEDB32R.dll
DBnetlib.dll
Security.dll
-> Exception-class EAccessViolation with message 'access violation at address ... in module 'Secur32.dll'.

Antaeus · Post by **Antaeus** » Wed 26 Sep 2007 07:28

Please send us a complete small test application at evgeniyd*crlab*com to reproduce the problem. Also specify the exact version of your Vista, and the exact client version. You can see the client version in the About sheet of TMSConnection Editor.

Flo77 · Post by **Flo77** » Wed 26 Sep 2007 11:21

I divided my program in seperate parts and seperatly the connect-statment did work. So I managed to trace down the error: it has to do with including RAPI functions. I don't know why the error occured when calling Connect() ...

Thanks for your help!