ODBC connection problems....

Also posted in the MSDE section...
From: "Chris" <Chris@.discussions.microsoft.com>
Subject: MSDE / ODBC install problem...please help...
Date: Tuesday, October 25, 2005 9:41 PM
I have installed MSDE (and ODBC) at my client site on their 2003 server. I
have attached my SQL database via Teratrax Database Manager to the MSDE
server however when I try to setup the ODBC connection it doesn't list the
database in the drop-down. I cannot attach to the database from my notebook
either because I am not authenticated onto their domain.
I have also applied the regedit on the LoginMode key setting it to 2 and
rebooted but I still cannot connect to the database via the ODBC manager.
What am I doing wrong? I am NOT good with the scripts for configuring
things
- generally I use the Enterprise Manager.Hi
If you don't have Enterprise Manager you may want to try logging in with
SQL. You don't say what SQL user your are using and if they have access to
this database. If you can connect to a database on that server then you may
want to see what sp_helpdb returns, you could also use sp_attach_db to
attach the original files to the server.
John
"Chris Marsh" <cmarsh@.synergy-intl.com> wrote in message
news:uSbDAWe2FHA.1268@.TK2MSFTNGP10.phx.gbl...
> Also posted in the MSDE section...
> From: "Chris" <Chris@.discussions.microsoft.com>
> Subject: MSDE / ODBC install problem...please help...
> Date: Tuesday, October 25, 2005 9:41 PM
> I have installed MSDE (and ODBC) at my client site on their 2003 server.
> I
> have attached my SQL database via Teratrax Database Manager to the MSDE
> server however when I try to setup the ODBC connection it doesn't list the
> database in the drop-down. I cannot attach to the database from my
> notebook
> either because I am not authenticated onto their domain.
> I have also applied the regedit on the LoginMode key setting it to 2 and
> rebooted but I still cannot connect to the database via the ODBC manager.
> What am I doing wrong? I am NOT good with the scripts for configuring
> things
> - generally I use the Enterprise Manager.
>

ODBC connection problems....

Also posted in the MSDE section...
From: "Chris" <Chris@.discussions.microsoft.com>
Subject: MSDE / ODBC install problem...please help...
Date: Tuesday, October 25, 2005 9:41 PM
I have installed MSDE (and ODBC) at my client site on their 2003 server. I
have attached my SQL database via Teratrax Database Manager to the MSDE
server however when I try to setup the ODBC connection it doesn't list the
database in the drop-down. I cannot attach to the database from my notebook
either because I am not authenticated onto their domain.
I have also applied the regedit on the LoginMode key setting it to 2 and
rebooted but I still cannot connect to the database via the ODBC manager.
What am I doing wrong? I am NOT good with the scripts for configuring
things
- generally I use the Enterprise Manager.
Hi
If you don't have Enterprise Manager you may want to try logging in with
SQL. You don't say what SQL user your are using and if they have access to
this database. If you can connect to a database on that server then you may
want to see what sp_helpdb returns, you could also use sp_attach_db to
attach the original files to the server.
John
"Chris Marsh" <cmarsh@.synergy-intl.com> wrote in message
news:uSbDAWe2FHA.1268@.TK2MSFTNGP10.phx.gbl...
> Also posted in the MSDE section...
> From: "Chris" <Chris@.discussions.microsoft.com>
> Subject: MSDE / ODBC install problem...please help...
> Date: Tuesday, October 25, 2005 9:41 PM
> I have installed MSDE (and ODBC) at my client site on their 2003 server.
> I
> have attached my SQL database via Teratrax Database Manager to the MSDE
> server however when I try to setup the ODBC connection it doesn't list the
> database in the drop-down. I cannot attach to the database from my
> notebook
> either because I am not authenticated onto their domain.
> I have also applied the regedit on the LoginMode key setting it to 2 and
> rebooted but I still cannot connect to the database via the ODBC manager.
> What am I doing wrong? I am NOT good with the scripts for configuring
> things
> - generally I use the Enterprise Manager.
>

ODBC connection problems....

Also posted in the MSDE section...
From: "Chris" <Chris@.discussions.microsoft.com>
Subject: MSDE / ODBC install problem...please help...
Date: Tuesday, October 25, 2005 9:41 PM
I have installed MSDE (and ODBC) at my client site on their 2003 server. I
have attached my SQL database via Teratrax Database Manager to the MSDE
server however when I try to setup the ODBC connection it doesn't list the
database in the drop-down. I cannot attach to the database from my notebook
either because I am not authenticated onto their domain.
I have also applied the regedit on the LoginMode key setting it to 2 and
rebooted but I still cannot connect to the database via the ODBC manager.
What am I doing wrong? I am NOT good with the scripts for configuring
things
- generally I use the Enterprise Manager.Hi
If you don't have Enterprise Manager you may want to try logging in with
SQL. You don't say what SQL user your are using and if they have access to
this database. If you can connect to a database on that server then you may
want to see what sp_helpdb returns, you could also use sp_attach_db to
attach the original files to the server.
John
"Chris Marsh" <cmarsh@.synergy-intl.com> wrote in message
news:uSbDAWe2FHA.1268@.TK2MSFTNGP10.phx.gbl...
> Also posted in the MSDE section...
> From: "Chris" <Chris@.discussions.microsoft.com>
> Subject: MSDE / ODBC install problem...please help...
> Date: Tuesday, October 25, 2005 9:41 PM
> I have installed MSDE (and ODBC) at my client site on their 2003 server.
> I
> have attached my SQL database via Teratrax Database Manager to the MSDE
> server however when I try to setup the ODBC connection it doesn't list the
> database in the drop-down. I cannot attach to the database from my
> notebook
> either because I am not authenticated onto their domain.
> I have also applied the regedit on the LoginMode key setting it to 2 and
> rebooted but I still cannot connect to the database via the ODBC manager.
> What am I doing wrong? I am NOT good with the scripts for configuring
> things
> - generally I use the Enterprise Manager.
>sql

