Connection error - DBNetLib invalid instance with SQL 2000 on SBS2003.
-
We have a connection error when we are trying to connect into SQL 2000 installed on Small Business Server 2003.
The error is:
[DBNETLIB][ConnectionOpen (Invalid Instance()).]Invalid connection
There are three instances of SQL Server installed and we are attempting to connect into the default instance on port 1433. We have TCP/IP and named pipes enabled but we cannot figure out how to get in, either by using our application or by using Query Analyzer.
Does anyone have any suggestions before the server gets drop kicked out the window? Does SBS '03 have any firewall stuff we need to know about, or do any ports need to be enabled for it work?
Thanks in advance for any help on this one.
Keith
-
COuld you post how you are connecting (the connection string)? and what application you are using?
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question -
We get the error when we try to connect using Query Analyzer so I can't post the connection details for that one, but our app use the following:
cnADO.ConnectionString = "Provider = SQLOLEDB; Data Source=" & mstrServer & _
"; Initial Catalog=" & mstrDatabase & "; UID=" & mstrUID & _
";PWD=" & mstrPWD & ";OLE DB Services=-1"
where mstrServer is the default instance name, mstrDatabase is a valid database name and the username and password are also valid.
This connection string is used throughout our app suite and has been working fine for the past 3 years so we don't think it is that.
Of further interest the clients network administrator went on to the server and managed to get our app connecting into the database, however they then started getting the same error message from users connecting into named instances on the server whilst our one now works fine. We don't know what the guy did, or whether there is something really screwy happening on the server but I would be really interested to find out what caused this problem, as we spent half a day playing with settings trying to get it to connect.
As soon as I know what happened I will post it.
-
I forgot all about this one
Two things we found out
1. Small business server does not like using '(Local)' as a database name. Specify the actual instance name.
2. Turn off performance monitor. When this is turned on it stops the applications from connecting. Don't ask us why as performance monitor is not part of our remit but we are assuming there is something a bit weird about how they have it set up.
Hope this helps anyone else who has to connect on in.
Keith
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply