MSDE timeout with wireless network enabled

Hi,
I have local MSDE installed on my laptop. When I am physically
connected to our network I can connect through my ODBC application
without issue.
However, when I have wireless networking enabled the first time I try to
connect I get a timeout. But, I'm able to immediately connect after
that initial timeout without a problem. This only occurs when wireless
networking is enabled, as the timeout does not occur with a physical LAN
connection.
I have the following installation:
MDAC SDK 2.8
MSDE 8.00.761
XP SP2
VS.NET 7.1
Any help would be greatly appreciated.
Thanks,
John
I am having a similar issue using SQL querries over a wireless connection.
Is there a technology that is better suited for wireless? Say .net?
Thanks in advance...
"JohnD" wrote:

> Hi,
> I have local MSDE installed on my laptop. When I am physically
> connected to our network I can connect through my ODBC application
> without issue.
> However, when I have wireless networking enabled the first time I try to
> connect I get a timeout. But, I'm able to immediately connect after
> that initial timeout without a problem. This only occurs when wireless
> networking is enabled, as the timeout does not occur with a physical LAN
> connection.
> I have the following installation:
> MDAC SDK 2.8
> MSDE 8.00.761
> XP SP2
> VS.NET 7.1
> Any help would be greatly appreciated.
> Thanks,
> John
>
|||Do you have the same problem if you use an IP address instead of the MSDE
instance name? Perhaps you're having a name resolution problem?
Jim
"Chris James" <Chris James@.discussions.microsoft.com> wrote in message
news:B19527EB-85E1-4DBC-9E51-A8CD463C1A89@.microsoft.com...[vbcol=seagreen]
>I am having a similar issue using SQL querries over a wireless connection.
> Is there a technology that is better suited for wireless? Say .net?
> Thanks in advance...
> "JohnD" wrote:
|||Thanks for the post Jim, Ive tried it using IP and Instance name... The
funny thing is that not all wireless installations have this issue, I have
two sites across the street and down about 1/4 mile. One site with approx
250' between wireless access point and client work fairly reliably, the other
is only 50' apart and they fail all the time. I wonder if its the
application making too many querries and boging down the wireless. Both
sites are using identical equipment as well.
"Jim Young" wrote:

> Do you have the same problem if you use an IP address instead of the MSDE
> instance name? Perhaps you're having a name resolution problem?
> Jim
> "Chris James" <Chris James@.discussions.microsoft.com> wrote in message
> news:B19527EB-85E1-4DBC-9E51-A8CD463C1A89@.microsoft.com...
>
>

MSDE SQL Connection error

I am trying to connect to a remote MSDE SQL database. When I set up the odbc connection I get a connection denied error. The SQL server is on a windows 2003 server. Any ideas are greatly appreciated.
Thanks, LinsLoMSDE won't allow remote connections on Windows 2003 unless you apply MSDE sp3a.

