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 to sql 7 fails

Have 3 XP machines running Office XP Pro. The odbc file
dsn sits in same file as the mdb on a server (on purpose
so it gets backed up regularly). The odbc file connects
to an SQL 7 database on an NT4 machine. All sql driver
versions are 2000.81.9042.00 The authentication is an
sql account - not windows.
Two people can open and connect fine. One gets a login
failure.
If we place the 'failed' user into the domain
administrator account and he logs in at another machine,
he connects fine. If he tries to login from his machine,
still fails.
Two questions:
Why does it fail in either scenario at his machine?
Using sql authentication, how can I let him connect
WITHOUT being a member of the admin group?
Many thanks for any help!
(P.S. Same account works fine through an asp page on the
web without the user having to be in the administrator's
group.)At some level, Named Pipes connections still do make NT calls to see if you
have Windows rights on the other machine.
My suggestion is to either share a network drive or find a network drive
that you don't mind this person connecting to. Make sure they can connect
to that shared drive. Then see how that affects the SQL connection attempt.
Unshare the drive. See what happens to the SQL connection attempt.
Suggestion #2 is to go into SQL Enterprise manager and add a Windows NT
authentication entry for his user account. Maybe that will help.
****************************************
***************************
Andy S.
MCSE NT/2000, MCDBA SQL 7/2000
andymcdba1@.NOMORESPAM.yahoo.com
Please remove NOMORESPAM before replying.
Always keep your antivirus and Microsoft software
up to date with the latest definitions and product updates.
Be suspicious of every email attachment, I will never send
or post anything other than the text of a http:// link nor
post the link directly to a file for downloading.
This posting is provided "as is" with no warranties
and confers no rights.
****************************************
***************************
"Janet" <janetb@.mtn.ncahec.org> wrote in message
news:27f501c3e104$cfd509b0$a501280a@.phx.gbl...

quote:

---

> Have 3 XP machines running Office XP Pro. The odbc file
> dsn sits in same file as the mdb on a server (on purpose
> so it gets backed up regularly). The odbc file connects
> to an SQL 7 database on an NT4 machine. All sql driver
> versions are 2000.81.9042.00 The authentication is an
> sql account - not windows.
> Two people can open and connect fine. One gets a login
> failure.
> If we place the 'failed' user into the domain
> administrator account and he logs in at another machine,
> he connects fine. If he tries to login from his machine,
> still fails.
> Two questions:
> Why does it fail in either scenario at his machine?
> Using sql authentication, how can I let him connect
> WITHOUT being a member of the admin group?
> Many thanks for any help!
> (P.S. Same account works fine through an asp page on the
> web without the user having to be in the administrator's
> group.)
>

---

|||Andy,
Many thanks for the reply.
I know this isn't the popular thinking, but I had set up
sql to take sql authentication only for security
purposes. That way, if someone compromises the network
he/she couldn't by default get to sql data and;
conversly, if someone compromises sql he/she couldn't by
default get to network files.
But, the only way I could get this guy connected was to
use Windows Authentication on a group, put him in it, and
then everything worked fine. I think it's because our pc
machines are XP and the server is still NT/sql7. (The
servers will be updated to 2003 soon with Active
Directory, so maybe this will "all go away".) So, by
default and no matter what you specify, authentication is
by Windows, not sql.
Again, thanks for your reply. If I continue to have
problems after the upgrade, I will be sure to try your
suggestion.
Janet

quote:

---

>--Original Message--
>At some level, Named Pipes connections still do make NT

---

calls to see if you

quote:

---

>have Windows rights on the other machine.
>My suggestion is to either share a network drive or find

---

a network drive

quote:

---

>that you don't mind this person connecting to. Make

---

sure they can connect

quote:

---

>to that shared drive. Then see how that affects the SQL

---

connection attempt.

quote:

---

>Unshare the drive. See what happens to the SQL

---

connection attempt.

quote:

---

>Suggestion #2 is to go into SQL Enterprise manager and

---

add a Windows NT

quote:

---

>authentication entry for his user account. Maybe that

---

will help.

quote:

---

>--
> ****************************************
*****************

---

**********

quote:

---

>Andy S.
>MCSE NT/2000, MCDBA SQL 7/2000
>andymcdba1@.NOMORESPAM.yahoo.com
>Please remove NOMORESPAM before replying.
>Always keep your antivirus and Microsoft software
>up to date with the latest definitions and product

---

updates.

quote:

---

>Be suspicious of every email attachment, I will never

---

send

quote:

---

>or post anything other than the text of a http:// link

---

nor

quote:

---

>post the link directly to a file for downloading.
>This posting is provided "as is" with no warranties
>and confers no rights.
> ****************************************
*****************

---

**********

quote:

---

>"Janet" <janetb@.mtn.ncahec.org> wrote in message
>news:27f501c3e104$cfd509b0$a501280a@.phx.gbl...
file[QUOTE]
purpose[QUOTE]
connects[QUOTE]
machine,[QUOTE]
machine,[QUOTE]
the[QUOTE]
administrator's[QUOTE]
>
>.
>

---

|||Unfortunately, SQL runs in mixed mode when it SQL security is used. If
someone compromises the administrative NT account, they'll get into Windows
and SQL. In that sense Windows NT authentication is secure.
To really secure your SQL server from a Windows perspective, always password
the SA account, consider restricting rights on xp_cmdshell (that procedure
in the master database grants DOS level access to administrators) and try
putting a proxy account for non-admin users for SQL Server agent.
The authentication models still get frustrating for me. I can't stand the
fact that when you restore a database to a separate server, the logins and
users can get out of sync requiring the procedure sp_change_users_login
auto_fix, user_id. (try restoring a database on a separate server), then
add a login with the user name of a user in the database. That is always a
minor annoyance.
****************************************
***************************
Andy S.
MCSE NT/2000, MCDBA SQL 7/2000
andymcdba1@.NOMORESPAM.yahoo.com
Please remove NOMORESPAM before replying.
Always keep your antivirus and Microsoft software
up to date with the latest definitions and product updates.
Be suspicious of every email attachment, I will never send
or post anything other than the text of a http:// link nor
post the link directly to a file for downloading.
This posting is provided "as is" with no warranties
and confers no rights.
****************************************
***************************
"Janet" <janetb@.mtn.ncahec.org> wrote in message
news:34f501c3e1d8$33367ba0$a601280a@.phx.gbl...[QUOTE]
> Andy,
> Many thanks for the reply.
> I know this isn't the popular thinking, but I had set up
> sql to take sql authentication only for security
> purposes. That way, if someone compromises the network
> he/she couldn't by default get to sql data and;
> conversly, if someone compromises sql he/she couldn't by
> default get to network files.
> But, the only way I could get this guy connected was to
> use Windows Authentication on a group, put him in it, and
> then everything worked fine. I think it's because our pc
> machines are XP and the server is still NT/sql7. (The
> servers will be updated to 2003 soon with Active
> Directory, so maybe this will "all go away".) So, by
> default and no matter what you specify, authentication is
> by Windows, not sql.
> Again, thanks for your reply. If I continue to have
> problems after the upgrade, I will be sure to try your
> suggestion.
> Janet
>
> calls to see if you
> a network drive
> sure they can connect
> connection attempt.
> connection attempt.
> add a Windows NT
> will help.
> **********
> updates.
> send
> nor
> **********
> file
> purpose
> connects
> machine,
> machine,
> the
> administrator's

ODBC Access Driver error in Vista

I am migrating my development environment from XP Pro to Vista, and my website is now serving up the following error:

Microsoft OLE DB Provider for ODBC Drivers error '80004005'

[Microsoft][ODBC Microsoft Access Driver] Disk or network error.

The code in question is as follows:

set dbConn = Server.CreateObject("ADODB.Connection")
szPath=Server.MapPath("http://../")
szProvider="Driver=Microsoft Access Driver (*.mdb); DBQ=" & szPath
szProvider=szProvider & "\database\" & szDir & "\" & szDB & ".mdb;"
if bDebug then fpDebug.WriteLine("szProvider: " & szProvider)
dbConn.Open szProvider

