Page 1 of 1
Cannot Logon to Data Base but Managment Studio can
Posted: Wed 16 Nov 2011 16:25
by Randy3W
I'm working with a data base at a new location. But cannot connect to it even though MS Management Studio can.
If I enter the login parameters in the Connection Dialog and press "Management Studio" It brings up the Management Studio with no problem. If I then press "Connect" I get :
[DBNETLIB][ConnectionOpen(Invalid Instance()).] Invalid connection..
Using :Delphi 2009
SDAC: 6.0.1 and 6.0.2
SQL Data Base : SQL server 2008 Express.
SQL Server Authentication : SQL Server
Posted: Wed 16 Nov 2011 17:35
by AndreyZ
Hello,
Please specify the value of the TMSConnection.ConnectString property. Make sure you set the correct SQL Server name with instance to the TMSConnection.Server property.
Posted: Wed 16 Nov 2011 17:47
by Randy3W
That has been double and triple checked.
My test was to
- double click on the TMSConnection to bring up the Connection Dialong box.
- Enter the Server signing in info.
- Press the "Management Studio" Button.
- This connected, and brooght up the Mgmt Studi. so I know the parameters were correct.
- I then pressed the "Connect" Button and got the indicated error. So I kno I was using the same parameters.
[/list]
Posted: Wed 16 Nov 2011 20:14
by Randy3W
AndreyZ,
If you need, I have set up a test login and data base that you can use to see if you get similar results. If so, let me know where I can email the specifics for you to try it.
Posted: Thu 17 Nov 2011 09:29
by AndreyZ
Please send your server IP, login, password, and database name to andreyz*devart*com.
Posted: Thu 17 Nov 2011 13:20
by Randy3W
Information has been sent
Posted: Mon 21 Nov 2011 10:47
by AndreyZ
I couldn't connect to your SQL Server neither with Microsoft SQL Server Management Studio nor with SDAC. Please check that you sent me the correct server IP.
Posted: Mon 21 Nov 2011 11:56
by Randy3W
Sorry, I sent you the wrong IP address. I re-sent you the info via email.
Posted: Mon 21 Nov 2011 15:55
by AndreyZ
I've reproduced this problem, it is caused by the OLEDB provider. You can check it using the standard ADO components. To solve the problem, you should use SQL Native provider instead of OLEDB provider. For this, you should set the TMSConnection.Options.Provider property to prAuto or prNativeClient.
Posted: Mon 21 Nov 2011 16:31
by Randy3W
THANKS!! That was exactly the problem. It had gotten changed to prSQL. I checked all my other connection and they were still set to prAuto, I must accidentally slipped and changed it at some point!
You are a life saver! Where do I send the check? LOL
Posted: Mon 21 Nov 2011 16:40
by AndreyZ
I'm happy that the problem has been solved. If any other questions come up, please contact us.