January 13, 2010 at 8:42 am
Hello SQL Guru,
I installed Microsoft SQL Server 2008 Enterprise edition in Window Server 2008 Standard edition x64 bits that run in VMWare environment.
--Enterprise Edition
--Version: 10.1.2531.0
I installed one Default instance and four named instances.
- NamedInstance01
- NamedInstance02
- NamedInstance03
- NamedInstance04
Then, I created Window Server 2008 local users account to run SQL Server services.
Login id: xxxxDBEngineUser Password: xxxxxP@ssw0rd with minimum priviledges
The NameInstance01 was running. NamedInstance02, NamedInstance03, and NamedInstance04 could not start.
Errrors:
-The request failed or the service did not respond in a timely fashion. Consult the event log or other applicable error logs for details
Window Server 2008 Events Logs
- SQL Server could not spawn FrunCM trhread. Check the SQL Server error log and the Windows events logs for iformation about possible related problems
-Event ID: 1720
SQL logs
2010-01-13 09:14:19.56 Server Error: 26023, Severity: 16, State: 1.
2010-01-13 09:14:19.56 Server Server TCP provider failed to listen on [ 'any' <ipv6> xxxx123]. Tcp port is already in use.
2010-01-13 09:14:19.57 Server Error: 17182, Severity: 16, State: 1.
2010-01-13 09:14:19.57 Server TDSSNIClient initialization failed with error 0x2740, status code 0xa. Reason: Unable to initialize the TCP/IP listener. Only one usage of each socket address (protocol/network address/port) is normally permitted.
2010-01-13 09:14:19.57 Server Error: 17182, Severity: 16, State: 1.
2010-01-13 09:14:19.57 Server TDSSNIClient initialization failed with error 0x2740, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Only one usage of each socket address (protocol/network address/port) is normally permitted.
2010-01-13 09:14:19.57 Server Error: 17826, Severity: 18, State: 3.
2010-01-13 09:14:19.57 Server Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
2010-01-13 09:14:19.57 Server Error: 17120, Severity: 16, State: 1.
2010-01-13 09:14:19.57 Server SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
Can someone help and advise.
Thanks,
January 13, 2010 at 1:03 pm
I figured out the problems. It was the port that I specified on TCP/IP.
Somehow VMWare (I suspected) did not allow the sql named instances to use the same port number.
So, I changed the port numbers each sql named instance and the database engine services run.
August 19, 2010 at 3:42 am
The problem is there is an application that uses the same port with the sql server instance. Changing the port number solves the problem.
August 19, 2010 at 4:41 am
1John19 (1/13/2010)
Somehow VMWare (I suspected) did not allow the sql named instances to use the same port number.
this is nothing to do with VMWare, the Windows Operating System will not let you use the same TCP port for each application. To see a list of currently assigned ports on the Windows server check the following file
C:\Windows\System32\Drivers\Etc\services
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
September 9, 2010 at 11:57 am
I have a two node cluster Win2008\SQL2008 and has been fine for a few months. All of a sudden now I try to fail over one instance to the other box, port 14002 in use. I assigned that port to the second instance. I had to physically reboot the server to get SQL Server to start. I have 14002 configured for the second instance AND it is using it. However when I run the query to display the port it thinks it is using it says 1433.... but... it IS using 14002. I am opening a case with MSFT on this issue.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply