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. Oxymoron?

We have a commercial application that uses a number of Access DBs. For security reasons we have to encrypt all the data. It's not personal data or anything, just proprietary information.

I've been thinking about MSDE instead of Access so I could stop encrypting. Since the user will only get MSDE they won't be able to get the data without our application since they won't know the user or pwd. Unless...

If they already have the full SQL Server on some other system, couldn't they just copy the MDF file from our application to that server, attach it as a new DB and have full access to it (using the admin account on the full system?)

I guess it comes down to can an MSDE database be read on a full SQL Server instance elsewhere?The scenario you describe is correct. The users would have to stop the SQL Services (no big challenge for most folks), in order to ensure they get a nice clean copy. They can even probably access the data with the SQL tools if they are a local admin on the MSDE machine (unless you removed the BUILTIN\ADMINISTRATORS group).

You may just want to go for the full fledged version of SQL Server, and put the server in a locked server room, with no user permissions on the data and backup directories.

MSDE sa password - newbie

I downloaded and installed (somehow) MSDE a couple weeks ago but have not used it. Now I try to access MSDE using sa account but it does not accept an empty password and I do not remember providing one at install. MSDE appears to be installed because I se
e data files at C:\Program Files\Microsoft SQL Server\MSSQL$VSDOTNET\Data. Is there any way I can start using this install or do I need to start all over?
hi Mike,
"Mike" <anonymous@.discussions.microsoft.com> ha scritto nel messaggio
news:C864FCBB-655C-4D66-9DC4-9215C74A47C7@.microsoft.com...
> I downloaded and installed (somehow) MSDE a couple weeks ago but have not
used it. Now I try to
>access MSDE using sa account but it does not accept an empty password and I
do not remember
>providing one at install. MSDE appears to be installed because I see data
files at C:\Program
>Files\Microsoft SQL Server\MSSQL$VSDOTNET\Data. Is there any way I can
start using this install or
>do I need to start all over?
you probably changed the sa password...
try login in using a trusted authenticated Windows login member of the
sysadmin group
all sysadmin are granted privilege to modify password of other user...
then execute (osql, or the query tool of your choice)
EXEC sp_password @.new = 'new_password', @.loginame = 'sa'
in order to modify the forgotten sa pwd..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hi,
If you have not provided a password for the SA login at installation time,
then it should be blank and it should accept it.
What I doubt is the Server name that you would be entering to connect to
the MSDE.
From the folder name that you have sent, I understand that it is a named
instance and you should use "computername\Instancename", in your case
"Computername\VSDOTNET", replace computername with the name of your
computer and try it.
HTH
Ashish
This posting is provided "AS IS" with no warranties, and confers no rights.

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

Sorry if this is basic stuff but I'm new to MSDE and SQL.

I am running MSDE as the server.

I created a Microsoft Access Project and connected to the MSDE. Security is
set to Integrated Security.

When I try to open the database from an application I am writing I get a
login error stating the user doesn't have rights to the database. I am
logged in to the computer with administrator privledges but get the error.

I know that I have to tell the server that users have access to the database
but how do I do that if I can't gain access to the database?

Thanks,

EricI have hit this problem with sql server as well. I fixed it by
creating a server based login. that is one that requires a user name
and password. That way in the program all you need for permission is
those to fields in teh Connection String. Of course you still need to
grant that login access to the relevent dbs

MSDE Problem - SQL Server not found or access denied

I am running the MSDE 2000 Setup off the SQL Server 2000 Developer Edition CD.

After installation is complete, there is a service under the Control Panel -> Services window
called MSSQL$GregInstance. I then start that service.

But now when I try to connect to the database using

osql -E -S GregInstance

I get told that the SQL Server does not exist or access denied. Even though the server is running. I have also tried

osql -E -S localhost

but no luck. Why can it not find the instance of SQL Server?

Note : SQL Server 2000 is not installed on the machine, only this MSDE instance.

Thanks
GregNot to worry, I forgot to add in the name of the pc with a \ before the instance name...

i.e

osql -E -S GREG\GregInstance

MSDE Performance Against Concurrent Access

