Cannot create a new ODBC connector to my SQL server

I am trying to install a third party application that requires a SQL server.
I am using SQL 2000 in an SBS Premium environment. It appears that my
install of SQL server has some issues. To test I tried creating a new ODBC
connector to my SQL server. Using the ODBC Data Source admin tool, from the
"User DSN" tab I select "Add". From the Create a New Data Source window I
select "SQL Server". I give it a Name, Description and select my SQL server
from the drop down menu. The next window "How should SQL server verify the
authenticity of the login ID?" I choose "With SQL Server authentication
using a login ID and password entered by the user". I enter my ID and
password and get an error.
"Connection Failed:
SQL State: '28000'
SQL Server Error: 18456
[Microsoft][ODBC SQL Server Driver][SQL Server] Login failed for sqladmin.
Note: This sqladmin ID is a member of the Domain Admins group and has DBO in
SQL server.
Did you activate Mixed mode authentication on the server ?
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
"AllenM" <allen@.majaro.com> schrieb im Newsbeitrag
news:u1jJQCYVFHA.2128@.TK2MSFTNGP14.phx.gbl...
>I am trying to install a third party application that requires a SQL
>server. I am using SQL 2000 in an SBS Premium environment. It appears that
>my install of SQL server has some issues. To test I tried creating a new
>ODBC connector to my SQL server. Using the ODBC Data Source admin tool,
>from the "User DSN" tab I select "Add". From the Create a New Data Source
>window I select "SQL Server". I give it a Name, Description and select my
>SQL server from the drop down menu. The next window "How should SQL server
>verify the authenticity of the login ID?" I choose "With SQL Server
>authentication using a login ID and password entered by the user". I enter
>my ID and password and get an error.
> "Connection Failed:
> SQL State: '28000'
> SQL Server Error: 18456
> [Microsoft][ODBC SQL Server Driver][SQL Server] Login failed for sqladmin.
> Note: This sqladmin ID is a member of the Domain Admins group and has DBO
> in SQL server.
>

Cannot create a new ODBC connector to my SQL server

I am trying to install a third party application that requires a SQL server.
I am using SQL 2000 in an SBS Premium environment. It appears that my
install of SQL server has some issues. To test I tried creating a new ODBC
connector to my SQL server. Using the ODBC Data Source admin tool, from the
"User DSN" tab I select "Add". From the Create a New Data Source window I
select "SQL Server". I give it a Name, Description and select my SQL server
from the drop down menu. The next window "How should SQL server verify the
authenticity of the login ID?" I choose "With SQL Server authentication
using a login ID and password entered by the user". I enter my ID and
password and get an error.
"Connection Failed:
SQL State: '28000'
SQL Server Error: 18456
[Microsoft][ODBC SQL Server Driver][SQL Server] Login failed for sqladmin.
Note: This sqladmin ID is a member of the Domain Admins group and has DBO in
SQL server.Did you activate Mixed mode authentication on the server ?
HTH, Jens Suessmeyer.
--
http://www.sqlserver2005.de
--
"AllenM" <allen@.majaro.com> schrieb im Newsbeitrag
news:u1jJQCYVFHA.2128@.TK2MSFTNGP14.phx.gbl...
>I am trying to install a third party application that requires a SQL
>server. I am using SQL 2000 in an SBS Premium environment. It appears that
>my install of SQL server has some issues. To test I tried creating a new
>ODBC connector to my SQL server. Using the ODBC Data Source admin tool,
>from the "User DSN" tab I select "Add". From the Create a New Data Source
>window I select "SQL Server". I give it a Name, Description and select my
>SQL server from the drop down menu. The next window "How should SQL server
>verify the authenticity of the login ID?" I choose "With SQL Server
>authentication using a login ID and password entered by the user". I enter
>my ID and password and get an error.
> "Connection Failed:
> SQL State: '28000'
> SQL Server Error: 18456
> [Microsoft][ODBC SQL Server Driver][SQL Server] Login failed for sqladmin.
> Note: This sqladmin ID is a member of the Domain Admins group and has DBO
> in SQL server.
>

Cannot create a new ODBC connector to my SQL server