ODBC Connection Problems

I'm having problems connecting to an MSDE database through ODBC.
The following message appears below:

Connection Failed:
SQL State: '01000'
SQL Server Error: 10061
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]
Connection Open (Connect())
Connection Failed:
SQL State '08001'
SQL Server Error 17
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL
Server does not exist or access denied

I've tried the following
1. Downloading the lastest version of MDAC.
2. Tried Pinging the server which was successful.
3. Setting up an ODBC connection to the server from another client which was successful.
4. Adding an entry in my hosts file to see the server.
5. Searching the archives for a solution.

Does anyone have any other ideas as I stumped?

Thanks.Are you sure you have declared the full server (and instance) name for the MSDE instance? Check services on the MSDE box, and look for MSSQL$___. The ___ is the instance name. Also, are you able to connect to the MSDE instance with any other tools (Query Analyzer, OSQL, etc.)?|||It's quite embarrassing but someone put the wrong IP address label on the server. Thanks for your help.|||As fate would have it, I am encountering a very similar problem. Everything was working fine and dandy up until two days ago when suddenly you were unable to connect to SQLServer.

At first, you were able to connect via EM but not Query Analyzer. Now suddenly you're unable to connect using either. This literally happened overnight. I'm gettign the same error message as referenced above. I'm able to ping the box just fine, but cannot isql into it or use Query Analyzer/EM.

I'm running SQL2K on SP3 / Windows 2000 Advanced Server.

ANY suggestions would be greatly appreciated.

P.S. - One of the boxes is a development box and one is a production machine. I have considered installing MDAC 8 on the dev machine to see if this does the trick. Has this worked for anyone else who was having a similar problem, and what - if any - were the side effects?

Thanks again!|||...also forgot to mention that I'm unable to create an ODBC connection to the servers as well.

Thanx

ODBC connection

