Hello,
I am building an Webserver Module (.so) for the Apache 2.0.61 Webserver using Delphi 7 Enterprise.
I am using the 4.30 version of SDAC.
Everytime I am using the local installed SQL 2000 Server it works fine, but when trying to connect to a Server which is not locally installed it fails.
Additionally I tried it on a small business Server with SQL 2005 installed locally this also don't works the way I want.
Is there any specific information I have to know or to set to get this working?
On the small business Server it generally don't work (as apache modul)... no difference between using a locally installed sql 2000 version or sql 2005 version.
Many thanks in advance.
/Günter
Apache Modul ... Connection Failure
-
- Posts: 9
- Joined: Fri 10 Nov 2006 12:01
Sadly there isn't any kind of error message. No one in the apache log and no one appear when debuging the apache modul. It simply stops without any kind of error message when passing the line with the Connect command.
It works if using a GUI application or service.
What I've found out in the meantime is that if I select as provider "prSQL" instead of "prAuto" it works, but I don't know why. It would provide a more trusted feeling for the correctness of the written code.
It works if using a GUI application or service.
What I've found out in the meantime is that if I select as provider "prSQL" instead of "prAuto" it works, but I don't know why. It would provide a more trusted feeling for the correctness of the written code.
SDAC can work through SQL OLEDB provider (prSQL) and through SQL Native Client provider (prNativeClient). With the prAuto option SDAC initially checks whether the SQL Native Client is installed. If it is installed, SDAC connects using SQL Native Client, otherwise the SQL OLEDB provider is used.
It looks that there is something wrong with the SQL Native Client provider installed on your computer. Try to download its last version by this link, and install it. Does it solve the connection problem with the prAuto option value.
It looks that there is something wrong with the SQL Native Client provider installed on your computer. Try to download its last version by this link, and install it. Does it solve the connection problem with the prAuto option value.
-
- Posts: 9
- Joined: Fri 10 Nov 2006 12:01
Hello,
thank you for your reply ... I will test this ...
But the question is for me now, when choosing prAuto and my native 2005 client is not correct installed, why does TMSConnection not automatically use OLEDB? And why does the prAuto setting works on same pc with same user if using a GUI application?
thank you for your reply ... I will test this ...
But the question is for me now, when choosing prAuto and my native 2005 client is not correct installed, why does TMSConnection not automatically use OLEDB? And why does the prAuto setting works on same pc with same user if using a GUI application?
SDAC can determine that SQL Native Client is installed, but it cannot determine its operability.guenter1978 wrote:But the question is for me now, when choosing prAuto and my native 2005 client is not correct installed, why does TMSConnection not automatically use OLEDB?
Probably it is a peculiarity of the project you are making. Could you send me a web server module example at sdac*crlab*com to demonstrate this connection issue?guenter1978 wrote:And why does the prAuto setting works on same pc with same user if using a GUI application?