connect from ASP app: winxp

Showing posts with label winxp. Show all posts

Thursday, March 8, 2012

Can't debug proc after Sp2 on WinXP

Hi,
After installation of SP2 on my WinXP Prof I can't run debug in SQL Query
Analyzer.
Unable to connect to debugger on "SERVER" (Error = 0x800706ba). Ensure that
client-side components, such as SQLDBREG.EXE, are installed and registered on
"MYXP". Debugging disabled for connection nn.
Server is Win 2003 and SQL 2000 with Sp3
Before Sp2 everything was OK.
Thanks for the help.
ML
Make sure you have followed all the steps in the help topic
in books online: Troubleshooting the Transact-SQL Debugger
You should also check the following knowledge base article:
INF: T-SQL Debugger Is Turned Off By Default for Earlier
Clients After You Install SQL Server 2000 Service Pack 3
http://support.microsoft.com/?id=328151
-Sue
On Wed, 27 Oct 2004 05:13:03 -0700, MarekL
<MarekL@.discussions.microsoft.com> wrote:

>Hi,
>After installation of SP2 on my WinXP Prof I can't run debug in SQL Query
>Analyzer.
>Unable to connect to debugger on "SERVER" (Error = 0x800706ba). Ensure that
>client-side components, such as SQLDBREG.EXE, are installed and registered on
>"MYXP". Debugging disabled for connection nn.
>Server is Win 2003 and SQL 2000 with Sp3
>Before Sp2 everything was OK.
>Thanks for the help.
>ML

Cant create table

I have just installed Mysql on winXP.

When I get to the mysql promt and type:

create table mytable(id int);

I get this error:

ERROR 1046 <3D000>: No database selected

It seems that I need to create a database first, but I was told this was not
necessary to create a table, is this right?You'll probably get a better response in a MySQL forum - this
newsgroup is for Microsoft SQL Server.

http://www.google.com/search?source...ySQL+ERROR+1046

Simon

Saturday, February 25, 2012

Can't connet to MSDE with Query Analyzer

I'm running MSDE on a WIN2K and I'm having a problem accessing the MSDE from
a laptop with WINXP Professional. I'm using a NETGEAR MR314 cable router w/
firewall to connect the two computers and I'm getting the following error:
Unable to connec to server SERVERNAME
Server: Msg 17, Level 16, State1
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
access denied
I've tried by creating a new account with owner rights to all databases and
I still get the same error when connecting with Query Analyzer. When I get
the "Connect to SQL Server" dialog box I can see the server but when I enter
the user name an password it gives me the error message.
The client is attempting to connect using TCP/IP so you will
want to make sure this protocol is enabled for MSDE. You can
use the server network utility to check, enable the
protocols. The utility file name is svrnetcn.exe. You can
find it in the Tools\Binn directory of your installation
path.
You can also find some general troubleshooting for the error
at:
INF: Potential Causes of the "SQL Server Does Not Exist or
Access Denied" Error Message
http://support.microsoft.com/?id=328306
-Sue
On Sun, 2 May 2004 16:00:49 -0500, "Sal Young"
<salyoung@.comcast.net> wrote:

>I'm running MSDE on a WIN2K and I'm having a problem accessing the MSDE from
>a laptop with WINXP Professional. I'm using a NETGEAR MR314 cable router w/
>firewall to connect the two computers and I'm getting the following error:
>Unable to connec to server SERVERNAME
>Server: Msg 17, Level 16, State1
>[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
>access denied
>
>I've tried by creating a new account with owner rights to all databases and
>I still get the same error when connecting with Query Analyzer. When I get
>the "Connect to SQL Server" dialog box I can see the server but when I enter
>the user name an password it gives me the error message.
>

Can't connet to MSDE with Query Analyzer

I'm running MSDE on a WIN2K and I'm having a problem accessing the MSDE from
a laptop with WINXP Professional. I'm using a NETGEAR MR314 cable router w/
firewall to connect the two computers and I'm getting the following error:
Unable to connec to server SERVERNAME
Server: Msg 17, Level 16, State1
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
access denied
I've tried by creating a new account with owner rights to all databases and
I still get the same error when connecting with Query Analyzer. When I get
the "Connect to SQL Server" dialog box I can see the server but when I enter
the user name an password it gives me the error message.
MSDE doesn't listen to any netlibs by default. You can enable netlibs using the svrnetcn.exe utility.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Sal Young" <salyoung@.comcast.net> wrote in message news:MMadnZ23tfPw_AjdRVn-sA@.comcast.com...
> I'm running MSDE on a WIN2K and I'm having a problem accessing the MSDE from
> a laptop with WINXP Professional. I'm using a NETGEAR MR314 cable router w/
> firewall to connect the two computers and I'm getting the following error:
> Unable to connec to server SERVERNAME
> Server: Msg 17, Level 16, State1
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
> access denied
>
> I've tried by creating a new account with owner rights to all databases and
> I still get the same error when connecting with Query Analyzer. When I get
> the "Connect to SQL Server" dialog box I can see the server but when I enter
> the user name an password it gives me the error message.
>

Can't connet to MSDE with Query Analyzer

Tuesday, February 14, 2012

Can't connect to MSDE with Query Analyzer

Sunday, February 12, 2012

Can't connect to MSDE

I've got two machines: 1) SBS 2003 Server, and 2) WinXP Pro.
SQL Server 2000 is installed on the server box, as well as MSDE for the default
SharePoint and SbsMonitoring databases (SBS setup created those). The
workstation is running MSDE.
The problem is that I can only connect to the workstation's MSDE from the
workstation. EM on the server can see the MSDE instance (the worksation's
machine name appears in the Add SQL Server Registration dialog box), but that's
as far as it can get. When I try to add the instance under a new registration, I
get 'access denied or server doesn't exist' (paraphrased).
I also can't connect via EM to the workstation's MSDE from within a Win98
VirtualPC instance running on the workstation, although I can connect to the
server's instances (both SQL Server and MSDE instances) from within that
instance.
I've compared the property sheets of all the instances to which I can connect
from WinXP, and everything seems to be the same. Nothing shows up in my ISA
logs, so I don't think packets are being blocked. Just in case I created a
temporary packet filter allowing all packets from anywhere (risky, I know), but
it still didn't work. Still nothing in the logs.
Does anyone know what this might be?
TIA,
Jeff
By default MSDE doesn't listen to any netlibs. On a regular SQL Server, you configure this using
"Server Network Utility". I'm not sure whether such comes with MSDE, but that would be the place to
start. The name of the exe is svrnetcn.exe
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Jeff Bowman" <write.to.me@.my.addess.com> wrote in message
news:%23Sv%23zABjFHA.3164@.TK2MSFTNGP15.phx.gbl...
> I've got two machines: 1) SBS 2003 Server, and 2) WinXP Pro.
> SQL Server 2000 is installed on the server box, as well as MSDE for the default SharePoint and
> SbsMonitoring databases (SBS setup created those). The workstation is running MSDE.
> The problem is that I can only connect to the workstation's MSDE from the workstation. EM on the
> server can see the MSDE instance (the worksation's machine name appears in the Add SQL Server
> Registration dialog box), but that's as far as it can get. When I try to add the instance under a
> new registration, I get 'access denied or server doesn't exist' (paraphrased).
> I also can't connect via EM to the workstation's MSDE from within a Win98 VirtualPC instance
> running on the workstation, although I can connect to the server's instances (both SQL Server and
> MSDE instances) from within that instance.
> I've compared the property sheets of all the instances to which I can connect from WinXP, and
> everything seems to be the same. Nothing shows up in my ISA logs, so I don't think packets are
> being blocked. Just in case I created a temporary packet filter allowing all packets from anywhere
> (risky, I know), but it still didn't work. Still nothing in the logs.
> Does anyone know what this might be?
> TIA,
> Jeff
>
>
|||That did the trick, thanks for the tip! :-)
(BTW, Server Network Utility appears to be installed with Client Tools.)
Tibor Karaszi wrote:[vbcol=seagreen]
> By default MSDE doesn't listen to any netlibs. On a regular SQL Server, you
> configure this using "Server Network Utility". I'm not sure whether such
> comes with MSDE, but that would be the place to start. The name of the exe is
> svrnetcn.exe
> "Jeff Bowman" <write.to.me@.my.addess.com> wrote in message
> news:%23Sv%23zABjFHA.3164@.TK2MSFTNGP15.phx.gbl...