Thx Andrea, Thx William,
Since u told me, I've made some test on the SQL model I
have running and the queries use to take just 1/100 sec (I
use to have up to 10 queries in chain per ASP page) due to
the volume of the info related (this intranet wouldnt
reach 100.000 records total in 38 tables, ever I think)
and the easyness of the queries (it has as maximum 2
subqueries) but there is more inner joins, up to 5 in the
same query, there is also 100's of relations between the
tables (38 total tables).
I think this information make sence to migrate the model
to MSDE and use it without translating the cost of a SQL
licence to my client since it wouldnt worth it.
Any other sugest?
Thx in advance...

>--Original Message--
>Hello,
>Can anybody tell me about your own experience using IIS
>with MSDE as repository?
>Would the concurrent access of the anonymous internet
user
>to the MSDE engine affect its performance if the
>concurrent access reach more than 5 at a time?
>Im planning to deploy an Intranet Application for
>consultant office and Im affraid the MSDE to cause a
>dregradation in performance if it gets more than 5
>concurrent access.
>Thx in Advance.
>Mike.
>.
>
1) MSDE is free
2) JET is not intended for use in a web site for several reasons.
3) JET will outperform MSDE for some queries but it does not scale.
4) See 1.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
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.
__________________________________
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:b13701c47973$8f7843c0$a501280a@.phx.gbl...[vbcol=seagreen]
> Thx Andrea, Thx William,
> Since u told me, I've made some test on the SQL model I
> have running and the queries use to take just 1/100 sec (I
> use to have up to 10 queries in chain per ASP page) due to
> the volume of the info related (this intranet wouldnt
> reach 100.000 records total in 38 tables, ever I think)
> and the easyness of the queries (it has as maximum 2
> subqueries) but there is more inner joins, up to 5 in the
> same query, there is also 100's of relations between the
> tables (38 total tables).
> I think this information make sence to migrate the model
> to MSDE and use it without translating the cost of a SQL
> licence to my client since it wouldnt worth it.
> Any other sugest?
> Thx in advance...
>
> user

MSDE Performance Against Concurrent Access

Hello,
Can anybody tell me about your own experience using IIS
with MSDE as repository?
Would the concurrent access of the anonymous internet user
to the MSDE engine affect its performance if the
concurrent access reach more than 5 at a time?
Im planning to deploy an Intranet Application for
consultant office and Im affraid the MSDE to cause a
dregradation in performance if it gets more than 5
concurrent access.
Thx in Advance.
Mike.
hi Mike,
"Mike" <anonymous@.discussions.microsoft.com> ha scritto nel messaggio
news:7be701c4771f$40cdd7e0$a401280a@.phx.gbl...
> Hello,
> Can anybody tell me about your own experience using IIS
> with MSDE as repository?
> Would the concurrent access of the anonymous internet user
> to the MSDE engine affect its performance if the
> concurrent access reach more than 5 at a time?
> Im planning to deploy an Intranet Application for
> consultant office and Im affraid the MSDE to cause a
> dregradation in performance if it gets more than 5
> concurrent access.
> Thx in Advance.
> Mike.
you simply have to test, becouse no other project will be the same as your,
depending on the base schema, coding conventions, transactions lengths,
objects involved, data involved and so on...
usually it' said that MSDE can afford about 25 concurrent users, but this is
not a magic number, only a guess
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
|||As Andrea said, there is no fixed number of users. It's like asking how many
orders can a fry cook work at the same time? It's a function of how
efficiently each order is processed. How fast is the CPU? How much RAM is
available to cache the data and procedures? How fast is the hard disk? How
much data is being shipped to and from the server? How efficient is the
query or update? A single application can bring a standard edition SQL
Server to its knees if you knew what to ask for. A thousand clients an hour
might not cause the MSDE engine to kick into governor mode. It all
depends...
hth
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
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.
__________________________________
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:2n21guFsegv1U1@.uni-berlin.de...
> hi Mike,
> "Mike" <anonymous@.discussions.microsoft.com> ha scritto nel messaggio
> news:7be701c4771f$40cdd7e0$a401280a@.phx.gbl...
> you simply have to test, becouse no other project will be the same as
your,
> depending on the base schema, coding conventions, transactions lengths,
> objects involved, data involved and so on...
> usually it' said that MSDE can afford about 25 concurrent users, but this
is
> not a magic number, only a guess
> --
> 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
>

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 Opinions