I am trying to install a third party application that requires a SQL server.
I am using SQL 2000 in an SBS Premium environment. It appears that my
install of SQL server has some issues. To test I tried creating a new ODBC
connector to my SQL server. Using the ODBC Data Source admin tool, from the
"User DSN" tab I select "Add". From the Create a New Data Source window I
select "SQL Server". I give it a Name, Description and select my SQL server
from the drop down menu. The next window "How should SQL server verify the
authenticity of the login ID?" I choose "With SQL Server authentication
using a login ID and password entered by the user". I enter my ID and
password and get an error.
"Connection Failed:
SQL State: '28000'
SQL Server Error: 18456
[Microsoft][ODBC SQL Server Driver][SQL Server] Login failed for
sqladmin.
Note: This sqladmin ID is a member of the Domain Admins group and has DBO in
SQL server.Did you activate Mixed mode authentication on the server ?
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--
"AllenM" <allen@.majaro.com> schrieb im Newsbeitrag
news:u1jJQCYVFHA.2128@.TK2MSFTNGP14.phx.gbl...
>I am trying to install a third party application that requires a SQL
>server. I am using SQL 2000 in an SBS Premium environment. It appears that
>my install of SQL server has some issues. To test I tried creating a new
>ODBC connector to my SQL server. Using the ODBC Data Source admin tool,
>from the "User DSN" tab I select "Add". From the Create a New Data Source
>window I select "SQL Server". I give it a Name, Description and select my
>SQL server from the drop down menu. The next window "How should SQL server
>verify the authenticity of the login ID?" I choose "With SQL Server
>authentication using a login ID and password entered by the user". I enter
>my ID and password and get an error.
> "Connection Failed:
> SQL State: '28000'
> SQL Server Error: 18456
> [Microsoft][ODBC SQL Server Driver][SQL Server] Login failed f
or sqladmin.
> Note: This sqladmin ID is a member of the Domain Admins group and has DBO
> in SQL server.
>

Cannot Connect to SQL instance on SBS 2003

I have a SBS2003 server that required a re-install of Sharepoint. I had 2
databases that are part of a document locator application, the application
made its' connection using sa and the associated password. I removed and
reinstalled Sharepoint and upgraded the sharepoint instance to SQL std as
recommended by MS. Now I must be missing something, I got as far as
re-installing SQL std and upgraded the instance of sharepoint, I did not
upgrade sbs monitoring. In services I see 2 services (mssql$sharepoint and
mssql$sbsmonitoring) both are
started. I have installed SQL SP-4, but the system tray icon shows "not
connected" , there are no errors in the event logs. I open enterprise
manager to restore the 2 databases I backed up and I do not have the ability
to restore them. What I see is the SQL server group and (LOCAL) under it, if
I click on it, I get "The SQL Server \\(LOCAL) is not known to be running.
Are you sure you wish to connect?, if I click Yes, I get "A connection could
not be established to(LOCAL). Reason: SQL server does not exist or access
denied. ConnectionOpen (Connect()).. Please verify SQL server is running and
check your SQL server registration properties (by right clicking on the
(LOCAL) node) and try again.
Any ideas on this?Try adding the Instance name to your server registration in Enterprise Manag
er.
"(local)\sharepoint"
"(local)" would connect you to the default instance, and it sounds like you
only have named instances set up.
On the Action Menu, select "New Registration"
On 08/16/2006 01:04:43 "Rick Barwig"<nouser@.nodomain.com> wrote:

> I have a SBS2003 server that required a re-install of Sharepoint. I had 2
> databases that are part of a document locator application, the application
> made its' connection using sa and the associated password. I removed and
> reinstalled Sharepoint and upgraded the sharepoint instance to SQL std as
> recommended by MS. Now I must be missing something, I got as far as
> re-installing SQL std and upgraded the instance of sharepoint, I did not
> upgrade sbs monitoring. In services I see 2 services (mssql$sharepoint
> and mssql$sbsmonitoring) both are started. I have installed SQL SP-4, but
> the system tray icon shows "not connected" , there are no errors in the
> event logs. I open enterprise manager to restore the 2 databases I backed
> up and I do not have the ability