Hi,
I would like to have a ODBC connection to a MSDE 2000 database on a Win 2003
server from a client PC. Can this be done?
On the client I can browse to the the SQL server, but I cannot connect to
it. Is there a way to connect and retreive the data ?
Arnold
What does it mean "cannot connect to it"? How do you do it, any error
message? Yes, there is way to connect to it, as long as you do it right.
The simplest way would be doing it from Control Panel->Administrative
Tools->ODBC Data Source and follows the wizard and make correct selection.
"Arnold" <Arnolddegreef@.quicknet.punt.nl> wrote in message
news:uFNlJ9vwHHA.3364@.TK2MSFTNGP02.phx.gbl...
> Hi,
> I would like to have a ODBC connection to a MSDE 2000 database on a Win
> 2003 server from a client PC. Can this be done?
> On the client I can browse to the the SQL server, but I cannot connect to
> it. Is there a way to connect and retreive the data ?
> Arnold
>
|||Hi Norman,
I can do what you suggest on the server, but I cannot do it on a PC
connected to the same server.
If I connect from a PC I get a message that either the SQL database does not
exist, or the username and password is not OK.
When I type in exactly the same settings on the server it all works OK. (I
have not got the exact message for you since it is in Dutch)
So it seems that I am not allowed to connect to the database via ODBC on a
PC. Is that correct, or is there another way to do this ?
Arnold
"Norman Yuan" <NotReal@.NotReal.not> schreef in bericht
news:e%23zxmswwHHA.4736@.TK2MSFTNGP04.phx.gbl...
> What does it mean "cannot connect to it"? How do you do it, any error
> message? Yes, there is way to connect to it, as long as you do it right.
> The simplest way would be doing it from Control Panel->Administrative
> Tools->ODBC Data Source and follows the wizard and make correct selection.
> "Arnold" <Arnolddegreef@.quicknet.punt.nl> wrote in message
> news:uFNlJ9vwHHA.3364@.TK2MSFTNGP02.phx.gbl...
>
|||After Windows 2000 SP2, MSDE was blinded and its ports were shut off. This
prevents it from being attacked by the slammer virus? worm...-whatever. These
ports and protocols must be reenabled for the service to be visible on the
network. Yes, you can connect via ODBC but there are a lot of other
alternatives that are more efficient. Are you building a .NET application,
VB6 or what?
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"Arnold" <Arnolddegreef@.quicknet.punt.nl> wrote in message
news:eZYofzwwHHA.2040@.TK2MSFTNGP03.phx.gbl...
> Hi Norman,
> I can do what you suggest on the server, but I cannot do it on a PC
> connected to the same server.
> If I connect from a PC I get a message that either the SQL database does
> not exist, or the username and password is not OK.
> When I type in exactly the same settings on the server it all works OK. (I
> have not got the exact message for you since it is in Dutch)
> So it seems that I am not allowed to connect to the database via ODBC on a
> PC. Is that correct, or is there another way to do this ?
> Arnold
> "Norman Yuan" <NotReal@.NotReal.not> schreef in bericht
> news:e%23zxmswwHHA.4736@.TK2MSFTNGP04.phx.gbl...
>
|||OK, let us see what exactly you ran into:
1. Strat Control Panel->Administrative Tools->Data Sources(ODBC) applet; You
should be OK.
2. Click User DSN or SYSTEM DSN tab (Assume to create a System DSN). You
should be OK.
3. Click "Add Button" -> select "SQL Server" ->Click "Finish" to get you
into "Create a New Data Source to SQL Server" wizard. You should be OK.
4. Enter DSN name, Description and select the SQL Server from dropdown list
(you can also type SQL Server/instance name, too). You should be OK to go to
Next step.
5. Here is your turn to describe what you did on each step for next three
steps that leads you to failure.
"Arnold" <Arnolddegreef@.quicknet.punt.nl> wrote in message
news:eZYofzwwHHA.2040@.TK2MSFTNGP03.phx.gbl...
> Hi Norman,
> I can do what you suggest on the server, but I cannot do it on a PC
> connected to the same server.
> If I connect from a PC I get a message that either the SQL database does
> not exist, or the username and password is not OK.
> When I type in exactly the same settings on the server it all works OK. (I
> have not got the exact message for you since it is in Dutch)
> So it seems that I am not allowed to connect to the database via ODBC on a
> PC. Is that correct, or is there another way to do this ?
> Arnold
> "Norman Yuan" <NotReal@.NotReal.not> schreef in bericht
> news:e%23zxmswwHHA.4736@.TK2MSFTNGP04.phx.gbl...
>
|||Hello Bill, I will explain my challenge a little more:
I would like to connect a visio drawing to sharepoint. In Visio I have a
task flowchart that visually represents the same (project)tasks in
Sharepoint.
Visio has an excelent Database wizzard that perfectly connects the Visio
tasks to lets say Excel or Access, but I need a connection to the Sharepoint
SQL (MSDE) database for it.
Since I do not want to run the Visio application on the server, I need the
connection from a client to the SQL database on the server.
Do you have any more suggestions ?
Thanks in advance,
Arnold
"William (Bill) Vaughn" <billvaRemoveThis@.betav.com> schreef in bericht
news:%23xzhe%23wwHHA.4568@.TK2MSFTNGP03.phx.gbl...
> After Windows 2000 SP2, MSDE was blinded and its ports were shut off. This
> prevents it from being attacked by the slammer virus? worm...-whatever.
> These ports and protocols must be reenabled for the service to be visible
> on the network. Yes, you can connect via ODBC but there are a lot of other
> alternatives that are more efficient. Are you building a .NET application,
> VB6 or what?
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ------
> "Arnold" <Arnolddegreef@.quicknet.punt.nl> wrote in message
> news:eZYofzwwHHA.2040@.TK2MSFTNGP03.phx.gbl...
>
|||Visio uses ODBC connection. You create ODBC connection to SQL Server exactly
the same way (the same wizard) as you do from Control Panel->Administrative
Tools->Data Source(ODBC).
To connect to SQL Server you need to:
1. Make sure the SQL Server can be connected from network. If you are not
sure, ask your network admin/database admin. If you installed the SQL
Server, you need to learn more beofre install it and use it.
2. Know the database name.
3. Ask the network admin/database admin for the SQL Server name, login
credential (if the SQL Server uses Windows security, make sure your windows
account has necessary access permission; if SQL server uses mixed security
mode, you can ask username/password instead). If you installed the SQL
Server, again, a bit more study on SQL Server security before using it.
The Wizard just does that: ask you SQL Server name, login credential, and
then database name. As long as you can supply them correctly, there
shouldn't any problem.
"Arnold" <Arnolddegreef@.quicknet.punt.nl> wrote in message
news:ena0PhywHHA.4228@.TK2MSFTNGP06.phx.gbl...
> Hello Bill, I will explain my challenge a little more:
> I would like to connect a visio drawing to sharepoint. In Visio I have a
> task flowchart that visually represents the same (project)tasks in
> Sharepoint.
> Visio has an excelent Database wizzard that perfectly connects the Visio
> tasks to lets say Excel or Access, but I need a connection to the
> Sharepoint SQL (MSDE) database for it.
> Since I do not want to run the Visio application on the server, I need the
> connection from a client to the SQL database on the server.
> Do you have any more suggestions ?
> Thanks in advance,
> Arnold
>
> "William (Bill) Vaughn" <billvaRemoveThis@.betav.com> schreef in bericht
> news:%23xzhe%23wwHHA.4568@.TK2MSFTNGP03.phx.gbl...
>
|||Hello Norman, thanks for your reply.
My answers are in your reply:
"Norman Yuan" <NotReal@.NotReal.not> schreef in bericht
news:%23xSVlAywHHA.1776@.TK2MSFTNGP03.phx.gbl...
> OK, let us see what exactly you ran into:
> 1. Strat Control Panel->Administrative Tools->Data Sources(ODBC) applet;
> You should be OK.
OK

> 2. Click User DSN or SYSTEM DSN tab (Assume to create a System DSN). You
> should be OK.
No problem

> 3. Click "Add Button" -> select "SQL Server" ->Click "Finish" to get you
> into "Create a New Data Source to SQL Server" wizard. You should be OK.

> 4. Enter DSN name, Description and select the SQL Server from dropdown
> list (you can also type SQL Server/instance name, too). You should be OK
> to go to Next step.
Also no problem. My name is : SERVER-FILE\MICROSOFT##SSEE
Server-File is the name of our Server, and MICROSOFT##SSEE is the standard
name Sharepoint give to the database.