Can't connect to MSDE

I've got two machines: 1) SBS 2003 Server, and 2) WinXP Pro.
SQL Server 2000 is installed on the server box, as well as MSDE for the defa
ult
SharePoint and SbsMonitoring databases (SBS setup created those). The
workstation is running MSDE.
The problem is that I can only connect to the workstation's MSDE from the
workstation. EM on the server can see the MSDE instance (the worksation's
machine name appears in the Add SQL Server Registration dialog box), but tha
t's
as far as it can get. When I try to add the instance under a new registratio
n, I
get 'access denied or server doesn't exist' (paraphrased).
I also can't connect via EM to the workstation's MSDE from within a Win98
VirtualPC instance running on the workstation, although I can connect to the
server's instances (both SQL Server and MSDE instances) from within that
instance.
I've compared the property sheets of all the instances to which I can connec
t
from WinXP, and everything seems to be the same. Nothing shows up in my ISA
logs, so I don't think packets are being blocked. Just in case I created a
temporary packet filter allowing all packets from anywhere (risky, I know),
but
it still didn't work. Still nothing in the logs.
Does anyone know what this might be?
TIA,
JeffBy default MSDE doesn't listen to any netlibs. On a regular SQL Server, you
configure this using
"Server Network Utility". I'm not sure whether such comes with MSDE, but tha
t would be the place to
start. The name of the exe is svrnetcn.exe
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Jeff Bowman" <write.to.me@.my.addess.com> wrote in message
news:%23Sv%23zABjFHA.3164@.TK2MSFTNGP15.phx.gbl...
> I've got two machines: 1) SBS 2003 Server, and 2) WinXP Pro.
> SQL Server 2000 is installed on the server box, as well as MSDE for the de
fault SharePoint and
> SbsMonitoring databases (SBS setup created those). The workstation is runn
ing MSDE.
> The problem is that I can only connect to the workstation's MSDE from the
workstation. EM on the
> server can see the MSDE instance (the worksation's machine name appears in
the Add SQL Server
> Registration dialog box), but that's as far as it can get. When I try to a
dd the instance under a
> new registration, I get 'access denied or server doesn't exist' (paraphras
ed).
> I also can't connect via EM to the workstation's MSDE from within a Win98
VirtualPC instance
> running on the workstation, although I can connect to the server's instanc
es (both SQL Server and
> MSDE instances) from within that instance.
> I've compared the property sheets of all the instances to which I can conn
ect from WinXP, and
> everything seems to be the same. Nothing shows up in my ISA logs, so I don
't think packets are
> being blocked. Just in case I created a temporary packet filter allowing a
ll packets from anywhere
> (risky, I know), but it still didn't work. Still nothing in the logs.
> Does anyone know what this might be?
> TIA,
> Jeff
>
>|||That did the trick, thanks for the tip! :-)
(BTW, Server Network Utility appears to be installed with Client Tools.)
Tibor Karaszi wrote:[vbcol=seagreen]
> By default MSDE doesn't listen to any netlibs. On a regular SQL Server, yo
u
> configure this using "Server Network Utility". I'm not sure whether such
> comes with MSDE, but that would be the place to start. The name of the exe
is
> svrnetcn.exe
> "Jeff Bowman" <write.to.me@.my.addess.com> wrote in message
> news:%23Sv%23zABjFHA.3164@.TK2MSFTNGP15.phx.gbl...

Can't connect to MSDE

