Showing posts with label SQLServer Install. Show all posts
Showing posts with label SQLServer Install. Show all posts

Wednesday, January 10, 2018

The action 'Move' did not complete

User might see below error when trying to failover the SQLServer instance from one node to another node. User might have recently installed a SQLServer cluster which has more than 1 node.

SQL Server cluster failover fails with Error Code: 0x80071398



The main reason for this error is the node where you are trying to failover might NOT the owner.

You need to verify all nodes in the Cluster are selected as Owenrs under “SQLServer Virtual Name” properties. As you see below screen shot, 2 nodes are not not part of the cluster . Once you check the box you will be able to failover SUCCESSFULLY without any issues.





Thanks
Satishbabu Gunukula
https://sqlserver-expert.com

Monday, July 16, 2012

Configure SQLServer to listen on a Static port or Multiple Static Ports

Dynamic port is used by named instance only. By default the named instance listens on Dynamic port.  When you start the SQL server for the first time, it requests for port from O/S and it is allocated to SQL Server. This port information is written into the windows registry.  
Every time you start the named SQLServer, it uses the port that is allocated. In case if the port is used by another program then SQL Server chooses another port at the time of restart.
You will receive “Error ID 10048” If the port is used by another program.
Static Port, If you configure an SQLServer instance to use a static port then you should restart the instance to take effect of changes and all clients must send their request to static port
By default, the default instance listens on fixed TCP Port 1433. The default instance of SQLServer does not support dynamic port allocation, but can also make the default instance to listen on multiple static ports.  The named instances of SQL Server support allocation of both static and dynamic ports
Follow these steps to configure Static TCP Port
1.      Click Start à All Programsà Microsoft SQLServer à Configuration Tools à Launch  “SQLServer Configuration Manager”
2.      Under “SQLServer Network Configuration” à Select “Protocols for <Instance Name” à Got to TCP/IP Properties
3.      Select “IP Addresses Tab” à Go to “IPAll” section
4.      Remove TCP Dynamic ports and update TCP Port: <Static port>
For ex: - 5000
Restart the SQLServer to take effect of new Static port.
You can configure the SQLServer to listen on multiple Static TCP Ports. Adding Additional ports to SQL Server will increase the performance of the SQL Server.
Follow these steps to configure additional TCP ports:
1.      Click Start à All Programsà Microsoft SQLServer à Configuration Tools à Launch  “SQLServer Configuration Manager”
2.      Under “SQLServer Network Configuration” à Select “Protocols for <Instance Name” à Got to TCP/IP Properties
3.      Select “IP Addresses Tab” à Go to “IPAll” section
4.      Enter the additional port separated by a comm for TCP ports
For ex:- TCP Port: 1234,5000
Verify the port configuration
1.      You should be able to see the new port information in error.log file

Server is listening on [ <IP Address> <Port Number>].
For ex: - Server is listening on [ <10.10.10.10> <ipv4>  <5000>].

If you have configured multiple static TCP ports then you should see below information in error.log file
  Server is listening on [ <IP Address> <Port Number>].
  Server is listening on [ <IP Address> <Port Number>].

  For ex: - Server is listening on [ 10.10.10.10 <ipv4> 1234].
   Server is listening on [ 10.10.10.10 <ipv4> 5000].
2.      You can also check the updated port information in “regedit
Start Registery (regedt32.exe) and locate the following registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\<InstanceName>\MSSQLServer\SuperSocketNetLib\Tcp
In case of 2005,
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\<MSSQL.x>\MSSQLServer\SuperSocketNetLib\Tcp\IPAll
If the allocated port is Static then you should see below values
TCPDynamicPorts = Blank
TCPPort = New Static port

If the allocated port is Dynamic then you should see below values
TCPDynamicPorts = Current used port
TCPPort = Current used port

To configure a static port for the specialized Dedicated Administrator Connection (DAC), you must update the registry key that corresponds to your instance.  For ex:-  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQLServer\ MSSQL.X\MSSQL Server\SuperSocketNetLib \AdminConnection\Tcp

Where X indicates the number

Please note that it is not recommended that named instance listen on port 1433

Regards,
Satishbabu Gunukula

Sunday, July 31, 2011

Add or Remove a node in SQLServer 2005 Failover Cluster

You need to follow the steps in case of adding or removing a node in a cluster or recover a failed node in a failover cluster environment. In case of node1 failure, the SQL Server failover cluster fails over to node2. Use Cluster administrator to evict node from cluster.

You may receive following error while adding or removing a node to the existing cluster.

Setup failed to start on the remote machine. Check the Task scheduler event log on the remote machine.

Error message from event log:-

"SQL Server Remote Setup .job" (setup.exe) 5/20/2011 10:15:00 PM ** ERROR **
Unable to start task.
The specific error is:
0×80070005: Access is denied.


Solution: You might be connected via Remote Desktop and you may have some active remote desktop session. Please note that you must close all your RDP sessions before proceeding to installation.

To add or remove a node you must be a local administration on all the nodes of the failover cluster.

Step 1. Add a node to the Cluster
• Assign the quorum
• Run Add node wizard in Custer administrator from new node
• Provide Cluster service account password to add the node
• On the New Node assign the clustered drives used by SQLServer and verify the node recognizes the cluster drives
• The drive where you install SQLServer should have same driver letter as other nodes

Step 2. Add or remove a node in SQL Server 2005 Cluster
• Login to the surviving Node or active node of the SQLServer Cluster
• Click Add or Remove Programs in Control Panel
• Select the Microsoft SQL Server 2005 and click change
• The SQL Server 2005 Installation Wizard starts
• On the Component Selection page, select the SQL Server 2005 instance name to change and click next
• On Feature Maintenance page select a Database Engine component to change and click next
• SQL Server 2005 System Configuration Checker starts
• On the Microsoft SQL 2005 Welcome screen click next
• The System Configuration Checker scans the existing configuration on the computer
• Review the warnings and error messages, correct the errors as needed and click next
• On the Change or Remove Instance page, click Maintain the Virtual Server.
• On the Cluster Node Configuration page select the node from the available nodes list and click add . To remove a node from the failover cluster, select the node and click remove.
• In Remote Account Information, provide the password of the user currently logged in(This user should be a local admin on all the nodes) and click next
• Enter the service account username/password for each listed service and click next.
• On Error and Usage Report page, do not select anything and click next
• On the Ready to Install page, click install
• On the Completing the Microsoft SQL Server Installation Wizard page, you can review the summary log by clicking on the link provided. To exit from Installation wizard click Finish.

Step 3.Install the Workstation Components and Service packs
• Run the setup.exe from Installation CD or software dump
• Install only workstation components (note that these are not part of the cluster)
• All nodes in a failover cluster must be at same service pack version, install the service packs as same as servicing node or active node.

Regards,
Satishbabu Gunukula
http://www.sqlserver-expert.com