Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Can not connect to sql2000 from some WS
- Thread starter sguslan
- Start date
tlbroadbent
MIS
What is the name of the SQL 2000 instance? What port is SQL 2000 set to listen on? Terry L. Broadbent
FAQ183-874 contains tips for posting questions in these forums.
NOTE: Reference to the FAQ is not directed at any individual.
hmmm....
I've experienced this too...
I don't know the exact solutions.... I'm trying to search for the solutions also...
But, for a moment, you can try to install SQL Tools named = Connectivity tools.
Try to install it from your SQL Server 2000 CD.
It works for me...
Jokauw
I've experienced this too...
I don't know the exact solutions.... I'm trying to search for the solutions also...
But, for a moment, you can try to install SQL Tools named = Connectivity tools.
Try to install it from your SQL Server 2000 CD.
It works for me...
Jokauw
- Thread starter
- #4
Thanx for replying ..
I resolved the issue by recreating the Standard SQL user (used by oledb/odbc) and re-applying the database permissions.
It still do not understand it, because when creating the user I did it in the same manner every time I created a SQL login.
The name of the instance is servername\servername1 and the port is the standard 1433.
I resolved the issue by recreating the Standard SQL user (used by oledb/odbc) and re-applying the database permissions.
It still do not understand it, because when creating the user I did it in the same manner every time I created a SQL login.
The name of the instance is servername\servername1 and the port is the standard 1433.
- Status
Similar threads
- Locked
- Question