I've got two machines: 1) SBS 2003 Server, and 2) WinXP Pro.
SQL Server 2000 is installed on the server box, as well as MSDE for the default
SharePoint and SbsMonitoring databases (SBS setup created those). The
workstation is running MSDE.
The problem is that I can only connect to the workstation's MSDE from the
workstation. EM on the server can see the MSDE instance (the worksation's
machine name appears in the Add SQL Server Registration dialog box), but that's
as far as it can get. When I try to add the instance under a new registration, I
get 'access denied or server doesn't exist' (paraphrased).
I also can't connect via EM to the workstation's MSDE from within a Win98
VirtualPC instance running on the workstation, although I can connect to the
server's instances (both SQL Server and MSDE instances) from within that
instance.
I've compared the property sheets of all the instances to which I can connect
from WinXP, and everything seems to be the same. Nothing shows up in my ISA
logs, so I don't think packets are being blocked. Just in case I created a
temporary packet filter allowing all packets from anywhere (risky, I know), but
it still didn't work. Still nothing in the logs.
Does anyone know what this might be?
TIA,
JeffBy default MSDE doesn't listen to any netlibs. On a regular SQL Server, you configure this using
"Server Network Utility". I'm not sure whether such comes with MSDE, but that would be the place to
start. The name of the exe is svrnetcn.exe
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Jeff Bowman" <write.to.me@.my.addess.com> wrote in message
news:%23Sv%23zABjFHA.3164@.TK2MSFTNGP15.phx.gbl...
> I've got two machines: 1) SBS 2003 Server, and 2) WinXP Pro.
> SQL Server 2000 is installed on the server box, as well as MSDE for the default SharePoint and
> SbsMonitoring databases (SBS setup created those). The workstation is running MSDE.
> The problem is that I can only connect to the workstation's MSDE from the workstation. EM on the
> server can see the MSDE instance (the worksation's machine name appears in the Add SQL Server
> Registration dialog box), but that's as far as it can get. When I try to add the instance under a
> new registration, I get 'access denied or server doesn't exist' (paraphrased).
> I also can't connect via EM to the workstation's MSDE from within a Win98 VirtualPC instance
> running on the workstation, although I can connect to the server's instances (both SQL Server and
> MSDE instances) from within that instance.
> I've compared the property sheets of all the instances to which I can connect from WinXP, and
> everything seems to be the same. Nothing shows up in my ISA logs, so I don't think packets are
> being blocked. Just in case I created a temporary packet filter allowing all packets from anywhere
> (risky, I know), but it still didn't work. Still nothing in the logs.
> Does anyone know what this might be?
> TIA,
> Jeff
>
>|||That did the trick, thanks for the tip! :-)
(BTW, Server Network Utility appears to be installed with Client Tools.)
Tibor Karaszi wrote:
> By default MSDE doesn't listen to any netlibs. On a regular SQL Server, you
> configure this using "Server Network Utility". I'm not sure whether such
> comes with MSDE, but that would be the place to start. The name of the exe is
> svrnetcn.exe
> "Jeff Bowman" <write.to.me@.my.addess.com> wrote in message
> news:%23Sv%23zABjFHA.3164@.TK2MSFTNGP15.phx.gbl...
>> I've got two machines: 1) SBS 2003 Server, and 2) WinXP Pro.
>> SQL Server 2000 is installed on the server box, as well as MSDE for the
>> default SharePoint and SbsMonitoring databases (SBS setup created those).
>> The workstation is running MSDE. The problem is that I can only connect to
>> the workstation's MSDE from the
>> workstation. EM on the server can see the MSDE instance (the worksation's
>> machine name appears in the Add SQL Server Registration dialog box), but
>> that's as far as it can get. When I try to add the instance under a new
>> registration, I get 'access denied or server doesn't exist' (paraphrased). I
>> also can't connect via EM to the workstation's MSDE from within a Win98
>> VirtualPC instance running on the workstation, although I can connect to the
>> server's instances (both SQL Server and MSDE instances) from within that
>> instance. I've compared the property sheets of all the instances to which I
>> can
>> connect from WinXP, and everything seems to be the same. Nothing shows up in
>> my ISA logs, so I don't think packets are being blocked. Just in case I
>> created a temporary packet filter allowing all packets from anywhere (risky,
>> I know), but it still didn't work. Still nothing in the logs. Does anyone
>> know what this might be?
>> TIA,
>> Jeff

Friday, February 10, 2012

Can't connect remotely to MSDE 2000 DB on WinXP Home Machine