The error happens on the last line where I try to open the connection. I've tried also using a dbConn.Provider="Microsoft.Jet.OLEDB.4.0" line, to no avail. The item that is passed to the Open command is

Driver=Microsoft Access Driver (*.mdb); DBQ=C:\bobstuff\database\demo\HMGA.mdb;

I'm not familiar enough with DNS and IIS to figure this out. Any suggestions -- other than porting over to SQL and .NET? You don't buy a Ferrari when you only drive in a 30 MPH town.

I'm having a similar problem. I checked my installed drivers and noticed I don't have a standard MS ODBC driver. You might want to make sure you have one. Control Panel --> Administrative Tools --> Data Sources --> Drivers Tab. MDAC doesn't seem to install on my Win Vista (x64) machine so I'm not sure where to go from here.

|||Does anyone have a solution to this issue. I have given IISUser full permissions to the Access file in the directory. I have checked the read permissions for IISUser and actually have given everyone read to the directory and the file in question. I can open the file in MS Access on my computer and update and change information in it. The same code works fine on my XP SP2 machine. I am at a loss.|||I am having exactly the same problem today... Vista ultimate, was fine on xp|||This article worked for me.

http://mikeplate.wordpress.com/2006/11/24/running-legacy-asp-scripts-on-vista-and-iis-70/|||

Thanks

This worked for me. The MS article at the bottom of the blog did not.

|||You beautiful geeks!!! I have spent hours talking to MS Tech Support, and they wanted to charge me $99 for email support, or $245 for phone support as this was a "pro-level" problem. Yes, I plan to convert over to .NET, but as a one guy development team who has over 50K lines of code, I don't want to do it right now. MSFT has a KB article that says the same thing (926939), but it uses command line instead of the GUI. Thanks for giving me a solution.

ODBC Access Driver error in Vista

I am migrating my development environment from XP Pro to Vista, and my website is now serving up the following error:

Microsoft OLE DB Provider for ODBC Drivers error '80004005'

[Microsoft][ODBC Microsoft Access Driver] Disk or network error.

The code in question is as follows:

set dbConn = Server.CreateObject("ADODB.Connection")
szPath=Server.MapPath("http://../")
szProvider="Driver=Microsoft Access Driver (*.mdb); DBQ=" & szPath
szProvider=szProvider & "\database\" & szDir & "\" & szDB & ".mdb;"
if bDebug then fpDebug.WriteLine("szProvider: " & szProvider)
dbConn.Open szProvider

The error happens on the last line where I try to open the connection. I've tried also using a dbConn.Provider="Microsoft.Jet.OLEDB.4.0" line, to no avail. The item that is passed to the Open command is

Driver=Microsoft Access Driver (*.mdb); DBQ=C:\bobstuff\database\demo\HMGA.mdb;

I'm not familiar enough with DNS and IIS to figure this out. Any suggestions -- other than porting over to SQL and .NET? You don't buy a Ferrari when you only drive in a 30 MPH town.

I'm having a similar problem. I checked my installed drivers and noticed I don't have a standard MS ODBC driver. You might want to make sure you have one. Control Panel --> Administrative Tools --> Data Sources --> Drivers Tab. MDAC doesn't seem to install on my Win Vista (x64) machine so I'm not sure where to go from here.

|||Does anyone have a solution to this issue. I have given IISUser full permissions to the Access file in the directory. I have checked the read permissions for IISUser and actually have given everyone read to the directory and the file in question. I can open the file in MS Access on my computer and update and change information in it. The same code works fine on my XP SP2 machine. I am at a loss.|||I am having exactly the same problem today... Vista ultimate, was fine on xp|||This article worked for me.

http://mikeplate.wordpress.com/2006/11/24/running-legacy-asp-scripts-on-vista-and-iis-70/|||

Thanks

This worked for me. The MS article at the bottom of the blog did not.

