Re: SQL Event Error Bind Failed on TCP port 1433
From: Steve Foster [SBS MVP] (steve.foster_at_picamar.co.uk)
Date: 03/02/05
- Next message: Bill Peng [MSFT]: "RE: ConnectComputer error "configuring network settings""
- Previous message: sam1967_at_hetnet.nl: "WTB: Evaluation copy of SBS on DVD"
- In reply to: Marty Marshfield: "Re: SQL Event Error Bind Failed on TCP port 1433"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 02 Mar 2005 00:30:38 -0800
Marty Marshfield wrote:
> In my research and reading on this I did see something to that effect.
> But do I need to do something to resolve this?
> Is it going to affect other applications using MS SQL?
>
Well, a default installation of SBS2003 does not install SQL Server at
all, and has nothing listening on port 1433.
If you have Premium, the installation of SQL Server as the default
instance from the Premium Technologies CD is usually the next step, and at
that point, it would take port 1433.
To get multiple instances of SQL Server trying to bind to port 1433 is not
standard, and whichever SQL instance is unable to bind to 1433 is not
going to be accessible via TCP/IP (since it couldn't bind).
You almost certainly don't want this, and need to find out which instances
of SQL are trying to bind to 1433, and adjust as necessary (either by
forcing one instance to another port, or removing an un-necessary
instance) to remove the conflict.
-- Steve Foster [SBS MVP] --------------------------------------- MVPs do not work for Microsoft. Please reply only to the newsgroups.
- Next message: Bill Peng [MSFT]: "RE: ConnectComputer error "configuring network settings""
- Previous message: sam1967_at_hetnet.nl: "WTB: Evaluation copy of SBS on DVD"
- In reply to: Marty Marshfield: "Re: SQL Event Error Bind Failed on TCP port 1433"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
