Ole DB Error occured. Code 80040E14h

amendes · Post by **amendes** » Thu 05 Jan 2006 19:13

When I run a query "select getdate() g, 1 s + 1" for the second time, the error raises is "Ole DB Error occured. Code 80040E14h".
Somebody can help me ?

Ikar · Post by **Ikar** » Fri 06 Jan 2006 10:41

We get this error on first execution.
This error code means "The command contained one or more errors".
Please specify your exact SDAC version.

Adriano · Post by **Adriano** » Fri 06 Jan 2006 11:17

Of course
my version is 3.55.2.21

and anoter information, my app is runing on Multi-thread architecture, when I call CoInitializeEx, I call with COINIT_MULTITHREADED.

Ikar · Post by **Ikar** » Fri 06 Jan 2006 12:50

> my app is runing on Multi-thread architecture

Most likely, it's a source of the incompleteness of the error message.

Adriano · Post by **Adriano** » Fri 06 Jan 2006 16:05

Ikar

Anoter information about this error.

1. My app works same a WebServer, aswer requests coming from clients.
2. For any thread I have one MSConnection and one MSQuery, and before each call MSConnection.Connect I call CoInitializeEx. So each thead have one CoInitializeEX, and is independent.
3. Is same cases a erros rised is EMSError, but in this cases the error is EOLEDBError. When it is EMSError, I have no problems, but, when it is EOLEDBError, the property Message is "Ole DB Error occured. Code 80040E14h".

This informations can help you to help me ???

Adriano · Post by **Adriano** » Tue 10 Jan 2006 10:43

Someone cam help me ??

Ikar · Post by **Ikar** » Tue 10 Jan 2006 10:50

Which problem disturbs you: error in SQL or wrong type of exception?

Adriano · Post by **Adriano** » Tue 10 Jan 2006 11:17

Ikar

None of then

The error message is my problem, because in same cases one trigger in DB raises an exception when it check data integrity, and the messages is raised to software user, so the message is "Ole DB Error occured. Code 80040E14h" is not a good message for a user.

This is a BUG in SDAC or a plataform limitation ?

Ikar · Post by **Ikar** » Tue 10 Jan 2006 13:11

This is OLED DB (MS SQL) limitation. Maybe we can provide a solution
to avoid this limitation, but we need a complete small sample to reproduce
the problem. Send us please such sample.

Adriano · Post by **Adriano** » Mon 16 Jan 2006 13:33

Ikar

When I building a sample to sendo to you, I change a bit the original code. With this, my program aparently woks well.

Now, for each "Thread".Execute procedure called, I call a CoInitializeEx in begin and call CoUninitialize before the end of procedure.

My application recive many request in a short time, it works well ???