My software currently runs on Access 2000 Engine. The database is 600 MB and
I can have up to 10 users (6 constantly). I currently run a terminal server
to share out access database. it is Dual XEON 2.8 Ghz with 4 GB RAM.
Is MSDE an option for my setup?
Would I need a second Database server?
Do I need to go all the way up to SQL 2000?
Our software company tells me that MSDE only can handle 10 connections. I
have read that that is not true. Are they basically trying to sell me full
blown SQL for nothing?
Opions greatly appreciated.
Chris
"Chris Blackwelder" <Chris Blackwelder@.discussions.microsoft.com> wrote in
message news:A1F1F198-3357-4657-A0F4-0F2EA7F2F84D@.microsoft.com...
| My software currently runs on Access 2000 Engine. The database is 600 MB and
| I can have up to 10 users (6 constantly). I currently run a terminal server
| to share out access database. it is Dual XEON 2.8 Ghz with 4 GB RAM.
|
| Is MSDE an option for my setup?
Yes.
| Would I need a second Database server?
No.
| Do I need to go all the way up to SQL 2000?
No.
|
| Our software company tells me that MSDE only can handle 10 connections.
Where did they get 10 from? That is a toatly made up number. 5 and 8 are at
least in the docs, but you can exceed them. I have tested heavy loads up to 26
and then my P2-333 server couldn't cope.
I
| have read that that is not true. Are they basically trying to sell me full
| blown SQL for nothing?
Yes, but don't be mad at them. My guess is they don't know better unless they
have load tested it themselvs. MS dosn't allow anyone to publish benchmarks and
there is no reason for MS to advertise them.
|
| Opions greatly appreciated.
I belive MSDE can handle just as much as Enterprise or any other flavor of SQL,
unless you need more than 2Gig of data or 4 CPUs. Here is my tests
http://fox.wikis.com/wc.dll?Wiki~MSD...ks~SoftwareEng
Carl K
sql

MSDE on SBS2003 from Network

I have created a new MSDE instance on my SBS 2003 Standard server, using
MSDE setup.
The service is started, and I can access the MSDE instance locally on the
server, but I am unable to access it from other PCs on the network (in the
domain).
Specifically, I am using SQL Server Enterprise Manager. It reports the
message "Sql Server does not exist or access denied" when I try to connect
to the instance (using "myserver\instance-name"). I tried ISQL and also get
access denied.
I installed Enterprise Manager locally on the server and it connects to the
instance without problem.
Looking at the Properties/General/Network Configuration I can see TCPIP is
enabled and now using port 1433 (although it was set to port 0 after
installation?).
My user account is a valid login with the "System Administrator" role an has
dbo access to all databases.
The Windows Firewall allows port 1433 at the client and no firewall on the
server.
What else to check?
richlm wrote:

>I have created a new MSDE instance on my SBS 2003 Standard server, using
>MSDE setup.
>The service is started, and I can access the MSDE instance locally on the
>server, but I am unable to access it from other PCs on the network (in the
>domain).
>Specifically, I am using SQL Server Enterprise Manager. It reports the
>message "Sql Server does not exist or access denied" when I try to connect
>to the instance (using "myserver\instance-name"). I tried ISQL and also
>get access denied.
The default for MSDE is to not listen to the network, only the local
machine.

>I installed Enterprise Manager locally on the server and it connects to
>the instance without problem.
>Looking at the Properties/General/Network Configuration I can see TCPIP is
>enabled and now using port 1433 (although it was set to port 0 after
>installation?).
This was in the Server Network Utility, yes?
Has the MSDE instance been restarted since you enabled a network protocol?

