Connection failed:
SQL State: '01000'
SQL Server Error: 10061
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]
ConnectionOpen (Connect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]
SQL Server does not exist or access denied.
now i cannot even create the DSN how to solve it please
help me iam in trouble please
How are you connecting to SQL Server? SQL Server login or Windows login?
Do you have Server Security configuration set up correcly?
Following error also comes up when security says "windows mode" and we
connect with "sql server login" or vice versa.
"SubhashChoowdary" wrote:
> Connection failed:
> SQL State: '01000'
> SQL Server Error: 10061
> [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]
> ConnectionOpen (Connect()).
> Connection failed:
> SQLState: '08001'
> SQL Server Error: 17
> [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]
> SQL Server does not exist or access denied.
> now i cannot even create the DSN how to solve it please
> help me iam in trouble please
>
Showing posts with label state. Show all posts
Showing posts with label state. Show all posts
Saturday, February 25, 2012
Connection Error
Connection failed:
SQL State: '01000'
SQL Server Error: 10061
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]
ConnectionOpen (Connect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]
SQL Server does not exist or access denied.
now i cannot even create the DSN how to solve it please
help me iam in trouble please
How are you connecting to SQL Server? SQL Server login or Windows login?
Do you have Server Security configuration set up correcly?
Following error also comes up when security says "windows mode" and we
connect with "sql server login" or vice versa.
"SubhashChoowdary" wrote:
> Connection failed:
> SQL State: '01000'
> SQL Server Error: 10061
> [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]
> ConnectionOpen (Connect()).
> Connection failed:
> SQLState: '08001'
> SQL Server Error: 17
> [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]
> SQL Server does not exist or access denied.
> now i cannot even create the DSN how to solve it please
> help me iam in trouble please
>
SQL State: '01000'
SQL Server Error: 10061
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]
ConnectionOpen (Connect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]
SQL Server does not exist or access denied.
now i cannot even create the DSN how to solve it please
help me iam in trouble please
How are you connecting to SQL Server? SQL Server login or Windows login?
Do you have Server Security configuration set up correcly?
Following error also comes up when security says "windows mode" and we
connect with "sql server login" or vice versa.
"SubhashChoowdary" wrote:
> Connection failed:
> SQL State: '01000'
> SQL Server Error: 10061
> [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]
> ConnectionOpen (Connect()).
> Connection failed:
> SQLState: '08001'
> SQL Server Error: 17
> [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]
> SQL Server does not exist or access denied.
> now i cannot even create the DSN how to solve it please
> help me iam in trouble please
>
Sunday, February 19, 2012
connection
Hello,
I'm getting the error below...
The connection was not closed. The connection's current state is open.
And heres the code thats casung the problem,...
publicstaticvoid JoinGroup(string GroupID,string User_ID){
SqlCommand cmd =newSqlCommand("insert into User_Joined_Groups (GroupID, User_ID) values (@.GroupID, @.User_ID)", conn);conn.Open();
cmd.Parameters.Add(newSqlParameter("@.GroupID", GroupID));cmd.Parameters.Add(newSqlParameter("@.User_ID", User_ID));
cmd.ExecuteNonQuery();
conn.Close();
}
The method is called on a button click
anyone know what I've done wrong?
Thank you
Open your connection before using it when establishing your command. Also, make sure you have created your connection with the proper connection string before opening it:
public static void JoinGroup(string GroupID,string User_ID) {conn =new SqlConnection(connStr);
conn.Open();SqlCommand cmd =new SqlCommand("insert into User_Joined_Groups (GroupID, User_ID) values (@.GroupID, @.User_ID)", conn); cmd.Parameters.Add(new SqlParameter("@.GroupID", GroupID));cmd.Parameters.Add(new SqlParameter("@.User_ID", User_ID)); cmd.ExecuteNonQuery();conn.Close();}|||
champion!
Tuesday, February 14, 2012
Connecting to to Sql server through ODBC
I am having problems accessing the sql server through ODBC.
I got the follong error:
Connection Failed:
SQL State: 01000
SQL Serve Error: 53[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectioOpen
(Connect()). Connection failed.
I then upgraded to Sql sp3a
Now I am receiving the error:
Connection Failed:
SQL State: 01000
SQL Server Error: 011001
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen
(Connect()). Connection failed.
Connection Failed:
SQL State: 08001
SQL Server Error: 6
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Specified SQL Server
Not found.
Let me give you an idea of our network structure and some of the issues:
We now have 2 servers. Win 2000 server and the Win 2003 server which is
running sql server 2000(This is a new server just bought).
The Win2000 server is running Active directory and is the main domain
controller.
The win 2003 server is not running Active directory.
I want all user to login to this server (Win 2000) and those requiring Great
Plains will then attach to the Win2003 Server after completing login to the
network through the win 2000 server.
The win 2003 server is running sql service pack3a
I can access shared folders on this Win 2003 server from Network places on
any machine on the network.
I can ping the 2003 server using the Ip address and Name.
Any ideas please?
cool lady
Was the SQL Server installed as the default or a named instance? What port
was it assigned to? What server name are you using in your ODBC connection?
Have you tried to connect via SQL Enterprise Manager or Query Analyzer? Do
you have permission to connect to this SQL Server installation?
Sincerely,
Anthony Thomas
"Betmck" wrote:
> I am having problems accessing the sql server through ODBC.
> I got the follong error:
> Connection Failed:
> SQL State: 01000
> SQL Serve Error: 53[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectioOpen
> (Connect()). Connection failed.
> I then upgraded to Sql sp3a
> Now I am receiving the error:
> Connection Failed:
> SQL State: 01000
> SQL Server Error: 011001
> [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen
> (Connect()). Connection failed.
> Connection Failed:
> SQL State: 08001
> SQL Server Error: 6
> [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Specified SQL Server
> Not found.
>
> Let me give you an idea of our network structure and some of the issues:
> We now have 2 servers. Win 2000 server and the Win 2003 server which is
> running sql server 2000(This is a new server just bought).
> The Win2000 server is running Active directory and is the main domain
> controller.
> The win 2003 server is not running Active directory.
> I want all user to login to this server (Win 2000) and those requiring Great
> Plains will then attach to the Win2003 Server after completing login to the
> network through the win 2000 server.
> The win 2003 server is running sql service pack3a
> I can access shared folders on this Win 2003 server from Network places on
> any machine on the network.
> I can ping the 2003 server using the Ip address and Name.
> Any ideas please?
>
> --
> cool lady
|||SQL Server installed with a named instance.
Port is 1433 which is automatically assigned
Server Name in the ODBC connection is SVBNTSQL\MBSGP
I have tried connecting via both Enterprise manager and query Analyzer.
Not sure if I have permission to connect. Where should I check for this?
Thanks
"AnthonyThomas" wrote:
[vbcol=seagreen]
> Was the SQL Server installed as the default or a named instance? What port
> was it assigned to? What server name are you using in your ODBC connection?
> Have you tried to connect via SQL Enterprise Manager or Query Analyzer? Do
> you have permission to connect to this SQL Server installation?
> Sincerely,
>
> Anthony Thomas
>
> "Betmck" wrote:
|||I also tried to Telnet the sql server. If I just use the Ip adress alone I
will get through. When I attached 1433 at the end I get an error "could not
open a connection to host on port 1433: connect failed.
"AnthonyThomas" wrote:
[vbcol=seagreen]
> Was the SQL Server installed as the default or a named instance? What port
> was it assigned to? What server name are you using in your ODBC connection?
> Have you tried to connect via SQL Enterprise Manager or Query Analyzer? Do
> you have permission to connect to this SQL Server installation?
> Sincerely,
>
> Anthony Thomas
>
> "Betmck" wrote:
|||This is what the error log.:
2004-11-08 14:37:30.40 server Microsoft SQL Server 2000 - 8.00.194
(Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: )
2004-11-08 14:37:30.40 server Copyright (C) 1988-2000 Microsoft
Corporation.
2004-11-08 14:37:30.40 server All rights reserved.
2004-11-08 14:37:30.40 server Server Process ID is 1532.
2004-11-08 14:37:30.40 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL$MBSGP\log\ERRORLOG'.
2004-11-08 14:37:30.43 server SQL Server is starting at priority class
'normal'(2 CPUs detected).
2004-11-08 14:37:30.67 server SQL Server configured for thread mode
processing.
2004-11-08 14:37:30.68 server Using dynamic lock allocation. [2500] Lock
Blocks, [5000] Lock Owner Blocks.
2004-11-08 14:37:30.71 server Attempting to initialize Distributed
Transaction Coordinator.
2004-11-08 14:37:35.48 spid4 Starting up database 'master'.
2004-11-08 14:37:40.40 server Using 'SSNETLIB.DLL' version '8.0.194'.
2004-11-08 14:37:40.40 spid5 Starting up database 'model'.
2004-11-08 14:37:40.40 spid4 Server name is 'SVBNTSQL\MBSGP'.
2004-11-08 14:37:40.40 spid8 Starting up database 'msdb'.
2004-11-08 14:37:40.40 spid9 Starting up database 'pubs'.
2004-11-08 14:37:40.40 spid10 Starting up database 'Northwind'.
2004-11-08 14:37:40.40 spid11 Starting up database 'DYNAMICS'.
2004-11-08 14:37:40.40 spid12 Starting up database 'TWO'.
2004-11-08 14:37:40.43 spid13 Starting up database 'SVB'.
2004-11-08 14:37:40.43 server SQL server listening on Shared Memory,
Named Pipes.
2004-11-08 14:37:40.43 server SQL Server is ready for client connections
2004-11-08 14:37:40.53 spid5 Clearing tempdb database.
2004-11-08 14:37:40.73 spid5 Starting up database 'tempdb'.
2004-11-08 14:37:40.75 spid4 Recovery complete.
2004-11-08 14:37:40.78 spid4 Launched startup procedure
'smDEX_Build_Locks'
2004-11-08 14:51:39.97 spid51 Using 'xpsqlbot.dll' version '2000.80.194'
to execute extended stored procedure 'xp_qv'.
2004-11-08 14:53:43.56 spid4 SQL Server is terminating due to 'stop'
request from Service Control Manager.
"AnthonyThomas" wrote:
[vbcol=seagreen]
> Was the SQL Server installed as the default or a named instance? What port
> was it assigned to? What server name are you using in your ODBC connection?
> Have you tried to connect via SQL Enterprise Manager or Query Analyzer? Do
> you have permission to connect to this SQL Server installation?
> Sincerely,
>
> Anthony Thomas
>
> "Betmck" wrote:
|||Your server has not been set up to use TCP/IP. If you look at your error
log, about 1/3 of the way through, you will see the line:
2004-11-08 14:37:40.43 server SQL server listening on Shared Memory,
Named Pipes.
No, TCP/IP. Usually, this is because it was never selected as part of the
installation or there was an IP Bind error. The Bind error also would have
shown up in the list. On the server, you need to, or have your server admin,
run the Server Network utility and add the TCP/IP protocol to the list. You
will also have to specify the port. If the Named Instance is the only
instance, then you can use 1433.
Sincerely,
Anthony Thomas
"Betmck" wrote:
[vbcol=seagreen]
> This is what the error log.:
> 2004-11-08 14:37:30.40 server Microsoft SQL Server 2000 - 8.00.194
> (Intel X86)
> Aug 6 2000 00:57:48
> Copyright (c) 1988-2000 Microsoft Corporation
> Standard Edition on Windows NT 5.2 (Build 3790: )
> 2004-11-08 14:37:30.40 server Copyright (C) 1988-2000 Microsoft
> Corporation.
> 2004-11-08 14:37:30.40 server All rights reserved.
> 2004-11-08 14:37:30.40 server Server Process ID is 1532.
> 2004-11-08 14:37:30.40 server Logging SQL Server messages in file
> 'C:\Program Files\Microsoft SQL Server\MSSQL$MBSGP\log\ERRORLOG'.
> 2004-11-08 14:37:30.43 server SQL Server is starting at priority class
> 'normal'(2 CPUs detected).
> 2004-11-08 14:37:30.67 server SQL Server configured for thread mode
> processing.
> 2004-11-08 14:37:30.68 server Using dynamic lock allocation. [2500] Lock
> Blocks, [5000] Lock Owner Blocks.
> 2004-11-08 14:37:30.71 server Attempting to initialize Distributed
> Transaction Coordinator.
> 2004-11-08 14:37:35.48 spid4 Starting up database 'master'.
> 2004-11-08 14:37:40.40 server Using 'SSNETLIB.DLL' version '8.0.194'.
> 2004-11-08 14:37:40.40 spid5 Starting up database 'model'.
> 2004-11-08 14:37:40.40 spid4 Server name is 'SVBNTSQL\MBSGP'.
> 2004-11-08 14:37:40.40 spid8 Starting up database 'msdb'.
> 2004-11-08 14:37:40.40 spid9 Starting up database 'pubs'.
> 2004-11-08 14:37:40.40 spid10 Starting up database 'Northwind'.
> 2004-11-08 14:37:40.40 spid11 Starting up database 'DYNAMICS'.
> 2004-11-08 14:37:40.40 spid12 Starting up database 'TWO'.
> 2004-11-08 14:37:40.43 spid13 Starting up database 'SVB'.
> 2004-11-08 14:37:40.43 server SQL server listening on Shared Memory,
> Named Pipes.
> 2004-11-08 14:37:40.43 server SQL Server is ready for client connections
> 2004-11-08 14:37:40.53 spid5 Clearing tempdb database.
> 2004-11-08 14:37:40.73 spid5 Starting up database 'tempdb'.
> 2004-11-08 14:37:40.75 spid4 Recovery complete.
> 2004-11-08 14:37:40.78 spid4 Launched startup procedure
> 'smDEX_Build_Locks'
> 2004-11-08 14:51:39.97 spid51 Using 'xpsqlbot.dll' version '2000.80.194'
> to execute extended stored procedure 'xp_qv'.
> 2004-11-08 14:53:43.56 spid4 SQL Server is terminating due to 'stop'
> request from Service Control Manager.
> "AnthonyThomas" wrote:
|||Thanks for you help Anthony. However after taking a closer look at the error
log, I realize that Sql Sp3 was not installed properly. After installing it
again, everything is working fine now.
"AnthonyThomas" wrote:
[vbcol=seagreen]
> Your server has not been set up to use TCP/IP. If you look at your error
> log, about 1/3 of the way through, you will see the line:
> 2004-11-08 14:37:40.43 server SQL server listening on Shared Memory,
> Named Pipes.
> No, TCP/IP. Usually, this is because it was never selected as part of the
> installation or there was an IP Bind error. The Bind error also would have
> shown up in the list. On the server, you need to, or have your server admin,
> run the Server Network utility and add the TCP/IP protocol to the list. You
> will also have to specify the port. If the Named Instance is the only
> instance, then you can use 1433.
> Sincerely,
>
> Anthony Thomas
>
> "Betmck" wrote:
I got the follong error:
Connection Failed:
SQL State: 01000
SQL Serve Error: 53[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectioOpen
(Connect()). Connection failed.
I then upgraded to Sql sp3a
Now I am receiving the error:
Connection Failed:
SQL State: 01000
SQL Server Error: 011001
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen
(Connect()). Connection failed.
Connection Failed:
SQL State: 08001
SQL Server Error: 6
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Specified SQL Server
Not found.
Let me give you an idea of our network structure and some of the issues:
We now have 2 servers. Win 2000 server and the Win 2003 server which is
running sql server 2000(This is a new server just bought).
The Win2000 server is running Active directory and is the main domain
controller.
The win 2003 server is not running Active directory.
I want all user to login to this server (Win 2000) and those requiring Great
Plains will then attach to the Win2003 Server after completing login to the
network through the win 2000 server.
The win 2003 server is running sql service pack3a
I can access shared folders on this Win 2003 server from Network places on
any machine on the network.
I can ping the 2003 server using the Ip address and Name.
Any ideas please?
cool lady
Was the SQL Server installed as the default or a named instance? What port
was it assigned to? What server name are you using in your ODBC connection?
Have you tried to connect via SQL Enterprise Manager or Query Analyzer? Do
you have permission to connect to this SQL Server installation?
Sincerely,
Anthony Thomas
"Betmck" wrote:
> I am having problems accessing the sql server through ODBC.
> I got the follong error:
> Connection Failed:
> SQL State: 01000
> SQL Serve Error: 53[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectioOpen
> (Connect()). Connection failed.
> I then upgraded to Sql sp3a
> Now I am receiving the error:
> Connection Failed:
> SQL State: 01000
> SQL Server Error: 011001
> [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen
> (Connect()). Connection failed.
> Connection Failed:
> SQL State: 08001
> SQL Server Error: 6
> [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Specified SQL Server
> Not found.
>
> Let me give you an idea of our network structure and some of the issues:
> We now have 2 servers. Win 2000 server and the Win 2003 server which is
> running sql server 2000(This is a new server just bought).
> The Win2000 server is running Active directory and is the main domain
> controller.
> The win 2003 server is not running Active directory.
> I want all user to login to this server (Win 2000) and those requiring Great
> Plains will then attach to the Win2003 Server after completing login to the
> network through the win 2000 server.
> The win 2003 server is running sql service pack3a
> I can access shared folders on this Win 2003 server from Network places on
> any machine on the network.
> I can ping the 2003 server using the Ip address and Name.
> Any ideas please?
>
> --
> cool lady
|||SQL Server installed with a named instance.
Port is 1433 which is automatically assigned
Server Name in the ODBC connection is SVBNTSQL\MBSGP
I have tried connecting via both Enterprise manager and query Analyzer.
Not sure if I have permission to connect. Where should I check for this?
Thanks
"AnthonyThomas" wrote:
[vbcol=seagreen]
> Was the SQL Server installed as the default or a named instance? What port
> was it assigned to? What server name are you using in your ODBC connection?
> Have you tried to connect via SQL Enterprise Manager or Query Analyzer? Do
> you have permission to connect to this SQL Server installation?
> Sincerely,
>
> Anthony Thomas
>
> "Betmck" wrote:
|||I also tried to Telnet the sql server. If I just use the Ip adress alone I
will get through. When I attached 1433 at the end I get an error "could not
open a connection to host on port 1433: connect failed.
"AnthonyThomas" wrote:
[vbcol=seagreen]
> Was the SQL Server installed as the default or a named instance? What port
> was it assigned to? What server name are you using in your ODBC connection?
> Have you tried to connect via SQL Enterprise Manager or Query Analyzer? Do
> you have permission to connect to this SQL Server installation?
> Sincerely,
>
> Anthony Thomas
>
> "Betmck" wrote:
|||This is what the error log.:
2004-11-08 14:37:30.40 server Microsoft SQL Server 2000 - 8.00.194
(Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: )
2004-11-08 14:37:30.40 server Copyright (C) 1988-2000 Microsoft
Corporation.
2004-11-08 14:37:30.40 server All rights reserved.
2004-11-08 14:37:30.40 server Server Process ID is 1532.
2004-11-08 14:37:30.40 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL$MBSGP\log\ERRORLOG'.
2004-11-08 14:37:30.43 server SQL Server is starting at priority class
'normal'(2 CPUs detected).
2004-11-08 14:37:30.67 server SQL Server configured for thread mode
processing.
2004-11-08 14:37:30.68 server Using dynamic lock allocation. [2500] Lock
Blocks, [5000] Lock Owner Blocks.
2004-11-08 14:37:30.71 server Attempting to initialize Distributed
Transaction Coordinator.
2004-11-08 14:37:35.48 spid4 Starting up database 'master'.
2004-11-08 14:37:40.40 server Using 'SSNETLIB.DLL' version '8.0.194'.
2004-11-08 14:37:40.40 spid5 Starting up database 'model'.
2004-11-08 14:37:40.40 spid4 Server name is 'SVBNTSQL\MBSGP'.
2004-11-08 14:37:40.40 spid8 Starting up database 'msdb'.
2004-11-08 14:37:40.40 spid9 Starting up database 'pubs'.
2004-11-08 14:37:40.40 spid10 Starting up database 'Northwind'.
2004-11-08 14:37:40.40 spid11 Starting up database 'DYNAMICS'.
2004-11-08 14:37:40.40 spid12 Starting up database 'TWO'.
2004-11-08 14:37:40.43 spid13 Starting up database 'SVB'.
2004-11-08 14:37:40.43 server SQL server listening on Shared Memory,
Named Pipes.
2004-11-08 14:37:40.43 server SQL Server is ready for client connections
2004-11-08 14:37:40.53 spid5 Clearing tempdb database.
2004-11-08 14:37:40.73 spid5 Starting up database 'tempdb'.
2004-11-08 14:37:40.75 spid4 Recovery complete.
2004-11-08 14:37:40.78 spid4 Launched startup procedure
'smDEX_Build_Locks'
2004-11-08 14:51:39.97 spid51 Using 'xpsqlbot.dll' version '2000.80.194'
to execute extended stored procedure 'xp_qv'.
2004-11-08 14:53:43.56 spid4 SQL Server is terminating due to 'stop'
request from Service Control Manager.
"AnthonyThomas" wrote:
[vbcol=seagreen]
> Was the SQL Server installed as the default or a named instance? What port
> was it assigned to? What server name are you using in your ODBC connection?
> Have you tried to connect via SQL Enterprise Manager or Query Analyzer? Do
> you have permission to connect to this SQL Server installation?
> Sincerely,
>
> Anthony Thomas
>
> "Betmck" wrote:
|||Your server has not been set up to use TCP/IP. If you look at your error
log, about 1/3 of the way through, you will see the line:
2004-11-08 14:37:40.43 server SQL server listening on Shared Memory,
Named Pipes.
No, TCP/IP. Usually, this is because it was never selected as part of the
installation or there was an IP Bind error. The Bind error also would have
shown up in the list. On the server, you need to, or have your server admin,
run the Server Network utility and add the TCP/IP protocol to the list. You
will also have to specify the port. If the Named Instance is the only
instance, then you can use 1433.
Sincerely,
Anthony Thomas
"Betmck" wrote:
[vbcol=seagreen]
> This is what the error log.:
> 2004-11-08 14:37:30.40 server Microsoft SQL Server 2000 - 8.00.194
> (Intel X86)
> Aug 6 2000 00:57:48
> Copyright (c) 1988-2000 Microsoft Corporation
> Standard Edition on Windows NT 5.2 (Build 3790: )
> 2004-11-08 14:37:30.40 server Copyright (C) 1988-2000 Microsoft
> Corporation.
> 2004-11-08 14:37:30.40 server All rights reserved.
> 2004-11-08 14:37:30.40 server Server Process ID is 1532.
> 2004-11-08 14:37:30.40 server Logging SQL Server messages in file
> 'C:\Program Files\Microsoft SQL Server\MSSQL$MBSGP\log\ERRORLOG'.
> 2004-11-08 14:37:30.43 server SQL Server is starting at priority class
> 'normal'(2 CPUs detected).
> 2004-11-08 14:37:30.67 server SQL Server configured for thread mode
> processing.
> 2004-11-08 14:37:30.68 server Using dynamic lock allocation. [2500] Lock
> Blocks, [5000] Lock Owner Blocks.
> 2004-11-08 14:37:30.71 server Attempting to initialize Distributed
> Transaction Coordinator.
> 2004-11-08 14:37:35.48 spid4 Starting up database 'master'.
> 2004-11-08 14:37:40.40 server Using 'SSNETLIB.DLL' version '8.0.194'.
> 2004-11-08 14:37:40.40 spid5 Starting up database 'model'.
> 2004-11-08 14:37:40.40 spid4 Server name is 'SVBNTSQL\MBSGP'.
> 2004-11-08 14:37:40.40 spid8 Starting up database 'msdb'.
> 2004-11-08 14:37:40.40 spid9 Starting up database 'pubs'.
> 2004-11-08 14:37:40.40 spid10 Starting up database 'Northwind'.
> 2004-11-08 14:37:40.40 spid11 Starting up database 'DYNAMICS'.
> 2004-11-08 14:37:40.40 spid12 Starting up database 'TWO'.
> 2004-11-08 14:37:40.43 spid13 Starting up database 'SVB'.
> 2004-11-08 14:37:40.43 server SQL server listening on Shared Memory,
> Named Pipes.
> 2004-11-08 14:37:40.43 server SQL Server is ready for client connections
> 2004-11-08 14:37:40.53 spid5 Clearing tempdb database.
> 2004-11-08 14:37:40.73 spid5 Starting up database 'tempdb'.
> 2004-11-08 14:37:40.75 spid4 Recovery complete.
> 2004-11-08 14:37:40.78 spid4 Launched startup procedure
> 'smDEX_Build_Locks'
> 2004-11-08 14:51:39.97 spid51 Using 'xpsqlbot.dll' version '2000.80.194'
> to execute extended stored procedure 'xp_qv'.
> 2004-11-08 14:53:43.56 spid4 SQL Server is terminating due to 'stop'
> request from Service Control Manager.
> "AnthonyThomas" wrote:
|||Thanks for you help Anthony. However after taking a closer look at the error
log, I realize that Sql Sp3 was not installed properly. After installing it
again, everything is working fine now.
"AnthonyThomas" wrote:
[vbcol=seagreen]
> Your server has not been set up to use TCP/IP. If you look at your error
> log, about 1/3 of the way through, you will see the line:
> 2004-11-08 14:37:40.43 server SQL server listening on Shared Memory,
> Named Pipes.
> No, TCP/IP. Usually, this is because it was never selected as part of the
> installation or there was an IP Bind error. The Bind error also would have
> shown up in the list. On the server, you need to, or have your server admin,
> run the Server Network utility and add the TCP/IP protocol to the list. You
> will also have to specify the port. If the Named Instance is the only
> instance, then you can use 1433.
> Sincerely,
>
> Anthony Thomas
>
> "Betmck" wrote:
Connecting to to Sql server through ODBC
I am having problems accessing the sql server through ODBC.
I got the follong error:
Connection Failed:
SQL State: 01000
SQL Serve Error: 53[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectioOpen
(Connect()). Connection failed.
I then upgraded to Sql sp3a
Now I am receiving the error:
Connection Failed:
SQL State: 01000
SQL Server Error: 011001
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen
(Connect()). Connection failed.
Connection Failed:
SQL State: 08001
SQL Server Error: 6
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Specified SQL Server
Not found.
Let me give you an idea of our network structure and some of the issues:
We now have 2 servers. Win 2000 server and the Win 2003 server which is
running sql server 2000(This is a new server just bought).
The Win2000 server is running Active directory and is the main domain
controller.
The win 2003 server is not running Active directory.
I want all user to login to this server (Win 2000) and those requiring Great
Plains will then attach to the Win2003 Server after completing login to the
network through the win 2000 server.
The win 2003 server is running sql service pack3a
I can access shared folders on this Win 2003 server from Network places on
any machine on the network.
I can ping the 2003 server using the Ip address and Name.
Any ideas please?
--
cool ladyWas the SQL Server installed as the default or a named instance? What port
was it assigned to? What server name are you using in your ODBC connection?
Have you tried to connect via SQL Enterprise Manager or Query Analyzer? Do
you have permission to connect to this SQL Server installation?
Sincerely,
Anthony Thomas
"Betmck" wrote:
> I am having problems accessing the sql server through ODBC.
> I got the follong error:
> Connection Failed:
> SQL State: 01000
> SQL Serve Error: 53[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectioOpen
> (Connect()). Connection failed.
> I then upgraded to Sql sp3a
> Now I am receiving the error:
> Connection Failed:
> SQL State: 01000
> SQL Server Error: 011001
> [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen
> (Connect()). Connection failed.
> Connection Failed:
> SQL State: 08001
> SQL Server Error: 6
> [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Specified SQL Server
> Not found.
>
> Let me give you an idea of our network structure and some of the issues:
> We now have 2 servers. Win 2000 server and the Win 2003 server which is
> running sql server 2000(This is a new server just bought).
> The Win2000 server is running Active directory and is the main domain
> controller.
> The win 2003 server is not running Active directory.
> I want all user to login to this server (Win 2000) and those requiring Great
> Plains will then attach to the Win2003 Server after completing login to the
> network through the win 2000 server.
> The win 2003 server is running sql service pack3a
> I can access shared folders on this Win 2003 server from Network places on
> any machine on the network.
> I can ping the 2003 server using the Ip address and Name.
> Any ideas please?
>
> --
> cool lady|||SQL Server installed with a named instance.
Port is 1433 which is automatically assigned
Server Name in the ODBC connection is SVBNTSQL\MBSGP
I have tried connecting via both Enterprise manager and query Analyzer.
Not sure if I have permission to connect. Where should I check for this?
Thanks
"AnthonyThomas" wrote:
> Was the SQL Server installed as the default or a named instance? What port
> was it assigned to? What server name are you using in your ODBC connection?
> Have you tried to connect via SQL Enterprise Manager or Query Analyzer? Do
> you have permission to connect to this SQL Server installation?
> Sincerely,
>
> Anthony Thomas
>
> "Betmck" wrote:
> > I am having problems accessing the sql server through ODBC.
> > I got the follong error:
> >
> > Connection Failed:
> > SQL State: 01000
> > SQL Serve Error: 53[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectioOpen
> > (Connect()). Connection failed.
> >
> > I then upgraded to Sql sp3a
> >
> > Now I am receiving the error:
> >
> > Connection Failed:
> > SQL State: 01000
> > SQL Server Error: 011001
> > [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen
> > (Connect()). Connection failed.
> >
> > Connection Failed:
> > SQL State: 08001
> > SQL Server Error: 6
> > [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Specified SQL Server
> > Not found.
> >
> >
> > Let me give you an idea of our network structure and some of the issues:
> >
> > We now have 2 servers. Win 2000 server and the Win 2003 server which is
> > running sql server 2000(This is a new server just bought).
> >
> > The Win2000 server is running Active directory and is the main domain
> > controller.
> >
> > The win 2003 server is not running Active directory.
> >
> > I want all user to login to this server (Win 2000) and those requiring Great
> > Plains will then attach to the Win2003 Server after completing login to the
> > network through the win 2000 server.
> >
> > The win 2003 server is running sql service pack3a
> >
> > I can access shared folders on this Win 2003 server from Network places on
> > any machine on the network.
> >
> > I can ping the 2003 server using the Ip address and Name.
> >
> > Any ideas please?
> >
> >
> > --
> > cool lady|||I also tried to Telnet the sql server. If I just use the Ip adress alone I
will get through. When I attached 1433 at the end I get an error "could not
open a connection to host on port 1433: connect failed.
"AnthonyThomas" wrote:
> Was the SQL Server installed as the default or a named instance? What port
> was it assigned to? What server name are you using in your ODBC connection?
> Have you tried to connect via SQL Enterprise Manager or Query Analyzer? Do
> you have permission to connect to this SQL Server installation?
> Sincerely,
>
> Anthony Thomas
>
> "Betmck" wrote:
> > I am having problems accessing the sql server through ODBC.
> > I got the follong error:
> >
> > Connection Failed:
> > SQL State: 01000
> > SQL Serve Error: 53[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectioOpen
> > (Connect()). Connection failed.
> >
> > I then upgraded to Sql sp3a
> >
> > Now I am receiving the error:
> >
> > Connection Failed:
> > SQL State: 01000
> > SQL Server Error: 011001
> > [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen
> > (Connect()). Connection failed.
> >
> > Connection Failed:
> > SQL State: 08001
> > SQL Server Error: 6
> > [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Specified SQL Server
> > Not found.
> >
> >
> > Let me give you an idea of our network structure and some of the issues:
> >
> > We now have 2 servers. Win 2000 server and the Win 2003 server which is
> > running sql server 2000(This is a new server just bought).
> >
> > The Win2000 server is running Active directory and is the main domain
> > controller.
> >
> > The win 2003 server is not running Active directory.
> >
> > I want all user to login to this server (Win 2000) and those requiring Great
> > Plains will then attach to the Win2003 Server after completing login to the
> > network through the win 2000 server.
> >
> > The win 2003 server is running sql service pack3a
> >
> > I can access shared folders on this Win 2003 server from Network places on
> > any machine on the network.
> >
> > I can ping the 2003 server using the Ip address and Name.
> >
> > Any ideas please?
> >
> >
> > --
> > cool lady|||This is what the error log.:
2004-11-08 14:37:30.40 server Microsoft SQL Server 2000 - 8.00.194
(Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: )
2004-11-08 14:37:30.40 server Copyright (C) 1988-2000 Microsoft
Corporation.
2004-11-08 14:37:30.40 server All rights reserved.
2004-11-08 14:37:30.40 server Server Process ID is 1532.
2004-11-08 14:37:30.40 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL$MBSGP\log\ERRORLOG'.
2004-11-08 14:37:30.43 server SQL Server is starting at priority class
'normal'(2 CPUs detected).
2004-11-08 14:37:30.67 server SQL Server configured for thread mode
processing.
2004-11-08 14:37:30.68 server Using dynamic lock allocation. [2500] Lock
Blocks, [5000] Lock Owner Blocks.
2004-11-08 14:37:30.71 server Attempting to initialize Distributed
Transaction Coordinator.
2004-11-08 14:37:35.48 spid4 Starting up database 'master'.
2004-11-08 14:37:40.40 server Using 'SSNETLIB.DLL' version '8.0.194'.
2004-11-08 14:37:40.40 spid5 Starting up database 'model'.
2004-11-08 14:37:40.40 spid4 Server name is 'SVBNTSQL\MBSGP'.
2004-11-08 14:37:40.40 spid8 Starting up database 'msdb'.
2004-11-08 14:37:40.40 spid9 Starting up database 'pubs'.
2004-11-08 14:37:40.40 spid10 Starting up database 'Northwind'.
2004-11-08 14:37:40.40 spid11 Starting up database 'DYNAMICS'.
2004-11-08 14:37:40.40 spid12 Starting up database 'TWO'.
2004-11-08 14:37:40.43 spid13 Starting up database 'SVB'.
2004-11-08 14:37:40.43 server SQL server listening on Shared Memory,
Named Pipes.
2004-11-08 14:37:40.43 server SQL Server is ready for client connections
2004-11-08 14:37:40.53 spid5 Clearing tempdb database.
2004-11-08 14:37:40.73 spid5 Starting up database 'tempdb'.
2004-11-08 14:37:40.75 spid4 Recovery complete.
2004-11-08 14:37:40.78 spid4 Launched startup procedure
'smDEX_Build_Locks'
2004-11-08 14:51:39.97 spid51 Using 'xpsqlbot.dll' version '2000.80.194'
to execute extended stored procedure 'xp_qv'.
2004-11-08 14:53:43.56 spid4 SQL Server is terminating due to 'stop'
request from Service Control Manager.
"AnthonyThomas" wrote:
> Was the SQL Server installed as the default or a named instance? What port
> was it assigned to? What server name are you using in your ODBC connection?
> Have you tried to connect via SQL Enterprise Manager or Query Analyzer? Do
> you have permission to connect to this SQL Server installation?
> Sincerely,
>
> Anthony Thomas
>
> "Betmck" wrote:
> > I am having problems accessing the sql server through ODBC.
> > I got the follong error:
> >
> > Connection Failed:
> > SQL State: 01000
> > SQL Serve Error: 53[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectioOpen
> > (Connect()). Connection failed.
> >
> > I then upgraded to Sql sp3a
> >
> > Now I am receiving the error:
> >
> > Connection Failed:
> > SQL State: 01000
> > SQL Server Error: 011001
> > [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen
> > (Connect()). Connection failed.
> >
> > Connection Failed:
> > SQL State: 08001
> > SQL Server Error: 6
> > [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Specified SQL Server
> > Not found.
> >
> >
> > Let me give you an idea of our network structure and some of the issues:
> >
> > We now have 2 servers. Win 2000 server and the Win 2003 server which is
> > running sql server 2000(This is a new server just bought).
> >
> > The Win2000 server is running Active directory and is the main domain
> > controller.
> >
> > The win 2003 server is not running Active directory.
> >
> > I want all user to login to this server (Win 2000) and those requiring Great
> > Plains will then attach to the Win2003 Server after completing login to the
> > network through the win 2000 server.
> >
> > The win 2003 server is running sql service pack3a
> >
> > I can access shared folders on this Win 2003 server from Network places on
> > any machine on the network.
> >
> > I can ping the 2003 server using the Ip address and Name.
> >
> > Any ideas please?
> >
> >
> > --
> > cool lady|||Your server has not been set up to use TCP/IP. If you look at your error
log, about 1/3 of the way through, you will see the line:
2004-11-08 14:37:40.43 server SQL server listening on Shared Memory,
Named Pipes.
No, TCP/IP. Usually, this is because it was never selected as part of the
installation or there was an IP Bind error. The Bind error also would have
shown up in the list. On the server, you need to, or have your server admin,
run the Server Network utility and add the TCP/IP protocol to the list. You
will also have to specify the port. If the Named Instance is the only
instance, then you can use 1433.
Sincerely,
Anthony Thomas
"Betmck" wrote:
> This is what the error log.:
> 2004-11-08 14:37:30.40 server Microsoft SQL Server 2000 - 8.00.194
> (Intel X86)
> Aug 6 2000 00:57:48
> Copyright (c) 1988-2000 Microsoft Corporation
> Standard Edition on Windows NT 5.2 (Build 3790: )
> 2004-11-08 14:37:30.40 server Copyright (C) 1988-2000 Microsoft
> Corporation.
> 2004-11-08 14:37:30.40 server All rights reserved.
> 2004-11-08 14:37:30.40 server Server Process ID is 1532.
> 2004-11-08 14:37:30.40 server Logging SQL Server messages in file
> 'C:\Program Files\Microsoft SQL Server\MSSQL$MBSGP\log\ERRORLOG'.
> 2004-11-08 14:37:30.43 server SQL Server is starting at priority class
> 'normal'(2 CPUs detected).
> 2004-11-08 14:37:30.67 server SQL Server configured for thread mode
> processing.
> 2004-11-08 14:37:30.68 server Using dynamic lock allocation. [2500] Lock
> Blocks, [5000] Lock Owner Blocks.
> 2004-11-08 14:37:30.71 server Attempting to initialize Distributed
> Transaction Coordinator.
> 2004-11-08 14:37:35.48 spid4 Starting up database 'master'.
> 2004-11-08 14:37:40.40 server Using 'SSNETLIB.DLL' version '8.0.194'.
> 2004-11-08 14:37:40.40 spid5 Starting up database 'model'.
> 2004-11-08 14:37:40.40 spid4 Server name is 'SVBNTSQL\MBSGP'.
> 2004-11-08 14:37:40.40 spid8 Starting up database 'msdb'.
> 2004-11-08 14:37:40.40 spid9 Starting up database 'pubs'.
> 2004-11-08 14:37:40.40 spid10 Starting up database 'Northwind'.
> 2004-11-08 14:37:40.40 spid11 Starting up database 'DYNAMICS'.
> 2004-11-08 14:37:40.40 spid12 Starting up database 'TWO'.
> 2004-11-08 14:37:40.43 spid13 Starting up database 'SVB'.
> 2004-11-08 14:37:40.43 server SQL server listening on Shared Memory,
> Named Pipes.
> 2004-11-08 14:37:40.43 server SQL Server is ready for client connections
> 2004-11-08 14:37:40.53 spid5 Clearing tempdb database.
> 2004-11-08 14:37:40.73 spid5 Starting up database 'tempdb'.
> 2004-11-08 14:37:40.75 spid4 Recovery complete.
> 2004-11-08 14:37:40.78 spid4 Launched startup procedure
> 'smDEX_Build_Locks'
> 2004-11-08 14:51:39.97 spid51 Using 'xpsqlbot.dll' version '2000.80.194'
> to execute extended stored procedure 'xp_qv'.
> 2004-11-08 14:53:43.56 spid4 SQL Server is terminating due to 'stop'
> request from Service Control Manager.
> "AnthonyThomas" wrote:
> > Was the SQL Server installed as the default or a named instance? What port
> > was it assigned to? What server name are you using in your ODBC connection?
> > Have you tried to connect via SQL Enterprise Manager or Query Analyzer? Do
> > you have permission to connect to this SQL Server installation?
> >
> > Sincerely,
> >
> >
> > Anthony Thomas
> >
> >
> > "Betmck" wrote:
> >
> > > I am having problems accessing the sql server through ODBC.
> > > I got the follong error:
> > >
> > > Connection Failed:
> > > SQL State: 01000
> > > SQL Serve Error: 53[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectioOpen
> > > (Connect()). Connection failed.
> > >
> > > I then upgraded to Sql sp3a
> > >
> > > Now I am receiving the error:
> > >
> > > Connection Failed:
> > > SQL State: 01000
> > > SQL Server Error: 011001
> > > [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen
> > > (Connect()). Connection failed.
> > >
> > > Connection Failed:
> > > SQL State: 08001
> > > SQL Server Error: 6
> > > [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Specified SQL Server
> > > Not found.
> > >
> > >
> > > Let me give you an idea of our network structure and some of the issues:
> > >
> > > We now have 2 servers. Win 2000 server and the Win 2003 server which is
> > > running sql server 2000(This is a new server just bought).
> > >
> > > The Win2000 server is running Active directory and is the main domain
> > > controller.
> > >
> > > The win 2003 server is not running Active directory.
> > >
> > > I want all user to login to this server (Win 2000) and those requiring Great
> > > Plains will then attach to the Win2003 Server after completing login to the
> > > network through the win 2000 server.
> > >
> > > The win 2003 server is running sql service pack3a
> > >
> > > I can access shared folders on this Win 2003 server from Network places on
> > > any machine on the network.
> > >
> > > I can ping the 2003 server using the Ip address and Name.
> > >
> > > Any ideas please?
> > >
> > >
> > > --
> > > cool lady|||Thanks for you help Anthony. However after taking a closer look at the error
log, I realize that Sql Sp3 was not installed properly. After installing it
again, everything is working fine now.
"AnthonyThomas" wrote:
> Your server has not been set up to use TCP/IP. If you look at your error
> log, about 1/3 of the way through, you will see the line:
> 2004-11-08 14:37:40.43 server SQL server listening on Shared Memory,
> Named Pipes.
> No, TCP/IP. Usually, this is because it was never selected as part of the
> installation or there was an IP Bind error. The Bind error also would have
> shown up in the list. On the server, you need to, or have your server admin,
> run the Server Network utility and add the TCP/IP protocol to the list. You
> will also have to specify the port. If the Named Instance is the only
> instance, then you can use 1433.
> Sincerely,
>
> Anthony Thomas
>
> "Betmck" wrote:
> > This is what the error log.:
> >
> > 2004-11-08 14:37:30.40 server Microsoft SQL Server 2000 - 8.00.194
> > (Intel X86)
> > Aug 6 2000 00:57:48
> > Copyright (c) 1988-2000 Microsoft Corporation
> > Standard Edition on Windows NT 5.2 (Build 3790: )
> >
> > 2004-11-08 14:37:30.40 server Copyright (C) 1988-2000 Microsoft
> > Corporation.
> > 2004-11-08 14:37:30.40 server All rights reserved.
> > 2004-11-08 14:37:30.40 server Server Process ID is 1532.
> > 2004-11-08 14:37:30.40 server Logging SQL Server messages in file
> > 'C:\Program Files\Microsoft SQL Server\MSSQL$MBSGP\log\ERRORLOG'.
> > 2004-11-08 14:37:30.43 server SQL Server is starting at priority class
> > 'normal'(2 CPUs detected).
> > 2004-11-08 14:37:30.67 server SQL Server configured for thread mode
> > processing.
> > 2004-11-08 14:37:30.68 server Using dynamic lock allocation. [2500] Lock
> > Blocks, [5000] Lock Owner Blocks.
> > 2004-11-08 14:37:30.71 server Attempting to initialize Distributed
> > Transaction Coordinator.
> > 2004-11-08 14:37:35.48 spid4 Starting up database 'master'.
> > 2004-11-08 14:37:40.40 server Using 'SSNETLIB.DLL' version '8.0.194'.
> > 2004-11-08 14:37:40.40 spid5 Starting up database 'model'.
> > 2004-11-08 14:37:40.40 spid4 Server name is 'SVBNTSQL\MBSGP'.
> > 2004-11-08 14:37:40.40 spid8 Starting up database 'msdb'.
> > 2004-11-08 14:37:40.40 spid9 Starting up database 'pubs'.
> > 2004-11-08 14:37:40.40 spid10 Starting up database 'Northwind'.
> > 2004-11-08 14:37:40.40 spid11 Starting up database 'DYNAMICS'.
> > 2004-11-08 14:37:40.40 spid12 Starting up database 'TWO'.
> > 2004-11-08 14:37:40.43 spid13 Starting up database 'SVB'.
> > 2004-11-08 14:37:40.43 server SQL server listening on Shared Memory,
> > Named Pipes.
> > 2004-11-08 14:37:40.43 server SQL Server is ready for client connections
> > 2004-11-08 14:37:40.53 spid5 Clearing tempdb database.
> > 2004-11-08 14:37:40.73 spid5 Starting up database 'tempdb'.
> > 2004-11-08 14:37:40.75 spid4 Recovery complete.
> > 2004-11-08 14:37:40.78 spid4 Launched startup procedure
> > 'smDEX_Build_Locks'
> > 2004-11-08 14:51:39.97 spid51 Using 'xpsqlbot.dll' version '2000.80.194'
> > to execute extended stored procedure 'xp_qv'.
> > 2004-11-08 14:53:43.56 spid4 SQL Server is terminating due to 'stop'
> > request from Service Control Manager.
> >
> > "AnthonyThomas" wrote:
> >
> > > Was the SQL Server installed as the default or a named instance? What port
> > > was it assigned to? What server name are you using in your ODBC connection?
> > > Have you tried to connect via SQL Enterprise Manager or Query Analyzer? Do
> > > you have permission to connect to this SQL Server installation?
> > >
> > > Sincerely,
> > >
> > >
> > > Anthony Thomas
> > >
> > >
> > > "Betmck" wrote:
> > >
> > > > I am having problems accessing the sql server through ODBC.
> > > > I got the follong error:
> > > >
> > > > Connection Failed:
> > > > SQL State: 01000
> > > > SQL Serve Error: 53[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectioOpen
> > > > (Connect()). Connection failed.
> > > >
> > > > I then upgraded to Sql sp3a
> > > >
> > > > Now I am receiving the error:
> > > >
> > > > Connection Failed:
> > > > SQL State: 01000
> > > > SQL Server Error: 011001
> > > > [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen
> > > > (Connect()). Connection failed.
> > > >
> > > > Connection Failed:
> > > > SQL State: 08001
> > > > SQL Server Error: 6
> > > > [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Specified SQL Server
> > > > Not found.
> > > >
> > > >
> > > > Let me give you an idea of our network structure and some of the issues:
> > > >
> > > > We now have 2 servers. Win 2000 server and the Win 2003 server which is
> > > > running sql server 2000(This is a new server just bought).
> > > >
> > > > The Win2000 server is running Active directory and is the main domain
> > > > controller.
> > > >
> > > > The win 2003 server is not running Active directory.
> > > >
> > > > I want all user to login to this server (Win 2000) and those requiring Great
> > > > Plains will then attach to the Win2003 Server after completing login to the
> > > > network through the win 2000 server.
> > > >
> > > > The win 2003 server is running sql service pack3a
> > > >
> > > > I can access shared folders on this Win 2003 server from Network places on
> > > > any machine on the network.
> > > >
> > > > I can ping the 2003 server using the Ip address and Name.
> > > >
> > > > Any ideas please?
> > > >
> > > >
> > > > --
> > > > cool lady
I got the follong error:
Connection Failed:
SQL State: 01000
SQL Serve Error: 53[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectioOpen
(Connect()). Connection failed.
I then upgraded to Sql sp3a
Now I am receiving the error:
Connection Failed:
SQL State: 01000
SQL Server Error: 011001
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen
(Connect()). Connection failed.
Connection Failed:
SQL State: 08001
SQL Server Error: 6
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Specified SQL Server
Not found.
Let me give you an idea of our network structure and some of the issues:
We now have 2 servers. Win 2000 server and the Win 2003 server which is
running sql server 2000(This is a new server just bought).
The Win2000 server is running Active directory and is the main domain
controller.
The win 2003 server is not running Active directory.
I want all user to login to this server (Win 2000) and those requiring Great
Plains will then attach to the Win2003 Server after completing login to the
network through the win 2000 server.
The win 2003 server is running sql service pack3a
I can access shared folders on this Win 2003 server from Network places on
any machine on the network.
I can ping the 2003 server using the Ip address and Name.
Any ideas please?
--
cool ladyWas the SQL Server installed as the default or a named instance? What port
was it assigned to? What server name are you using in your ODBC connection?
Have you tried to connect via SQL Enterprise Manager or Query Analyzer? Do
you have permission to connect to this SQL Server installation?
Sincerely,
Anthony Thomas
"Betmck" wrote:
> I am having problems accessing the sql server through ODBC.
> I got the follong error:
> Connection Failed:
> SQL State: 01000
> SQL Serve Error: 53[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectioOpen
> (Connect()). Connection failed.
> I then upgraded to Sql sp3a
> Now I am receiving the error:
> Connection Failed:
> SQL State: 01000
> SQL Server Error: 011001
> [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen
> (Connect()). Connection failed.
> Connection Failed:
> SQL State: 08001
> SQL Server Error: 6
> [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Specified SQL Server
> Not found.
>
> Let me give you an idea of our network structure and some of the issues:
> We now have 2 servers. Win 2000 server and the Win 2003 server which is
> running sql server 2000(This is a new server just bought).
> The Win2000 server is running Active directory and is the main domain
> controller.
> The win 2003 server is not running Active directory.
> I want all user to login to this server (Win 2000) and those requiring Great
> Plains will then attach to the Win2003 Server after completing login to the
> network through the win 2000 server.
> The win 2003 server is running sql service pack3a
> I can access shared folders on this Win 2003 server from Network places on
> any machine on the network.
> I can ping the 2003 server using the Ip address and Name.
> Any ideas please?
>
> --
> cool lady|||SQL Server installed with a named instance.
Port is 1433 which is automatically assigned
Server Name in the ODBC connection is SVBNTSQL\MBSGP
I have tried connecting via both Enterprise manager and query Analyzer.
Not sure if I have permission to connect. Where should I check for this?
Thanks
"AnthonyThomas" wrote:
> Was the SQL Server installed as the default or a named instance? What port
> was it assigned to? What server name are you using in your ODBC connection?
> Have you tried to connect via SQL Enterprise Manager or Query Analyzer? Do
> you have permission to connect to this SQL Server installation?
> Sincerely,
>
> Anthony Thomas
>
> "Betmck" wrote:
> > I am having problems accessing the sql server through ODBC.
> > I got the follong error:
> >
> > Connection Failed:
> > SQL State: 01000
> > SQL Serve Error: 53[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectioOpen
> > (Connect()). Connection failed.
> >
> > I then upgraded to Sql sp3a
> >
> > Now I am receiving the error:
> >
> > Connection Failed:
> > SQL State: 01000
> > SQL Server Error: 011001
> > [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen
> > (Connect()). Connection failed.
> >
> > Connection Failed:
> > SQL State: 08001
> > SQL Server Error: 6
> > [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Specified SQL Server
> > Not found.
> >
> >
> > Let me give you an idea of our network structure and some of the issues:
> >
> > We now have 2 servers. Win 2000 server and the Win 2003 server which is
> > running sql server 2000(This is a new server just bought).
> >
> > The Win2000 server is running Active directory and is the main domain
> > controller.
> >
> > The win 2003 server is not running Active directory.
> >
> > I want all user to login to this server (Win 2000) and those requiring Great
> > Plains will then attach to the Win2003 Server after completing login to the
> > network through the win 2000 server.
> >
> > The win 2003 server is running sql service pack3a
> >
> > I can access shared folders on this Win 2003 server from Network places on
> > any machine on the network.
> >
> > I can ping the 2003 server using the Ip address and Name.
> >
> > Any ideas please?
> >
> >
> > --
> > cool lady|||I also tried to Telnet the sql server. If I just use the Ip adress alone I
will get through. When I attached 1433 at the end I get an error "could not
open a connection to host on port 1433: connect failed.
"AnthonyThomas" wrote:
> Was the SQL Server installed as the default or a named instance? What port
> was it assigned to? What server name are you using in your ODBC connection?
> Have you tried to connect via SQL Enterprise Manager or Query Analyzer? Do
> you have permission to connect to this SQL Server installation?
> Sincerely,
>
> Anthony Thomas
>
> "Betmck" wrote:
> > I am having problems accessing the sql server through ODBC.
> > I got the follong error:
> >
> > Connection Failed:
> > SQL State: 01000
> > SQL Serve Error: 53[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectioOpen
> > (Connect()). Connection failed.
> >
> > I then upgraded to Sql sp3a
> >
> > Now I am receiving the error:
> >
> > Connection Failed:
> > SQL State: 01000
> > SQL Server Error: 011001
> > [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen
> > (Connect()). Connection failed.
> >
> > Connection Failed:
> > SQL State: 08001
> > SQL Server Error: 6
> > [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Specified SQL Server
> > Not found.
> >
> >
> > Let me give you an idea of our network structure and some of the issues:
> >
> > We now have 2 servers. Win 2000 server and the Win 2003 server which is
> > running sql server 2000(This is a new server just bought).
> >
> > The Win2000 server is running Active directory and is the main domain
> > controller.
> >
> > The win 2003 server is not running Active directory.
> >
> > I want all user to login to this server (Win 2000) and those requiring Great
> > Plains will then attach to the Win2003 Server after completing login to the
> > network through the win 2000 server.
> >
> > The win 2003 server is running sql service pack3a
> >
> > I can access shared folders on this Win 2003 server from Network places on
> > any machine on the network.
> >
> > I can ping the 2003 server using the Ip address and Name.
> >
> > Any ideas please?
> >
> >
> > --
> > cool lady|||This is what the error log.:
2004-11-08 14:37:30.40 server Microsoft SQL Server 2000 - 8.00.194
(Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: )
2004-11-08 14:37:30.40 server Copyright (C) 1988-2000 Microsoft
Corporation.
2004-11-08 14:37:30.40 server All rights reserved.
2004-11-08 14:37:30.40 server Server Process ID is 1532.
2004-11-08 14:37:30.40 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL$MBSGP\log\ERRORLOG'.
2004-11-08 14:37:30.43 server SQL Server is starting at priority class
'normal'(2 CPUs detected).
2004-11-08 14:37:30.67 server SQL Server configured for thread mode
processing.
2004-11-08 14:37:30.68 server Using dynamic lock allocation. [2500] Lock
Blocks, [5000] Lock Owner Blocks.
2004-11-08 14:37:30.71 server Attempting to initialize Distributed
Transaction Coordinator.
2004-11-08 14:37:35.48 spid4 Starting up database 'master'.
2004-11-08 14:37:40.40 server Using 'SSNETLIB.DLL' version '8.0.194'.
2004-11-08 14:37:40.40 spid5 Starting up database 'model'.
2004-11-08 14:37:40.40 spid4 Server name is 'SVBNTSQL\MBSGP'.
2004-11-08 14:37:40.40 spid8 Starting up database 'msdb'.
2004-11-08 14:37:40.40 spid9 Starting up database 'pubs'.
2004-11-08 14:37:40.40 spid10 Starting up database 'Northwind'.
2004-11-08 14:37:40.40 spid11 Starting up database 'DYNAMICS'.
2004-11-08 14:37:40.40 spid12 Starting up database 'TWO'.
2004-11-08 14:37:40.43 spid13 Starting up database 'SVB'.
2004-11-08 14:37:40.43 server SQL server listening on Shared Memory,
Named Pipes.
2004-11-08 14:37:40.43 server SQL Server is ready for client connections
2004-11-08 14:37:40.53 spid5 Clearing tempdb database.
2004-11-08 14:37:40.73 spid5 Starting up database 'tempdb'.
2004-11-08 14:37:40.75 spid4 Recovery complete.
2004-11-08 14:37:40.78 spid4 Launched startup procedure
'smDEX_Build_Locks'
2004-11-08 14:51:39.97 spid51 Using 'xpsqlbot.dll' version '2000.80.194'
to execute extended stored procedure 'xp_qv'.
2004-11-08 14:53:43.56 spid4 SQL Server is terminating due to 'stop'
request from Service Control Manager.
"AnthonyThomas" wrote:
> Was the SQL Server installed as the default or a named instance? What port
> was it assigned to? What server name are you using in your ODBC connection?
> Have you tried to connect via SQL Enterprise Manager or Query Analyzer? Do
> you have permission to connect to this SQL Server installation?
> Sincerely,
>
> Anthony Thomas
>
> "Betmck" wrote:
> > I am having problems accessing the sql server through ODBC.
> > I got the follong error:
> >
> > Connection Failed:
> > SQL State: 01000
> > SQL Serve Error: 53[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectioOpen
> > (Connect()). Connection failed.
> >
> > I then upgraded to Sql sp3a
> >
> > Now I am receiving the error:
> >
> > Connection Failed:
> > SQL State: 01000
> > SQL Server Error: 011001
> > [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen
> > (Connect()). Connection failed.
> >
> > Connection Failed:
> > SQL State: 08001
> > SQL Server Error: 6
> > [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Specified SQL Server
> > Not found.
> >
> >
> > Let me give you an idea of our network structure and some of the issues:
> >
> > We now have 2 servers. Win 2000 server and the Win 2003 server which is
> > running sql server 2000(This is a new server just bought).
> >
> > The Win2000 server is running Active directory and is the main domain
> > controller.
> >
> > The win 2003 server is not running Active directory.
> >
> > I want all user to login to this server (Win 2000) and those requiring Great
> > Plains will then attach to the Win2003 Server after completing login to the
> > network through the win 2000 server.
> >
> > The win 2003 server is running sql service pack3a
> >
> > I can access shared folders on this Win 2003 server from Network places on
> > any machine on the network.
> >
> > I can ping the 2003 server using the Ip address and Name.
> >
> > Any ideas please?
> >
> >
> > --
> > cool lady|||Your server has not been set up to use TCP/IP. If you look at your error
log, about 1/3 of the way through, you will see the line:
2004-11-08 14:37:40.43 server SQL server listening on Shared Memory,
Named Pipes.
No, TCP/IP. Usually, this is because it was never selected as part of the
installation or there was an IP Bind error. The Bind error also would have
shown up in the list. On the server, you need to, or have your server admin,
run the Server Network utility and add the TCP/IP protocol to the list. You
will also have to specify the port. If the Named Instance is the only
instance, then you can use 1433.
Sincerely,
Anthony Thomas
"Betmck" wrote:
> This is what the error log.:
> 2004-11-08 14:37:30.40 server Microsoft SQL Server 2000 - 8.00.194
> (Intel X86)
> Aug 6 2000 00:57:48
> Copyright (c) 1988-2000 Microsoft Corporation
> Standard Edition on Windows NT 5.2 (Build 3790: )
> 2004-11-08 14:37:30.40 server Copyright (C) 1988-2000 Microsoft
> Corporation.
> 2004-11-08 14:37:30.40 server All rights reserved.
> 2004-11-08 14:37:30.40 server Server Process ID is 1532.
> 2004-11-08 14:37:30.40 server Logging SQL Server messages in file
> 'C:\Program Files\Microsoft SQL Server\MSSQL$MBSGP\log\ERRORLOG'.
> 2004-11-08 14:37:30.43 server SQL Server is starting at priority class
> 'normal'(2 CPUs detected).
> 2004-11-08 14:37:30.67 server SQL Server configured for thread mode
> processing.
> 2004-11-08 14:37:30.68 server Using dynamic lock allocation. [2500] Lock
> Blocks, [5000] Lock Owner Blocks.
> 2004-11-08 14:37:30.71 server Attempting to initialize Distributed
> Transaction Coordinator.
> 2004-11-08 14:37:35.48 spid4 Starting up database 'master'.
> 2004-11-08 14:37:40.40 server Using 'SSNETLIB.DLL' version '8.0.194'.
> 2004-11-08 14:37:40.40 spid5 Starting up database 'model'.
> 2004-11-08 14:37:40.40 spid4 Server name is 'SVBNTSQL\MBSGP'.
> 2004-11-08 14:37:40.40 spid8 Starting up database 'msdb'.
> 2004-11-08 14:37:40.40 spid9 Starting up database 'pubs'.
> 2004-11-08 14:37:40.40 spid10 Starting up database 'Northwind'.
> 2004-11-08 14:37:40.40 spid11 Starting up database 'DYNAMICS'.
> 2004-11-08 14:37:40.40 spid12 Starting up database 'TWO'.
> 2004-11-08 14:37:40.43 spid13 Starting up database 'SVB'.
> 2004-11-08 14:37:40.43 server SQL server listening on Shared Memory,
> Named Pipes.
> 2004-11-08 14:37:40.43 server SQL Server is ready for client connections
> 2004-11-08 14:37:40.53 spid5 Clearing tempdb database.
> 2004-11-08 14:37:40.73 spid5 Starting up database 'tempdb'.
> 2004-11-08 14:37:40.75 spid4 Recovery complete.
> 2004-11-08 14:37:40.78 spid4 Launched startup procedure
> 'smDEX_Build_Locks'
> 2004-11-08 14:51:39.97 spid51 Using 'xpsqlbot.dll' version '2000.80.194'
> to execute extended stored procedure 'xp_qv'.
> 2004-11-08 14:53:43.56 spid4 SQL Server is terminating due to 'stop'
> request from Service Control Manager.
> "AnthonyThomas" wrote:
> > Was the SQL Server installed as the default or a named instance? What port
> > was it assigned to? What server name are you using in your ODBC connection?
> > Have you tried to connect via SQL Enterprise Manager or Query Analyzer? Do
> > you have permission to connect to this SQL Server installation?
> >
> > Sincerely,
> >
> >
> > Anthony Thomas
> >
> >
> > "Betmck" wrote:
> >
> > > I am having problems accessing the sql server through ODBC.
> > > I got the follong error:
> > >
> > > Connection Failed:
> > > SQL State: 01000
> > > SQL Serve Error: 53[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectioOpen
> > > (Connect()). Connection failed.
> > >
> > > I then upgraded to Sql sp3a
> > >
> > > Now I am receiving the error:
> > >
> > > Connection Failed:
> > > SQL State: 01000
> > > SQL Server Error: 011001
> > > [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen
> > > (Connect()). Connection failed.
> > >
> > > Connection Failed:
> > > SQL State: 08001
> > > SQL Server Error: 6
> > > [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Specified SQL Server
> > > Not found.
> > >
> > >
> > > Let me give you an idea of our network structure and some of the issues:
> > >
> > > We now have 2 servers. Win 2000 server and the Win 2003 server which is
> > > running sql server 2000(This is a new server just bought).
> > >
> > > The Win2000 server is running Active directory and is the main domain
> > > controller.
> > >
> > > The win 2003 server is not running Active directory.
> > >
> > > I want all user to login to this server (Win 2000) and those requiring Great
> > > Plains will then attach to the Win2003 Server after completing login to the
> > > network through the win 2000 server.
> > >
> > > The win 2003 server is running sql service pack3a
> > >
> > > I can access shared folders on this Win 2003 server from Network places on
> > > any machine on the network.
> > >
> > > I can ping the 2003 server using the Ip address and Name.
> > >
> > > Any ideas please?
> > >
> > >
> > > --
> > > cool lady|||Thanks for you help Anthony. However after taking a closer look at the error
log, I realize that Sql Sp3 was not installed properly. After installing it
again, everything is working fine now.
"AnthonyThomas" wrote:
> Your server has not been set up to use TCP/IP. If you look at your error
> log, about 1/3 of the way through, you will see the line:
> 2004-11-08 14:37:40.43 server SQL server listening on Shared Memory,
> Named Pipes.
> No, TCP/IP. Usually, this is because it was never selected as part of the
> installation or there was an IP Bind error. The Bind error also would have
> shown up in the list. On the server, you need to, or have your server admin,
> run the Server Network utility and add the TCP/IP protocol to the list. You
> will also have to specify the port. If the Named Instance is the only
> instance, then you can use 1433.
> Sincerely,
>
> Anthony Thomas
>
> "Betmck" wrote:
> > This is what the error log.:
> >
> > 2004-11-08 14:37:30.40 server Microsoft SQL Server 2000 - 8.00.194
> > (Intel X86)
> > Aug 6 2000 00:57:48
> > Copyright (c) 1988-2000 Microsoft Corporation
> > Standard Edition on Windows NT 5.2 (Build 3790: )
> >
> > 2004-11-08 14:37:30.40 server Copyright (C) 1988-2000 Microsoft
> > Corporation.
> > 2004-11-08 14:37:30.40 server All rights reserved.
> > 2004-11-08 14:37:30.40 server Server Process ID is 1532.
> > 2004-11-08 14:37:30.40 server Logging SQL Server messages in file
> > 'C:\Program Files\Microsoft SQL Server\MSSQL$MBSGP\log\ERRORLOG'.
> > 2004-11-08 14:37:30.43 server SQL Server is starting at priority class
> > 'normal'(2 CPUs detected).
> > 2004-11-08 14:37:30.67 server SQL Server configured for thread mode
> > processing.
> > 2004-11-08 14:37:30.68 server Using dynamic lock allocation. [2500] Lock
> > Blocks, [5000] Lock Owner Blocks.
> > 2004-11-08 14:37:30.71 server Attempting to initialize Distributed
> > Transaction Coordinator.
> > 2004-11-08 14:37:35.48 spid4 Starting up database 'master'.
> > 2004-11-08 14:37:40.40 server Using 'SSNETLIB.DLL' version '8.0.194'.
> > 2004-11-08 14:37:40.40 spid5 Starting up database 'model'.
> > 2004-11-08 14:37:40.40 spid4 Server name is 'SVBNTSQL\MBSGP'.
> > 2004-11-08 14:37:40.40 spid8 Starting up database 'msdb'.
> > 2004-11-08 14:37:40.40 spid9 Starting up database 'pubs'.
> > 2004-11-08 14:37:40.40 spid10 Starting up database 'Northwind'.
> > 2004-11-08 14:37:40.40 spid11 Starting up database 'DYNAMICS'.
> > 2004-11-08 14:37:40.40 spid12 Starting up database 'TWO'.
> > 2004-11-08 14:37:40.43 spid13 Starting up database 'SVB'.
> > 2004-11-08 14:37:40.43 server SQL server listening on Shared Memory,
> > Named Pipes.
> > 2004-11-08 14:37:40.43 server SQL Server is ready for client connections
> > 2004-11-08 14:37:40.53 spid5 Clearing tempdb database.
> > 2004-11-08 14:37:40.73 spid5 Starting up database 'tempdb'.
> > 2004-11-08 14:37:40.75 spid4 Recovery complete.
> > 2004-11-08 14:37:40.78 spid4 Launched startup procedure
> > 'smDEX_Build_Locks'
> > 2004-11-08 14:51:39.97 spid51 Using 'xpsqlbot.dll' version '2000.80.194'
> > to execute extended stored procedure 'xp_qv'.
> > 2004-11-08 14:53:43.56 spid4 SQL Server is terminating due to 'stop'
> > request from Service Control Manager.
> >
> > "AnthonyThomas" wrote:
> >
> > > Was the SQL Server installed as the default or a named instance? What port
> > > was it assigned to? What server name are you using in your ODBC connection?
> > > Have you tried to connect via SQL Enterprise Manager or Query Analyzer? Do
> > > you have permission to connect to this SQL Server installation?
> > >
> > > Sincerely,
> > >
> > >
> > > Anthony Thomas
> > >
> > >
> > > "Betmck" wrote:
> > >
> > > > I am having problems accessing the sql server through ODBC.
> > > > I got the follong error:
> > > >
> > > > Connection Failed:
> > > > SQL State: 01000
> > > > SQL Serve Error: 53[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectioOpen
> > > > (Connect()). Connection failed.
> > > >
> > > > I then upgraded to Sql sp3a
> > > >
> > > > Now I am receiving the error:
> > > >
> > > > Connection Failed:
> > > > SQL State: 01000
> > > > SQL Server Error: 011001
> > > > [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen
> > > > (Connect()). Connection failed.
> > > >
> > > > Connection Failed:
> > > > SQL State: 08001
> > > > SQL Server Error: 6
> > > > [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Specified SQL Server
> > > > Not found.
> > > >
> > > >
> > > > Let me give you an idea of our network structure and some of the issues:
> > > >
> > > > We now have 2 servers. Win 2000 server and the Win 2003 server which is
> > > > running sql server 2000(This is a new server just bought).
> > > >
> > > > The Win2000 server is running Active directory and is the main domain
> > > > controller.
> > > >
> > > > The win 2003 server is not running Active directory.
> > > >
> > > > I want all user to login to this server (Win 2000) and those requiring Great
> > > > Plains will then attach to the Win2003 Server after completing login to the
> > > > network through the win 2000 server.
> > > >
> > > > The win 2003 server is running sql service pack3a
> > > >
> > > > I can access shared folders on this Win 2003 server from Network places on
> > > > any machine on the network.
> > > >
> > > > I can ping the 2003 server using the Ip address and Name.
> > > >
> > > > Any ideas please?
> > > >
> > > >
> > > > --
> > > > cool lady
Connecting to to Sql server through ODBC
I am having problems accessing the sql server through ODBC.
I got the follong error:
Connection Failed:
SQL State: 01000
SQL Serve Error: 53[Microsoft][ODBC SQL Server Driver][DBNETLIB]
ConnectioOpen
(Connect()). Connection failed.
I then upgraded to Sql sp3a
Now I am receiving the error:
Connection Failed:
SQL State: 01000
SQL Server Error: 011001
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpe
n
(Connect()). Connection failed.
Connection Failed:
SQL State: 08001
SQL Server Error: 6
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Specified SQL
Server
Not found.
Let me give you an idea of our network structure and some of the issues:
We now have 2 servers. Win 2000 server and the Win 2003 server which is
running sql server 2000(This is a new server just bought).
The Win2000 server is running Active directory and is the main domain
controller.
The win 2003 server is not running Active directory.
I want all user to login to this server (Win 2000) and those requiring Great
Plains will then attach to the Win2003 Server after completing login to the
network through the win 2000 server.
The win 2003 server is running sql service pack3a
I can access shared folders on this Win 2003 server from Network places on
any machine on the network.
I can ping the 2003 server using the Ip address and Name.
Any ideas please?
cool ladyWas the SQL Server installed as the default or a named instance? What port
was it assigned to? What server name are you using in your ODBC connection?
Have you tried to connect via SQL Enterprise Manager or Query Analyzer? Do
you have permission to connect to this SQL Server installation?
Sincerely,
Anthony Thomas
"Betmck" wrote:
> I am having problems accessing the sql server through ODBC.
> I got the follong error:
> Connection Failed:
> SQL State: 01000
> SQL Serve Error: 53[Microsoft][ODBC SQL Server Driver][DBNETLI
B]ConnectioOpen
> (Connect()). Connection failed.
> I then upgraded to Sql sp3a
> Now I am receiving the error:
> Connection Failed:
> SQL State: 01000
> SQL Server Error: 011001
> [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionO
pen
> (Connect()). Connection failed.
> Connection Failed:
> SQL State: 08001
> SQL Server Error: 6
> [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Specified S
QL Server
> Not found.
>
> Let me give you an idea of our network structure and some of the issues:
> We now have 2 servers. Win 2000 server and the Win 2003 server which is
> running sql server 2000(This is a new server just bought).
> The Win2000 server is running Active directory and is the main domain
> controller.
> The win 2003 server is not running Active directory.
> I want all user to login to this server (Win 2000) and those requiring Gre
at
> Plains will then attach to the Win2003 Server after completing login to th
e
> network through the win 2000 server.
> The win 2003 server is running sql service pack3a
> I can access shared folders on this Win 2003 server from Network places on
> any machine on the network.
> I can ping the 2003 server using the Ip address and Name.
> Any ideas please?
>
> --
> cool lady|||SQL Server installed with a named instance.
Port is 1433 which is automatically assigned
Server Name in the ODBC connection is SVBNTSQL\MBSGP
I have tried connecting via both Enterprise manager and query Analyzer.
Not sure if I have permission to connect. Where should I check for this?
Thanks
"AnthonyThomas" wrote:
[vbcol=seagreen]
> Was the SQL Server installed as the default or a named instance? What por
t
> was it assigned to? What server name are you using in your ODBC connectio
n?
> Have you tried to connect via SQL Enterprise Manager or Query Analyzer? D
o
> you have permission to connect to this SQL Server installation?
> Sincerely,
>
> Anthony Thomas
>
> "Betmck" wrote:
>|||I also tried to Telnet the sql server. If I just use the Ip adress alone I
will get through. When I attached 1433 at the end I get an error "could not
open a connection to host on port 1433: connect failed.
"AnthonyThomas" wrote:
[vbcol=seagreen]
> Was the SQL Server installed as the default or a named instance? What por
t
> was it assigned to? What server name are you using in your ODBC connectio
n?
> Have you tried to connect via SQL Enterprise Manager or Query Analyzer? D
o
> you have permission to connect to this SQL Server installation?
> Sincerely,
>
> Anthony Thomas
>
> "Betmck" wrote:
>|||This is what the error log.:
2004-11-08 14:37:30.40 server Microsoft SQL Server 2000 - 8.00.194
(Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: )
2004-11-08 14:37:30.40 server Copyright (C) 1988-2000 Microsoft
Corporation.
2004-11-08 14:37:30.40 server All rights reserved.
2004-11-08 14:37:30.40 server Server Process ID is 1532.
2004-11-08 14:37:30.40 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL$MBSGP\log\ERRORLOG'.
2004-11-08 14:37:30.43 server SQL Server is starting at priority class
'normal'(2 CPUs detected).
2004-11-08 14:37:30.67 server SQL Server configured for thread mode
processing.
2004-11-08 14:37:30.68 server Using dynamic lock allocation. [2500] L
ock
Blocks, [5000] Lock Owner Blocks.
2004-11-08 14:37:30.71 server Attempting to initialize Distributed
Transaction Coordinator.
2004-11-08 14:37:35.48 spid4 Starting up database 'master'.
2004-11-08 14:37:40.40 server Using 'SSNETLIB.DLL' version '8.0.194'.
2004-11-08 14:37:40.40 spid5 Starting up database 'model'.
2004-11-08 14:37:40.40 spid4 Server name is 'SVBNTSQL\MBSGP'.
2004-11-08 14:37:40.40 spid8 Starting up database 'msdb'.
2004-11-08 14:37:40.40 spid9 Starting up database 'pubs'.
2004-11-08 14:37:40.40 spid10 Starting up database 'Northwind'.
2004-11-08 14:37:40.40 spid11 Starting up database 'DYNAMICS'.
2004-11-08 14:37:40.40 spid12 Starting up database 'TWO'.
2004-11-08 14:37:40.43 spid13 Starting up database 'SVB'.
2004-11-08 14:37:40.43 server SQL server listening on Shared Memory,
Named Pipes.
2004-11-08 14:37:40.43 server SQL Server is ready for client connections
2004-11-08 14:37:40.53 spid5 Clearing tempdb database.
2004-11-08 14:37:40.73 spid5 Starting up database 'tempdb'.
2004-11-08 14:37:40.75 spid4 Recovery complete.
2004-11-08 14:37:40.78 spid4 Launched startup procedure
'smDEX_Build_Locks'
2004-11-08 14:51:39.97 spid51 Using 'xpsqlbot.dll' version '2000.80.194'
to execute extended stored procedure 'xp_qv'.
2004-11-08 14:53:43.56 spid4 SQL Server is terminating due to 'stop'
request from Service Control Manager.
"AnthonyThomas" wrote:
[vbcol=seagreen]
> Was the SQL Server installed as the default or a named instance? What por
t
> was it assigned to? What server name are you using in your ODBC connectio
n?
> Have you tried to connect via SQL Enterprise Manager or Query Analyzer? D
o
> you have permission to connect to this SQL Server installation?
> Sincerely,
>
> Anthony Thomas
>
> "Betmck" wrote:
>|||Your server has not been set up to use TCP/IP. If you look at your error
log, about 1/3 of the way through, you will see the line:
2004-11-08 14:37:40.43 server SQL server listening on Shared Memory,
Named Pipes.
No, TCP/IP. Usually, this is because it was never selected as part of the
installation or there was an IP Bind error. The Bind error also would have
shown up in the list. On the server, you need to, or have your server admin
,
run the Server Network utility and add the TCP/IP protocol to the list. You
will also have to specify the port. If the Named Instance is the only
instance, then you can use 1433.
Sincerely,
Anthony Thomas
"Betmck" wrote:
[vbcol=seagreen]
> This is what the error log.:
> 2004-11-08 14:37:30.40 server Microsoft SQL Server 2000 - 8.00.194
> (Intel X86)
> Aug 6 2000 00:57:48
> Copyright (c) 1988-2000 Microsoft Corporation
> Standard Edition on Windows NT 5.2 (Build 3790: )
> 2004-11-08 14:37:30.40 server Copyright (C) 1988-2000 Microsoft
> Corporation.
> 2004-11-08 14:37:30.40 server All rights reserved.
> 2004-11-08 14:37:30.40 server Server Process ID is 1532.
> 2004-11-08 14:37:30.40 server Logging SQL Server messages in file
> 'C:\Program Files\Microsoft SQL Server\MSSQL$MBSGP\log\ERRORLOG'.
> 2004-11-08 14:37:30.43 server SQL Server is starting at priority class
> 'normal'(2 CPUs detected).
> 2004-11-08 14:37:30.67 server SQL Server configured for thread mode
> processing.
> 2004-11-08 14:37:30.68 server Using dynamic lock allocation. [2500]
Lock
> Blocks, [5000] Lock Owner Blocks.
> 2004-11-08 14:37:30.71 server Attempting to initialize Distributed
> Transaction Coordinator.
> 2004-11-08 14:37:35.48 spid4 Starting up database 'master'.
> 2004-11-08 14:37:40.40 server Using 'SSNETLIB.DLL' version '8.0.194'.
> 2004-11-08 14:37:40.40 spid5 Starting up database 'model'.
> 2004-11-08 14:37:40.40 spid4 Server name is 'SVBNTSQL\MBSGP'.
> 2004-11-08 14:37:40.40 spid8 Starting up database 'msdb'.
> 2004-11-08 14:37:40.40 spid9 Starting up database 'pubs'.
> 2004-11-08 14:37:40.40 spid10 Starting up database 'Northwind'.
> 2004-11-08 14:37:40.40 spid11 Starting up database 'DYNAMICS'.
> 2004-11-08 14:37:40.40 spid12 Starting up database 'TWO'.
> 2004-11-08 14:37:40.43 spid13 Starting up database 'SVB'.
> 2004-11-08 14:37:40.43 server SQL server listening on Shared Memory,
> Named Pipes.
> 2004-11-08 14:37:40.43 server SQL Server is ready for client connection
s
> 2004-11-08 14:37:40.53 spid5 Clearing tempdb database.
> 2004-11-08 14:37:40.73 spid5 Starting up database 'tempdb'.
> 2004-11-08 14:37:40.75 spid4 Recovery complete.
> 2004-11-08 14:37:40.78 spid4 Launched startup procedure
> 'smDEX_Build_Locks'
> 2004-11-08 14:51:39.97 spid51 Using 'xpsqlbot.dll' version '2000.80.194
'
> to execute extended stored procedure 'xp_qv'.
> 2004-11-08 14:53:43.56 spid4 SQL Server is terminating due to 'stop'
> request from Service Control Manager.
> "AnthonyThomas" wrote:
>|||Thanks for you help Anthony. However after taking a closer look at the erro
r
log, I realize that Sql Sp3 was not installed properly. After installing it
again, everything is working fine now.
"AnthonyThomas" wrote:
[vbcol=seagreen]
> Your server has not been set up to use TCP/IP. If you look at your error
> log, about 1/3 of the way through, you will see the line:
> 2004-11-08 14:37:40.43 server SQL server listening on Shared Memory,
> Named Pipes.
> No, TCP/IP. Usually, this is because it was never selected as part of the
> installation or there was an IP Bind error. The Bind error also would hav
e
> shown up in the list. On the server, you need to, or have your server adm
in,
> run the Server Network utility and add the TCP/IP protocol to the list. Y
ou
> will also have to specify the port. If the Named Instance is the only
> instance, then you can use 1433.
> Sincerely,
>
> Anthony Thomas
>
> "Betmck" wrote:
>
I got the follong error:
Connection Failed:
SQL State: 01000
SQL Serve Error: 53[Microsoft][ODBC SQL Server Driver][DBNETLIB]
ConnectioOpen
(Connect()). Connection failed.
I then upgraded to Sql sp3a
Now I am receiving the error:
Connection Failed:
SQL State: 01000
SQL Server Error: 011001
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpe
n
(Connect()). Connection failed.
Connection Failed:
SQL State: 08001
SQL Server Error: 6
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Specified SQL
Server
Not found.
Let me give you an idea of our network structure and some of the issues:
We now have 2 servers. Win 2000 server and the Win 2003 server which is
running sql server 2000(This is a new server just bought).
The Win2000 server is running Active directory and is the main domain
controller.
The win 2003 server is not running Active directory.
I want all user to login to this server (Win 2000) and those requiring Great
Plains will then attach to the Win2003 Server after completing login to the
network through the win 2000 server.
The win 2003 server is running sql service pack3a
I can access shared folders on this Win 2003 server from Network places on
any machine on the network.
I can ping the 2003 server using the Ip address and Name.
Any ideas please?
cool ladyWas the SQL Server installed as the default or a named instance? What port
was it assigned to? What server name are you using in your ODBC connection?
Have you tried to connect via SQL Enterprise Manager or Query Analyzer? Do
you have permission to connect to this SQL Server installation?
Sincerely,
Anthony Thomas
"Betmck" wrote:
> I am having problems accessing the sql server through ODBC.
> I got the follong error:
> Connection Failed:
> SQL State: 01000
> SQL Serve Error: 53[Microsoft][ODBC SQL Server Driver][DBNETLI
B]ConnectioOpen
> (Connect()). Connection failed.
> I then upgraded to Sql sp3a
> Now I am receiving the error:
> Connection Failed:
> SQL State: 01000
> SQL Server Error: 011001
> [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionO
pen
> (Connect()). Connection failed.
> Connection Failed:
> SQL State: 08001
> SQL Server Error: 6
> [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Specified S
QL Server
> Not found.
>
> Let me give you an idea of our network structure and some of the issues:
> We now have 2 servers. Win 2000 server and the Win 2003 server which is
> running sql server 2000(This is a new server just bought).
> The Win2000 server is running Active directory and is the main domain
> controller.
> The win 2003 server is not running Active directory.
> I want all user to login to this server (Win 2000) and those requiring Gre
at
> Plains will then attach to the Win2003 Server after completing login to th
e
> network through the win 2000 server.
> The win 2003 server is running sql service pack3a
> I can access shared folders on this Win 2003 server from Network places on
> any machine on the network.
> I can ping the 2003 server using the Ip address and Name.
> Any ideas please?
>
> --
> cool lady|||SQL Server installed with a named instance.
Port is 1433 which is automatically assigned
Server Name in the ODBC connection is SVBNTSQL\MBSGP
I have tried connecting via both Enterprise manager and query Analyzer.
Not sure if I have permission to connect. Where should I check for this?
Thanks
"AnthonyThomas" wrote:
[vbcol=seagreen]
> Was the SQL Server installed as the default or a named instance? What por
t
> was it assigned to? What server name are you using in your ODBC connectio
n?
> Have you tried to connect via SQL Enterprise Manager or Query Analyzer? D
o
> you have permission to connect to this SQL Server installation?
> Sincerely,
>
> Anthony Thomas
>
> "Betmck" wrote:
>|||I also tried to Telnet the sql server. If I just use the Ip adress alone I
will get through. When I attached 1433 at the end I get an error "could not
open a connection to host on port 1433: connect failed.
"AnthonyThomas" wrote:
[vbcol=seagreen]
> Was the SQL Server installed as the default or a named instance? What por
t
> was it assigned to? What server name are you using in your ODBC connectio
n?
> Have you tried to connect via SQL Enterprise Manager or Query Analyzer? D
o
> you have permission to connect to this SQL Server installation?
> Sincerely,
>
> Anthony Thomas
>
> "Betmck" wrote:
>|||This is what the error log.:
2004-11-08 14:37:30.40 server Microsoft SQL Server 2000 - 8.00.194
(Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: )
2004-11-08 14:37:30.40 server Copyright (C) 1988-2000 Microsoft
Corporation.
2004-11-08 14:37:30.40 server All rights reserved.
2004-11-08 14:37:30.40 server Server Process ID is 1532.
2004-11-08 14:37:30.40 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL$MBSGP\log\ERRORLOG'.
2004-11-08 14:37:30.43 server SQL Server is starting at priority class
'normal'(2 CPUs detected).
2004-11-08 14:37:30.67 server SQL Server configured for thread mode
processing.
2004-11-08 14:37:30.68 server Using dynamic lock allocation. [2500] L
ock
Blocks, [5000] Lock Owner Blocks.
2004-11-08 14:37:30.71 server Attempting to initialize Distributed
Transaction Coordinator.
2004-11-08 14:37:35.48 spid4 Starting up database 'master'.
2004-11-08 14:37:40.40 server Using 'SSNETLIB.DLL' version '8.0.194'.
2004-11-08 14:37:40.40 spid5 Starting up database 'model'.
2004-11-08 14:37:40.40 spid4 Server name is 'SVBNTSQL\MBSGP'.
2004-11-08 14:37:40.40 spid8 Starting up database 'msdb'.
2004-11-08 14:37:40.40 spid9 Starting up database 'pubs'.
2004-11-08 14:37:40.40 spid10 Starting up database 'Northwind'.
2004-11-08 14:37:40.40 spid11 Starting up database 'DYNAMICS'.
2004-11-08 14:37:40.40 spid12 Starting up database 'TWO'.
2004-11-08 14:37:40.43 spid13 Starting up database 'SVB'.
2004-11-08 14:37:40.43 server SQL server listening on Shared Memory,
Named Pipes.
2004-11-08 14:37:40.43 server SQL Server is ready for client connections
2004-11-08 14:37:40.53 spid5 Clearing tempdb database.
2004-11-08 14:37:40.73 spid5 Starting up database 'tempdb'.
2004-11-08 14:37:40.75 spid4 Recovery complete.
2004-11-08 14:37:40.78 spid4 Launched startup procedure
'smDEX_Build_Locks'
2004-11-08 14:51:39.97 spid51 Using 'xpsqlbot.dll' version '2000.80.194'
to execute extended stored procedure 'xp_qv'.
2004-11-08 14:53:43.56 spid4 SQL Server is terminating due to 'stop'
request from Service Control Manager.
"AnthonyThomas" wrote:
[vbcol=seagreen]
> Was the SQL Server installed as the default or a named instance? What por
t
> was it assigned to? What server name are you using in your ODBC connectio
n?
> Have you tried to connect via SQL Enterprise Manager or Query Analyzer? D
o
> you have permission to connect to this SQL Server installation?
> Sincerely,
>
> Anthony Thomas
>
> "Betmck" wrote:
>|||Your server has not been set up to use TCP/IP. If you look at your error
log, about 1/3 of the way through, you will see the line:
2004-11-08 14:37:40.43 server SQL server listening on Shared Memory,
Named Pipes.
No, TCP/IP. Usually, this is because it was never selected as part of the
installation or there was an IP Bind error. The Bind error also would have
shown up in the list. On the server, you need to, or have your server admin
,
run the Server Network utility and add the TCP/IP protocol to the list. You
will also have to specify the port. If the Named Instance is the only
instance, then you can use 1433.
Sincerely,
Anthony Thomas
"Betmck" wrote:
[vbcol=seagreen]
> This is what the error log.:
> 2004-11-08 14:37:30.40 server Microsoft SQL Server 2000 - 8.00.194
> (Intel X86)
> Aug 6 2000 00:57:48
> Copyright (c) 1988-2000 Microsoft Corporation
> Standard Edition on Windows NT 5.2 (Build 3790: )
> 2004-11-08 14:37:30.40 server Copyright (C) 1988-2000 Microsoft
> Corporation.
> 2004-11-08 14:37:30.40 server All rights reserved.
> 2004-11-08 14:37:30.40 server Server Process ID is 1532.
> 2004-11-08 14:37:30.40 server Logging SQL Server messages in file
> 'C:\Program Files\Microsoft SQL Server\MSSQL$MBSGP\log\ERRORLOG'.
> 2004-11-08 14:37:30.43 server SQL Server is starting at priority class
> 'normal'(2 CPUs detected).
> 2004-11-08 14:37:30.67 server SQL Server configured for thread mode
> processing.
> 2004-11-08 14:37:30.68 server Using dynamic lock allocation. [2500]
Lock
> Blocks, [5000] Lock Owner Blocks.
> 2004-11-08 14:37:30.71 server Attempting to initialize Distributed
> Transaction Coordinator.
> 2004-11-08 14:37:35.48 spid4 Starting up database 'master'.
> 2004-11-08 14:37:40.40 server Using 'SSNETLIB.DLL' version '8.0.194'.
> 2004-11-08 14:37:40.40 spid5 Starting up database 'model'.
> 2004-11-08 14:37:40.40 spid4 Server name is 'SVBNTSQL\MBSGP'.
> 2004-11-08 14:37:40.40 spid8 Starting up database 'msdb'.
> 2004-11-08 14:37:40.40 spid9 Starting up database 'pubs'.
> 2004-11-08 14:37:40.40 spid10 Starting up database 'Northwind'.
> 2004-11-08 14:37:40.40 spid11 Starting up database 'DYNAMICS'.
> 2004-11-08 14:37:40.40 spid12 Starting up database 'TWO'.
> 2004-11-08 14:37:40.43 spid13 Starting up database 'SVB'.
> 2004-11-08 14:37:40.43 server SQL server listening on Shared Memory,
> Named Pipes.
> 2004-11-08 14:37:40.43 server SQL Server is ready for client connection
s
> 2004-11-08 14:37:40.53 spid5 Clearing tempdb database.
> 2004-11-08 14:37:40.73 spid5 Starting up database 'tempdb'.
> 2004-11-08 14:37:40.75 spid4 Recovery complete.
> 2004-11-08 14:37:40.78 spid4 Launched startup procedure
> 'smDEX_Build_Locks'
> 2004-11-08 14:51:39.97 spid51 Using 'xpsqlbot.dll' version '2000.80.194
'
> to execute extended stored procedure 'xp_qv'.
> 2004-11-08 14:53:43.56 spid4 SQL Server is terminating due to 'stop'
> request from Service Control Manager.
> "AnthonyThomas" wrote:
>|||Thanks for you help Anthony. However after taking a closer look at the erro
r
log, I realize that Sql Sp3 was not installed properly. After installing it
again, everything is working fine now.
"AnthonyThomas" wrote:
[vbcol=seagreen]
> Your server has not been set up to use TCP/IP. If you look at your error
> log, about 1/3 of the way through, you will see the line:
> 2004-11-08 14:37:40.43 server SQL server listening on Shared Memory,
> Named Pipes.
> No, TCP/IP. Usually, this is because it was never selected as part of the
> installation or there was an IP Bind error. The Bind error also would hav
e
> shown up in the list. On the server, you need to, or have your server adm
in,
> run the Server Network utility and add the TCP/IP protocol to the list. Y
ou
> will also have to specify the port. If the Named Instance is the only
> instance, then you can use 1433.
> Sincerely,
>
> Anthony Thomas
>
> "Betmck" wrote:
>
Subscribe to:
Posts (Atom)