|||You beautiful geeks!!! I have spent hours talking to MS Tech Support, and they wanted to charge me $99 for email support, or $245 for phone support as this was a "pro-level" problem. Yes, I plan to convert over to .NET, but as a one guy development team who has over 50K lines of code, I don't want to do it right now. MSFT has a KB article that says the same thing (926939), but it uses command line instead of the GUI. Thanks for giving me a solution.

ODBC Access Driver error in Vista

I am migrating my development environment from XP Pro to Vista, and my website is now serving up the following error:

Microsoft OLE DB Provider for ODBC Drivers error '80004005'

[Microsoft][ODBC Microsoft Access Driver] Disk or network error.

The code in question is as follows:

set dbConn = Server.CreateObject("ADODB.Connection")
szPath=Server.MapPath("http://../")
szProvider="Driver=Microsoft Access Driver (*.mdb); DBQ=" & szPath
szProvider=szProvider & "\database\" & szDir & "\" & szDB & ".mdb;"
if bDebug then fpDebug.WriteLine("szProvider: " & szProvider)
dbConn.Open szProvider

The error happens on the last line where I try to open the connection. I've tried also using a dbConn.Provider="Microsoft.Jet.OLEDB.4.0" line, to no avail. The item that is passed to the Open command is

Driver=Microsoft Access Driver (*.mdb); DBQ=C:\bobstuff\database\demo\HMGA.mdb;

I'm not familiar enough with DNS and IIS to figure this out. Any suggestions -- other than porting over to SQL and .NET? You don't buy a Ferrari when you only drive in a 30 MPH town.

I'm having a similar problem. I checked my installed drivers and noticed I don't have a standard MS ODBC driver. You might want to make sure you have one. Control Panel --> Administrative Tools --> Data Sources --> Drivers Tab. MDAC doesn't seem to install on my Win Vista (x64) machine so I'm not sure where to go from here.

|||Does anyone have a solution to this issue. I have given IISUser full permissions to the Access file in the directory. I have checked the read permissions for IISUser and actually have given everyone read to the directory and the file in question. I can open the file in MS Access on my computer and update and change information in it. The same code works fine on my XP SP2 machine. I am at a loss.|||I am having exactly the same problem today... Vista ultimate, was fine on xp|||This article worked for me.

http://mikeplate.wordpress.com/2006/11/24/running-legacy-asp-scripts-on-vista-and-iis-70/|||

Thanks

This worked for me. The MS article at the bottom of the blog did not.

|||You beautiful geeks!!! I have spent hours talking to MS Tech Support, and they wanted to charge me $99 for email support, or $245 for phone support as this was a "pro-level" problem. Yes, I plan to convert over to .NET, but as a one guy development team who has over 50K lines of code, I don't want to do it right now. MSFT has a KB article that says the same thing (926939), but it uses command line instead of the GUI. Thanks for giving me a solution.

Obtaining SQL RSS Developer Addition

