We were having problems with our SQL Server so we rebooted
it and when it came back up it was listening on a
different port.
Does anyone have any idea on how this could happen?
Thanks
Kris Bilou
If you specify 0 for the port number in the server network
utility, it will use a dynamic port.
And named instances will use a dynamic port.
-Sue
On Wed, 21 Apr 2004 08:21:26 -0700, "Kris Bilou"
<kbilou@.suncor.com> wrote:
>We were having problems with our SQL Server so we rebooted
>it and when it came back up it was listening on a
>different port.
>Does anyone have any idea on how this could happen?
>Thanks
>Kris Bilou
|||I understand the dynamic ports but we were using a static
port.
When I shut it down it was using 1245 as it should and was
specified in server newtwork. When I started it back up
it used 1246.
I didn't change it and there were no errors that 1245 was
in use.
[vbcol=seagreen]
>--Original Message--
>If you specify 0 for the port number in the server network
>utility, it will use a dynamic port.
>And named instances will use a dynamic port.
>-Sue
>On Wed, 21 Apr 2004 08:21:26 -0700, "Kris Bilou"
><kbilou@.suncor.com> wrote:
rebooted
>.
>
|||Dynamic ports. See Sue's post.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
Showing posts with label port. Show all posts
Showing posts with label port. Show all posts
Monday, March 19, 2012
Can the port change automatically?
We were having problems with our SQL Server so we rebooted
it and when it came back up it was listening on a
different port.
Does anyone have any idea on how this could happen?
Thanks
Kris BilouIf you specify 0 for the port number in the server network
utility, it will use a dynamic port.
And named instances will use a dynamic port.
-Sue
On Wed, 21 Apr 2004 08:21:26 -0700, "Kris Bilou"
<kbilou@.suncor.com> wrote:
>We were having problems with our SQL Server so we rebooted
>it and when it came back up it was listening on a
>different port.
>Does anyone have any idea on how this could happen?
>Thanks
>Kris Bilou|||I understand the dynamic ports but we were using a static
port.
When I shut it down it was using 1245 as it should and was
specified in server newtwork. When I started it back up
it used 1246.
I didn't change it and there were no errors that 1245 was
in use.
>--Original Message--
>If you specify 0 for the port number in the server network
>utility, it will use a dynamic port.
>And named instances will use a dynamic port.
>-Sue
>On Wed, 21 Apr 2004 08:21:26 -0700, "Kris Bilou"
><kbilou@.suncor.com> wrote:
>
rebooted[vbcol=seagreen]
>.
>|||Dynamic ports. See Sue's post.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
it and when it came back up it was listening on a
different port.
Does anyone have any idea on how this could happen?
Thanks
Kris BilouIf you specify 0 for the port number in the server network
utility, it will use a dynamic port.
And named instances will use a dynamic port.
-Sue
On Wed, 21 Apr 2004 08:21:26 -0700, "Kris Bilou"
<kbilou@.suncor.com> wrote:
>We were having problems with our SQL Server so we rebooted
>it and when it came back up it was listening on a
>different port.
>Does anyone have any idea on how this could happen?
>Thanks
>Kris Bilou|||I understand the dynamic ports but we were using a static
port.
When I shut it down it was using 1245 as it should and was
specified in server newtwork. When I started it back up
it used 1246.
I didn't change it and there were no errors that 1245 was
in use.
>--Original Message--
>If you specify 0 for the port number in the server network
>utility, it will use a dynamic port.
>And named instances will use a dynamic port.
>-Sue
>On Wed, 21 Apr 2004 08:21:26 -0700, "Kris Bilou"
><kbilou@.suncor.com> wrote:
>
rebooted[vbcol=seagreen]
>.
>|||Dynamic ports. See Sue's post.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
Sunday, February 19, 2012
can see sql2k sp3, but cannot connect?
With Enterprise manager, I can see a remote sql 2000 sp3 instance. I can al
so
see that port 1433 is open.
But, when I try to connect to it, I get the connection could not be
estiablished.
sql server does not exist or access denied.
I have pretty much all the port except for 1433 tcp and udp blocked.
How can I troubleshoot getting this connected. It is located on my local
network - so it is not a connection problem.
--
Thanks in advance, Les CaudleI think it was a name resolution problem, with so few ports open.
When I created a registration by ip address rather than name, it connected
immediately.
Confusing that the name showed up in Enterprise Manager. Would be nice if i
t
would automatically try to use just the ip (which it must know, as it can se
e
it).
On Wed, 18 Aug 2004 19:17:14 -0500, Les Caudle <very@.tiredofspam.com> wrote:
>With Enterprise manager, I can see a remote sql 2000 sp3 instance. I can a
lso
>see that port 1433 is open.
>But, when I try to connect to it, I get the connection could not be
>estiablished.
>sql server does not exist or access denied.
>I have pretty much all the port except for 1433 tcp and udp blocked.
>How can I troubleshoot getting this connected. It is located on my local
>network - so it is not a connection problem.
so
see that port 1433 is open.
But, when I try to connect to it, I get the connection could not be
estiablished.
sql server does not exist or access denied.
I have pretty much all the port except for 1433 tcp and udp blocked.
How can I troubleshoot getting this connected. It is located on my local
network - so it is not a connection problem.
--
Thanks in advance, Les CaudleI think it was a name resolution problem, with so few ports open.
When I created a registration by ip address rather than name, it connected
immediately.
Confusing that the name showed up in Enterprise Manager. Would be nice if i
t
would automatically try to use just the ip (which it must know, as it can se
e
it).
On Wed, 18 Aug 2004 19:17:14 -0500, Les Caudle <very@.tiredofspam.com> wrote:
>With Enterprise manager, I can see a remote sql 2000 sp3 instance. I can a
lso
>see that port 1433 is open.
>But, when I try to connect to it, I get the connection could not be
>estiablished.
>sql server does not exist or access denied.
>I have pretty much all the port except for 1433 tcp and udp blocked.
>How can I troubleshoot getting this connected. It is located on my local
>network - so it is not a connection problem.
can see sql2k sp3, but cannot connect?
With Enterprise manager, I can see a remote sql 2000 sp3 instance. I can also
see that port 1433 is open.
But, when I try to connect to it, I get the connection could not be
estiablished.
sql server does not exist or access denied.
I have pretty much all the port except for 1433 tcp and udp blocked.
How can I troubleshoot getting this connected. It is located on my local
network - so it is not a connection problem.
Thanks in advance, Les Caudle
I think it was a name resolution problem, with so few ports open.
When I created a registration by ip address rather than name, it connected
immediately.
Confusing that the name showed up in Enterprise Manager. Would be nice if it
would automatically try to use just the ip (which it must know, as it can see
it).
On Wed, 18 Aug 2004 19:17:14 -0500, Les Caudle <very@.tiredofspam.com> wrote:
>With Enterprise manager, I can see a remote sql 2000 sp3 instance. I can also
>see that port 1433 is open.
>But, when I try to connect to it, I get the connection could not be
>estiablished.
>sql server does not exist or access denied.
>I have pretty much all the port except for 1433 tcp and udp blocked.
>How can I troubleshoot getting this connected. It is located on my local
>network - so it is not a connection problem.
see that port 1433 is open.
But, when I try to connect to it, I get the connection could not be
estiablished.
sql server does not exist or access denied.
I have pretty much all the port except for 1433 tcp and udp blocked.
How can I troubleshoot getting this connected. It is located on my local
network - so it is not a connection problem.
Thanks in advance, Les Caudle
I think it was a name resolution problem, with so few ports open.
When I created a registration by ip address rather than name, it connected
immediately.
Confusing that the name showed up in Enterprise Manager. Would be nice if it
would automatically try to use just the ip (which it must know, as it can see
it).
On Wed, 18 Aug 2004 19:17:14 -0500, Les Caudle <very@.tiredofspam.com> wrote:
>With Enterprise manager, I can see a remote sql 2000 sp3 instance. I can also
>see that port 1433 is open.
>But, when I try to connect to it, I get the connection could not be
>estiablished.
>sql server does not exist or access denied.
>I have pretty much all the port except for 1433 tcp and udp blocked.
>How can I troubleshoot getting this connected. It is located on my local
>network - so it is not a connection problem.
Thursday, February 16, 2012
can Profiler display port number?
Where - in SQL Server Profiler - can I see the port number that someone has used to connect to a database?
e.g. given the connect string "tcp:MACHINE1\INSTANCE7,3045" - where in Profiler does it tell me that the connection is using port 3045? I looked at "audit login" and "existing connection" but I don't see a port number...
Any other SQL/Windows tools that I can use to monitor connections to databases on specific ports?
thanks
Hi,
open ports can be monitored using the commandline tool netstat -a.
HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de
Sunday, February 12, 2012
Can not start tcp port 1433 on MSDE
I've got an installation of MSDE that insists on only allowing shared memory
access. This works fine but I would like to access th db via tcp. I have
ran SVRNETCN.exe and verified that TCP is selected. I have even verified
that the port number etc. is set in the registry. It just refuses to
avtivate tcp when I restart MSDE or the box it's runinning on.
Here's the errorlog:
2004-04-30 00:03:33.20 server Microsoft SQL Server 2000 - 8.00.884
(Intel X86)
Nov 29 2003 20:52:47
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine (Windows) on Windows NT 5.2 (Build 3790: )
2004-04-30 00:03:33.20 server Copyright (C) 1988-2002 Microsoft
Corporation.
2004-04-30 00:03:33.20 server All rights reserved.
2004-04-30 00:03:33.20 server Server Process ID is 4416.
2004-04-30 00:03:33.20 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL$SHAREPOINT\LOG\ERRORLOG'.
2004-04-30 00:03:33.30 server SQL Server is starting at priority class
'normal'(1 CPU detected).
2004-04-30 00:03:33.38 server SQL Server configured for thread mode
processing.
2004-04-30 00:03:33.38 server Using dynamic lock allocation. [500] Lock
Blocks, [1000] Lock Owner Blocks.
2004-04-30 00:03:33.40 spid3 Starting up database 'master'.
2004-04-30 00:03:34.20 server Using 'SSNETLIB.DLL' version '8.0.880'.
2004-04-30 00:03:34.21 server SQL server listening on Shared Memory.
2004-04-30 00:03:34.21 server SQL Server is ready for client connections
2004-04-30 00:03:34.21 spid5 Starting up database 'model'.
2004-04-30 00:03:34.27 spid3 Server name is 'CHEF\SHAREPOINT'.
2004-04-30 00:03:34.27 spid3 Skipping startup of clean database id 4
2004-04-30 00:03:34.27 spid3 Skipping startup of clean database id 5
2004-04-30 00:03:34.27 spid3 Skipping startup of clean database id 6
2004-04-30 00:03:34.44 spid5 Clearing tempdb database.
2004-04-30 00:03:35.35 spid5 Starting up database 'tempdb'.
2004-04-30 00:03:35.55 spid3 Recovery complete.
Where in that log do you see evidence of SQL Server "refusing to activate
tcp"? Did you really mean, "I can't connect to SQL Server on port 1433"?
If so, I would check your network/router/firewall settings before assuming
the problem is service- or machine-specific.
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"Karl Foley" <karl@.thefoleyhouse.co.uk> wrote in message
news:e3R9sIkLEHA.2456@.TK2MSFTNGP12.phx.gbl...
> I've got an installation of MSDE that insists on only allowing shared
> memory
> access. This works fine but I would like to access th db via tcp. I have
> ran SVRNETCN.exe and verified that TCP is selected. I have even verified
> that the port number etc. is set in the registry. It just refuses to
> avtivate tcp when I restart MSDE or the box it's runinning on.
> Here's the errorlog:
> 2004-04-30 00:03:33.20 server Microsoft SQL Server 2000 - 8.00.884
> (Intel X86)
> Nov 29 2003 20:52:47
> Copyright (c) 1988-2003 Microsoft Corporation
> Desktop Engine (Windows) on Windows NT 5.2 (Build 3790: )
> 2004-04-30 00:03:33.20 server Copyright (C) 1988-2002 Microsoft
> Corporation.
> 2004-04-30 00:03:33.20 server All rights reserved.
> 2004-04-30 00:03:33.20 server Server Process ID is 4416.
> 2004-04-30 00:03:33.20 server Logging SQL Server messages in file
> 'C:\Program Files\Microsoft SQL Server\MSSQL$SHAREPOINT\LOG\ERRORLOG'.
> 2004-04-30 00:03:33.30 server SQL Server is starting at priority class
> 'normal'(1 CPU detected).
> 2004-04-30 00:03:33.38 server SQL Server configured for thread mode
> processing.
> 2004-04-30 00:03:33.38 server Using dynamic lock allocation. [500] Lock
> Blocks, [1000] Lock Owner Blocks.
> 2004-04-30 00:03:33.40 spid3 Starting up database 'master'.
> 2004-04-30 00:03:34.20 server Using 'SSNETLIB.DLL' version '8.0.880'.
> 2004-04-30 00:03:34.21 server SQL server listening on Shared Memory.
> 2004-04-30 00:03:34.21 server SQL Server is ready for client
> connections
> 2004-04-30 00:03:34.21 spid5 Starting up database 'model'.
> 2004-04-30 00:03:34.27 spid3 Server name is 'CHEF\SHAREPOINT'.
> 2004-04-30 00:03:34.27 spid3 Skipping startup of clean database id 4
> 2004-04-30 00:03:34.27 spid3 Skipping startup of clean database id 5
> 2004-04-30 00:03:34.27 spid3 Skipping startup of clean database id 6
> 2004-04-30 00:03:34.44 spid5 Clearing tempdb database.
> 2004-04-30 00:03:35.35 spid5 Starting up database 'tempdb'.
> 2004-04-30 00:03:35.55 spid3 Recovery complete.
>
>
|||"Aaron Bertrand [MVP]" <aaron@.TRASHaspfaq.com> wrote in message
news:%237IBIxnLEHA.2592@.tk2msftngp13.phx.gbl...
> Where in that log do you see evidence of SQL Server "refusing to activate
> tcp"?
Thanks for the offer of help, I'm just abut ready to give up on this!
Just about here:
2004-04-30 00:03:34.20 server Using 'SSNETLIB.DLL' version '8.0.880'.
2004-04-30 00:03:34.21 server SQL server listening on Shared Memory.
2004-04-30 00:03:34.21 server SQL Server is ready for client connections
You can see it's only using shared memory.
> Did you really mean, "I can't connect to SQL Server on port 1433"?
> If so, I would check your network/router/firewall settings before assuming
> the problem is service- or machine-specific.
No. I've tried to read all the posts on here regarding the problem and have
done multiple searches on google to try and solve this problem. No matter
what I do, MSDE will not listen on TCP port 1433. Here's a quick snip of
the output of netstat -an:
Active Connections
Proto Local Address Foreign Address State
TCP 0.0.0.0:25 0.0.0.0:0 LISTENING
TCP 0.0.0.0:53 0.0.0.0:0 LISTENING
[Snip]
TCP 0.0.0.0:691 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1025 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1026 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1028 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1533 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1723 0.0.0.0:0 LISTENING
[Snip]
As you can see, no port 1433 is listening here. I have only tried
connecting to port 1433 from this machine but can't see the point of trying
another machine if I can see the port is not open. This machine does not
have any firewall software enabled\installed on it. That functionality is
being provided by a hardware device.
As the version of MSDE seems so much newer than anything else I've seen
posted I am beginning to wonder if it is some kind of security feature...
|||> As the version of MSDE seems so much newer
Yes, 880 is quite a recent patch. Care to share where you obtained it?
Anyway, run svrnetcn.exe (it should execute from command line just like
that, otherwise it's in SQL Server's Tools\Binn folder) and make sure TCP/IP
is on the enabled side. If it isn't, move it over, hit apply, and restart
SQL Server. If that doesn't help, highlight TCP/IP and hit properties.
Make sure hide server is unchecked, then try changing the default TCP port
to some other number, hit apply, restart SQL Server, then change the default
TCP port back to 1433, hit apply, and restart SQL Server.
If TCP/IP is the ONLY enabled protocol, you might try enabling named pipes
just for fun, and then see http://support.microsoft.com/?id=306865 for a
registry setting that may need a fix.
If this is the way it has worked since you installed MSDE, you might
consider uninstalling and reinstalling (from SP3a) making sure to set
DISABLENETWORKPROTOCOL=0 in the setup ini file. Your patch level of 880
leads me to believe that installing from scratch would be the cleanest
solution anyway... sometimes these one-off patches have various side effects
that simply haven't been tested (which is why they are typically not
announced and readily available to the masses).
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
|||You might also need to check to see if it is truly MSDE or is it WMSDE.. If
it is WMSDE it can only be accessed from the same machine. Based on the
instance name of SharePoint I would assume that it is really WMSDE..
http://www.microsoft.com/resources/d...us/stsf17.mspx
If you need to access/use it for other purposes and/or from other machines
you will need to upgrade the instance to full SQL server.. or another
possible option would be to use a different instance of MSDE for your other
needs.
Hope that helps,
David Copeland
Microsoft Small Business Server Support
This posting is provided "AS IS" with no warranties, and confers no rights.
"Aaron Bertrand [MVP]" <aaron@.TRASHaspfaq.com> wrote in message
news:u0HZpsyLEHA.2148@.TK2MSFTNGP09.phx.gbl...
> Yes, 880 is quite a recent patch. Care to share where you obtained it?
> Anyway, run svrnetcn.exe (it should execute from command line just like
> that, otherwise it's in SQL Server's Tools\Binn folder) and make sure
TCP/IP
> is on the enabled side. If it isn't, move it over, hit apply, and restart
> SQL Server. If that doesn't help, highlight TCP/IP and hit properties.
> Make sure hide server is unchecked, then try changing the default TCP port
> to some other number, hit apply, restart SQL Server, then change the
default
> TCP port back to 1433, hit apply, and restart SQL Server.
> If TCP/IP is the ONLY enabled protocol, you might try enabling named pipes
> just for fun, and then see http://support.microsoft.com/?id=306865 for a
> registry setting that may need a fix.
> If this is the way it has worked since you installed MSDE, you might
> consider uninstalling and reinstalling (from SP3a) making sure to set
> DISABLENETWORKPROTOCOL=0 in the setup ini file. Your patch level of 880
> leads me to believe that installing from scratch would be the cleanest
> solution anyway... sometimes these one-off patches have various side
effects
> that simply haven't been tested (which is why they are typically not
> announced and readily available to the masses).
> --
> Aaron Bertrand
> SQL Server MVP
> http://www.aspfaq.com/
>
|||"David Copeland [MSFT]" <davidcop@.online.microsoft.com> wrote in message
news:e7Aoio6LEHA.3216@.TK2MSFTNGP12.phx.gbl...
> You might also need to check to see if it is truly MSDE or is it WMSDE..
If
> it is WMSDE it can only be accessed from the same machine. Based on the
> instance name of SharePoint I would assume that it is really WMSDE..
Fantastic - That's exactly it.
I installed another instance of MSDE and this runs perfectly over TCP port
1433 as expected. I found it confusing because:
I didn't know that WMSDE was a different product to MSDE or that WMSDE
indeed even existed.
The tools are all there to enable network connectivity even though WMSDE
doesn't use them.
Thanks everyone.
access. This works fine but I would like to access th db via tcp. I have
ran SVRNETCN.exe and verified that TCP is selected. I have even verified
that the port number etc. is set in the registry. It just refuses to
avtivate tcp when I restart MSDE or the box it's runinning on.
Here's the errorlog:
2004-04-30 00:03:33.20 server Microsoft SQL Server 2000 - 8.00.884
(Intel X86)
Nov 29 2003 20:52:47
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine (Windows) on Windows NT 5.2 (Build 3790: )
2004-04-30 00:03:33.20 server Copyright (C) 1988-2002 Microsoft
Corporation.
2004-04-30 00:03:33.20 server All rights reserved.
2004-04-30 00:03:33.20 server Server Process ID is 4416.
2004-04-30 00:03:33.20 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL$SHAREPOINT\LOG\ERRORLOG'.
2004-04-30 00:03:33.30 server SQL Server is starting at priority class
'normal'(1 CPU detected).
2004-04-30 00:03:33.38 server SQL Server configured for thread mode
processing.
2004-04-30 00:03:33.38 server Using dynamic lock allocation. [500] Lock
Blocks, [1000] Lock Owner Blocks.
2004-04-30 00:03:33.40 spid3 Starting up database 'master'.
2004-04-30 00:03:34.20 server Using 'SSNETLIB.DLL' version '8.0.880'.
2004-04-30 00:03:34.21 server SQL server listening on Shared Memory.
2004-04-30 00:03:34.21 server SQL Server is ready for client connections
2004-04-30 00:03:34.21 spid5 Starting up database 'model'.
2004-04-30 00:03:34.27 spid3 Server name is 'CHEF\SHAREPOINT'.
2004-04-30 00:03:34.27 spid3 Skipping startup of clean database id 4
2004-04-30 00:03:34.27 spid3 Skipping startup of clean database id 5
2004-04-30 00:03:34.27 spid3 Skipping startup of clean database id 6
2004-04-30 00:03:34.44 spid5 Clearing tempdb database.
2004-04-30 00:03:35.35 spid5 Starting up database 'tempdb'.
2004-04-30 00:03:35.55 spid3 Recovery complete.
Where in that log do you see evidence of SQL Server "refusing to activate
tcp"? Did you really mean, "I can't connect to SQL Server on port 1433"?
If so, I would check your network/router/firewall settings before assuming
the problem is service- or machine-specific.
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"Karl Foley" <karl@.thefoleyhouse.co.uk> wrote in message
news:e3R9sIkLEHA.2456@.TK2MSFTNGP12.phx.gbl...
> I've got an installation of MSDE that insists on only allowing shared
> memory
> access. This works fine but I would like to access th db via tcp. I have
> ran SVRNETCN.exe and verified that TCP is selected. I have even verified
> that the port number etc. is set in the registry. It just refuses to
> avtivate tcp when I restart MSDE or the box it's runinning on.
> Here's the errorlog:
> 2004-04-30 00:03:33.20 server Microsoft SQL Server 2000 - 8.00.884
> (Intel X86)
> Nov 29 2003 20:52:47
> Copyright (c) 1988-2003 Microsoft Corporation
> Desktop Engine (Windows) on Windows NT 5.2 (Build 3790: )
> 2004-04-30 00:03:33.20 server Copyright (C) 1988-2002 Microsoft
> Corporation.
> 2004-04-30 00:03:33.20 server All rights reserved.
> 2004-04-30 00:03:33.20 server Server Process ID is 4416.
> 2004-04-30 00:03:33.20 server Logging SQL Server messages in file
> 'C:\Program Files\Microsoft SQL Server\MSSQL$SHAREPOINT\LOG\ERRORLOG'.
> 2004-04-30 00:03:33.30 server SQL Server is starting at priority class
> 'normal'(1 CPU detected).
> 2004-04-30 00:03:33.38 server SQL Server configured for thread mode
> processing.
> 2004-04-30 00:03:33.38 server Using dynamic lock allocation. [500] Lock
> Blocks, [1000] Lock Owner Blocks.
> 2004-04-30 00:03:33.40 spid3 Starting up database 'master'.
> 2004-04-30 00:03:34.20 server Using 'SSNETLIB.DLL' version '8.0.880'.
> 2004-04-30 00:03:34.21 server SQL server listening on Shared Memory.
> 2004-04-30 00:03:34.21 server SQL Server is ready for client
> connections
> 2004-04-30 00:03:34.21 spid5 Starting up database 'model'.
> 2004-04-30 00:03:34.27 spid3 Server name is 'CHEF\SHAREPOINT'.
> 2004-04-30 00:03:34.27 spid3 Skipping startup of clean database id 4
> 2004-04-30 00:03:34.27 spid3 Skipping startup of clean database id 5
> 2004-04-30 00:03:34.27 spid3 Skipping startup of clean database id 6
> 2004-04-30 00:03:34.44 spid5 Clearing tempdb database.
> 2004-04-30 00:03:35.35 spid5 Starting up database 'tempdb'.
> 2004-04-30 00:03:35.55 spid3 Recovery complete.
>
>
|||"Aaron Bertrand [MVP]" <aaron@.TRASHaspfaq.com> wrote in message
news:%237IBIxnLEHA.2592@.tk2msftngp13.phx.gbl...
> Where in that log do you see evidence of SQL Server "refusing to activate
> tcp"?
Thanks for the offer of help, I'm just abut ready to give up on this!
Just about here:
2004-04-30 00:03:34.20 server Using 'SSNETLIB.DLL' version '8.0.880'.
2004-04-30 00:03:34.21 server SQL server listening on Shared Memory.
2004-04-30 00:03:34.21 server SQL Server is ready for client connections
You can see it's only using shared memory.
> Did you really mean, "I can't connect to SQL Server on port 1433"?
> If so, I would check your network/router/firewall settings before assuming
> the problem is service- or machine-specific.
No. I've tried to read all the posts on here regarding the problem and have
done multiple searches on google to try and solve this problem. No matter
what I do, MSDE will not listen on TCP port 1433. Here's a quick snip of
the output of netstat -an:
Active Connections
Proto Local Address Foreign Address State
TCP 0.0.0.0:25 0.0.0.0:0 LISTENING
TCP 0.0.0.0:53 0.0.0.0:0 LISTENING
[Snip]
TCP 0.0.0.0:691 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1025 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1026 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1028 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1533 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1723 0.0.0.0:0 LISTENING
[Snip]
As you can see, no port 1433 is listening here. I have only tried
connecting to port 1433 from this machine but can't see the point of trying
another machine if I can see the port is not open. This machine does not
have any firewall software enabled\installed on it. That functionality is
being provided by a hardware device.
As the version of MSDE seems so much newer than anything else I've seen
posted I am beginning to wonder if it is some kind of security feature...
|||> As the version of MSDE seems so much newer
Yes, 880 is quite a recent patch. Care to share where you obtained it?
Anyway, run svrnetcn.exe (it should execute from command line just like
that, otherwise it's in SQL Server's Tools\Binn folder) and make sure TCP/IP
is on the enabled side. If it isn't, move it over, hit apply, and restart
SQL Server. If that doesn't help, highlight TCP/IP and hit properties.
Make sure hide server is unchecked, then try changing the default TCP port
to some other number, hit apply, restart SQL Server, then change the default
TCP port back to 1433, hit apply, and restart SQL Server.
If TCP/IP is the ONLY enabled protocol, you might try enabling named pipes
just for fun, and then see http://support.microsoft.com/?id=306865 for a
registry setting that may need a fix.
If this is the way it has worked since you installed MSDE, you might
consider uninstalling and reinstalling (from SP3a) making sure to set
DISABLENETWORKPROTOCOL=0 in the setup ini file. Your patch level of 880
leads me to believe that installing from scratch would be the cleanest
solution anyway... sometimes these one-off patches have various side effects
that simply haven't been tested (which is why they are typically not
announced and readily available to the masses).
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
|||You might also need to check to see if it is truly MSDE or is it WMSDE.. If
it is WMSDE it can only be accessed from the same machine. Based on the
instance name of SharePoint I would assume that it is really WMSDE..
http://www.microsoft.com/resources/d...us/stsf17.mspx
If you need to access/use it for other purposes and/or from other machines
you will need to upgrade the instance to full SQL server.. or another
possible option would be to use a different instance of MSDE for your other
needs.
Hope that helps,
David Copeland
Microsoft Small Business Server Support
This posting is provided "AS IS" with no warranties, and confers no rights.
"Aaron Bertrand [MVP]" <aaron@.TRASHaspfaq.com> wrote in message
news:u0HZpsyLEHA.2148@.TK2MSFTNGP09.phx.gbl...
> Yes, 880 is quite a recent patch. Care to share where you obtained it?
> Anyway, run svrnetcn.exe (it should execute from command line just like
> that, otherwise it's in SQL Server's Tools\Binn folder) and make sure
TCP/IP
> is on the enabled side. If it isn't, move it over, hit apply, and restart
> SQL Server. If that doesn't help, highlight TCP/IP and hit properties.
> Make sure hide server is unchecked, then try changing the default TCP port
> to some other number, hit apply, restart SQL Server, then change the
default
> TCP port back to 1433, hit apply, and restart SQL Server.
> If TCP/IP is the ONLY enabled protocol, you might try enabling named pipes
> just for fun, and then see http://support.microsoft.com/?id=306865 for a
> registry setting that may need a fix.
> If this is the way it has worked since you installed MSDE, you might
> consider uninstalling and reinstalling (from SP3a) making sure to set
> DISABLENETWORKPROTOCOL=0 in the setup ini file. Your patch level of 880
> leads me to believe that installing from scratch would be the cleanest
> solution anyway... sometimes these one-off patches have various side
effects
> that simply haven't been tested (which is why they are typically not
> announced and readily available to the masses).
> --
> Aaron Bertrand
> SQL Server MVP
> http://www.aspfaq.com/
>
|||"David Copeland [MSFT]" <davidcop@.online.microsoft.com> wrote in message
news:e7Aoio6LEHA.3216@.TK2MSFTNGP12.phx.gbl...
> You might also need to check to see if it is truly MSDE or is it WMSDE..
If
> it is WMSDE it can only be accessed from the same machine. Based on the
> instance name of SharePoint I would assume that it is really WMSDE..
Fantastic - That's exactly it.
I installed another instance of MSDE and this runs perfectly over TCP port
1433 as expected. I found it confusing because:
I didn't know that WMSDE was a different product to MSDE or that WMSDE
indeed even existed.
The tools are all there to enable network connectivity even though WMSDE
doesn't use them.
Thanks everyone.
Can not run SQL Server 2005 Upgrade Advisor on server that does not use the standard port
I tried creating an alias to the server to get it to connect to analyze the server but it will not recognize the SQL 2000 server as a valid server to analyze. I can use the alias to connect in EM or SSMS. Any ideas? The server is not clustered and is at SP4. I've connected to several others in my environment but this one is causing me grief!
Thanks,
Linda
After trying several other things, insuing I had the correct permissions on the destination server, one issue was discovered and that was I had permissions on the instance of SQL server I wanted to look at but not the defautl. Adding me did not fix the problem.
The fix actually came using an alias for the full default instance name and not using the "detect" button on the server entry screen. The instance name also had to be manually typed in. This worked after setting up an alias to the full instance name and not just the server name for the default instance.
Subscribe to:
Posts (Atom)