> 5. Here is your turn to describe what you did on each step for next three
> steps that leads you to failure.
I can choose between Windows NT verification, or SQL server verification. If
I choose NT verification, I get this message (not an exact reply, since it
is in Dutch):
Connection failure:
SQL State 01000
SQL Server error 223
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).
Connection failure:
SQL State: 08001
SQL Server error 17
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL-server does not exist, or
the login is refused (someting like that).
The same thing goed for a SQL server verification. I would not know that
username and pass to fill in here. The administrator login does not work
here.
If I do this on Server-file however, I do get a connection.
Arnold
> "Arnold" <Arnolddegreef@.quicknet.punt.nl> wrote in message
> news:eZYofzwwHHA.2040@.TK2MSFTNGP03.phx.gbl...
>
|||Hi Norman,
I am the administratror and have all the rights to my network/database
admin.
I have not installed the server myself. A third IT party did that for us.
They also do not know why I cannot connect directly from a PC. They did not
put in a specific password. It is a standard installation.
Furthermore the SQL server works perfectly OK on the Win 2003 server. We are
using this for more than two years. The only problem I have is making a
connection from ODBC on a PC.
Arnold
"Norman Yuan" <NotReal@.NotReal.not> schreef in bericht
news:uExHC2ywHHA.4308@.TK2MSFTNGP02.phx.gbl...
> Visio uses ODBC connection. You create ODBC connection to SQL Server
> exactly the same way (the same wizard) as you do from Control
> Panel->Administrative Tools->Data Source(ODBC).
> To connect to SQL Server you need to:
> 1. Make sure the SQL Server can be connected from network. If you are not
> sure, ask your network admin/database admin. If you installed the SQL
> Server, you need to learn more beofre install it and use it.
> 2. Know the database name.
> 3. Ask the network admin/database admin for the SQL Server name, login
> credential (if the SQL Server uses Windows security, make sure your
> windows account has necessary access permission; if SQL server uses mixed
> security mode, you can ask username/password instead). If you installed
> the SQL Server, again, a bit more study on SQL Server security before
> using it.
> The Wizard just does that: ask you SQL Server name, login credential, and
> then database name. As long as you can supply them correctly, there
> shouldn't any problem.
>
> "Arnold" <Arnolddegreef@.quicknet.punt.nl> wrote in message
> news:ena0PhywHHA.4228@.TK2MSFTNGP06.phx.gbl...
>
|||"Arnold" <Arnolddegreef@.quicknet.punt.nl> wrote in message
news:%23H%23b1s6wHHA.1168@.TK2MSFTNGP02.phx.gbl...
> Hello Norman, thanks for your reply.
> My answers are in your reply:
> "Norman Yuan" <NotReal@.NotReal.not> schreef in bericht
> news:%23xSVlAywHHA.1776@.TK2MSFTNGP03.phx.gbl...
> OK
>
> No problem
>
> Also no problem. My name is : SERVER-FILE\MICROSOFT##SSEE
> Server-File is the name of our Server, and MICROSOFT##SSEE is the standard
> name Sharepoint give to the database.
>
> I can choose between Windows NT verification, or SQL server verification.
> If I choose NT verification, I get this message (not an exact reply, since
> it is in Dutch):
> Connection failure:
> SQL State 01000
> SQL Server error 223
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).
> Connection failure:
> SQL State: 08001
> SQL Server error 17
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL-server does not exist, or
> the login is refused (someting like that).
It is obvious that the user account you used on the client PC, where you
want to create a ODBC connection to SQL Server, does not have access to the
SQL Server. Since you alread passed previous step (i.e. you have selected
the SQL Server name from a list), we are sure the SQL Server DOES exists and
can be seen by the client PC. So, you are facing SQL Server security
problem. No offence, I recommend you study a bit more on SQL Server
security, especially how to create SQL Server login, Database user and map
Windows/Domain user account to logins and users. If you kown a window/domain
user account can access the sql server/database, then use that account to
log on the PC. If you are to create System DSN, you need to use an admin
account.
Most likely, if you log on the PC as domain admin, you would be able to
access the database. Or, you could log on to the server computer, where the
SQL Server sits, as local admin, you should be able to get into the SQL
Server, then you can create necessary SQL Server logins/database users, and
map them to different computer users/groupd on your network/domain. Again,
do the due study before doing so, you do not want to open the SQL Server too
widely to put in risk.

> The same thing goed for a SQL server verification. I would not know that
> username and pass to fill in here. The administrator login does not work
> here.
If you choose SQL Server authentication, you have to make sure the SQL
Server's mixed security mode is enabled (it is disable by default). If not
enable, of course you can not use it. You must know a login's
username/password in pair, which is not the windows username/password,
whether it is admin or not.

> If I do this on Server-file however, I do get a connection.
> Arnold
>
>
sql

ODBC Compliant

Can anyone tell me if MSDE is ODBC compliant?
It is not the DBMS which is ODBC compliant or not. The question is whether there exist an ODBC driver for the
DBMS. And the answer is "yes", obviously. MS invented ODBC (*), and MSDE is SQL Server and SQL Server is MS's
strategic DBMS :-)
(*) ODBC is actually just an implementation of the ANSI SQL CLI standard...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Stephanie Locklear" <anonymous@.discussions.microsoft.com> wrote in message
news:F30539C5-E3E1-440C-8DA3-B27CCD0CAC3D@.microsoft.com...
> Can anyone tell me if MSDE is ODBC compliant?

