Can't Change TCP Port Using Configuration Manager For X64 SQL 2005 SP1 Virtual Instance
Feb 27, 2007
Hi, I hope someone can help me! I changed the TCP port that the default instance of SQL 2005 x64 SP1 is listening on and now SQL server won't start as the port is being used - no problem I say to myself, I'll just change it again, however I can't!
My problem is that I can not change the TCP Port back again using Configuration Manager - no matter what values I put in, after a restart of the instance it comes up with this in the IP Addresses tab for TCP/IP Properties and SQL Server won't start:
IP1
Active Yes
Enabled No
IP Address aaa.bbb.ccc.111
TCP Dynamic Ports
TCP Port 0
IP2
Active Yes
Enabled No
IP Address aaa.bbb.ccc.222
TCP Dynamic Ports
TCP Port 0
IP3
Active Yes
Enabled No
IP Address aaa.bbb.ccc.333
TCP Dynamic Ports
TCP Port 0
IP4
Active Yes
Enabled No
IP Address 10.1.1.1
TCP Dynamic Ports
TCP Port 0
IP5
Active Yes
Enabled No
IP Address 127.0.0.1
TCP Dynamic Ports
TCP Port 0
IPALL
TCP Dynamic Ports 2020
TCP Port 2020
Interestingly, the ip address that the server is listening on aaa.bbb.ccc.444 is not reported in the list of IP addresses in the configuration manager for this instance, yet it is when I view the available IP addresses for the other two instances - is this significant?
I have tried failing to the other node, changing it there, changing it at the console and also while logged onto the the virtual machine remote desktop, rebooting both nodes, etc, etc. There are two other instances on this cluster that are still working fine but I hvae not attempted to change the TCP ports they listen on.
I used the same method to change this default instance as I did for a named instance on a similarly configured cluster and it worked fine. How to fix this?
Regards, Mike
2007-02-27 12:03:17.69 Server Server is listening on [ aaa.bbb.ccc.444<ipv4> 2020].
2007-02-27 12:03:17.71 spid9s Starting up database 'tempdb'.
2007-02-27 12:03:17.72 Server Error: 26023, Severity: 16, State: 1.
2007-02-27 12:03:17.72 Server Server TCP provider failed to listen on [ aaa.bbb.ccc.444<ipv4> 2020]. Tcp port is already in use.
2007-02-27 12:03:17.75 Server Error: 17182, Severity: 16, State: 1.
2007-02-27 12:03:17.75 Server TDSSNIClient initialization failed with error 0x2740, status code 0xa.
2007-02-27 12:03:17.75 Server Error: 17182, Severity: 16, State: 1.
2007-02-27 12:03:17.75 Server TDSSNIClient initialization failed with error 0x2740, status code 0x1.
2007-02-27 12:03:17.75 Server Error: 17826, Severity: 18, State: 3.
2007-02-27 12:03:17.75 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.
2007-02-27 12:03:17.77 Server Error: 17120, Severity: 16, State: 1.
2007-02-27 12:03:17.77 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.
Hi, I have a problem with SQL Server 2005 Reporting Service. I installed Reporting Service in my machine. When I was trying to configure the Reporting Service, Report Manager Virtual Directory got disabled. I need to enable this Report Manager Virtual directory. I can see the disabled link for Report Manager Virtual Directory and it shows the error: Report Manager Virtual Directory is not configurable for the current mode. Kindly help me out of this problem. Thanks Subhendu
Hi, I have a problem with SQL Server 2005 Reporting Service. I installed Reporting Service in my machine. When I was trying to configure the Reporting Service, Report Manager Virtual Directory got disabled. I need to enable this Report Manager Virtual directory. I can see the disabled link for Report Manager Virtual Directory and it shows the error: Report Manager Virtual Directory is not configurable for the current mode. Kindly help me out of this problem. Thanks Subhendu
I have done a fresh sql 2012 standalone installation but the instance services are not getting reflected in SQL server configuration manager
Although I can find the instance details in services.msc and also in n/w configuration of configuration manager but in the sql services tab of config manager , it is not showing .
The hide instance is unchecked when I check the protocol properties.
After installing SQL Server Express Advanced 2012 64-bit edition, we are unable to see the 64-bit Server Network Configuration in the left pane. Â We need to edit the TCP/IP and Named Pipes to enable them. Â All that is showing is the 32-bit instance for our Acronis backups.how to view or add a SQL server instance to the Server Network Configuration msc?
I have just installed SQL 2005 enterprise and every apeared to install ok. But using SQL config manager nothing is showing up under SQL 2005 Services tab.
Hi All, I have two drive, C and D. When first time I installed SQL Server 2005, I think that I point to C drive which is having only 10 GB, instead of drive D which has bigger space. Now, I have a problem of restoring my database due to lack of space on my C drive. Can anyone guide me to change the instance of database from drive C to drive D. TIA
Hi, I have installed SQL Server 2005 Express Edition on my system. The default instance name is set as SQLEXPRESS. I want to change this to something else. Is there anyway I can do that? Thanks, pravi
I have just finished installing SQL 2005 Ent Edition on Win 2000 Adv Server, SQL2005 SP2, and SP2 Hotfix KB934458. After the installation, I could see and configure all services via SQL Configuration Manager and SQL Server Surface Area Configuration tools. This worked for a couple of days and now both configuration tools no longer detect SQL2005 components. SQL Server Surface Area Configuration issued an error that said "No SQL Server 2005 components were found on specified computer. Either no components are installed, or you are not an administrator on this computer. (SQLAC)". SQL Configuration Manager did not list any installed services. I don€™t know what caused this. Anyone has any idea? Please help! Below is the Installation Report which shows installed components.
===================================
The following components are installed on this server
Can I Install a default instance on Virtual SQL Server on a 2 node Cluster. If I already have a default instance on a different Virtual SQL Server on the same clustered Server.
What i am trying to do..
if i create 2 virtual sql Server (say sqlVi1 and sqlVi2).. i want o connect using sqlVi1 and sqlVi2..not Sqlvi1 and SQlvi2Namedinstance.
If yes..How can I do it?
Thanks in advance I Hope someone from Microsoft or MVPs will help me.
if this is not the corrcet forum...please point me the correct one
We regularly deploy our product to client's sites and install a named instance of SQL Server 2005 and Reporting Services on their Windows Server. We use the instance name "lgs" during SQL setup and it automatically ensures we have a http://server/Reports$lgs and http://server/ReportServer$lgs to work with.
A recent deployment had some trouble with their OS and we have needed to reinstall the Reporting Services component of SQL. After reinstalling, the virtual directories for Reports$lgs and ReportServer$lgs are gone. I have used the Reporting Services Configuration tool to create new virtual directories but when I enter Reports$lgs or ReportServer$lgs as the names I get an error. The error says that the virtual directories cannot
be created due to illegal characters in the names.
How can I create the same virtual dirs that would have normally been created during initial installation?
It seems to me, that the best way is to have one Environment Varible containing the name of the SQL Server, so that you can look up the configuration in the SSIS Configuration Table when you run the package.
Is this the preferable way of doing it ? I would like to hear some positive/negative comment of why chosing a configuration type instead of another.
It seems to me that putting all of the configuration in the Environment variable is harder work but most secure (server breakdown vs table corruption/database error...)
I am trying to configure the Report Manager Virtual Directory but cannot do it. In the Configure Report Server screen, the option is greyed out (there is a tick next to it to say that it has been configured, but this is greyed out too)!
Thanks for Microsoft's Windows XP Service Pack 2 and Windows Server 2003 that make the security much stronger. However, besides the invisible benefit so far, I have become the victim of this security policy.
I have several named instances of SQL 7/2000 installed in my machine. They are not visible out of the Microsoft new fire wall. I need to access the instances from outside the fire wall, but I don't know which port I should open for the instances.
From SQL online, the default instance of SQL server is connected through TCP/IP by default port 1433. I could successful open that port and made the default instance visible to outside. However, the port 1433 doesn't work for the named instances. SQL online said, the port for named instance is dynamically (by default) chosen the first time the instance is started. So, actually, I have no way to know the port.
Is there anyway that I can check the database or somewhere to get the port that is used by the named instance?
Hi all,I'm having some trouble with connecting to SQL server instance latelywithout adding a port number. I used to be able to always connect toinstance without having to input SQLSERVER,portnumber. However nowthis is not the case. I doing this through an ADO connection object,and creating the connection string. Does anyone know if there was arecent Microsoft update or patch that would've cause this to stopallowing me to connect to a SQL instance without having to put in theport information? Thanks.
I installed a new instance and changed the default tcp/ip port and configured the applications. based on request i have changed the port to default 1433. now the problem is, the instance is not coming up. Then I restored the port now its working fine. But the application user wants 1433. could you please tell me why the instances is not comming up if the port is 1433? Thanks in advance
We have default instance "MSSQLSERVER" with Port number 1433. We Installed another Instance "MGMT" on the same windows server, it came as same Port number "1433".
We decided to Change the Port number for Instance "MGMT".
1. We changed the port number for "MGMT" to like "1234"
2. After the change we did telnet to "MGMT" Instance with "1433", it worked.
3. Then we changed the Port number for Instance "MSSQLSERVER" also to like "4321".
4. After change of these setting and followed with rules framed in link as said: http://www.databasejournal.com/features/mssql/article.php/3689846
5. Now we did telnet with changed port number, it works fine.
6. We can not do telnet with Port number 1433 for both Instances "MSSQLSERVER" and "MGMT".. This is fine, what we want, and what we intent to do...
Question to MVP OR SQL Gurus:
A) If you want to change port number to Second Instance, shall we need to change for Default Instance?
B) How the port numbers will be configured? please advice.
I have opened up a port on a remote SQL instance and can see that the port is LISTENING when using the PortQry tool. I have also set the TCP port in the TCP/IP properties in the IPAll section for that instance, yet I am unable to connect and get an error of
Connection Timeout Expired. The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement. This could be because the pre-login handshake failed or the server was unable to respond back in time. The duration spent while attempting to connect to this server was - [Pre-Login] initialization=1; handshake=14998; (.Net SqlClient Data Provider)
I have done this on other instances, although they were default instances, and it has always worked fine.
I installed a default SQL Server 2012 instance on Windows Server 2012.I enabled the SQL Browser and changed the TCP port of the instance to 1435. I changed port 1433 to 1435 I was able to connect to the instance using SSMS on another server. Now I have to enter Servername,1435 to make a connection.Why does the SQL Browser not resolve the servername to the right IP address and port 1435? Why am I not able to make a connection when I enter the servername or <servername>MSSQLSERVER? Is a SQL Browser only resolving named instances?This works fine for a named instance. Is there something special about default instances or the SQL Browser?
Having problems running the BPA for 2012. We setup using a clustered environment, SQL Server installed using default instance, and a static port not 1433. When I try to run the BPA using the instance name it says it doesn't exist, and won't let me add a port number. However, if I use MSSQLSERVER as the instance name it runs with no port specified and returns results. I assume that it doesn't require a port because the default instance would pull from the Browser Service and the using MSSQLSERVER is the same as running the default on a standalone server. Are those assumptions correct?
I have TWO named SQL Server instances (on the same machine) and I need to know the port of each of them, how can I do that? Is it write to check the following:
Which one to take: "TCP Dynamic Ports" or "TCP Port"? and what is the difference between them anyways?Â
Can the two instances (or more)Â on the same machine use the same port?!
Im having a prob with enterprise manager and im hoping that you can help.
my host has moved my sql database to another server. They gave me a new IP address, but they said that I have to connect through a certain port through enterprise manager. That port is 1042 not the default 1433.
So, I created a new sql server registration using the ip address. it didnt connect, of course. I went ahead and told EM to keep the registration even though it wasnt completed. I heard that you can right click on the node on the left and choose properties to change the port number. Well every time that I right click on the bugger, it tries to connect to the sql database, not give me a choice of properties to change.
I also highlighted the thing and chose properties from the toolbar at the top. Still nothing. The only thing I do get is an option to type in the username/password. There is NO PLACE to change the port.
I even tried going into the registry and changing the default port of 1433 to 1042. NOTHING. EM still craps out and tells me the connection failed due to the db not being there or the connection was refused.
How do I get this thing to connect to the sql server?
Also, is there another program that will do what Entreprise Manager does, but isn't such a piece of......?
Hi there, I want to change the default sql-server port number 1433 to a new one. Can i do that? If yes, how? Also, i have noticed that there is no port number option in the sql server 2005 management studio login window. So, what if the server has changed its port number? Any suggestions would be appreciated. thanks
How can i define a different TCP/IP port number , other than the default 1433; to replicate the database over a firewall on the source and the destination servers ? My source servers are SQL SERVER 7.0 with SP3 on Windows NT Server 4.0 and the destination servers are SQL 2000 with SP2 on Windows 2000 .
Where do i have to make changes in SQL server and Windows NT ? And further how secured it is to use this way for security ?
hai all, I need to change the default port number of the SQL server from 1433 to some other port number. i know that it can be done thru SERVER NETWORK UTILITY. Can some one confirm that. It will be helpful. Also i want to make sure that port to given is free port. how can i find that particular port is free.
I'm trying to configure a named instances of SQL Server 2012 SP2 to have specific IP addresses and listen to that IP on port 1433. Alongside this, I have the default instance running on a different IP and listening to that on port 1433.I've managed to get them configured so that they are reachable using the IP, and looking at the log for each they are listening correctly on that IP on port 1433; in addition, the default instance connects fine using the SERVERNAME.However, when I try and connect to the named instance using the SERVERNAME/INSTANCENAME syntax, I receive the following:-
"Cannot connect to SERVERINSTANCE. Instance failure. (System.Data)"
Configuration for the TCP/IP protocol for that instance is as follows:-
Protocol Tab
Enabled= Yes Keep Alive = 30000 Listen All = No
IP addresses Tab
IP1 Active = Yes Enabled = Yes IP Address = 10.1.1.1 TCP Dynamic Ports = 0 TCP Port = 1433
[code]...
The SQL Browser service is running and prior to switching off Listen To All, I could connect to the instance remotely using the instance name.
I changed the Port of my named instance to use static port but still error log is giving two values ,why??
spid15sServer is listening on [ 'any' <ipv6> 50152]. spid15sServer is listening on [ 'any' <ipv4> 50152]. ServerServer is listening on [ ::1 <ipv6> 57518]. ServerServer is listening on [ 127.0.0.1 <ipv4> 57518].
Hi all. I have ran into a annoying situatin on sql cluster. Config is: w2k3 EE x64 r2 - two nodes sql 2005 x64 standart v2153 2instances, active-active cluster. While changing tcp port configuration of one instance (using configuration manager) I have acidentaly created that setting: - All IP dynamic port and All IP port was set to same number while separate IPs have enabled dynamic ports and does not have static port set. This situation leads to unability of starting the instance anymore. There is no need wide explanation, its quite clear - while starting instace, it was configured with static port and with dynamic port with the same number, so port conflict error takes place. Problem was how to escape from this situation. On non clustered sql is quite easy, because these settings are stored in registry and also can be changed thorough Configuration manager, easy solution. Nor on the cluster.. Modifying the registry even on both nodes was unefective, every try to start instance fails with port conflict error and bad config was saved to registry again. I wasnt able to find where this config resides and change it to corect values. I have revealed only that it is not stored in instance master DB (restoring it from backup). Looks like its held somehow by cluster service itself, but I didnt find where it should be and how to edit it. So the last possible option take place (time was against me) - reinstalation of whole clustered instance. Nice example of how one click can create you a 2 days of work... Iam still interested if there is a smooth and easy way out of this situatin:-) So if anyone knows..... If there is not, I realy warn everybody.
I have a named sql instance on SQL 2012. The issue is that the clients is having problem connecting to it when the firewall is on, this is not consistent. The connection is fine when I disabled the firewall. When I turned the Windows firewall back on, it will work for awhile and it fails. I checked the SQL configuration manager and saw that a dynamic port is assigned to the named instance. I did put that in the firewall rule and unblock it. I also put TCP 1433 and 1434 as well as the browser service port, TCPUDP 2382 and it still didn't work.What is the best way to determine what port does the named instance are listening?
connecting to a SQL Server Instance. I have a SQL server DB on a server having an Instance not running on the default port. Let's say ServerAInstanceA has the services exposed on Port 12345. When I'm trying to connect to ServerAInstanceA without specifying the port number, while I can connect from one client machine (ClientA), I am unable to connect from a different client machine (ClientB).On a side note, when I provide the port number, I can connect both from clients A and B. My question is, when I do not provide the port number, why is one client machine able to connect while the other isn't?
I have a new named instance (SQL Server 2005 x64 SP2 (Build 3159) Developer edition) setup with dynamic port selection. A default instance was also running on the server prior to the named instance setup.
SQL Server Browser service is running. Remote connections are configured on the named instance. But still remote clients can only connect when the port number is specified after the instance name (servernameinstancename,9999). Without the port number, "error 26 - Error locating Server/instance specified" is thrown.
Doesn't the SQL Server Browser service eliminate the need for clients to specify the port number? What am I missing?
