Re: SQL Server and SP2

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Z (Z_at_webcast.net)
Date: 11/17/04 

Date: Wed, 17 Nov 2004 14:29:09 -0800

Thank you, Jon, for replying. I did open UDP port 1434 as per your
suggestion, but it was not helpful. I also opened tcp port 445 as discussed
in the knowledge base article at http://support.microsoft.com/?id=836269. I
know sql server is not listening for tcp connections because the sql log file
does not report it. It reports only that it's listening on shared memory and
named pipes.

I'm still stuck.

"Jon Jahren" wrote:

> I understand your frustration. You've probably already done this, but just
> in case:
> - Have you opened UDP port 1434 as well as TCP port 1433? If no, try it.
> - Are you absolutely sure your client is using TCP/IP netlib to connect to
> SQL Server? If both TCP/IP and Named Pipes are enabled both on the client
> and server, you might see that Named Pipes is the one chosen in certain
> OS/SQL/Network configurations. In this case, you need to open port 445 in
> you firewall as well. Even better, specify in your connection string that
> you only want TCP/IP, for example by prefixing your server name with the
> netlib hint : "tcp:myserver".
>
> Jon Jahren
>
> "Z" <Z@webcast.net> wrote in message
> news:99E0049E-EC70-4ADA-99FB-B033C242A676@microsoft.com...
> > Hi all. I join those who have installed sp2 and have lost the ability to
> > communicate with sql server over port 1433. I have read all of the posts
> at
> > this forum and have tried all of the fixes recommended. Microsoft's
> > publication (841521) about running firewall.cpl and allowing sql server to
> > run just does not work. The registry reports that sql server is listening
> on
> > port 1433 as the static port for my named instance of sql server. The
> server
> > network utility and client network utility both show tcpip is enabled and
> set
> > for port 1433. I have applied sp3a to sql server and have run the
> > SQLCritUpdPkg_ENU.exe program that Robert Buscemi reports worked for him
> (see
> > post 6/19 below with 17 responses).
> >
> > This is terribly frustrating and a real bone-headed move on MS's part. How
> > can they ship an "upgrade" that disables their own database server, and
> then
> > come out with lame responses about running firewall.cpl as if that will
> > magically fix it? They should spend more time on serious, critical issues
> > such as this instead of the stupid dancing paper clip. And I have to
> teach
> > this stuff!
> >
> > I would very much like an answer to this problem that just works. No lies,
> > no false directions, just the plain truth about a plan of action that is
> > guaranteed to work.
>
>
>

Relevant Pages

  • Re: Efficient INSERT of rows- .NET
    ... In case Jon wants to stick with INSERT ... Group several INSERT in the same transaction. ... Each batch requires a network roundtrip, ... mean what we see as "GO" in Query Analyzer and the method you use in ADO.NET to send the command to SQL Server ...
    (microsoft.public.sqlserver.programming)
  • Re: Issues
    ... yes asp.net and sql server 2000 - database is big. ... just having a blank page saying please wait. ... Jon ...
    (microsoft.public.frontpage.client)
  • Re: SQL Server and SP2
    ... Thanks again, Jon. ... I looked through all of those bug reports and I don't ... I might try uninstalling and reinstalling sql server. ...
    (microsoft.public.sqlserver.connect)
  • Re: Changing from an Access DB
    ... Jon ... >> to the question when should you upgrade from Access. ... >> to SQL Server and then ask if your sitecan justify the cost. ...
    (microsoft.public.frontpage.client)