I want to install SQL Reporting Services on my laptop which has Windows XP
Pro, SQL 2000 Dev. Edition, and Visual Studio .NET 2003.
Where can I download or obtain the install file for SQL Reporting Services
Developer Edition?
- MaxI tried the same question a while ago with no reply out here.
No I bought msdn pro subscription to get visual studio and here I can
download rep s dev. edition as well.
You should think that you could get it for free if you have sql 2000 dev
edition, though...
"Max Tyack" <MaxTyack@.discussions.microsoft.com> wrote in message
news:89C903A1-E927-4F26-93B0-6D8C63CEFDF5@.microsoft.com...
> I want to install SQL Reporting Services on my laptop which has Windows XP
> Pro, SQL 2000 Dev. Edition, and Visual Studio .NET 2003.
> Where can I download or obtain the install file for SQL Reporting Services
> Developer Edition?
> - Max|||What are you trying to achieve Max?, the Reporting Services server-part does
not run on MSDE you can't install the reports-database on MSDE and it also
needs IIS to host the reports website.
Ed
"Max Tyack" <MaxTyack@.discussions.microsoft.com> wrote in message
news:89C903A1-E927-4F26-93B0-6D8C63CEFDF5@.microsoft.com...
>I want to install SQL Reporting Services on my laptop which has Windows XP
> Pro, SQL 2000 Dev. Edition, and Visual Studio .NET 2003.
> Where can I download or obtain the install file for SQL Reporting Services
> Developer Edition?
> - Max|||But you have different versions of rep s as welle as different versions of
sql server:
developers ediition
standard edition
entreprise edition
dev ed is much cheaper and can be used for dev purposes.
"Ed Richard" <Ed_XXX_@.wss-ed_REMOVE_.nl> wrote in message
news:%23mIKQ8tgFHA.3788@.tk2msftngp13.phx.gbl...
> What are you trying to achieve Max?, the Reporting Services server-part
does
> not run on MSDE you can't install the reports-database on MSDE and it also
> needs IIS to host the reports website.
> Ed
> "Max Tyack" <MaxTyack@.discussions.microsoft.com> wrote in message
> news:89C903A1-E927-4F26-93B0-6D8C63CEFDF5@.microsoft.com...
> >I want to install SQL Reporting Services on my laptop which has Windows
XP
> > Pro, SQL 2000 Dev. Edition, and Visual Studio .NET 2003.
> >
> > Where can I download or obtain the install file for SQL Reporting
Services
> > Developer Edition?
> >
> > - Max
>|||I got lucky and found someone who had the setup file for SQL RSS Dev.
Edition. I am using it on SQL Dev Edition, not SQL MSDE (Desktop Edition).
And running iis on WinXP as well. All are working fine on my XP machine now.
"Michael Vardinghus" wrote:
> But you have different versions of rep s as welle as different versions of
> sql server:
> developers ediition
> standard edition
> entreprise edition
> dev ed is much cheaper and can be used for dev purposes.
> "Ed Richard" <Ed_XXX_@.wss-ed_REMOVE_.nl> wrote in message
> news:%23mIKQ8tgFHA.3788@.tk2msftngp13.phx.gbl...
> > What are you trying to achieve Max?, the Reporting Services server-part
> does
> > not run on MSDE you can't install the reports-database on MSDE and it also
> > needs IIS to host the reports website.
> >
> > Ed
> >
> > "Max Tyack" <MaxTyack@.discussions.microsoft.com> wrote in message
> > news:89C903A1-E927-4F26-93B0-6D8C63CEFDF5@.microsoft.com...
> > >I want to install SQL Reporting Services on my laptop which has Windows
> XP
> > > Pro, SQL 2000 Dev. Edition, and Visual Studio .NET 2003.
> > >
> > > Where can I download or obtain the install file for SQL Reporting
> Services
> > > Developer Edition?
> > >
> > > - Max
> >
> >
>
>|||You can order a CD here:
http://www.microsoft.com/sql/reporting/howtobuy/retailfulfillment.mspx
Ed
"Max Tyack" <MaxTyack@.discussions.microsoft.com> wrote in message
news:89C903A1-E927-4F26-93B0-6D8C63CEFDF5@.microsoft.com...
>I want to install SQL Reporting Services on my laptop which has Windows XP
> Pro, SQL 2000 Dev. Edition, and Visual Studio .NET 2003.
> Where can I download or obtain the install file for SQL Reporting Services
> Developer Edition?
> - Max|||Hi,
This discussion is probably closed, but maybe you can still help me.
Could anyone ever find a link to download the Reporting Services Developer
Edition?
I have Reporting Services Evaluation Edition on my XP machine, but I wonder
what will happen when the 120 day trial duration expires and therefore wanna
install the developer edition.
Thanks,
Gul
"Ed Richard" wrote:
> You can order a CD here:
> http://www.microsoft.com/sql/reporting/howtobuy/retailfulfillment.mspx
> Ed
> "Max Tyack" <MaxTyack@.discussions.microsoft.com> wrote in message
> news:89C903A1-E927-4F26-93B0-6D8C63CEFDF5@.microsoft.com...
> >I want to install SQL Reporting Services on my laptop which has Windows XP
> > Pro, SQL 2000 Dev. Edition, and Visual Studio .NET 2003.
> >
> > Where can I download or obtain the install file for SQL Reporting Services
> > Developer Edition?
> >
> > - Max
>
>