About Me

My photo
I am an MCSE in Data Management and Analytics, specializing in MS SQL Server, and an MCP in Azure. With over 19+ years of experience in the IT industry, I bring expertise in data management, Azure Cloud, Data Center Migration, Infrastructure Architecture planning, as well as Virtualization and automation. I have a deep passion for driving innovation through infrastructure automation, particularly using Terraform for efficient provisioning. If you're looking for guidance on automating your infrastructure or have questions about Azure, SQL Server, or cloud migration, feel free to reach out. I often write to capture my own experiences and insights for future reference, but I hope that sharing these experiences through my blog will help others on their journey as well. Thank you for reading!

Unable to find a volume with enough disk space for file extraction.



Issue:-

Sometime while extracting SQL Server setup file, the extraction do not gets complete successfully, because of less space on C:\ drive.

By default any SQL Server setup file, extract to C:\temp folder, and if C:\drive does not have space the setup  extraction gets fail with below error Message. 





Resolution:-

 In order to resolve this issue 

In order to extract file to specified location you can issue below command



>setup.exe /extract :< destination drive location>
Example:-

D:\abcd>SQLServer2014SP1-KB3058865-X64-ENU.exe /extract:D:\abcd

here abcd is a folder in D:\ drive and setup will extract to D:\abcd folder.






hence just by passing above command extraction will occur on another drive.


Thanks for reading.. 
Labels:

The availability replica for availability group 'Win2k12AG' on this instance of SQL Server cannot become the primary replica because the WSFC cluster was started in Force Quorum mode. Consider performing a forced manual failover (with possible data loss).


Error:-
The availability replica for availability group 'Win2k12AG' on this instance of SQL Server cannot become the primary replica because the WSFC cluster was started in Force Quorum mode. Consider performing a forced manual failover (with possible data loss).

Read more »
Labels:

Error Message:

Sometime after some maintenance you will find Windows cluster services are up on nodes,however  when you try to bring Cluster core resources online, it will not come up and kerberos status says -- When trying to update a password,return status indicates that the value provided as the current password is not correct.
And resultant CNO is in failed state..  



In order to resolve this issue,
->you have to make sure all required Firewall ports (Inbound and outbound) are open on Active directory server.
->you have to make sure all required Firewall ports (Inbound and outbound) are open on all corresponding nodes of cluster
--> Important ports are:-

Service Protocol port
ICMP ICMP
RDP Endpoint Mapper TCP 135
RDP Dynamic Assignment TCP 6000-6199
LDAP TCP/UDP 389
LDAP over SSL TCP 636
Global catalog LDAP TCP 3268
Global catalog LDAP TCP 3269
SMB over IP(Microsoft-DS) TCP/UDP 445
Kerberos change/set password TCP/UDP 464
Kerberos  TCP/UDP 88
DNS TCP/UDP 53
NTP TCP/UDP 123

After engaging Firewall team, they opened all firewall ports and then the issue resolved...
now Kerberos status started showing OK.



Hence issue got resolved, Cluster Core Resources started successfully and Status shows online.
And i was successfully able to move Cluster core resource from one node to another node.

Thanks for reading..

These 2 blogs can also help in troubleshooting step by step..

https://blogs.technet.microsoft.com/askcore/2012/03/27/why-is-the-cno-in-a-failed-state/

https://blogs.technet.microsoft.com/coremusketeers/2016/03/03/cluster-name-object-failed-repairing-it-gives-the-password-does-not-meet-the-password-policy-requirements/

Labels: , , ,
Subscribe to: Posts (Atom)