ODBC cannot connect to MSDE 2000a

Using MSDE 2000a (w/spk3a). XP Pro. Cannot connect w/ ODBC driver to server.
Have tried many things.
Below is the error when trying to connect via ODBC.
Help!
GIL
Microsoft SQL Server Login
Connection failed:
SQLState: '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.
hi,
"Padji" <gil.pajany@.free.fr> ha scritto nel messaggio
news:410f60ea$0$1890$636a15ce@.news.free.fr...
> Using MSDE 2000a (w/spk3a). XP Pro. Cannot connect w/ ODBC driver to
server.
> Have tried many things.
> Below is the error when trying to connect via ODBC.
> Help!
> GIL
>
> --
> Microsoft SQL Server Login
> --
> Connection failed:
> SQLState: '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.
>
>
please verify your instance has netwrok protocols enabled... run Server
Network Utility (svrnetcnexe) to check that and, eventually, enable TCP/IP
as needed..
eventually, run Client Network Utility (cliconfg.exe) and make sure TCP/IP
are enabled ... try to make an alias using TCP using SQL server name and
test connection. if it still fails, try creating an alias with the IP
address of the SQL server.
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||I am having the exact same problem. I'm using SQL Server 2005 beta.
In the SQL manager utility I did what you suggested, which is to enable all
network protocols, and am getting the same issue.
It doesn't matter what client configuration I use for ODBC -- shared memory,
named pipes, tcp.
Should I uninstall the DB, delete all registry settings related to it, and
then reinstall?
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:2n9m2eFti527U1@.uni-berlin.de...
> hi,
> "Padji" <gil.pajany@.free.fr> ha scritto nel messaggio
> news:410f60ea$0$1890$636a15ce@.news.free.fr...
> server.
> exist
> please verify your instance has netwrok protocols enabled... run Server
> Network Utility (svrnetcnexe) to check that and, eventually, enable TCP/IP
> as needed..
> eventually, run Client Network Utility (cliconfg.exe) and make sure TCP/IP
> are enabled ... try to make an alias using TCP using SQL server name and
> test connection. if it still fails, try creating an alias with the IP
> address of the SQL server.
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||hi,
"Yair Sageev" <geekyheeb-news@.yahoo.com> ha scritto nel messaggio
news:eFIcuAkeEHA.3792@.TK2MSFTNGP09.phx.gbl...
> I am having the exact same problem. I'm using SQL Server 2005 beta.
> In the SQL manager utility I did what you suggested, which is to enable
all
> network protocols, and am getting the same issue.
> It doesn't matter what client configuration I use for ODBC -- shared
memory,
> named pipes, tcp.
> Should I uninstall the DB, delete all registry settings related to it, and
> then reinstall?
>
before reinstalling, pleas have a look at
http://support.microsoft.com/default...06&Product=sql
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

ODBC Call fail - Strange behaviour

Hi.
I just installed Sql server (in fact MSDE) and exported my Access 2002
projet to this database instance.
I then linked my Sql server tables within my access project.
I get a strange behaviour for some queries. I receive the message 'ODBC -
Call fail'. It seems to be a timeout pb.
The query involves two tables.
I checked my query. Everithing is ok.
I checked the first table. I can read data and filter it.
I checked the second table. I can read data, but if I want to filter any
column, I get an ODBC call fail. The table contains only 802 records.
Any idea ?
Configuration :
MSDE Rel A on XP home SP1.
Access 2002 client, MDAC 2.8, on XP Pro.
Check your data on the SQL server. You may have some data that is null and
the SQL server table def is not allowing nulls? Just a thought. Usually
these errors are caught during the import process...
I would start by creating a brand new query and only add one column at a
time. See if you can then sort on that column. Carry on like this - adding
new columns each time until the error happens. Then check that columns data
on the SQL server so see if there happens to be null values present...
"Alain" <alain.roghi_nospam@.laposte.net> wrote in message
news:uU5H9BEmEHA.2180@.TK2MSFTNGP12.phx.gbl...
> Hi.
> I just installed Sql server (in fact MSDE) and exported my Access 2002
> projet to this database instance.
> I then linked my Sql server tables within my access project.
> I get a strange behaviour for some queries. I receive the message 'ODBC -
> Call fail'. It seems to be a timeout pb.
> The query involves two tables.
> I checked my query. Everithing is ok.
> I checked the first table. I can read data and filter it.
> I checked the second table. I can read data, but if I want to filter any
> column, I get an ODBC call fail. The table contains only 802 records.
> Any idea ?
> Configuration :
> MSDE Rel A on XP home SP1.
> Access 2002 client, MDAC 2.8, on XP Pro.
>

ODBC and Windows 98

We set up a MSDE 2000 database on a Windows 98 machine. We're trying to
connect to the W98 DB from a XP machine using an ODBC and a Windows
authentication. We get the following error when trying to test-connect the
DB:
SQL Server error 18452 : Login failed. Not associated with trusted SQL
server.
The machines are on the same workgroup, and we made the Windows logins and
passwords the same as the SQL logins and password. What is the issue, and
can it be solved?
Thanks,
Matt
I forgot to mention that the ODBC is in mixed mode.
Matt
"Matt" <mrocha@.camicro.com> wrote in message
news:uC8%23XqNKFHA.1540@.TK2MSFTNGP14.phx.gbl...
> We set up a MSDE 2000 database on a Windows 98 machine. We're trying to
> connect to the W98 DB from a XP machine using an ODBC and a Windows
> authentication. We get the following error when trying to test-connect
the
> DB:
> SQL Server error 18452 : Login failed. Not associated with trusted SQL
> server.
> The machines are on the same workgroup, and we made the Windows logins and
> passwords the same as the SQL logins and password. What is the issue, and
> can it be solved?
> Thanks,
> Matt
>

