Page 1 of 1

Problem with "prDirect" provider

Posted: Mon 10 May 2021 10:49
by DanielNTM
Hello,

I have a random problem with certain workstations in a company.

When there is no activity for a while on
our software and that a connection has remained open,
the following error appears "OLE DB error occured. Code 80004005h" then the message
"[DBNETLIB] ConnectionWrite (Send ()).] General Network error
".

I saw on the following link: viewtopic.php?t=41337 that put the provider
the uniconnection that I use in "prdirect" could solve the problem.

The problem is that when I try to put this, all the TMemo of the software become problematic because
he tells me he expects a string type rather than a memo.

Does anyone have any idea where the problem might be?

Re: Problem with "prDirect" provider

Posted: Mon 10 May 2021 21:05
by ertank
Hello,

It is sometimes firewall devices breaking connections after a certain idle time in a corporate environment. It worth to check this out.

Regards,
Ertan

Re: Problem with "prDirect" provider

Posted: Tue 11 May 2021 07:46
by FCS
Hello,

To prevent disconnection try:
- check antivirus software /hardware for closing inactive connections.
- turn off hibernation (powercfg -h off having admin rights) and disk turning off.
- check version of Windows, between 1909 and 20H2 might be differences leading to this behaviour.

Regards
M.

Re: Problem with "prDirect" provider

Posted: Tue 18 May 2021 14:06
by Stellar
Hi Kevin,

Please be informed that “OLE DB error occurred. Code 80004005h” is relate to usage of outdated prSQL provider.
Kindly note that PrSQL uses the preinstalled Windows provider which has limited functionality.
We recommend using a different provider (prDirect, prNativeClient, or prMSOLEDB).
Please try to set Provider to prNativeClient or prDirect, for example:

Code: Select all

uses
  MSClasses;

...

MSConnection1.Options.Provider := prDirect; // prNativeClient;

More information on supported providers:
https://www.devart.com/sdac/docs/devart.sdac.tmsprovider.htm