-PatP|||This is currently on the server, but it is still not connecting...|||what are you using to connect? a programming language (c, c++, c#) and are they .net? If you are using .net then i would suggest trying to use the sql connection library instead of the odbc. are you on the same network as the db server? please provide more info on your situation. I can not give an accurate answer with out more information

MSDE sp3a & XP-sp2

My clients are reporting they cannot connect to the msde database using my
application - generic failed to connect message.
My software application installs the MSDE. Their computer is a brand new
machine with XP-sp2 installed. The sp2 is not an upgrade. We have only
seen this phenomena with a machine where we cannot uninstall sp2. On
machines we can, our application can connect. On most (to all) machines
where we install xp-sp2 ourselves there is no problem.
Any ideas?
Check wheter the firewall of the XPs opened up the port to connect to the
msde, if not open up.
For a fast try deactivate the firewallfor checking, if its working open up
dedicated ports.
HTH, Jens Smeyer
http://www.sqlserver2005.de
"Robert A. DiFrancesco" <bob.difrancesco@.comcash.com> schrieb im Newsbeitrag
news:u6h0w7TQFHA.3596@.TK2MSFTNGP15.phx.gbl...
> My clients are reporting they cannot connect to the msde database using my
> application - generic failed to connect message.
> My software application installs the MSDE. Their computer is a brand new
> machine with XP-sp2 installed. The sp2 is not an upgrade. We have only
> seen this phenomena with a machine where we cannot uninstall sp2. On
> machines we can, our application can connect. On most (to all) machines
> where we install xp-sp2 ourselves there is no problem.
> Any ideas?
>
|||Did all that.
What could be different about a machine pre-loaded with xp-sp2?
"Jens Smeyer" <Jens@.Remove_this_For_Contacting.sqlserver2005.de> wrote in
message news:%23Pbrs%23TQFHA.1172@.TK2MSFTNGP12.phx.gbl...
> Check wheter the firewall of the XPs opened up the port to connect to the
> msde, if not open up.
> For a fast try deactivate the firewallfor checking, if its working open up
> dedicated ports.
>
> HTH, Jens Smeyer
> --
> http://www.sqlserver2005.de
> --
>
> "Robert A. DiFrancesco" <bob.difrancesco@.comcash.com> schrieb im
> Newsbeitrag news:u6h0w7TQFHA.3596@.TK2MSFTNGP15.phx.gbl...
>

MSDE sp3a & XP-sp2

My clients are reporting they cannot connect to the msde database using my
application - generic failed to connect message.
My software application installs the MSDE. Their computer is a brand new
machine with XP-sp2 installed. The sp2 is not an upgrade. We have only
seen this phenomena with a machine where we cannot uninstall sp2. On
machines we can, our application can connect. On most (to all) machines
where we install xp-sp2 ourselves there is no problem.
Any ideas?Check wheter the firewall of the XPs opened up the port to connect to the
msde, if not open up.
For a fast try deactivate the firewallfor checking, if its working open up
dedicated ports.
HTH, Jens Smeyer
http://www.sqlserver2005.de
--
"Robert A. DiFrancesco" <bob.difrancesco@.comcash.com> schrieb im Newsbeitrag
news:u6h0w7TQFHA.3596@.TK2MSFTNGP15.phx.gbl...
> My clients are reporting they cannot connect to the msde database using my
> application - generic failed to connect message.
> My software application installs the MSDE. Their computer is a brand new
> machine with XP-sp2 installed. The sp2 is not an upgrade. We have only
> seen this phenomena with a machine where we cannot uninstall sp2. On
> machines we can, our application can connect. On most (to all) machines
> where we install xp-sp2 ourselves there is no problem.
> Any ideas?
>|||Did all that.
What could be different about a machine pre-loaded with xp-sp2'
"Jens Smeyer" <Jens@.Remove_this_For_Contacting.sqlserver2005.de> wrote in
message news:%23Pbrs%23TQFHA.1172@.TK2MSFTNGP12.phx.gbl...
> Check wheter the firewall of the XPs opened up the port to connect to the
> msde, if not open up.
> For a fast try deactivate the firewallfor checking, if its working open up
> dedicated ports.
>
> HTH, Jens Smeyer
> --
> http://www.sqlserver2005.de
> --
>
> "Robert A. DiFrancesco" <bob.difrancesco@.comcash.com> schrieb im
> Newsbeitrag news:u6h0w7TQFHA.3596@.TK2MSFTNGP15.phx.gbl...
>

MSDE Sp3 client connection

Hi, I am trying to connect to a MSDE Sp3 database remotely, however I always
got "server does not exist or access denied". I was told that the problem is
from sp3.
Any idea how can I solved the problem'
Met vriendelijke groet,
Guoqi Zheng
Tel: +31 (0) 23 5343545
http://www.meetholland.comMSDE has limitations on how many workloads it can accept, not what kind of
connections it can take. One question though, what kind of OS is MSDE
running on? Windows 98 does not provide Named Pipes support, so you may
have to change your connection protocol to TCP/IP sockets. Also TCP/IP
sockets runs on port 1433 by default, if there is a hardware or software
firewall blocking that port, you will be in trouble.
The biggest troubleshooting step I can suggest is to just try and map
another shared network resource from that computer -- printer, shared drive,
ipc$ (if available), whatever. Do you have any problems with that? Can you
connect after that?
Good luck. Hope that helps.
****************************************
***************************
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.
****************************************
***************************
"Guoqi Zheng" <no@.sorry.com> wrote in message
news:%23uJUoH9zDHA.2568@.TK2MSFTNGP09.phx.gbl...

quote:

---

> Hi, I am trying to connect to a MSDE Sp3 database remotely, however I

---

always

quote:

---

> got "server does not exist or access denied". I was told that the problem

---

is

quote:

---

> from sp3.
> Any idea how can I solved the problem'
> --
> Met vriendelijke groet,
> Guoqi Zheng
> Tel: +31 (0) 23 5343545
> http://www.meetholland.com
>

---

|||Thanks a lot for your quick reply. It is running under MS 2003 server web
edition.
The server is a dedicated server, I can not put any shared driver there.
What should I do'
Met vriendelijke groet,
Guoqi Zheng
Tel: +31 (0) 23 5343545
http://www.meetholland.com
"Andy Svendsen" <andymcdba1@.NOMORESPAM.yahoo.com> д?
:uZPzzN9zDHA.2180@.TK2MSFTNGP12.phx.gbl...

quote:

---

> MSDE has limitations on how many workloads it can accept, not what kind of
> connections it can take. One question though, what kind of OS is MSDE
> running on? Windows 98 does not provide Named Pipes support, so you may
> have to change your connection protocol to TCP/IP sockets. Also TCP/IP
> sockets runs on port 1433 by default, if there is a hardware or software
> firewall blocking that port, you will be in trouble.
> The biggest troubleshooting step I can suggest is to just try and map
> another shared network resource from that computer -- printer, shared

---

drive,

quote:

---

> ipc$ (if available), whatever. Do you have any problems with that? Can

---

you

quote:

---

> connect after that?
> Good luck. Hope that helps.
> --
> ****************************************
***************************
> 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.
> ****************************************
***************************
> "Guoqi Zheng" <no@.sorry.com> wrote in message
> news:%23uJUoH9zDHA.2568@.TK2MSFTNGP09.phx.gbl...
> always
m[QUOTE]
> is
>

---

|||Check the firewall logs with the network admin.
Verify that your client application is sending TCP traffic not SMB. (Named
Pipes)
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

msde security - windows mode?

Hi,
I want to be able to use SQL authentication on my local MSDE 2000 , I've
added a user using sp_addlogin, and try to connect using it, however it
always gives me 'not associated with a trusted SQL server connection'. Is
there any way I can force it to go to SQL mode without reinstalling it?
Thanks> I want to be able to use SQL authentication on my local MSDE 2000 , I've
> added a user using sp_addlogin, and try to connect using it, however it
> always gives me 'not associated with a trusted SQL server connection'. Is
> there any way I can force it to go to SQL mode without reinstalling it?
Yes - check the article at http://support.microsoft.com/kb/285097/EN-US/.
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com|||> I want to be able to use SQL authentication on my local MSDE 2000 , I've
> added a user using sp_addlogin, and try to connect using it, however it
> always gives me 'not associated with a trusted SQL server connection'. Is
> there any way I can force it to go to SQL mode without reinstalling it?
Look at my answer in .security group.
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com

MSDE remote connection on Windows Home - Windows Authentication

I installed an MSDE on a PC running Windows Home Edition. I would like
to connect to this MSDE installation from an oher PC using Windows
Authentication.
What do I have to do (add account on Home Edition)
hi,
xavierdaull@.gmail.com wrote:
> I installed an MSDE on a PC running Windows Home Edition. I would like
> to connect to this MSDE installation from an oher PC using Windows
> Authentication.
> What do I have to do (add account on Home Edition)
without a Domain Controller, thought in a Workgroup environment, usually you
should rely on standard SQL Server authenticated connections for remote
ones, as all the authentication features are resolved and managed by the
Domain Controller it self..
you can however setup a local account to map the remote account of the other
machine... that's to say, on your local PC you have to add another account
with the very same "credentials" of other account(s) present on the remote
PCs...
all this (still) works becouse of the underlying OS gets somehow confused
and a sort of "embezzlement" where 2 differents accounts, YourPC\YourAccount
and OtherPC\YourAccount "share" a kind of uniqueness becouse of netbios
intrusion... a preventive netbios connection, even on a share or using NET
USE can help...
but this is not granted to work in future releases or even OS service
packs...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.18.0 - DbaMgr ver 0.62.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

MSDE Remote Connect strange problem

I'm trying to connect to the SharePoint MSDE database from Windows XP

SP2 machine over Ethernet LAN. I was getting server not found or access

denied, until I enabled TCP/IP via svrnetcn.exe. Now, I'm getting

OK

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.

I just did an netstat -an and I don't see the server listening on 1433.

What am I not doing?

The svrnetcn tool has no effect. I make a change and check the logs,

but nothing happens. What would be causing this?

Did you ever get an answer to this problem? I'm having a similar error on Windows XP SP2 machines that have MDAC 2.8SP1. I have an MS Access front end that links to SQL Server database using ODBC connections. The report will run, but keeps asking for SQL Server login info, then finally I get the same Connection failed error you listed with the exception on the line: SQL Server Error: 10048. However, the report actually finishes with all the data requested.

I have this same Access front end running on other XP machines with SP1 and Windows 2000 machines with MDAC 2.7 SP1. When the report runs on those machines it only asks for SQL Server login info when the program is first connecting to the db.

Any ideas?

|||

Thank you thank you for letting me know about the svrnetcn.exe tool. I have been trying for hours to get a Sharepoint portal going and whilst for the error I had MS KB said enable tcp/ip, it didn't say how to do it for msde. Where did you find out about svrnetcn.exe and are there other useful tools I should know about? I'm ok with osql.

I have seen the error you are getting. It will happen if I'm not using Windows integrated authentication. If I try to connect with osql -U sa -S servername\instancename it doesn't work and gives a server does not exist or access denied. I have to use osql -E -S servername\instancename and it goes in fine.

Hope this helps - even if its a bit late!

Nath

|||

Nathan,

here is the linke which might be useful to you guys

http://www.codeproject.com/database/ConfigureMSDE.asp

Best regards,
Web

sql

MSDE Remote Connect strange problem

I'm trying to connect to the SharePoint MSDE database from Windows XP
SP2 machine over Ethernet LAN. I was getting server not found or access
denied, until I enabled TCP/IP via svrnetcn.exe. Now, I'm getting
OK
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.
I just did an netstat -an and I don't see the server listening on 1433.
What am I not doing?
The svrnetcn tool has no effect. I make a change and check the logs,
but nothing happens. What would be causing this?

Did you ever get an answer to this problem? I'm having a similar error on Windows XP SP2 machines that have MDAC 2.8SP1. I have an MS Access front end that links to SQL Server database using ODBC connections. The report will run, but keeps asking for SQL Server login info, then finally I get the same Connection failed error you listed with the exception on the line: SQL Server Error: 10048. However, the report actually finishes with all the data requested.

I have this same Access front end running on other XP machines with SP1 and Windows 2000 machines with MDAC 2.7 SP1. When the report runs on those machines it only asks for SQL Server login info when the program is first connecting to the db.

Any ideas?

|||

Thank you thank you for letting me know about the svrnetcn.exe tool. I have been trying for hours to get a Sharepoint portal going and whilst for the error I had MS KB said enable tcp/ip, it didn't say how to do it for msde. Where did you find out about svrnetcn.exe and are there other useful tools I should know about? I'm ok with osql.

I have seen the error you are getting. It will happen if I'm not using Windows integrated authentication. If I try to connect with osql -U sa -S servername\instancename it doesn't work and gives a server does not exist or access denied. I have to use osql -E -S servername\instancename and it goes in fine.

Hope this helps - even if its a bit late!

Nath

|||

Nathan,

here is the linke which might be useful to you guys

http://www.codeproject.com/database/ConfigureMSDE.asp

Best regards,
Web

MSDE Remote Connect strange problem

I'm trying to connect to the SharePoint MSDE database from Windows XP
SP2 machine over Ethernet LAN. I was getting server not found or access
denied, until I enabled TCP/IP via svrnetcn.exe. Now, I'm getting
OK
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.
I just did an netstat -an and I don't see the server listening on 1433.
What am I not doing?
The svrnetcn tool has no effect. I make a change and check the logs,
but nothing happens. What would be causing this?

Did you ever get an answer to this problem? I'm having a similar error on Windows XP SP2 machines that have MDAC 2.8SP1. I have an MS Access front end that links to SQL Server database using ODBC connections. The report will run, but keeps asking for SQL Server login info, then finally I get the same Connection failed error you listed with the exception on the line: SQL Server Error: 10048. However, the report actually finishes with all the data requested.

I have this same Access front end running on other XP machines with SP1 and Windows 2000 machines with MDAC 2.7 SP1. When the report runs on those machines it only asks for SQL Server login info when the program is first connecting to the db.

Any ideas?

|||

Thank you thank you for letting me know about the svrnetcn.exe tool. I have been trying for hours to get a Sharepoint portal going and whilst for the error I had MS KB said enable tcp/ip, it didn't say how to do it for msde. Where did you find out about svrnetcn.exe and are there other useful tools I should know about? I'm ok with osql.

I have seen the error you are getting. It will happen if I'm not using Windows integrated authentication. If I try to connect with osql -U sa -S servername\instancename it doesn't work and gives a server does not exist or access denied. I have to use osql -E -S servername\instancename and it goes in fine.

Hope this helps - even if its a bit late!

Nath

|||

Nathan,

here is the linke which might be useful to you guys

http://www.codeproject.com/database/ConfigureMSDE.asp

Best regards,
Web

MSDE question

Hi all
I want to know that can I use MSDE as server that other clients connect to
it'
If yes,what limitations does it have'
thanksperspolis wrote:
> Hi all
> I want to know that can I use MSDE as server that other clients
> connect to it'
> If yes,what limitations does it have'
> thanks
http://msdn2.microsoft.com/en-us/library/ms165672.aspx
http://www.microsoft.com/sql/msde/p...o/features.mspx
David Gugick
Quest Software|||Clients can connect to MSDE.
For the differences between SQL Server editions refer to the documentation
below:
http://www.microsoft.com/sql/techin...ing/ChoosEd.doc
http://www.microsoft.com/sql/evalua...ew/default.mspx
One of the main limitations on MSDE apart from the 2GB per Database size
limitation is the query governor. MSDE's query governor kicks in at above 8
concurrent operations. See
http://msdn.microsoft.com/library/d... />
_0ciq.asp.
Below is a quote from Greg Low on the MSDE query governor that was recentlty
posted to the that SQLDownUnder mailing List
~~~ Start Quote ~~~
When additional workload is detected, they don't queue the extra operations.
What occurs is a delay is inserted in each logical page read or write on the
data files (ie log files are not affected). The more you exceed 8, the more
delay is inserted on each page. The effect that it ends up having depends on
how much data you are reading or writing. Small delays (milliseconds) quickl
y
get multiplied up into large delays when you are doing scans of large
(relative to the MSDE) tables.
~~ End Quote ~~
- Peter Ward
WARDY IT Solutions
"perspolis" wrote:

> Hi all
> I want to know that can I use MSDE as server that other clients connect to
> it'
> If yes,what limitations does it have'
> thanks
>
>

MSDE over TCP/IP

I've got a SQL Server Desktop Engine (version 8.00.2039 - SP4) installation
running our SharePoint site. I now need to connect to this database remotely
via TCP/IP, but can't get it to enable the protocol.
The log file always just says:
2007-12-11 12:13:46.39 server Using 'SSNETLIB.DLL' version '8.0.2039'.
2007-12-11 12:13:46.39 server SQL server listening on Shared Memory.
I've tried all the suggestions I've heard on the internet. What I've tried:
Install the latest MSDE Service Pack (SP4)
Use SVRNETCN.exe to enable the TCP/IP Protocol
Enable TCP/IP, Set to Port 0, Restart Service, Set to Port 1433, Restart
Service.
I've hard reset the machine, I've installed all the latest service packs on
this machine. I've disabled the firewall. I've tried ports other than 1433.
I've tried enabling Named Pipes & NWLink at various times as well. No matter
what I do, the log still shows it listening only on shared memory.
Any assistance would be greatly appreciated as I'm completely stumped.
Andrew Faust
http://www.andrewfaust.com
=?Utf-8?B?QW5kcmV3IEZhdXN0?= <andrew [at] andrewfaust.com> wrote in
news:23AE3B12-517E-4970-8F7D-3E094BE07541@.microsoft.com:

> I've got a SQL Server Desktop Engine (version 8.00.2039 - SP4)
> installation running our SharePoint site. I now need to connect to
> this database remotely via TCP/IP, but can't get it to enable the
> protocol.
> The log file always just says:
> 2007-12-11 12:13:46.39 server Using 'SSNETLIB.DLL' version
> '8.0.2039'. 2007-12-11 12:13:46.39 server SQL server listening on
> Shared Memory.
> I've tried all the suggestions I've heard on the internet. What I've
> tried:
> Install the latest MSDE Service Pack (SP4)
> Use SVRNETCN.exe to enable the TCP/IP Protocol
> Enable TCP/IP, Set to Port 0, Restart Service, Set to Port 1433,
> Restart Service.
> I've hard reset the machine, I've installed all the latest service
> packs on this machine. I've disabled the firewall. I've tried ports
> other than 1433. I've tried enabling Named Pipes & NWLink at various
> times as well. No matter what I do, the log still shows it listening
> only on shared memory.
> Any assistance would be greatly appreciated as I'm completely stumped.
If you see no effects at all from using svrnetcn.exe, perhaps you have got
multiple instances installed. Drop down the "Instances on this server"
combo at the top of the General tab of the svrnetcn.exe dialog (similarly
the Server combo at the top of the SQL Server Service Manager dialog).
|||Thanks for the response.
Unfortunately, that's not the problem. There is only 1 instance installed on
this server. I forgot to mention this before and don't know if it makes a
difference, but this is a named instance. It's called DOCMGR\SHAREPOINT. It's
also running on Windows Server 2003 with all the latest service packs
installed.
Andrew Faust
http://www.andrewfaust.com
"Chris.Cheney" wrote:

> =?Utf-8?B?QW5kcmV3IEZhdXN0?= <andrew [at] andrewfaust.com> wrote in
> news:23AE3B12-517E-4970-8F7D-3E094BE07541@.microsoft.com:
>
> If you see no effects at all from using svrnetcn.exe, perhaps you have got
> multiple instances installed. Drop down the "Instances on this server"
> combo at the top of the General tab of the svrnetcn.exe dialog (similarly
> the Server combo at the top of the SQL Server Service Manager dialog).
>
|||=?Utf-8?B?QW5kcmV3IEZhdXN0?= <andrew [at] andrewfaust.com> wrote in
news:B66EA507-0750-48F2-8E5F-F7B8FC60ED9F@.microsoft.com:

> Thanks for the response.
> Unfortunately, that's not the problem. There is only 1 instance
> installed on this server. I forgot to mention this before and don't
> know if it makes a difference, but this is a named instance. It's
> called DOCMGR\SHAREPOINT. It's also running on Windows Server 2003
> with all the latest service packs installed.
>
Well, it was something that was possible, given the symptoms you described.
Sorry, I'm out of further ideas. Good luck!
|||I appreciate the effort. I've finally given up on trying to make it work and
have moved my SharePoint to a full install of SQL Server 2000 and gotten the
functionality I needed.
Andrew Faust
http://www.andrewfaust.com
"Chris.Cheney" wrote:

> =?Utf-8?B?QW5kcmV3IEZhdXN0?= <andrew [at] andrewfaust.com> wrote in
> news:B66EA507-0750-48F2-8E5F-F7B8FC60ED9F@.microsoft.com:
>
> Well, it was something that was possible, given the symptoms you described.
> Sorry, I'm out of further ideas. Good luck!
>

MSDE over firewall

Succesfully created a MSDE 2000 rel A backend on 2003
server. I can connect a MS Access project frontend to it
from an XP client on the same LAN segment. I can connect
the same frontend over the internet to this server when
set out in the firewall's DMZ.
And now for my next trick! When I tuck the MSDE server
back behind the firewall and open up TCP and UDP ports at
1433 and 1434 for both incoming and outgoing traffic, I
cannot connect. I include a filtered log showing traffic
between the Access client on the Internet and the firewall
for detail. It appears that the Netgear firewall passes
packets to the server but it times out in a little less
than a minute... I am looking forward to any ideas that
may move this project forward!
TimeProtocolSrcDstApplication
Message
13:58:28UDP645521434ms-sql-m
[Service access request successful]
13:58:28TCP645532418cas[Access
Policy not found, dropping packet]
13:58:31TCP645532418cas[Access
Policy not found, dropping packet]
13:58:37TCP645532418cas[Access
Policy not found, dropping packet]
13:58:51TCP645582418cas[Access
Policy not found, dropping packet]
13:58:54TCP645582418cas[Access
Policy not found, dropping packet]
13:59:00TCP645582418cas[Access
Policy not found, dropping packet]
13:59:14TCP64564445ms-ds[Access
Policy not found, dropping packet]
13:59:14TCP64565139netbios-ssn
[Access Policy not found, dropping packet]
13:59:17TCP64565139netbios-ssn
[Access Policy not found, dropping packet]
13:59:17TCP64564445ms-ds[Access
Policy not found, dropping packet]
13:59:20UDP645521434ms-sql-m
[Connection timed out.Bytes transferred : 137]
13:59:23TCP64565139netbios-ssn
[Access Policy not found, dropping packet]
13:59:23TCP64564445ms-ds[Access
Policy not found, dropping packet]
From your trace it appears that many more IP ports (than 1433 & 1434) are
being attempted to be used.
I suspect it's failing because of the attempt to do name resolution.
Steve
"Ed Morra" <ed@.orl-inc.com> wrote in message
news:36f801c4297b$6a642240$a601280a@.phx.gbl...
> Succesfully created a MSDE 2000 rel A backend on 2003
> server. I can connect a MS Access project frontend to it
> from an XP client on the same LAN segment. I can connect
> the same frontend over the internet to this server when
> set out in the firewall's DMZ.
> And now for my next trick! When I tuck the MSDE server
> back behind the firewall and open up TCP and UDP ports at
> 1433 and 1434 for both incoming and outgoing traffic, I
> cannot connect. I include a filtered log showing traffic
> between the Access client on the Internet and the firewall
> for detail. It appears that the Netgear firewall passes
> packets to the server but it times out in a little less
> than a minute... I am looking forward to any ideas that
> may move this project forward!
> Time Protocol Src Dst Application
> Message
> 13:58:28 UDP 64552 1434 ms-sql-m
> [Service access request successful]
> 13:58:28 TCP 64553 2418 cas [Access
> Policy not found, dropping packet]
> 13:58:31 TCP 64553 2418 cas [Access
> Policy not found, dropping packet]
> 13:58:37 TCP 64553 2418 cas [Access
> Policy not found, dropping packet]
> 13:58:51 TCP 64558 2418 cas [Access
> Policy not found, dropping packet]
> 13:58:54 TCP 64558 2418 cas [Access
> Policy not found, dropping packet]
> 13:59:00 TCP 64558 2418 cas [Access
> Policy not found, dropping packet]
> 13:59:14 TCP 64564 445 ms-ds [Access
> Policy not found, dropping packet]
> 13:59:14 TCP 64565 139 netbios-ssn
> [Access Policy not found, dropping packet]
> 13:59:17 TCP 64565 139 netbios-ssn
> [Access Policy not found, dropping packet]
> 13:59:17 TCP 64564 445 ms-ds [Access
> Policy not found, dropping packet]
> 13:59:20 UDP 64552 1434 ms-sql-m
> [Connection timed out.Bytes transferred : 137]
> 13:59:23 TCP 64565 139 netbios-ssn
> [Access Policy not found, dropping packet]
> 13:59:23 TCP 64564 445 ms-ds [Access
> Policy not found, dropping packet]
>

MSDE over firewall

Succesfully created a MSDE 2000 rel A backend on 2003
server. I can connect a MS Access project frontend to it
from an XP client on the same LAN segment. I can connect
the same frontend over the internet to this server when
set out in the firewall's DMZ.
And now for my next trick! When I tuck the MSDE server
back behind the firewall and open up TCP and UDP ports at
1433 and 1434 for both incoming and outgoing traffic, I
cannot connect. I include a filtered log showing traffic
between the Access client on the Internet and the firewall
for detail. It appears that the Netgear firewall passes
packets to the server but it times out in a little less
than a minute... I am looking forward to any ideas that
may move this project forward!
Time Protocol Src Dst Application
Message
13:58:28 UDP 64552 1434 ms-sql-m
[Service access request successful]
13:58:28 TCP 64553 2418 cas [Access
Policy not found, dropping packet]
13:58:31 TCP 64553 2418 cas [Access
Policy not found, dropping packet]
13:58:37 TCP 64553 2418 cas [Access
Policy not found, dropping packet]
13:58:51 TCP 64558 2418 cas [Access
Policy not found, dropping packet]
13:58:54 TCP 64558 2418 cas [Access
Policy not found, dropping packet]
13:59:00 TCP 64558 2418 cas [Access
Policy not found, dropping packet]
13:59:14 TCP 64564 445 ms-ds [Access
Policy not found, dropping packet]
13:59:14 TCP 64565 139 netbios-ssn
[Access Policy not found, dropping packet]
13:59:17 TCP 64565 139 netbios-ssn
[Access Policy not found, dropping packet]
13:59:17 TCP 64564 445 ms-ds [Access
Policy not found, dropping packet]
13:59:20 UDP 64552 1434 ms-sql-m
[Connection timed out.Bytes transferred : 137]
13:59:23 TCP 64565 139 netbios-ssn
[Access Policy not found, dropping packet]
13:59:23 TCP 64564 445 ms-ds [Access
Policy not found, dropping packet]From your trace it appears that many more IP ports (than 1433 & 1434) are
being attempted to be used.
I suspect it's failing because of the attempt to do name resolution.
Steve
"Ed Morra" <ed@.orl-inc.com> wrote in message
news:36f801c4297b$6a642240$a601280a@.phx.gbl...
> Succesfully created a MSDE 2000 rel A backend on 2003
> server. I can connect a MS Access project frontend to it
> from an XP client on the same LAN segment. I can connect
> the same frontend over the internet to this server when
> set out in the firewall's DMZ.
> And now for my next trick! When I tuck the MSDE server
> back behind the firewall and open up TCP and UDP ports at
> 1433 and 1434 for both incoming and outgoing traffic, I
> cannot connect. I include a filtered log showing traffic
> between the Access client on the Internet and the firewall
> for detail. It appears that the Netgear firewall passes
> packets to the server but it times out in a little less
> than a minute... I am looking forward to any ideas that
> may move this project forward!
> Time Protocol Src Dst Application
> Message
> 13:58:28 UDP 64552 1434 ms-sql-m
> [Service access request successful]
> 13:58:28 TCP 64553 2418 cas [Access
> Policy not found, dropping packet]
> 13:58:31 TCP 64553 2418 cas [Access
> Policy not found, dropping packet]
> 13:58:37 TCP 64553 2418 cas [Access
> Policy not found, dropping packet]
> 13:58:51 TCP 64558 2418 cas [Access
> Policy not found, dropping packet]
> 13:58:54 TCP 64558 2418 cas [Access
> Policy not found, dropping packet]
> 13:59:00 TCP 64558 2418 cas [Access
> Policy not found, dropping packet]
> 13:59:14 TCP 64564 445 ms-ds [Access
> Policy not found, dropping packet]
> 13:59:14 TCP 64565 139 netbios-ssn
> [Access Policy not found, dropping packet]
> 13:59:17 TCP 64565 139 netbios-ssn
> [Access Policy not found, dropping packet]
> 13:59:17 TCP 64564 445 ms-ds [Access
> Policy not found, dropping packet]
> 13:59:20 UDP 64552 1434 ms-sql-m
> [Connection timed out.Bytes transferred : 137]
> 13:59:23 TCP 64565 139 netbios-ssn
> [Access Policy not found, dropping packet]
> 13:59:23 TCP 64564 445 ms-ds [Access
> Policy not found, dropping packet]
>

MSDE on Windows 2003

I am trying to connect to a MSDE from XP pro SP2, the MSDE is running on Windows 2003 server and the only way I can connect to the MSDE is if I make the network user an Administrator of the Windows 2003 server.
How can I connect to MSDE without making the user an Admin?
Thanks
Peter
hi Peter,
Peter wrote:
> I am trying to connect to a MSDE from XP pro SP2, the MSDE is running
> on Windows 2003 server and the only way I can connect to the MSDE is
> if I make the network user an Administrator of the Windows 2003
> server.
> How can I connect to MSDE without making the user an Admin?
assuming you've no network problem ( :-D ), what kind of authentication are
you using for that?
I guess you are using Windows authentication (trusted connection)... MSDE
installs by default granting local Windows admins membership to the SQL
Server sysadmins role (BUILTIN\Administrator) so that they are "naturally"
granted login to the MSDE instance... if you want your power/limited users
to be granted to, you have to manually create a SQL Server "Windows"
Login(s) or Windows Group login for all your required users...
please have a look at
http://msdn.microsoft.com/library/de...ga-gz_8dri.asp
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||I have added a domain user the the database
EXEC sp_grantlogin 'MyDomain\Peter'
Go
but still user Peter can not connect to the database unless Peter is an
Admin
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3ngpceF1f9poU1@.individual.net...
> hi Peter,
> Peter wrote:
> assuming you've no network problem ( :-D ), what kind of authentication
> are you using for that?
> I guess you are using Windows authentication (trusted connection)... MSDE
> installs by default granting local Windows admins membership to the SQL
> Server sysadmins role (BUILTIN\Administrator) so that they are "naturally"
> granted login to the MSDE instance... if you want your power/limited users
> to be granted to, you have to manually create a SQL Server "Windows"
> Login(s) or Windows Group login for all your required users...
> please have a look at
> http://msdn.microsoft.com/library/de...ga-gz_8dri.asp
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||hi Peter,
Peter wrote:
> I have added a domain user the the database
> EXEC sp_grantlogin 'MyDomain\Peter'
> Go
> but still user Peter can not connect to the database unless Peter is
> an Admin
using and accessing MSDE/SQL Server and it's databases belongs to an
authentication area of the product...
SQL Server uses a sort of 2 phase authentication..
the first one regards login, where someone try to connect to a particular
instance using WinNT (trusted) connections or standard SQL Server
connections (yes, handling both is known as "mixed authentication")
in the second case, standard SQL Server connections, a user id and a
password must be provided, and this information has to be matched against
available SQL Server logins... if a match is found the connecting person has
provided correct information and can log in...
the WinNT (trusted) method does not require this kind of information as the
underlaying OS provides the sid of the against the DC authenticated OS
login, that only need to be matched against a WinNT SQL Server already
granted login or WinNT granted group..
that's to say both kind of authentications need a match in the granted
logins...
Standard SQL Server logins must all be manually added via sp_addlogin system
stored procedure but "sa" "super" login, which is provided by default and
that can not be removed..
as regard WinNT connections, the setup automatically adds a WinNT group
including all WinNT administrators, and this is the reason you can log in
MSDE when logged in Windows as admin...
but all other Windows users/groups have to be manually added via sytem
stored procedure sp_grantlogin
so you have to add you specific WinNT group (say "powerusers") in order to
grant all them permission to log in, or only your specific WinNT account
Domain\Account if you want only him to be granted login...
as regard the second authentication phase, it regards specific access to
each database, and this is done via the sp_grantdbaccess system stored
procedures, that adds an entry in each specific database.dbo.sysusers system
table matching the master.dbo.syslogins system view in the join of the sid
column... this operation generate a database user mapped to a specific
login, allowing him/her to access the desired database with the provided
database role privileges... additional permission can be granted/denied to
each db user, defining the specific security design as required on every db
object and so on, but this is a successive step...
please start reading at
http://msdn.microsoft.com/library/de...ar_da_0n77.asp
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Andrea,
Thanks for all of your help. I ran both cleanup tools. Still did not solve
problem. I would not give up! After many hours of trial and error I
determine the problem was with a corrupted MDAC component. Reinstall MDAC on
XP sp2? Yes there is a way to do that (very simple). Once I reinstalled
MDAC the client application connected and installed just fine. --RS
"Andrea Montanari" wrote:

> hi Peter,
> Peter wrote:
> using and accessing MSDE/SQL Server and it's databases belongs to an
> authentication area of the product...
> SQL Server uses a sort of 2 phase authentication..
> the first one regards login, where someone try to connect to a particular
> instance using WinNT (trusted) connections or standard SQL Server
> connections (yes, handling both is known as "mixed authentication")
> in the second case, standard SQL Server connections, a user id and a
> password must be provided, and this information has to be matched against
> available SQL Server logins... if a match is found the connecting person has
> provided correct information and can log in...
> the WinNT (trusted) method does not require this kind of information as the
> underlaying OS provides the sid of the against the DC authenticated OS
> login, that only need to be matched against a WinNT SQL Server already
> granted login or WinNT granted group..
> that's to say both kind of authentications need a match in the granted
> logins...
> Standard SQL Server logins must all be manually added via sp_addlogin system
> stored procedure but "sa" "super" login, which is provided by default and
> that can not be removed..
> as regard WinNT connections, the setup automatically adds a WinNT group
> including all WinNT administrators, and this is the reason you can log in
> MSDE when logged in Windows as admin...
> but all other Windows users/groups have to be manually added via sytem
> stored procedure sp_grantlogin
> so you have to add you specific WinNT group (say "powerusers") in order to
> grant all them permission to log in, or only your specific WinNT account
> Domain\Account if you want only him to be granted login...
> as regard the second authentication phase, it regards specific access to
> each database, and this is done via the sp_grantdbaccess system stored
> procedures, that adds an entry in each specific database.dbo.sysusers system
> table matching the master.dbo.syslogins system view in the join of the sid
> column... this operation generate a database user mapped to a specific
> login, allowing him/her to access the desired database with the provided
> database role privileges... additional permission can be granted/denied to
> each db user, defining the specific security design as required on every db
> object and so on, but this is a successive step...
> please start reading at
> http://msdn.microsoft.com/library/de...ar_da_0n77.asp
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
|||Wrong thread, see above... RS
"Andrea Montanari" wrote:

> hi Peter,
> Peter wrote:
> using and accessing MSDE/SQL Server and it's databases belongs to an
> authentication area of the product...
> SQL Server uses a sort of 2 phase authentication..
> the first one regards login, where someone try to connect to a particular
> instance using WinNT (trusted) connections or standard SQL Server
> connections (yes, handling both is known as "mixed authentication")
> in the second case, standard SQL Server connections, a user id and a
> password must be provided, and this information has to be matched against
> available SQL Server logins... if a match is found the connecting person has
> provided correct information and can log in...
> the WinNT (trusted) method does not require this kind of information as the
> underlaying OS provides the sid of the against the DC authenticated OS
> login, that only need to be matched against a WinNT SQL Server already
> granted login or WinNT granted group..
> that's to say both kind of authentications need a match in the granted
> logins...
> Standard SQL Server logins must all be manually added via sp_addlogin system
> stored procedure but "sa" "super" login, which is provided by default and
> that can not be removed..
> as regard WinNT connections, the setup automatically adds a WinNT group
> including all WinNT administrators, and this is the reason you can log in
> MSDE when logged in Windows as admin...
> but all other Windows users/groups have to be manually added via sytem
> stored procedure sp_grantlogin
> so you have to add you specific WinNT group (say "powerusers") in order to
> grant all them permission to log in, or only your specific WinNT account
> Domain\Account if you want only him to be granted login...
> as regard the second authentication phase, it regards specific access to
> each database, and this is done via the sp_grantdbaccess system stored
> procedures, that adds an entry in each specific database.dbo.sysusers system
> table matching the master.dbo.syslogins system view in the join of the sid
> column... this operation generate a database user mapped to a specific
> login, allowing him/her to access the desired database with the provided
> database role privileges... additional permission can be granted/denied to
> each db user, defining the specific security design as required on every db
> object and so on, but this is a successive step...
> please start reading at
> http://msdn.microsoft.com/library/de...ar_da_0n77.asp
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>

MSDE no show in server explorer

I have installed default instance of SQLServer 2005 DE on Windows Server 2003 host. I also installed a named instance of MSDE rel A. I can connect to the MSDE instance from Management Studio but it does not appear in the list of servers when I try to add the connection in VS2005 server explorer. What am I doing wrong?

- Dick

Anybody?

I can connect to the named MSDE instance (now upgraded to SP4) with management studio and osql, but it does not appear in the server list in VS2005 studio explorer, or in the OS ODBC DataSources utility.

The log shows the MSDE instance is listening on shared memory. I cannot configure it for named pipes because I can only see the default SS2K5 instance in SQL Server Configuration Manager.

All contributions massively appreciated.

|||

MSDE instances listening only on shared memory generally do not show up in the list boxes you mention.

You can configure the MSDE to listen on named pipes (or TCP) through the Server Network Utility.

|||

Thanks Peter

That cracked it. Here's what I did:

- I ran Microsoft SQL Server\80\Tools\binn\SVRNETCN.exe and enabled Named Pipes and TCP/IP

- restarted the server instance but it did not fix it.

- rebooted the machine, got various system errors e.g. reporting services could not connect to db. There was a conflict on port 1433.

- re-ran Server Network Configuration utility, set TCP/IP port to 0. (Bit confused by this, I thought MSDE sp 3 sorted out port sharing issue ...? I havn't tried a remote connection yet)

- Ran SQL Configuration Manager and created np aliases for both the default and named instances.

- rebooted and everything fixed. Able to create a System DSN. MSDE instance did not appear in server list when I tried to add a new a connection in VS2005 server explorer, but I was able to type in the server name and connect ok.

As a general observation I have to say I am not a member of SQL Server 2005 fan club yet. It promises simplicity, but delivers frustration.

MSDE NewBie

Dear all I did this.
I installed client version of SQL 2000 to connect to my server
(I can connect to my server and access the database there).
I installed MSDE2000RelA on my Win ME PC. Installation all
went smooth,(no errors). How do I use MSDE now. In the
enterprise manager I dont see any reference to MSDE. Am
I missing something. pls help
Joy -
Here is what you need to do.
First thing first , the network libraries are not enabled in MSDE by default
if it is a NAMED INSTANCE. In order to enable the libraries -
- Go to the Server Network Utilities of SQL Server from the Start Menu.
- Select the MSDE Instance from drop down list
- enable Named Pipes, TCP-IP and Shared Memory
- highlight TCP-IP and go to its Properties.
- if MSDE is a default instance then set the port number to 1433, but if it
is not a default instance then set the Port Number to 0. This will enable
dynamic port allocation.
- apply the above changes.
- close all client tools including Enterprise Manager and Query Analyser
- restart MSDE
- after restarting , Open Enterprise Manager
- right click on the SQL Server Group Icon, and select NEW SQL SERVER
REGISTRATION.
- give the details of the MSDE Instance.
You should be able to see the MSDE Instance in the EM . try connecting to
MSDE from Query Analyser.
This should help.
Regards
Pragya
"Joy H" wrote:

> Dear all I did this.
> I installed client version of SQL 2000 to connect to my server
> (I can connect to my server and access the database there).
> I installed MSDE2000RelA on my Win ME PC. Installation all
> went smooth,(no errors). How do I use MSDE now. In the
> enterprise manager I dont see any reference to MSDE. Am
> I missing something. pls help
|||Just to add to my previous posting, the MSDE by default does not get
registered in the Enterprise Manager. ...
"Joy H" wrote:

> Dear all I did this.
> I installed client version of SQL 2000 to connect to my server
> (I can connect to my server and access the database there).
> I installed MSDE2000RelA on my Win ME PC. Installation all
> went smooth,(no errors). How do I use MSDE now. In the
> enterprise manager I dont see any reference to MSDE. Am
> I missing something. pls help

msde login problem

I installed MSDE in my computer. When I try to connect to a database from a
program I get an error message:
Code = 80004005
Code meaning = Unspecified error
Source = Microsoft OLE DB Provider for SQL Server
Description = Login failed for user 'sa'. Reason: Not associated with
a trusted SQL Server connection.
Please help.
Antonin
By default, MSDE is installed with Windows Authentication only. So
unless you've changed it to mixed mode you'll only be able to login with
trusted logins (not 'sa'). To change to mixed mode you have to change a
reg value, viz.
"HKLM\Software\Microsoft\MSSQLServer\MSSQLServer\L oginMode" or
"HKLM\Software\Microsoft\Microsoft SQL Server\<Instance
Name>\MSSQLServer\LoginMode" for a named instance (detailed in
http://support.microsoft.com/default...;EN-US;Q325022). The
values for the reg key are:
1 - Windows only mode
2 - Mixed mode (Windows & SQL authentication)
Cheers,
*mike hodgson* |/ database administrator/ | mallesons stephen jaques
*T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
*E* mailto:mike.hodgson@.mallesons.nospam.com |* W* http://www.mallesons.com
Antonin Koudelka wrote:

>I installed MSDE in my computer. When I try to connect to a database from a
>program I get an error message:
> Code = 80004005
> Code meaning = Unspecified error
> Source = Microsoft OLE DB Provider for SQL Server
> Description = Login failed for user 'sa'. Reason: Not associated with
>a trusted SQL Server connection.
>Please help.
>Antonin
>
>
|||Thanks Mike,
It works now.
Antonin
"Mike Hodgson" <mike.hodgson@.mallesons.nospam.com> wrote in message news:eThC6n8FFHA.2156@.TK2MSFTNGP09.phx.gbl...
By default, MSDE is installed with Windows Authentication only. So unless you've changed it to mixed mode you'll only be able to login with trusted logins (not 'sa'). To change to mixed mode you have to change a reg value, viz. "HKLM\Software\Microsoft\MSSQLServer\MSSQLServer\L oginMode" or "HKLM\Software\Microsoft\Microsoft SQL Server\<Instance Name>\MSSQLServer\LoginMode" for a named instance (detailed in http://support.microsoft.com/default...;EN-US;Q325022). The values for the reg key are:
1 - Windows only mode
2 - Mixed mode (Windows & SQL authentication)
Cheers,
mike hodgson | database administrator | mallesons stephen jaques
T +61 (2) 9296 3668 | F +61 (2) 9296 3885 | M +61 (408) 675 907
E mailto:mike.hodgson@.mallesons.nospam.com | W http://www.mallesons.com
Antonin Koudelka wrote:
I installed MSDE in my computer. When I try to connect to a database from a
program I get an error message:
Code = 80004005
Code meaning = Unspecified error
Source = Microsoft OLE DB Provider for SQL Server
Description = Login failed for user 'sa'. Reason: Not associated with
a trusted SQL Server connection.
Please help.
Antonin

msde login problem

I installed MSDE in my computer. When I try to connect to a database from a
program I get an error message:
Code = 80004005
Code meaning = Unspecified error
Source = Microsoft OLE DB Provider for SQL Server
Description = Login failed for user 'sa'. Reason: Not associated with
a trusted SQL Server connection.
Please help.
AntoninBy default, MSDE is installed with Windows Authentication only. So
unless you've changed it to mixed mode you'll only be able to login with
trusted logins (not 'sa'). To change to mixed mode you have to change a
reg value, viz.
" HKLM\Software\Microsoft\MSSQLServer\MSSQ
LServer\LoginMode" or
"HKLM\Software\Microsoft\Microsoft SQL Server\<Instance
Name>\MSSQLServer\LoginMode" for a named instance (detailed in
http://support.microsoft.com/defaul...b;EN-US;Q325022). The
values for the reg key are:
1 - Windows only mode
2 - Mixed mode (Windows & SQL authentication)
Cheers,
*mike hodgson* |/ database administrator/ | mallesons stephen jaques
*T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
*E* mailto:mike.hodgson@.mallesons.nospam.com |* W* http://www.mallesons.com
Antonin Koudelka wrote:

>I installed MSDE in my computer. When I try to connect to a database from a
>program I get an error message:
> Code = 80004005
> Code meaning = Unspecified error
> Source = Microsoft OLE DB Provider for SQL Server
> Description = Login failed for user 'sa'. Reason: Not associated with
>a trusted SQL Server connection.
>Please help.
>Antonin
>
>|||Thanks Mike,
It works now.
Antonin
"Mike Hodgson" <mike.hodgson@.mallesons.nospam.com> wrote in message news:eTh
C6n8FFHA.2156@.TK2MSFTNGP09.phx.gbl...
By default, MSDE is installed with Windows Authentication only. So unless you've chang
ed it to mixed mode you'll only be able to login with trusted logins (not 'sa'). To ch
ange to mixed mode you have to change a reg value, viz. "HKLM\Software\Microsoft\MSSQLS
erver\MSSQLServer\LoginMode" or "HKLM\Software\Microsoft\Microsoft SQL Server\<Instance
Name>\MSSQLServer\LoginMode" for a named instance (detailed in http://support.mic
rosoft.co...b;EN-US;Q325022). The values for the reg key
are:
1 - Windows only mode
2 - Mixed mode (Windows & SQL authentication)
Cheers,
mike hodgson | database administrator | mallesons stephen jaques
T +61 (2) 9296 3668 | F +61 (2) 9296 3885 | M +61 (408) 675 907
E mailto:mike.hodgson@.mallesons.nospam.com | W http://www.mallesons.com
Antonin Koudelka wrote:
I installed MSDE in my computer. When I try to connect to a database from a
program I get an error message:
Code = 80004005
Code meaning = Unspecified error
Source = Microsoft OLE DB Provider for SQL Server
Description = Login failed for user 'sa'. Reason: Not associated with
a trusted SQL Server connection.
Please help.
Antonin

msde login problem

I installed MSDE in my computer. When I try to connect to a database from a
program I get an error message:
Code = 80004005
Code meaning = Unspecified error
Source = Microsoft OLE DB Provider for SQL Server
Description = Login failed for user 'sa'. Reason: Not associated with
a trusted SQL Server connection.
Please help.
AntoninThis is a multi-part message in MIME format.
--010506050301020900000107
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
By default, MSDE is installed with Windows Authentication only. So
unless you've changed it to mixed mode you'll only be able to login with
trusted logins (not 'sa'). To change to mixed mode you have to change a
reg value, viz.
"HKLM\Software\Microsoft\MSSQLServer\MSSQLServer\LoginMode" or
"HKLM\Software\Microsoft\Microsoft SQL Server\<Instance
Name>\MSSQLServer\LoginMode" for a named instance (detailed in
http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q325022). The
values for the reg key are:
1 - Windows only mode
2 - Mixed mode (Windows & SQL authentication)
Cheers,
--
*mike hodgson* |/ database administrator/ | mallesons stephen jaques
*T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
*E* mailto:mike.hodgson@.mallesons.nospam.com |* W* http://www.mallesons.com
Antonin Koudelka wrote:
>I installed MSDE in my computer. When I try to connect to a database from a
>program I get an error message:
> Code = 80004005
> Code meaning = Unspecified error
> Source = Microsoft OLE DB Provider for SQL Server
> Description = Login failed for user 'sa'. Reason: Not associated with
>a trusted SQL Server connection.
>Please help.
>Antonin
>
>
--010506050301020900000107
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>By default, MSDE is installed with Windows Authentication only. So
unless you've changed it to mixed mode you'll only be able to login
with trusted logins (not 'sa'). To change to mixed mode you have to
change a reg value, viz.
"HKLM\Software\Microsoft\MSSQLServer\MSSQLServer\LoginMode" or
"HKLM\Software\Microsoft\Microsoft SQL Server\<Instance
Name>\MSSQLServer\LoginMode" for a named instance (detailed in
<a class="moz-txt-link-freetext" href="http://links.10026.com/?link=http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q325022</a>). ">http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q325022">http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q325022</a>). The
values for the reg key are:<br>
1 - Windows only mode<br>
2 - Mixed mode (Windows & SQL authentication)<br>
<br>
Cheers,<br>
</tt>
<div class="moz-signature">
<title></title>
<meta http-equiv="Content-Type" content="text/html; ">
<p><span lang="en-au"><font face="Tahoma" size="2">--<br>
</font> </span><b><span lang="en-au"><font face="Tahoma" size="2">mike
hodgson</font></span></b><span lang="en-au"> <font face="Tahoma"
size="2">|</font><i><font face="Tahoma"> </font><font face="Tahoma"
size="2"> database administrator</font></i><font face="Tahoma" size="2">
| mallesons</font><font face="Tahoma"> </font><font face="Tahoma"
size="2">stephen</font><font face="Tahoma"> </font><font face="Tahoma"
size="2"> jaques</font><font face="Tahoma"><br>
</font><b><font face="Tahoma" size="2">T</font></b><font face="Tahoma"
size="2"> +61 (2) 9296 3668 |</font><b><font face="Tahoma"> </font><font
face="Tahoma" size="2"> F</font></b><font face="Tahoma" size="2"> +61
(2) 9296 3885 |</font><b><font face="Tahoma"> </font><font
face="Tahoma" size="2">M</font></b><font face="Tahoma" size="2"> +61
(408) 675 907</font><br>
<b><font face="Tahoma" size="2">E</font></b><font face="Tahoma" size="2">
<a href="http://links.10026.com/?link=mailto:mike.hodgson@.mallesons.nospam.com">
mailto:mike.hodgson@.mallesons.nospam.com</a> |</font><b><font
face="Tahoma"> </font><font face="Tahoma" size="2">W</font></b><font
face="Tahoma" size="2"> <a href="http://links.10026.com/?link=/">http://www.mallesons.com">
http://www.mallesons.com</a></font></span> </p>
</div>
<br>
<br>
Antonin Koudelka wrote:
<blockquote cite="mid%23uTSP87FFHA.3888@.TK2MSFTNGP12.phx.gbl"
type="cite">
<pre wrap="">I installed MSDE in my computer. When I try to connect to a database from a
program I get an error message:
Code = 80004005
Code meaning = Unspecified error
Source = Microsoft OLE DB Provider for SQL Server
Description = Login failed for user 'sa'. Reason: Not associated with
a trusted SQL Server connection.
Please help.
Antonin
</pre>
</blockquote>
</body>
</html>
--010506050301020900000107--|||This is a multi-part message in MIME format.
--=_NextPart_000_0009_01C5182A.2893B8F0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Thanks Mike,
It works now.
Antonin
"Mike Hodgson" <mike.hodgson@.mallesons.nospam.com> wrote in message =news:eThC6n8FFHA.2156@.TK2MSFTNGP09.phx.gbl...
By default, MSDE is installed with Windows Authentication only. So =unless you've changed it to mixed mode you'll only be able to login with =trusted logins (not 'sa'). To change to mixed mode you have to change a =reg value, viz. ="HKLM\Software\Microsoft\MSSQLServer\MSSQLServer\LoginMode" or ="HKLM\Software\Microsoft\Microsoft SQL Server\<Instance =Name>\MSSQLServer\LoginMode" for a named instance (detailed in =http://support.microsoft.com/default.aspx?scid=3Dkb;EN-US;Q325022). The =values for the reg key are:
1 - Windows only mode
2 - Mixed mode (Windows & SQL authentication)
Cheers,
--
mike hodgson | database administrator | mallesons stephen jaques
T +61 (2) 9296 3668 | F +61 (2) 9296 3885 | M +61 (408) 675 907
E mailto:mike.hodgson@.mallesons.nospam.com | W =http://www.mallesons.com=20
Antonin Koudelka wrote: I installed MSDE in my computer. When I try to connect to a database =from a
program I get an error message:
Code =3D 80004005
Code meaning =3D Unspecified error
Source =3D Microsoft OLE DB Provider for SQL Server
Description =3D Login failed for user 'sa'. Reason: Not associated =with
a trusted SQL Server connection.
Please help.
Antonin
--=_NextPart_000_0009_01C5182A.2893B8F0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&

---

Thanks Mike,
It works now.
Antonin
"Mike Hodgson" wrote in message news:eThC6n8FFHA.2156=@.TK2MSFTNGP09.phx.gbl...By default, MSDE is installed with Windows Authentication only. So =unless you've changed it to mixed mode you'll only be able to login with =trusted logins (not 'sa'). To change to mixed mode you have to change a =reg value, viz. ="HKLM\Software\Microsoft\MSSQLServer\MSSQLServer\LoginMode" or "HKLM\Software\Microsoft\Microsoft SQL Server\\MSSQLServer\LoginMode" for a named instance (detailed in http://support.microsoft.com/default.aspx?scid=3Dkb;EN-US;Q325022).= The values for the reg key are: 1 - Windows only = mode 2 - Mixed mode (Windows & SQL authentication)Cheers,
--mike =hodgson | database =administrator | mallesons =stephen jaquesT +61 (2) 9296 3668 | F +61 (2) 9296 3885 | M +61 (408) 675 907E mailto:mike.hodgson@.mal=lesons.nospam.com | W http://www.mallesons.com Antonin Koudelka wrote: I installed MSDE in my computer. When I try =to connect to a database from a
program I get an error message:
Code =3D 80004005
Code meaning =3D Unspecified error
Source =3D Microsoft OLE DB Provider for SQL Server
Description =3D Login failed for user 'sa'. Reason: Not associated =with
a trusted SQL Server connection.
Please help.
Antonin

---

--=_NextPart_000_0009_01C5182A.2893B8F0--