ODBC and Windows 98

We set up a MSDE 2000 database on a Windows 98 machine. We're trying to
connect to the W98 DB from a XP machine using an ODBC and a Windows
authentication. We get the following error when trying to test-connect the
DB:
SQL Server error 18452 : Login failed. Not associated with trusted SQL
server.
The machines are on the same workgroup, and we made the Windows logins and
passwords the same as the SQL logins and password. What is the issue, and
can it be solved?
Thanks,
MattI forgot to mention that the ODBC is in mixed mode.
Matt
"Matt" <mrocha@.camicro.com> wrote in message
news:uC8%23XqNKFHA.1540@.TK2MSFTNGP14.phx.gbl...
> We set up a MSDE 2000 database on a Windows 98 machine. We're trying to
> connect to the W98 DB from a XP machine using an ODBC and a Windows
> authentication. We get the following error when trying to test-connect
the
> DB:
> SQL Server error 18452 : Login failed. Not associated with trusted SQL
> server.
> The machines are on the same workgroup, and we made the Windows logins and
> passwords the same as the SQL logins and password. What is the issue, and
> can it be solved?
> Thanks,
> Matt
>

ODBC and MSDE

Hello,
I'm not sure if it is right group for this question, but I hope that
I'll get help here...
I'm using MSDE to store data for my application. And I'm having such
problem. I'm creating a table in DB for string connection information:
CREATE TABLE sql (
action_id int NOT NULL default '0',
database_name varchar(20) NOT NULL default '',
username varchar(15) NOT NULL default '',
password varchar(15) NOT NULL default '',
PRIMARY KEY (action_id)
);
Field 'database_name' stands for the DB name used by ODBC (In my Java
application I'm using ODBC, to connect to particular DB). So when I'm
adding a record to this table, for instance:
1, "MySQL", "root", "password"
ODBC || MSDE || JDBC changes the values by adding free space to fill all
the field's spaces (Instead of "MySQL" it adds "MySQL "). It
seems like some component doesn't understand that I'm using varchar(20),
not char.
For instance, when I'm using MySQL DB server, such problem doesn't
introduce itself... Does anyone know how to manage this?
Thank you,
Audrius
Audrius wrote:
> Hello,
> I'm not sure if it is right group for this question, but I hope that
> I'll get help here...
> I'm using MSDE to store data for my application. And I'm having such
> problem. I'm creating a table in DB for string connection information:
> CREATE TABLE sql (
> action_id int NOT NULL default '0',
> database_name varchar(20) NOT NULL default '',
> username varchar(15) NOT NULL default '',
> password varchar(15) NOT NULL default '',
> PRIMARY KEY (action_id)
> );
> Field 'database_name' stands for the DB name used by ODBC (In my Java
> application I'm using ODBC, to connect to particular DB). So when I'm
> adding a record to this table, for instance:
> 1, "MySQL", "root", "password"
> ODBC || MSDE || JDBC changes the values by adding free space to fill all
> the field's spaces (Instead of "MySQL" it adds "MySQL "). It
> seems like some component doesn't understand that I'm using varchar(20),
> not char.
> For instance, when I'm using MySQL DB server, such problem doesn't
> introduce itself... Does anyone know how to manage this?
> Thank you,
> Audrius
When I tried to insert data into MSDE table using console, everything
worked fine. The data occupies exactly as it should ("MySQL" - 5
symbols). But when I do this using ODBC from my application, it doesn't
work right. Can anyone suggest me a solution?
|||Audrius wrote:
> Audrius wrote:
>
> When I tried to insert data into MSDE table using console, everything
> worked fine. The data occupies exactly as it should ("MySQL" - 5
> symbols). But when I do this using ODBC from my application, it doesn't
> work right. Can anyone suggest me a solution?
The problem was solved.

ODBC and MSDE

Hello,
I'm not sure if it is right group for this question, but I hope that
I'll get help here...
I'm using MSDE to store data for my application. And I'm having such
problem. I'm creating a table in DB for string connection information:
CREATE TABLE sql (
action_id int NOT NULL default '0',
database_name varchar(20) NOT NULL default '',
username varchar(15) NOT NULL default '',
password varchar(15) NOT NULL default '',
PRIMARY KEY (action_id)
);
Field 'database_name' stands for the DB name used by ODBC (In my Java
application I'm using ODBC, to connect to particular DB). So when I'm
adding a record to this table, for instance:
1, "MySQL", "root", "password"
ODBC || MSDE || JDBC changes the values by adding free space to fill all
the field's spaces (Instead of "MySQL" it adds "MySQL "). It
seems like some component doesn't understand that I'm using varchar(20),
not char.
For instance, when I'm using MySQL DB server, such problem doesn't
introduce itself... Does anyone know how to manage this?
Thank you,
Audrius
Audrius wrote:
> Hello,
> I'm not sure if it is right group for this question, but I hope that
> I'll get help here...
> I'm using MSDE to store data for my application. And I'm having such
> problem. I'm creating a table in DB for string connection information:
> CREATE TABLE sql (
> action_id int NOT NULL default '0',
> database_name varchar(20) NOT NULL default '',
> username varchar(15) NOT NULL default '',
> password varchar(15) NOT NULL default '',
> PRIMARY KEY (action_id)
> );
> Field 'database_name' stands for the DB name used by ODBC (In my Java
> application I'm using ODBC, to connect to particular DB). So when I'm
> adding a record to this table, for instance:
> 1, "MySQL", "root", "password"
> ODBC || MSDE || JDBC changes the values by adding free space to fill all
> the field's spaces (Instead of "MySQL" it adds "MySQL "). It
> seems like some component doesn't understand that I'm using varchar(20),
> not char.
> For instance, when I'm using MySQL DB server, such problem doesn't
> introduce itself... Does anyone know how to manage this?
> Thank you,
> Audrius
When I tried to insert data into MSDE table using console, everything
worked fine. The data occupies exactly as it should ("MySQL" - 5
symbols). But when I do this using ODBC from my application, it doesn't
work right. Can anyone suggest me a solution?
|||Audrius wrote:
> Audrius wrote:
>
> When I tried to insert data into MSDE table using console, everything
> worked fine. The data occupies exactly as it should ("MySQL" - 5
> symbols). But when I do this using ODBC from my application, it doesn't
> work right. Can anyone suggest me a solution?
The problem was solved.

ODBC and MSDE

Hello,

I'm not sure if it is right group for this question, but I hope that
I'll get help here...

I'm using MSDE to store data for my application. And I'm having such
problem. I'm creating a table in DB for string connection information:

CREATE TABLE sql (
action_id int NOT NULL default '0',
database_name varchar(20) NOT NULL default '',
username varchar(15) NOT NULL default '',
password varchar(15) NOT NULL default '',
PRIMARY KEY (action_id)
);

Field 'database_name' stands for the DB name used by ODBC (In my Java
application I'm using ODBC, to connect to particular DB). So when I'm
adding a record to this table, for instance:
1, "MySQL", "root", "password"
ODBC || MSDE || JDBC changes the values by adding free space to fill
all the field's spaces (Instead of "MySQL" it adds "MySQL
"). It seems like some component doesn't understand that I'm using
varchar(20), not char.

For instance, when I'm using MySQL DB server, such problem doesn't
introduce itself... Does anyone know how to manage this?

Thank you,
AudriusWhen I tried to insert data into MSDE table using console, everything
worked fine. The data occupies exactly as it should ("MySQL" - 5
symbols). But when I do this using ODBC from my application, it doesn't
work right. Can anyone suggest me a solution?|||Audrius (audrius.peseckis@.gmail.com) writes:
> I'm not sure if it is right group for this question, but I hope that
> I'll get help here...
> I'm using MSDE to store data for my application. And I'm having such
> problem. I'm creating a table in DB for string connection information:
> CREATE TABLE sql (
> action_id int NOT NULL default '0',
> database_name varchar(20) NOT NULL default '',
> username varchar(15) NOT NULL default '',
> password varchar(15) NOT NULL default '',
> PRIMARY KEY (action_id)
> );
> Field 'database_name' stands for the DB name used by ODBC (In my Java
> application I'm using ODBC, to connect to particular DB). So when I'm
> adding a record to this table, for instance:
> 1, "MySQL", "root", "password"
> ODBC || MSDE || JDBC changes the values by adding free space to fill
> all the field's spaces (Instead of "MySQL" it adds "MySQL
> "). It seems like some component doesn't understand that I'm using
> varchar(20), not char.

It appears that your app passes "MySQL ". In such case,
SQL Server will store the trailing spaces when the ANSI_PADDING
option is in effect, which it is by default when you use ODBC. You
need to trim the trailing spaces somewhere on the line.

There are a few more possibilities, but I can't really speculate
about them, as you did not provide any code.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Yes, it solved the problem. ODBC was set to use ANSI padding by
default. Your reply saved me a lot of time, thank you.

Audrius|||Audrius (audrius.peseckis@.gmail.com) writes:
> Yes, it solved the problem. ODBC was set to use ANSI padding by
> default. Your reply saved me a lot of time, thank you.

While turning of ANSI_PADDING may solve the problem, be aware of
that there are features in SQL Server that require ANSI_PADDING to
be on. In SQL 2000 that is indexed views and indexes on computed
columns. I believe there are more features in SQL 2005.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

ODBC and MSDE

Hello,
I'm not sure if it is right group for this question, but I hope that
I'll get help here...
I'm using MSDE to store data for my application. And I'm having such
problem. I'm creating a table in DB for string connection information:
CREATE TABLE sql (
action_id int NOT NULL default '0',
database_name varchar(20) NOT NULL default '',
username varchar(15) NOT NULL default '',
password varchar(15) NOT NULL default '',
PRIMARY KEY (action_id)
);
Field 'database_name' stands for the DB name used by ODBC (In my Java
application I'm using ODBC, to connect to particular DB). So when I'm
adding a record to this table, for instance:
1, "MySQL", "root", "password"
ODBC || MSDE || JDBC changes the values by adding free space to fill all
the field's spaces (Instead of "MySQL" it adds "MySQL "). It
seems like some component doesn't understand that I'm using varchar(20),
not char.
For instance, when I'm using mysql DB server, such problem doesn't
introduce itself... Does anyone know how to manage this?
Thank you,
AudriusAudrius wrote:
> Hello,
> I'm not sure if it is right group for this question, but I hope that
> I'll get help here...
> I'm using MSDE to store data for my application. And I'm having such
> problem. I'm creating a table in DB for string connection information:
> CREATE TABLE sql (
> action_id int NOT NULL default '0',
> database_name varchar(20) NOT NULL default '',
> username varchar(15) NOT NULL default '',
> password varchar(15) NOT NULL default '',
> PRIMARY KEY (action_id)
> );
> Field 'database_name' stands for the DB name used by ODBC (In my Java
> application I'm using ODBC, to connect to particular DB). So when I'm
> adding a record to this table, for instance:
> 1, "MySQL", "root", "password"
> ODBC || MSDE || JDBC changes the values by adding free space to fill all
> the field's spaces (Instead of "MySQL" it adds "MySQL "). It
> seems like some component doesn't understand that I'm using varchar(20),
> not char.
> For instance, when I'm using mysql DB server, such problem doesn't
> introduce itself... Does anyone know how to manage this?
> Thank you,
> Audrius
When I tried to insert data into MSDE table using console, everything
worked fine. The data occupies exactly as it should ("MySQL" - 5
symbols). But when I do this using ODBC from my application, it doesn't
work right. Can anyone suggest me a solution?|||Audrius wrote:
> Audrius wrote:
>
>
> When I tried to insert data into MSDE table using console, everything
> worked fine. The data occupies exactly as it should ("MySQL" - 5
> symbols). But when I do this using ODBC from my application, it doesn't
> work right. Can anyone suggest me a solution?
The problem was solved.

ODBC access errors

I have just rebuilt the boot drive of a PC used as a
server using MSDE 2000. It is running under Windows 2000
SP4.
Since the rebuild, anyone with less that administrator
priveliges on the local machine have been denied access to
the SQL server.
In the ODBC server DSN configration settings, attempting
to login produces SQL Server errors 11004 and 6, while
attempting to run the application attempting to access the
server gives errorcode 61440.
Any suggestions as to the cause of this problem will be
gratefully received.
Many thanks in advance.
Ian CoatesSorted. It appears the application makes use of the Guest account which was
disabled. Renabling it sorted the problem.
Ian Coates
"Ian Coates" <anonymous@.discussions.microsoft.com> wrote in message
news:433a01c47325$57138de0$a301280a@.phx.gbl...
> I have just rebuilt the boot drive of a PC used as a
> server using MSDE 2000. It is running under Windows 2000
> SP4.
> Since the rebuild, anyone with less that administrator
> priveliges on the local machine have been denied access to
> the SQL server.
> In the ODBC server DSN configration settings, attempting
> to login produces SQL Server errors 11004 and 6, while
> attempting to run the application attempting to access the
> server gives errorcode 61440.
> Any suggestions as to the cause of this problem will be
> gratefully received.
> Many thanks in advance.
> Ian Coates

ODBC access errors

I have just rebuilt the boot drive of a PC used as a
server using MSDE 2000. It is running under Windows 2000
SP4.
Since the rebuild, anyone with less that administrator
priveliges on the local machine have been denied access to
the SQL server.
In the ODBC server DSN configration settings, attempting
to login produces SQL Server errors 11004 and 6, while
attempting to run the application attempting to access the
server gives errorcode 61440.
Any suggestions as to the cause of this problem will be
gratefully received.
Many thanks in advance.
Ian Coates
Sorted. It appears the application makes use of the Guest account which was
disabled. Renabling it sorted the problem.
Ian Coates
"Ian Coates" <anonymous@.discussions.microsoft.com> wrote in message
news:433a01c47325$57138de0$a301280a@.phx.gbl...
> I have just rebuilt the boot drive of a PC used as a
> server using MSDE 2000. It is running under Windows 2000
> SP4.
> Since the rebuild, anyone with less that administrator
> priveliges on the local machine have been denied access to
> the SQL server.
> In the ODBC server DSN configration settings, attempting
> to login produces SQL Server errors 11004 and 6, while
> attempting to run the application attempting to access the
> server gives errorcode 61440.
> Any suggestions as to the cause of this problem will be
> gratefully received.
> Many thanks in advance.
> Ian Coates

Obscure linked server error

Hello,

I've got 2 SQL servers in a test environment - one is 2000 and the other is MSDE and they are seperate machines. I have added the MSDE server as a linked server to my 2000 box by issuing the following command:

EXEC sp_addlinkedserver '192.168.1.108', N'SQL Server'

I can query the database using an openquery in a select statement like so:

select * from openquery([192.168.1.108], 'select * from remote_test.dbo.products')

but when I try a direct query like the following:

select * from [192.168.1.108].remote_test.dbo.products

I get the following error:

An error occurred while executing batch. Error message is: Processing of results from SQL Server failed because of an invalid multipart name "192.168.1.108.remote_test.dbo.products", the current limit of "4" is insufficient.

I can't seem to figure out anything about this error. Anyone have any ideas?

Thanks,

Jeff Balcerzak

What about choosing another name than the IP ;-) ?

Jens K. Suessmeyer.

http://www.sqlserver2005.de
--|||That does work if I specify the server name on my local network. If the production server is not going to be in the local network, would I create an alias to it with the public IP address?|||What about using an entry in the lmhost file to the outside IP?

Jens K. Suessmeyer.

http://www.sqlserver2005.de
|||I actually added an entry in hosts file and created an alias to my public IP to test. I physically moved my test server to a different part of my network so it is not visible to the lan and created a port forward on my router to direct wan traffic on 1433 to the test server. Now when I execute the sp_addlinked server with the server name, it seems to work fine. Thanks for your help.