Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!aioe.org!.POSTED!not-for-mail From: sql464 Newsgroups: comp.databases.ms-sqlserver,microsoft.public.sqlserver.server Subject: Re: IP1, IP2...IPALL Date: Fri, 18 Nov 2011 14:40:55 +0500 Organization: Aioe.org NNTP Server Lines: 29 Message-ID: References: NNTP-Posting-Host: O30Lph8q/jdGQAKU1I2W0A.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0 X-Antivirus-Status: Clean X-Notice: Filtered by postfilter v. 0.8.2 X-Antivirus: avast! (VPS 111118-0, 11/18/2011), Outbound message Xref: x330-a1.tempe.blueboxinc.net comp.databases.ms-sqlserver:810 On 18/11/2011 1:32 PM, Erland Sommarskog wrote: > sql464 (sql464@nowhere.com) writes: >> What are these IP addresses in the properties of TCP/IP in configuration >> Manager of SQL Server 2005 Standard? How do I know what to type here? >> The problem is that if I enable TCP/IP and stop/start SQL Server service >> it doesn't start. It starts only if TCP/IP is disabled. And the only >> reason I can think of is that there are strange hex numbers in the these >> IP Addresses. Can any one help me to figure out what goes in here? > > Interesting. I don't think I've ever heard of SQL Server not starting > because TCP/IP is enabled. > > Have you looked in the LOG directory of the SQL Server installation? You > should see the files ERRORLOG and ERRORLOG.1 to .6. There is one for each > time you start SQL Server. However, if SQL Server dies before it creates > the file, there is no file. So that is the first thing to check. Do you get > an Errorlog file, and in such case, is there any error message in it? If > you don't get any Errorlog, is there something else? A dump file? > I think I found the cause. SQL Server 2000 was also running on the computer and both were trying to listen to the same port so I was getting the below error in log 2011-11-18 15:27:32.80 Server Error: 26023, Severity: 16, State: 1. 2011-11-18 15:27:32.80 Server Server TCP provider failed to listen on [ 'any' 1433]. Tcp port is already in use. When I stopped SQL 2000 and changed port everything was fine.