>My user account is a valid login with the "System Administrator" role an
>has dbo access to all databases.
>The Windows Firewall allows port 1433 at the client and no firewall on the
>server.
The Windows Firewall on a client is irrelevant, since it has no impact on
outgoing connections. It would only be of interest if MSDE (or SQL) was
installed on the workstation itself.
Out of interest, where did you get the SQL client utilities from? They're
not included with SBS2003 Standard, nor are you licenced to use them in an
SBS2003 Standard environment.
Steve Foster [SBS MVP]
MVPs do not work for Microsoft. Please reply only to the newsgroups.
|||Yes, TCP 1433 is at the top of the list of "enabled protocols" in the server
network utility, and I restarted the MSDE service after setting the port.
But I just realized that cliconfg does not allow me to choose which MSDE
instance to apply the changes to.
I just found a Microsoft support notice "Server Network Utility may display
incorrect protocol properties in SQL Server 2000" at
http://support.microsoft.com/?kbid=887700 - I'll investigate this further
(although I'm using SP4 so the hotfix does not apply).
As for licencing, I have an MSDN Universal subscription which includes the
use of SQL client tools for development purposes. But thanks for the
reminder, and I'll re-check the licence terms to make sure I've not
misunderstood something about where the tools can be used.
Richard.
|||richlm wrote:

>Yes, TCP 1433 is at the top of the list of "enabled protocols" in the
>server network utility, and I restarted the MSDE service after setting the
>port.
>But I just realized that cliconfg does not allow me to choose which MSDE
>instance to apply the changes to.
Eh?

>I just found a Microsoft support notice "Server Network Utility may
>display incorrect protocol properties in SQL Server 2000" at
>http://support.microsoft.com/?kbid=887700 - I'll investigate this further
>(although I'm using SP4 so the hotfix does not apply).
>As for licencing, I have an MSDN Universal subscription which includes the
>use of SQL client tools for development purposes. But thanks for the
>reminder, and I'll re-check the licence terms to make sure I've not
>misunderstood something about where the tools can be used.
AIUI, the MSDN licence does not cover using the SQL client utilities to
manage a production server. So, unless your SBS is only used for your
development network, you are not legally allowed to use the MSDN licence
to manage SQL services on SBS. But hey, IANAL, nor a member of the licence
police...
Steve Foster [SBS MVP]
MVPs do not work for Microsoft. Please reply only to the newsgroups.
|||OK - I should be running svrnetcn.exe and not cliconfg.exe...
Now I can choose the instance - and can confirm that the problem referred to
at http://support.microsoft.com/?kbid=887700 also applies to SP4. The
workaround suggested there (choose another instance then go back to the one
you really wanted) refreshes the UI correctly.
But I still can't connect remotely using EM or OSQL - yet both work locally.
I've googled to the end of the earth and not found other suggestions so my
guess now is it's probably due to the fact I have installed VS2005 on my
client - which also installs SQL 2005 express.
When I try to connect using OSQL I get the following error:
[SQL Native Client]Unable to complete login process due to delay in opening
server connection.
This perhaps implies my client PC is "broken" for connecting to SQL 2000
instances?
The version of "SQL Server Native Client" I currently use is 9.00.1314.06.
I think I'll wait for SQL 2005 launch in a couple of weeks, where
(hopefully) this problem goes away.
Can anyone confirm this?
|||Richard Money wrote:

>OK - I should be running svrnetcn.exe and not cliconfg.exe...
>Now I can choose the instance - and can confirm that the problem referred
>to at http://support.microsoft.com/?kbid=887700 also applies to SP4. The
>workaround suggested there (choose another instance then go back to the
>one you really wanted) refreshes the UI correctly.
>But I still can't connect remotely using EM or OSQL - yet both work
>locally. I've googled to the end of the earth and not found other
>suggestions so my guess now is it's probably due to the fact I have
>installed VS2005 on my client - which also installs SQL 2005 express.
>When I try to connect using OSQL I get the following error:
>[SQL Native Client]Unable to complete login process due to delay in
>opening server connection.
>This perhaps implies my client PC is "broken" for connecting to SQL 2000
>instances?
>The version of "SQL Server Native Client" I currently use is 9.00.1314.06.
>I think I'll wait for SQL 2005 launch in a couple of weeks, where
>(hopefully) this problem goes away.
>Can anyone confirm this?
I don't know whether SQL2005 beta client tools can communicate with
SQL2000. I suspect that that is something likely to be left until very
close to RTM (and may require that SQL2000 gets an update of some sort).
I'd stick to trying with SQL2000 client utilities.
Steve Foster [SBS MVP]
MVPs do not work for Microsoft. Please reply only to the newsgroups.
|||Pretty sure that my problem connecting to MSDE over network was due to a
pre-release version of SQL2005 Express (sept. CTP) on my client.
Have just successfully installed the RTM of SQL Express on SBS as a named
instance, enabled networking using the SQL Server Configuration Manager, and
I can connect to the instance from VS2005 (RTM) running on another machine.
The default SBS instances for Sharepoint and SBSMonitoring are still running
MSDE (and still work!).
Now I'm happy:-)

MSDE no access on database objects

I have installed MSDE 2000 A, but I can't edit the database objects (tables,
stored procedures, etc.) in Access 2000. If I try, the window appears only
for a moment.
Any suggestions to solve the problem?
Frank
Hi Frank,
"FAT" <FAT@.discussions.microsoft.com> ha scritto nel messaggio
news:D74106D3-FDF3-4359-9AFA-1DB9A25C809E@.microsoft.com
> I have installed MSDE 2000 A, but I can't edit the database objects
> (tables, stored procedures, etc.) in Access 2000. If I try, the
> window appears only for a moment.
> Any suggestions to solve the problem?
> Frank
I think you've probably better resort on alternate tools.. perhaps Acces
2003, or other 3rd party tools...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||ehm........
please have a look at http://www.microsoft.com/sql/msde/partners/default.asp
and/or http://www.aspfaq.com/show.asp?id=2442 ... google for others..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

MSDE newbie question: connection strings

I installed MSDE on a Windows XP SP1 PC on our network. We don't have a
domain controller.
If I access this database via ADO, how do I construct the connection
string? As I understand it, this is of the form:
Provider=SQLOLEDB; Data Source=server_name; Initial
Catalog=database_name; User ID=username; Password=password;
Is the server name just the name or IP address of the PC running MSDE?
Are there any other subtleties I should be aware of?
Simon Elliott http://www.ctsn.co.uk
hi Simon,
"Simon Elliott" <Simon at ctsn.co.uk> ha scritto nel messaggio
news:OuUGwZwQEHA.3580@.TK2MSFTNGP11.phx.gbl...
> I installed MSDE on a Windows XP SP1 PC on our network. We don't have a
> domain controller.
> If I access this database via ADO, how do I construct the connection
> string? As I understand it, this is of the form:
> Provider=SQLOLEDB; Data Source=server_name; Initial
> Catalog=database_name; User ID=username; Password=password;
> Is the server name just the name or IP address of the PC running MSDE?
> Are there any other subtleties I should be aware of?
if the MSDE instance has been installed as the default intance, it's name
will just be the ComputerName and/or it's IP address... if it has been
installed as a named instance, it's name will be
ComputerName\InstanceName...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

MSDE Newbie Blooper

Another newbie here, hope yaw dont mind!
Yes I am redneck newbie
I have been using access for a few years and have decided to further
educate myself(untrain) and start allover withh SQL. I have the developers
edition of SQL 2000 and VisualStudio.net 2003, I did look at SQL 2005
Express. I know the newer the better, but as of this time I cannot afford to
take the plung for the devlopers edition of SQL 2005. So back to my
questions.
I am learning here so take it easy on me. I got SQL 2000 loaded and I can
access the server, make tables,etc,
I cant get MSDE to work in VS for some reason?(dont know what I am doing
probably) Every time I lanch VS and try to connect to the database, I get
"VS can only connect using MSDE,etc".I did download MSDE2000 and installed
as per instruction went to a command prompted and entered Setup.exe /qb+
INSTANCENAME=VSDOTNET DISABLENETWORKPROTOCOLS=1 SAPWD=<YOUR
SA PASSWORD>
as told, an error was promtped, saying to go to the control panel to make
changes?
-not what the instructions said-
, anyhow, to make it short, can someone point me in the right direction to
make this work so I can start doodling in my mind with what I have ahead of
me..
I have order a few books to enrich my tastebuds with whats ahead, but I like
jumping in over my head first..
Thanks in advance
David W
hi David,
DavidW wrote:
>...
> I cant get MSDE to work in VS for some reason?(dont know what I am
> doing probably) Every time I lanch VS and try to connect to the
> database, I get "VS can only connect using MSDE,etc".
I think to rember that the Standard edition of VS2003 only allowed to
connect to MSDE and not to full blown editions...

>I did download
> MSDE2000 and installed as per instruction went to a command prompted
> and entered Setup.exe /qb+ INSTANCENAME=VSDOTNET
> DISABLENETWORKPROTOCOLS=1 SAPWD=<YOUR SA PASSWORD>
> as told, an error was promtped, saying to go to the control panel to
> make changes?
> -not what the instructions said-
> , anyhow, to make it short, can someone point me in the right
> direction to make this work so I can start doodling in my mind with
> what I have ahead of me..
try adding the
/L*v "c:\MsdeLog.txt"
parameter to your setup syntax in order to enable verbose logging of the
installation process.. this will result in an about 2mb text file (for a
succesfull installation) you can inspect in case of troubles..
seek for
RETURN VALUE 3
entries, and about 10 lines before each entry some (sometime cryptinc)
description of the problem will be reported...
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 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 memory usage

I am using VB .NET to convert data from Access to MSDE.
While I am transferring table by table, the memory usage of 'sqlsvr' keeps increasing, and also CPU usage is @. 100 %
Some Tables have more than 10,000 records. Is there a way to reduce the memory usage or an explaination why would memory usage increase each time MDSE is accessed.
Just to note, there is only one connection to each database(Acces97 and MSDE)
and all the recordset connections are opened and closed
Thanks
Bobby
hi Bobby,
"Bobby" <Bobby@.discussions.microsoft.com> ha scritto nel messaggio
news:70184C7E-3CBF-4BEB-9381-A3AA8174A646@.microsoft.com...
> I am using VB .NET to convert data from Access to MSDE.
> While I am transferring table by table, the memory usage of 'sqlsvr' keeps
increasing, and also CPU usage is @. 100 %
> Some Tables have more than 10,000 records. Is there a way to reduce the
memory usage or an explaination why would memory usage increase each time
MDSE is accessed.
> Just to note, there is only one connection to each database(Acces97 and
MSDE)
> and all the recordset connections are opened and closed
>
i think Ken Henderson's book extracted, available at
http://msdn.microsoft.com/library/de...v_03252004.asp
is worth reading..
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

MSDE login problem

After installing MSDE 2000 in mixed mode local access worked fine.
Accessing through network with enterprice manager at first didn't work.
Fixed by activating network protocols "TCP/IP" and "Named pipes" in database properties.
But only the first time. After that login by SQL user and password is denied after restart local MSDE machine.

Anyone know why?

thanks in advanceAfter that login by SQL user and password is denied after restart local MSDE machine

With this I mean access from other machines on the network. Local login is working ok.|||Solution found!

Install MSDE again with DISABLENETWORKPROTOCOLS=0.
Changing it afterwards with SQL Server enterprice manager doesn't work.

just for those who are having the same problem

MSDE Login

Hi All,

I've been using NT authentication to access my MSDE without any problem, but when I try to login using an account with SQL Server username and password it returns

"Login failed for user 'testuser'. Reason: Not associated with a trusted SQL Server Connection."

I tried with Visual Studio, Query Analyzer and ODBC, they all return the same error.

Is this a limitation of MSDE or are there configurations that I'm not aware of?

Thanks!

WillIndeed, you should make sure MSDE is installed the right way to allow it to use SQL authentication as well. Just take a look at theMSDE website to find out more about how to configure and install it in the right way. The limitations are listed on this website as well...|||Maybe the next URL can be of interest as well:
http://www.asp.net/msde/default.aspx?tabindex=0&tabid=1.

It describes how to setup MSDE in mixed mode (both Windows and SQL authentication).|||The only thing that was left out in the above link is that the username is sa. It took me a while to figure that one out :-)

Is there a way to add other users?