Hi All
Having 'Google-ised' I've found that there does appear to be a problem
connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN), but
I haven't found what the concrete solution is.
It definitely appears to be a Windows inflicted problem, as I can connect to
the DB no problem if I create and connect to the ODBC DSN on the same
machine as the MSDE installation and if I use a remote Apple Mac machine to
connect to it via a combo of a router program and the local ODBC DSN then it
works fine.
I have also eliminated the other possibilities by disabling all of the
firewalls (ie Windows' own and Norton) and ultimately when I put the full
blown version of SQL Server on the same machine the remote connection works
perfectly.
Looking through the sites it appears that you have to put
DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
queries are:
Is it a problem with the original MSDE 2000 installer being installed on a
WinXP SP2 machine or just a later version, ie MSDE SP3?
Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
SP1?
Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE 2000
installer or do you have to update it to Service Pack 3 to perform this
task?
Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
Is there anyway of patching/fixing this installation to correct it or have I
got to de-tach the DBs and re-install MSDE with this
DISABLENETWORKPROTOCOLS=0 switch in the ini?
Thanks
Hi
If you have not service packed the MSDE installation what is @.@.VERSION?
Use DISABLENETWORKPROTOCOLS=0 if you want to have the protocols
automatically enabled on a new installation see
http://msdn.microsoft.com/library/de...stsql_84xl.asp
for more.
You can enable them afterwards by running the command utility svrnetcn.exe
John
"Macsicarr" <nospam@.nospam.com> wrote in message
news:uW2w$E5jFHA.3064@.TK2MSFTNGP15.phx.gbl...
> Hi All
> Having 'Google-ised' I've found that there does appear to be a problem
> connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN),
> but
> I haven't found what the concrete solution is.
> It definitely appears to be a Windows inflicted problem, as I can connect
> to
> the DB no problem if I create and connect to the ODBC DSN on the same
> machine as the MSDE installation and if I use a remote Apple Mac machine
> to
> connect to it via a combo of a router program and the local ODBC DSN then
> it
> works fine.
> I have also eliminated the other possibilities by disabling all of the
> firewalls (ie Windows' own and Norton) and ultimately when I put the full
> blown version of SQL Server on the same machine the remote connection
> works
> perfectly.
> Looking through the sites it appears that you have to put
> DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
> queries are:
> Is it a problem with the original MSDE 2000 installer being installed on a
> WinXP SP2 machine or just a later version, ie MSDE SP3?
> Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
> SP1?
> Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE
> 2000
> installer or do you have to update it to Service Pack 3 to perform this
> task?
> Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
> Is there anyway of patching/fixing this installation to correct it or have
> I
> got to de-tach the DBs and re-install MSDE with this
> DISABLENETWORKPROTOCOLS=0 switch in the ini?
> Thanks
>
>
|||Hi John
My version of MSDE is:
Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
But I still can't get a remote LAN or WAN machine to connect to my MSDE
installation. It still says SQL Server does not exist or access denied,
even though local machine use is fine and I have no firewall security on to
block it.
I've even run the Server Network Utility (svrnetcn.exe) that you suggested
and found that Named Pipes and TCP/IP are already enabled and ready to go.
What am I doing wrong?
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:O6Rcs%237jFHA.2644@.TK2MSFTNGP09.phx.gbl...
Hi
If you have not service packed the MSDE installation what is @.@.VERSION?
Use DISABLENETWORKPROTOCOLS=0 if you want to have the protocols
automatically enabled on a new installation see
http://msdn.microsoft.com/library/de...stsql_84xl.asp
for more.
You can enable them afterwards by running the command utility svrnetcn.exe
John
"Macsicarr" <nospam@.nospam.com> wrote in message
news:uW2w$E5jFHA.3064@.TK2MSFTNGP15.phx.gbl...
> Hi All
> Having 'Google-ised' I've found that there does appear to be a problem
> connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN),
> but
> I haven't found what the concrete solution is.
> It definitely appears to be a Windows inflicted problem, as I can connect
> to
> the DB no problem if I create and connect to the ODBC DSN on the same
> machine as the MSDE installation and if I use a remote Apple Mac machine
> to
> connect to it via a combo of a router program and the local ODBC DSN then
> it
> works fine.
> I have also eliminated the other possibilities by disabling all of the
> firewalls (ie Windows' own and Norton) and ultimately when I put the full
> blown version of SQL Server on the same machine the remote connection
> works
> perfectly.
> Looking through the sites it appears that you have to put
> DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
> queries are:
> Is it a problem with the original MSDE 2000 installer being installed on a
> WinXP SP2 machine or just a later version, ie MSDE SP3?
> Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
> SP1?
> Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE
> 2000
> installer or do you have to update it to Service Pack 3 to perform this
> task?
> Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
> Is there anyway of patching/fixing this installation to correct it or have
> I
> got to de-tach the DBs and re-install MSDE with this
> DISABLENETWORKPROTOCOLS=0 switch in the ini?
> Thanks
>
>
|||I've just checked the log and it still doesn't state that it's using TCP/IP
even though the network util only has TCP/IP in the right-hand box:
2005-07-25 18:42:40.29 server SQL Server is starting at priority class
'normal'(1 CPU detected).
2005-07-25 18:42:40.60 server SQL Server configured for thread mode
processing.
2005-07-25 18:42:40.60 server Using dynamic lock allocation. [500] Lock
Blocks, [1000] Lock Owner Blocks.
2005-07-25 18:42:40.62 spid3 Starting up database 'master'.
2005-07-25 18:42:41.04 server Using 'SSNETLIB.DLL' version '8.0.194'.
2005-07-25 18:42:41.07 spid5 Starting up database 'model'.
2005-07-25 18:42:41.12 spid3 Server name is 'FREDPC'.
2005-07-25 18:42:41.12 spid3 Skipping startup of clean database id 4
2005-07-25 18:42:41.12 spid3 Skipping startup of clean database id 5
2005-07-25 18:42:41.35 spid5 Clearing tempdb database.
2005-07-25 18:42:42.54 spid5 Starting up database 'tempdb'.
2005-07-25 18:42:42.65 spid3 Recovery complete.
2005-07-25 18:42:56.09 server SQL server listening on Shared Memory,
Named Pipes. <<<<
2005-07-25 18:42:56.09 server SQL Server is ready for client connections
2005-07-25 18:43:17.17 spid51 Starting up database 'DemoData'.
2005-07-25 19:08:22.85 spid3 SQL Server is terminating due to 'stop'
request from Service Control Manager.
What am I doing wrong?
"Macsicarr" <No3@.Spam67.com> wrote in message
news:ulbflFUkFHA.3164@.TK2MSFTNGP15.phx.gbl...
Hi John
My version of MSDE is:
Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
But I still can't get a remote LAN or WAN machine to connect to my MSDE
installation. It still says SQL Server does not exist or access denied,
even though local machine use is fine and I have no firewall security on to
block it.
I've even run the Server Network Utility (svrnetcn.exe) that you suggested
and found that Named Pipes and TCP/IP are already enabled and ready to go.
What am I doing wrong?
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:O6Rcs%237jFHA.2644@.TK2MSFTNGP09.phx.gbl...
Hi
If you have not service packed the MSDE installation what is @.@.VERSION?
Use DISABLENETWORKPROTOCOLS=0 if you want to have the protocols
automatically enabled on a new installation see
http://msdn.microsoft.com/library/de...stsql_84xl.asp
for more.
You can enable them afterwards by running the command utility svrnetcn.exe
John
"Macsicarr" <nospam@.nospam.com> wrote in message
news:uW2w$E5jFHA.3064@.TK2MSFTNGP15.phx.gbl...
> Hi All
> Having 'Google-ised' I've found that there does appear to be a problem
> connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN),
> but
> I haven't found what the concrete solution is.
> It definitely appears to be a Windows inflicted problem, as I can connect
> to
> the DB no problem if I create and connect to the ODBC DSN on the same
> machine as the MSDE installation and if I use a remote Apple Mac machine
> to
> connect to it via a combo of a router program and the local ODBC DSN then
> it
> works fine.
> I have also eliminated the other possibilities by disabling all of the
> firewalls (ie Windows' own and Norton) and ultimately when I put the full
> blown version of SQL Server on the same machine the remote connection
> works
> perfectly.
> Looking through the sites it appears that you have to put
> DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
> queries are:
> Is it a problem with the original MSDE 2000 installer being installed on a
> WinXP SP2 machine or just a later version, ie MSDE SP3?
> Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
> SP1?
> Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE
> 2000
> installer or do you have to update it to Service Pack 3 to perform this
> task?
> Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
> Is there anyway of patching/fixing this installation to correct it or have
> I
> got to de-tach the DBs and re-install MSDE with this
> DISABLENETWORKPROTOCOLS=0 switch in the ini?
> Thanks
>
>
|||Hi
You need to make sure that TCP/IP is in the client protocols (using the
client network configuration utitilty on the client) as well as on the
server. You may want to try pinging the server from the client. If it
responds try using telnet to connect to the port you are using (the
default port is 1433).
You @.@.VERSION shows that no patches or service packs have been
installed. http://www.sqlsecurity.com/DesktopDe...aspx?tabid=37.
John

Can't connect remotely to MSDE 2000 DB on WinXP Home Machine

Hi All
Having 'Google-ised' I've found that there does appear to be a problem
connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN), but
I haven't found what the concrete solution is.
It definitely appears to be a Windows inflicted problem, as I can connect to
the DB no problem if I create and connect to the ODBC DSN on the same
machine as the MSDE installation and if I use a remote Apple Mac machine to
connect to it via a combo of a router program and the local ODBC DSN then it
works fine.
I have also eliminated the other possibilities by disabling all of the
firewalls (ie Windows' own and Norton) and ultimately when I put the full
blown version of SQL Server on the same machine the remote connection works
perfectly.
Looking through the sites it appears that you have to put
DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
queries are:
Is it a problem with the original MSDE 2000 installer being installed on a
WinXP SP2 machine or just a later version, ie MSDE SP3?
Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
SP1?
Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE 2000
installer or do you have to update it to Service Pack 3 to perform this
task?
Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
Is there anyway of patching/fixing this installation to correct it or have I
got to de-tach the DBs and re-install MSDE with this
DISABLENETWORKPROTOCOLS=0 switch in the ini?
ThanksHi
If you have not service packed the MSDE installation what is @.@.VERSION?
Use DISABLENETWORKPROTOCOLS=0 if you want to have the protocols
automatically enabled on a new installation see
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/distsql/distsql_84xl.asp
for more.
You can enable them afterwards by running the command utility svrnetcn.exe
John
"Macsicarr" <nospam@.nospam.com> wrote in message
news:uW2w$E5jFHA.3064@.TK2MSFTNGP15.phx.gbl...
> Hi All
> Having 'Google-ised' I've found that there does appear to be a problem
> connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN),
> but
> I haven't found what the concrete solution is.
> It definitely appears to be a Windows inflicted problem, as I can connect
> to
> the DB no problem if I create and connect to the ODBC DSN on the same
> machine as the MSDE installation and if I use a remote Apple Mac machine
> to
> connect to it via a combo of a router program and the local ODBC DSN then
> it
> works fine.
> I have also eliminated the other possibilities by disabling all of the
> firewalls (ie Windows' own and Norton) and ultimately when I put the full
> blown version of SQL Server on the same machine the remote connection
> works
> perfectly.
> Looking through the sites it appears that you have to put
> DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
> queries are:
> Is it a problem with the original MSDE 2000 installer being installed on a
> WinXP SP2 machine or just a later version, ie MSDE SP3?
> Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
> SP1?
> Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE
> 2000
> installer or do you have to update it to Service Pack 3 to perform this
> task?
> Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
> Is there anyway of patching/fixing this installation to correct it or have
> I
> got to de-tach the DBs and re-install MSDE with this
> DISABLENETWORKPROTOCOLS=0 switch in the ini?
> Thanks
>
>|||Hi John
My version of MSDE is:
Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
But I still can't get a remote LAN or WAN machine to connect to my MSDE
installation. It still says SQL Server does not exist or access denied,
even though local machine use is fine and I have no firewall security on to
block it.
I've even run the Server Network Utility (svrnetcn.exe) that you suggested
and found that Named Pipes and TCP/IP are already enabled and ready to go.
What am I doing wrong?
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:O6Rcs%237jFHA.2644@.TK2MSFTNGP09.phx.gbl...
Hi
If you have not service packed the MSDE installation what is @.@.VERSION?
Use DISABLENETWORKPROTOCOLS=0 if you want to have the protocols
automatically enabled on a new installation see
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/distsql/distsql_84xl.asp
for more.
You can enable them afterwards by running the command utility svrnetcn.exe
John
"Macsicarr" <nospam@.nospam.com> wrote in message
news:uW2w$E5jFHA.3064@.TK2MSFTNGP15.phx.gbl...
> Hi All
> Having 'Google-ised' I've found that there does appear to be a problem
> connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN),
> but
> I haven't found what the concrete solution is.
> It definitely appears to be a Windows inflicted problem, as I can connect
> to
> the DB no problem if I create and connect to the ODBC DSN on the same
> machine as the MSDE installation and if I use a remote Apple Mac machine
> to
> connect to it via a combo of a router program and the local ODBC DSN then
> it
> works fine.
> I have also eliminated the other possibilities by disabling all of the
> firewalls (ie Windows' own and Norton) and ultimately when I put the full
> blown version of SQL Server on the same machine the remote connection
> works
> perfectly.
> Looking through the sites it appears that you have to put
> DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
> queries are:
> Is it a problem with the original MSDE 2000 installer being installed on a
> WinXP SP2 machine or just a later version, ie MSDE SP3?
> Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
> SP1?
> Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE
> 2000
> installer or do you have to update it to Service Pack 3 to perform this
> task?
> Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
> Is there anyway of patching/fixing this installation to correct it or have
> I
> got to de-tach the DBs and re-install MSDE with this
> DISABLENETWORKPROTOCOLS=0 switch in the ini?
> Thanks
>
>|||I've just checked the log and it still doesn't state that it's using TCP/IP
even though the network util only has TCP/IP in the right-hand box:
2005-07-25 18:42:40.29 server SQL Server is starting at priority class
'normal'(1 CPU detected).
2005-07-25 18:42:40.60 server SQL Server configured for thread mode
processing.
2005-07-25 18:42:40.60 server Using dynamic lock allocation. [500] Lock
Blocks, [1000] Lock Owner Blocks.
2005-07-25 18:42:40.62 spid3 Starting up database 'master'.
2005-07-25 18:42:41.04 server Using 'SSNETLIB.DLL' version '8.0.194'.
2005-07-25 18:42:41.07 spid5 Starting up database 'model'.
2005-07-25 18:42:41.12 spid3 Server name is 'FREDPC'.
2005-07-25 18:42:41.12 spid3 Skipping startup of clean database id 4
2005-07-25 18:42:41.12 spid3 Skipping startup of clean database id 5
2005-07-25 18:42:41.35 spid5 Clearing tempdb database.
2005-07-25 18:42:42.54 spid5 Starting up database 'tempdb'.
2005-07-25 18:42:42.65 spid3 Recovery complete.
2005-07-25 18:42:56.09 server SQL server listening on Shared Memory,
Named Pipes. <<<<
2005-07-25 18:42:56.09 server SQL Server is ready for client connections
2005-07-25 18:43:17.17 spid51 Starting up database 'DemoData'.
2005-07-25 19:08:22.85 spid3 SQL Server is terminating due to 'stop'
request from Service Control Manager.
What am I doing wrong?
"Macsicarr" <No3@.Spam67.com> wrote in message
news:ulbflFUkFHA.3164@.TK2MSFTNGP15.phx.gbl...
Hi John
My version of MSDE is:
Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
But I still can't get a remote LAN or WAN machine to connect to my MSDE
installation. It still says SQL Server does not exist or access denied,
even though local machine use is fine and I have no firewall security on to
block it.
I've even run the Server Network Utility (svrnetcn.exe) that you suggested
and found that Named Pipes and TCP/IP are already enabled and ready to go.
What am I doing wrong?
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:O6Rcs%237jFHA.2644@.TK2MSFTNGP09.phx.gbl...
Hi
If you have not service packed the MSDE installation what is @.@.VERSION?
Use DISABLENETWORKPROTOCOLS=0 if you want to have the protocols
automatically enabled on a new installation see
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/distsql/distsql_84xl.asp
for more.
You can enable them afterwards by running the command utility svrnetcn.exe
John
"Macsicarr" <nospam@.nospam.com> wrote in message
news:uW2w$E5jFHA.3064@.TK2MSFTNGP15.phx.gbl...
> Hi All
> Having 'Google-ised' I've found that there does appear to be a problem
> connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN),
> but
> I haven't found what the concrete solution is.
> It definitely appears to be a Windows inflicted problem, as I can connect
> to
> the DB no problem if I create and connect to the ODBC DSN on the same
> machine as the MSDE installation and if I use a remote Apple Mac machine
> to
> connect to it via a combo of a router program and the local ODBC DSN then
> it
> works fine.
> I have also eliminated the other possibilities by disabling all of the
> firewalls (ie Windows' own and Norton) and ultimately when I put the full
> blown version of SQL Server on the same machine the remote connection
> works
> perfectly.
> Looking through the sites it appears that you have to put
> DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
> queries are:
> Is it a problem with the original MSDE 2000 installer being installed on a
> WinXP SP2 machine or just a later version, ie MSDE SP3?
> Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
> SP1?
> Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE
> 2000
> installer or do you have to update it to Service Pack 3 to perform this
> task?
> Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
> Is there anyway of patching/fixing this installation to correct it or have
> I
> got to de-tach the DBs and re-install MSDE with this
> DISABLENETWORKPROTOCOLS=0 switch in the ini?
> Thanks
>
>|||Hi
You need to make sure that TCP/IP is in the client protocols (using the
client network configuration utitilty on the client) as well as on the
server. You may want to try pinging the server from the client. If it
responds try using telnet to connect to the port you are using (the
default port is 1433).
You @.@.VERSION shows that no patches or service packs have been
installed. http://www.sqlsecurity.com/DesktopDefault.aspx?tabid=37.
John

Can't connect remotely to MSDE 2000 DB on WinXP Home Machine

Hi All
Having 'Google-ised' I've found that there does appear to be a problem
connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN), but
I haven't found what the concrete solution is.
It definitely appears to be a Windows inflicted problem, as I can connect to
the DB no problem if I create and connect to the ODBC DSN on the same
machine as the MSDE installation and if I use a remote Apple Mac machine to
connect to it via a combo of a router program and the local ODBC DSN then it
works fine.
I have also eliminated the other possibilities by disabling all of the
firewalls (ie Windows' own and Norton) and ultimately when I put the full
blown version of SQL Server on the same machine the remote connection works
perfectly.
Looking through the sites it appears that you have to put
DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
queries are:
Is it a problem with the original MSDE 2000 installer being installed on a
WinXP SP2 machine or just a later version, ie MSDE SP3?
Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
SP1?
Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE 2000
installer or do you have to update it to Service Pack 3 to perform this
task?
Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
Is there anyway of patching/fixing this installation to correct it or have I
got to de-tach the DBs and re-install MSDE with this
DISABLENETWORKPROTOCOLS=0 switch in the ini?
Thanks
hi,
Macsicarr wrote:
> Looking through the sites it appears that you have to put
> DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but
> my queries are:
> Is it a problem with the original MSDE 2000 installer being installed
> on a WinXP SP2 machine or just a later version, ie MSDE SP3?
just up from service pack 3/3a.. before that sp, MSDE installed enabling
network protocols..

> Is it that no MSDE 2000 installer will work on WinXP SP2 when they
> did on SP1?
both sp3 (and MSDE Rel A) and sp4 can be installed on WinXP sp2..

> Can you use this DISABLENETWORKPROTOCOLS=0 command on the original
> MSDE 2000 installer or do you have to update it to Service Pack 3 to
> perform this task?
the very first package did not support that parameter, that is new with sp3
(and MSDE Rel A)

> Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
0= enable network protocols

> Is there anyway of patching/fixing this installation to correct it or
> have I got to de-tach the DBs and re-install MSDE with this
> DISABLENETWORKPROTOCOLS=0 switch in the ini?
>
you can enable the desired network protocol you can use the Server Network
Utility (svrnetcn.exe)
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hi Andrea
My version of MSDE is:
Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
But I still can't get a remote LAN or WAN machine to connect to my MSDE
installation. It still says SQL Server does not exist or access denied,
even though local machine use is fine and I have no firewall security on to
block it.
I've even run the Server Network Utility (svrnetcn.exe) that you suggested
and found that Named Pipes and TCP/IP are already enabled and ready to go.
What am I doing wrong?
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3kfaa4Ftvsl3U1@.individual.net...
hi,
Macsicarr wrote:
> Looking through the sites it appears that you have to put
> DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but
> my queries are:
> Is it a problem with the original MSDE 2000 installer being installed
> on a WinXP SP2 machine or just a later version, ie MSDE SP3?
just up from service pack 3/3a.. before that sp, MSDE installed enabling
network protocols..

> Is it that no MSDE 2000 installer will work on WinXP SP2 when they
> did on SP1?
both sp3 (and MSDE Rel A) and sp4 can be installed on WinXP sp2..

> Can you use this DISABLENETWORKPROTOCOLS=0 command on the original
> MSDE 2000 installer or do you have to update it to Service Pack 3 to
> perform this task?
the very first package did not support that parameter, that is new with sp3
(and MSDE Rel A)

> Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
0= enable network protocols

> Is there anyway of patching/fixing this installation to correct it or
> have I got to de-tach the DBs and re-install MSDE with this
> DISABLENETWORKPROTOCOLS=0 switch in the ini?
>
you can enable the desired network protocol you can use the Server Network
Utility (svrnetcn.exe)
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||I've just checked the log and it still doesn't state that it's using TCP/IP
even though the network util only has TCP/IP in the right-hand box:
2005-07-25 18:42:40.29 server SQL Server is starting at priority class
'normal'(1 CPU detected).
2005-07-25 18:42:40.60 server SQL Server configured for thread mode
processing.
2005-07-25 18:42:40.60 server Using dynamic lock allocation. [500] Lock
Blocks, [1000] Lock Owner Blocks.
2005-07-25 18:42:40.62 spid3 Starting up database 'master'.
2005-07-25 18:42:41.04 server Using 'SSNETLIB.DLL' version '8.0.194'.
2005-07-25 18:42:41.07 spid5 Starting up database 'model'.
2005-07-25 18:42:41.12 spid3 Server name is 'FREDPC'.
2005-07-25 18:42:41.12 spid3 Skipping startup of clean database id 4
2005-07-25 18:42:41.12 spid3 Skipping startup of clean database id 5
2005-07-25 18:42:41.35 spid5 Clearing tempdb database.
2005-07-25 18:42:42.54 spid5 Starting up database 'tempdb'.
2005-07-25 18:42:42.65 spid3 Recovery complete.
2005-07-25 18:42:56.09 server SQL server listening on Shared Memory,
Named Pipes. <<<<
2005-07-25 18:42:56.09 server SQL Server is ready for client connections
2005-07-25 18:43:17.17 spid51 Starting up database 'DemoData'.
2005-07-25 19:08:22.85 spid3 SQL Server is terminating due to 'stop'
request from Service Control Manager.
What am I doing wrong?
"Macsicarr" <No3@.Spam67.com> wrote in message
news:e4aBmFUkFHA.3164@.TK2MSFTNGP15.phx.gbl...
Hi Andrea
My version of MSDE is:
Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
But I still can't get a remote LAN or WAN machine to connect to my MSDE
installation. It still says SQL Server does not exist or access denied,
even though local machine use is fine and I have no firewall security on to
block it.
I've even run the Server Network Utility (svrnetcn.exe) that you suggested
and found that Named Pipes and TCP/IP are already enabled and ready to go.
What am I doing wrong?
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3kfaa4Ftvsl3U1@.individual.net...
hi,
Macsicarr wrote:
> Looking through the sites it appears that you have to put
> DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but
> my queries are:
> Is it a problem with the original MSDE 2000 installer being installed
> on a WinXP SP2 machine or just a later version, ie MSDE SP3?
just up from service pack 3/3a.. before that sp, MSDE installed enabling
network protocols..

> Is it that no MSDE 2000 installer will work on WinXP SP2 when they
> did on SP1?
both sp3 (and MSDE Rel A) and sp4 can be installed on WinXP sp2..

> Can you use this DISABLENETWORKPROTOCOLS=0 command on the original
> MSDE 2000 installer or do you have to update it to Service Pack 3 to
> perform this task?
the very first package did not support that parameter, that is new with sp3
(and MSDE Rel A)

> Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
0= enable network protocols

> Is there anyway of patching/fixing this installation to correct it or
> have I got to de-tach the DBs and re-install MSDE with this
> DISABLENETWORKPROTOCOLS=0 switch in the ini?
>
you can enable the desired network protocol you can use the Server Network
Utility (svrnetcn.exe)
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||hi,
Macsicarr wrote:
> Hi Andrea
> My version of MSDE is:
> Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
> Aug 6 2000 00:57:48
> Copyright (c) 1988-2000 Microsoft Corporation
> Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
and this is MSDE retail version (RTM) on WinXP sp2

> But I still can't get a remote LAN or WAN machine to connect to my
> MSDE installation. It still says SQL Server does not exist or access
> denied, even though local machine use is fine and I have no firewall
> security on to block it.
are you sure the Windows Firewall, automatically enabled when installing
WinXP sp2, is not trapping you?

> I've even run the Server Network Utility (svrnetcn.exe) that you
> suggested and found that Named Pipes and TCP/IP are already enabled
> and ready to go.
MSDE retail version default behavior...
try a telnet connection on the MSDE port..
c:\..\>telnet ComputerName port_used_by_MSDE
if the screen becomes black you are connected to MSDE...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||HI Andrea
Thanks for the prompt reply.
In Windows Firewall it is set to Off. Although I would have thought
Microsoft would dim the other tabs (eg Exceptions and Advanced) seeing as
I've turned the firewall off I'm presuming that these have no effect.
The problem I have is that the error log quite clearly states that it is
listening on Shared Memory and Named Pipes - no TCP/IP is mentioned. Why is
this so?
The telnet test confirmed that it couldn't connect.
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3kkp0tFull7hU1@.individual.net...
hi,
Macsicarr wrote:
> Hi Andrea
> My version of MSDE is:
> Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
> Aug 6 2000 00:57:48
> Copyright (c) 1988-2000 Microsoft Corporation
> Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
and this is MSDE retail version (RTM) on WinXP sp2

> But I still can't get a remote LAN or WAN machine to connect to my
> MSDE installation. It still says SQL Server does not exist or access
> denied, even though local machine use is fine and I have no firewall
> security on to block it.
are you sure the Windows Firewall, automatically enabled when installing
WinXP sp2, is not trapping you?

> I've even run the Server Network Utility (svrnetcn.exe) that you
> suggested and found that Named Pipes and TCP/IP are already enabled
> and ready to go.
MSDE retail version default behavior...
try a telnet connection on the MSDE port..
c:\..\>telnet ComputerName port_used_by_MSDE
if the screen becomes black you are connected to MSDE...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hello,
You may need to backup you registry file first, then check if you have the
following registry key:
HKLM/Software/Microsoft/Microsoft SQL
Server/mssql$<instancename>/MSSQLServer/SuperSocketNetLib/Tcp/
If not, add above registry key. Restart SQL server. Check the SQL log again
to see if it is listening on the TCP port.
The following articles are for your reference:
841251 How to enable SQL Server connectivity on Windows XP Service Pack 2
http://support.microsoft.com/?id=841251
841252 How to manually enable TCP/IP on Windows XP Service Pack 2 for SQL
http://support.microsoft.com/?id=841252
328306 Potential causes of the "SQL Server does not exist or access denied"
http://support.microsoft.com/?id=328306
I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.
This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/tec...rview/40010469
Others: https://partner.microsoft.com/US/tec...pportoverview/
If you are outside the United States, please visit our International
Support page:
http://support.microsoft.com/common/international.aspx
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.

Can't connect remotely to MSDE 2000 DB on WinXP Home Machine

Hi All
Having 'Google-ised' I've found that there does appear to be a problem
connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN), but
I haven't found what the concrete solution is.
It definitely appears to be a Windows inflicted problem, as I can connect to
the DB no problem if I create and connect to the ODBC DSN on the same
machine as the MSDE installation and if I use a remote Apple Mac machine to
connect to it via a combo of a router program and the local ODBC DSN then it
works fine.
I have also eliminated the other possibilities by disabling all of the
firewalls (ie Windows' own and Norton) and ultimately when I put the full
blown version of SQL Server on the same machine the remote connection works
perfectly.
Looking through the sites it appears that you have to put
DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
queries are:
Is it a problem with the original MSDE 2000 installer being installed on a
WinXP SP2 machine or just a later version, ie MSDE SP3?
Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
SP1?
Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE 2000
installer or do you have to update it to Service Pack 3 to perform this
task?
Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
Is there anyway of patching/fixing this installation to correct it or have I
got to de-tach the DBs and re-install MSDE with this
DISABLENETWORKPROTOCOLS=0 switch in the ini?
ThanksHi
If you have not service packed the MSDE installation what is @.@.VERSION?
Use DISABLENETWORKPROTOCOLS=0 if you want to have the protocols
automatically enabled on a new installation see
http://msdn.microsoft.com/library/d...
4xl.asp
for more.
You can enable them afterwards by running the command utility svrnetcn.exe
John
"Macsicarr" <nospam@.nospam.com> wrote in message
news:uW2w$E5jFHA.3064@.TK2MSFTNGP15.phx.gbl...
> Hi All
> Having 'Google-ised' I've found that there does appear to be a problem
> connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN),
> but
> I haven't found what the concrete solution is.
> It definitely appears to be a Windows inflicted problem, as I can connect
> to
> the DB no problem if I create and connect to the ODBC DSN on the same
> machine as the MSDE installation and if I use a remote Apple Mac machine
> to
> connect to it via a combo of a router program and the local ODBC DSN then
> it
> works fine.
> I have also eliminated the other possibilities by disabling all of the
> firewalls (ie Windows' own and Norton) and ultimately when I put the full
> blown version of SQL Server on the same machine the remote connection
> works
> perfectly.
> Looking through the sites it appears that you have to put
> DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
> queries are:
> Is it a problem with the original MSDE 2000 installer being installed on a
> WinXP SP2 machine or just a later version, ie MSDE SP3?
> Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
> SP1?
> Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE
> 2000
> installer or do you have to update it to Service Pack 3 to perform this
> task?
> Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
> Is there anyway of patching/fixing this installation to correct it or have
> I
> got to de-tach the DBs and re-install MSDE with this
> DISABLENETWORKPROTOCOLS=0 switch in the ini?
> Thanks
>
>|||Hi John
My version of MSDE is:
Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
But I still can't get a remote LAN or WAN machine to connect to my MSDE
installation. It still says SQL Server does not exist or access denied,
even though local machine use is fine and I have no firewall security on to
block it.
I've even run the Server Network Utility (svrnetcn.exe) that you suggested
and found that Named Pipes and TCP/IP are already enabled and ready to go.
What am I doing wrong?
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:O6Rcs%237jFHA.2644@.TK2MSFTNGP09.phx.gbl...
Hi
If you have not service packed the MSDE installation what is @.@.VERSION?
Use DISABLENETWORKPROTOCOLS=0 if you want to have the protocols
automatically enabled on a new installation see
http://msdn.microsoft.com/library/d...
4xl.asp
for more.
You can enable them afterwards by running the command utility svrnetcn.exe
John
"Macsicarr" <nospam@.nospam.com> wrote in message
news:uW2w$E5jFHA.3064@.TK2MSFTNGP15.phx.gbl...
> Hi All
> Having 'Google-ised' I've found that there does appear to be a problem
> connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN),
> but
> I haven't found what the concrete solution is.
> It definitely appears to be a Windows inflicted problem, as I can connect
> to
> the DB no problem if I create and connect to the ODBC DSN on the same
> machine as the MSDE installation and if I use a remote Apple Mac machine
> to
> connect to it via a combo of a router program and the local ODBC DSN then
> it
> works fine.
> I have also eliminated the other possibilities by disabling all of the
> firewalls (ie Windows' own and Norton) and ultimately when I put the full
> blown version of SQL Server on the same machine the remote connection
> works
> perfectly.
> Looking through the sites it appears that you have to put
> DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
> queries are:
> Is it a problem with the original MSDE 2000 installer being installed on a
> WinXP SP2 machine or just a later version, ie MSDE SP3?
> Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
> SP1?
> Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE
> 2000
> installer or do you have to update it to Service Pack 3 to perform this
> task?
> Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
> Is there anyway of patching/fixing this installation to correct it or have
> I
> got to de-tach the DBs and re-install MSDE with this
> DISABLENETWORKPROTOCOLS=0 switch in the ini?
> Thanks
>
>|||I've just checked the log and it still doesn't state that it's using TCP/IP
even though the network util only has TCP/IP in the right-hand box:
2005-07-25 18:42:40.29 server SQL Server is starting at priority class
'normal'(1 CPU detected).
2005-07-25 18:42:40.60 server SQL Server configured for thread mode
processing.
2005-07-25 18:42:40.60 server Using dynamic lock allocation. [500] Lo
ck
Blocks, [1000] Lock Owner Blocks.
2005-07-25 18:42:40.62 spid3 Starting up database 'master'.
2005-07-25 18:42:41.04 server Using 'SSNETLIB.DLL' version '8.0.194'.
2005-07-25 18:42:41.07 spid5 Starting up database 'model'.
2005-07-25 18:42:41.12 spid3 Server name is 'FREDPC'.
2005-07-25 18:42:41.12 spid3 Skipping startup of clean database id 4
2005-07-25 18:42:41.12 spid3 Skipping startup of clean database id 5
2005-07-25 18:42:41.35 spid5 Clearing tempdb database.
2005-07-25 18:42:42.54 spid5 Starting up database 'tempdb'.
2005-07-25 18:42:42.65 spid3 Recovery complete.
2005-07-25 18:42:56.09 server SQL server listening on Shared Memory,
Named Pipes. <<<<
2005-07-25 18:42:56.09 server SQL Server is ready for client connections
2005-07-25 18:43:17.17 spid51 Starting up database 'DemoData'.
2005-07-25 19:08:22.85 spid3 SQL Server is terminating due to 'stop'
request from Service Control Manager.
What am I doing wrong?
"Macsicarr" <No3@.Spam67.com> wrote in message
news:ulbflFUkFHA.3164@.TK2MSFTNGP15.phx.gbl...
Hi John
My version of MSDE is:
Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
But I still can't get a remote LAN or WAN machine to connect to my MSDE
installation. It still says SQL Server does not exist or access denied,
even though local machine use is fine and I have no firewall security on to
block it.
I've even run the Server Network Utility (svrnetcn.exe) that you suggested
and found that Named Pipes and TCP/IP are already enabled and ready to go.
What am I doing wrong?
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:O6Rcs%237jFHA.2644@.TK2MSFTNGP09.phx.gbl...
Hi
If you have not service packed the MSDE installation what is @.@.VERSION?
Use DISABLENETWORKPROTOCOLS=0 if you want to have the protocols
automatically enabled on a new installation see
http://msdn.microsoft.com/library/d...
4xl.asp
for more.
You can enable them afterwards by running the command utility svrnetcn.exe
John
"Macsicarr" <nospam@.nospam.com> wrote in message
news:uW2w$E5jFHA.3064@.TK2MSFTNGP15.phx.gbl...
> Hi All
> Having 'Google-ised' I've found that there does appear to be a problem
> connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN),
> but
> I haven't found what the concrete solution is.
> It definitely appears to be a Windows inflicted problem, as I can connect
> to
> the DB no problem if I create and connect to the ODBC DSN on the same
> machine as the MSDE installation and if I use a remote Apple Mac machine
> to
> connect to it via a combo of a router program and the local ODBC DSN then
> it
> works fine.
> I have also eliminated the other possibilities by disabling all of the
> firewalls (ie Windows' own and Norton) and ultimately when I put the full
> blown version of SQL Server on the same machine the remote connection
> works
> perfectly.
> Looking through the sites it appears that you have to put
> DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
> queries are:
> Is it a problem with the original MSDE 2000 installer being installed on a
> WinXP SP2 machine or just a later version, ie MSDE SP3?
> Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
> SP1?
> Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE
> 2000
> installer or do you have to update it to Service Pack 3 to perform this
> task?
> Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
> Is there anyway of patching/fixing this installation to correct it or have
> I
> got to de-tach the DBs and re-install MSDE with this
> DISABLENETWORKPROTOCOLS=0 switch in the ini?
> Thanks
>
>|||Hi
You need to make sure that TCP/IP is in the client protocols (using the
client network configuration utitilty on the client) as well as on the
server. You may want to try pinging the server from the client. If it
responds try using telnet to connect to the port you are using (the
default port is 1433).
You @.@.VERSION shows that no patches or service packs have been
installed. http://www.sqlsecurity.com/DesktopD...aspx?tabid=37.
John

Thursday, March 8, 2012

Can't debug proc after Sp2 on WinXP

Cant create table

Saturday, February 25, 2012

Can't connet to MSDE with Query Analyzer

Can't connet to MSDE with Query Analyzer

Can't connet to MSDE with Query Analyzer

Can't connet to MSDE with Query Analyzer

Tuesday, February 14, 2012

Can't connect to MSDE with Query Analyzer

Sunday, February 12, 2012

Can't connect to MSDE

Can't connect to MSDE

Can't connect to MSDE

Friday, February 10, 2012

Can't connect remotely to MSDE 2000 DB on WinXP Home Machine

Can't connect remotely to MSDE 2000 DB on WinXP Home Machine

Can't connect remotely to MSDE 2000 DB on WinXP Home Machine

Can't connect remotely to MSDE 2000 DB on WinXP Home Machine

Can't connect remotely to MSDE 2000 DB on WinXP Home Machine

Can't connect remotely to MSDE 2000 DB on WinXP Home Machine

Can't connect remotely to MSDE 2000 DB on WinXP Home Machine

connect from ASP app

Blog Archive

About Me