Devart Forums

Dear Fried,


I´m a customer. I´m Development Manager of Freire Informática Brazil. We bought the MS SQL DBX Driver from you.


We are having some problems with MS SQL Server 2005 when trying to connect with tcp/ip. With named pipes we don’t have any problems. Therefore, we might connect with tcp/ip.


My connection params are:


SQLConnection.DriverName := 'SQLServer';

SQLConnection.LibraryName := 'dbexpsda.dll';

SQLConnection.VendorLib := 'sqloledb.dll';

SQLConnection.GetDriverFunc := 'getSQLDriverSQLServer';

SQLConnection.Params.Clear;

SQLConnection.Params.Add('User_Name=MyName');

SQLConnection.Params.Add('Password=MyPassword');

SQLConnection.Params.Add('HostName=MyServer');

SQLConnection.Params.Add('Database=MyDatabase');



The driver raises the error: [DBNETLIB][ConnectionOpen(Invalid Instance()).]Invalid Connection



If I change to named pipes like:



SQLConnection.DriverName := 'SQLServer';

SQLConnection.LibraryName := 'dbexpsda.dll';

SQLConnection.VendorLib := 'sqloledb.dll';

SQLConnection.GetDriverFunc := 'getSQLDriverSQLServer';

SQLConnection.Params.Clear;

SQLConnection.Params.Add('User_Name=MyName');

SQLConnection.Params.Add('Password=MyPassword');

SQLConnection.Params.Add('HostName=MyServer\');

SQLConnection.Params.Add('Database=MyDatabase');



The connection is sucessful.



How can i resolve my problem?



Thanks

Thiago Alves Costa

Freire Informática - http://www.freire.com.br

[email protected]

My Tcp/ip protocol is enabled in SQl Server in port 1433. I can conect via tcp via java jdbc with no problems.

What is your environment?

I´m using SQL Server 2005 9.00.1.1399.06 in Win XP with dbexpsda.dll 2.50.5.0

Can you establish connection using ADO and QueryAnalyzer?

Yes... Via ado using ODBC bridge i can. I'm using the MSDE version that not contains query analizer and the old version (2000) dont connect to 2005 server. I can connect with JTDS (driver for java) with tcp/ip and named pipes with no problems. With corelab driver for delphi only with named pipes it is possible: \. With SQL server 2000 i have no problems with corelab. Only with sql server 2005 MSDE. The server is running at 1433 port. The port is opened. The service is up. I use telnet 1433 and it is ok.

Thanks

Please try to connect to your SQL Server 2005 using ADO with OLE DB Provider for SQL Server or SQL Native Client.

Dear Friend,

I´ve put some captured images of my enviroment in http://www.freire.com.br/des/crlab/

That will help you to solve my problem!

---- ADO OBJECT:

object ADOConnection1: TADOConnection
ConnectionString =
'Provider=SQLNCLI.1;Persist Security Info=False;User ID=sa;Data S' +
'ource=localhost'
Provider = 'SQLNCLI.1'
Left = 168
Top = 152
end

---- CRLAB OBJECT:

object CRSQLConnection1: TCRSQLConnection
ConnectionName = 'SQLServerConnection'
DriverName = 'SQLServer'
GetDriverFunc = 'getSQLDriverSQLServer'
LibraryName = 'dbexpsda.dll'
Params.Strings = (
'BlobSize=-1'
'HostName=localhost'
'DataBase=freire'
'DriverName=SQLServer'
'User_Name=sa'
'Password=freire'
'LongStrings=True'
'EnableBCD=True'
'FetchAll=True')
VendorLib = 'sqloledb.dll'
Left = 400
Top = 136
end


Using Ado the connection was sucessful and using crlab the connection failed. Look at http://www.freire.com.br/des/crlab/ and see my problem!

Thanks

Thiago

Thank you for information.
We reproduced the problem and fixed it. This fix will be included in the next DbxSda 3.00.5 build. It will be available in about one week.
Please watch for announcements at the forum http://crlab.com/forums/viewforum.php?f=10

Thanks. I'll wait.

I have a question. Web have bougth the 2.50.5.0 version. How can i download a registered version with that correction next week? In the email that i have received from you, the link to download always redirect to 2.50.5.0 version. There dont say how can i download a most recently version.

Thiago Costa
Freire Informática

Unfortunately you can't get the last build of DbxSda using your current license. To get DbxSda 3 you have to upgrade first.

Ok, but how can i download the version 2 with that correction. That is a bug, not a new implementation. So, we have right to obtain a correction. We bougth the version 2 that has in documentation that suports sql server 2005. In pactice it was not true.

If the version 3 has some functionality that is interesting, we will buy it, but the version 2 appears to be good for us, except when connect to sql server 2005. But that not correspont with the documentation.

Thanks

Thiago

Please send your registration information to EvgeniyD*crlab*com.

Ok... Done