> to restore them. What I see is the SQL server group and (LOCAL) under it,
> if I click on it, I get "The SQL Server \\(LOCAL) is not known to be
> running. Are you sure you wish to connect?, if I click Yes, I get "A
> connection could not be established to(LOCAL). Reason: SQL server does
> not exist or access denied. ConnectionOpen (Connect()).. Please verify
> SQL server is running and check your SQL server registration properties
> (by right clicking on the (LOCAL) node) and try again.

> Any ideas on this?
Glenn Adams
Tiber Creek Consulting
http://www.tibercreek.com
glenn@.tibercreek.com ---
Please DO NOT respond to me directly but post all responses here in the news
group so that all can share the information.

Cannot connect to MSDE on SBS 2003

My client has installed e scanner program wich is suposed til run on a MSDE
database. The program has to run on a reasently installed SBS 2003 server.
The server is installed with only standard features, the isa server is not
installed. Clients are running in a standard 2003 domain.
The program is working fine on the server but clients cannot connect. I test
from Excel to make the test as basic as possible. The primary client is a
terminal server 2000 but trying from XP machines do not make any difference.
I get the following error fra Excel:
Connection failed:
SQLState: '01000'
SQL Server Error: 2
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL server does not exist or
acces is denied.
To your infomation, the msde is the latest build and updates. The MDAC is
updatet on the terminalserver.
I suspect the SBS 2003 has shut down something somewhere but I have no clue
where to look. I am a total norvice in SQL.
I have checked the port 1433 an it is not "LISTENING" (nor 1434 if thats the
port) Shall it be Listening and if so, how do I get it to listen?
Michael,
I had this exact problem on one of my SBS 2003 machines running MSDE.
Often 3rd party backup software like Veritas Backup Exec, attaches to
SQL/MSDE and modifies settings. Sometimes all communication protocols
are disabled.
To fix this, on the server run 'svrnetcn' and make sure that at least
one protocol is enabled. As you checked port 1433 I assume you want to
use TCP/IP, so ensure that at least TCP is in the 'Enabled Protocols'
section.
You also need to confirm that SQL is configured to communicate via this
protocol on the client machines. To do this, run 'cliconfg' on the
client machines. You will see a similar configuration tool to the
server. Make sure the 'Enabled Protocols' match the server, ie
confirm/add TCP.
Good luck, Al.
*** Sent via Developersdex http://www.codecomments.com ***

Cannot connect to MSDE on SBS 2003

My client has installed e scanner program wich is suposed til run on a MSDE
database. The program has to run on a reasently installed SBS 2003 server.
The server is installed with only standard features, the ISA server is not
installed. Clients are running in a standard 2003 domain.
The program is working fine on the server but clients cannot connect. I test
from Excel to make the test as basic as possible. The primary client is a
terminal server 2000 but trying from XP machines do not make any difference.
I get the following error fra Excel:
Connection failed:
SQLState: '01000'
SQL Server Error: 2
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Con
nect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL server does not
exist or
acces is denied.
To your infomation, the msde is the latest build and updates. The MDAC is
updatet on the terminalserver.
I suspect the SBS 2003 has shut down something somewhere but I have no clue
where to look. I am a total norvice in SQL.
I have checked the port 1433 an it is not "LISTENING" (nor 1434 if thats the
port) Shall it be Listening and if so, how do I get it to listen?Michael,
I had this exact problem on one of my SBS 2003 machines running MSDE.
Often 3rd party backup software like Veritas Backup Exec, attaches to
SQL/MSDE and modifies settings. Sometimes all communication protocols
are disabled.
To fix this, on the server run 'svrnetcn' and make sure that at least
one protocol is enabled. As you checked port 1433 I assume you want to
use TCP/IP, so ensure that at least TCP is in the 'Enabled Protocols'
section.
You also need to confirm that SQL is configured to communicate via this
protocol on the client machines. To do this, run 'cliconfg' on the
client machines. You will see a similar configuration tool to the
server. Make sure the 'Enabled Protocols' match the server, ie
confirm/add TCP.
Good luck, Al.
*** Sent via Developersdex http://www.codecomments.com ***