Issues: SQL failover cluster automatically failing over. Windows Failover Cluster Log: Cluster node xxxxx was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration... » read more
Issue: All the sql job stuck in the state “Performing completion action” An AlwaysOn failure would sometimes cause this issue. A network glitch between SQL Server and Exchange Server can also cause this issue. Fix: Restart the SQL Agent service.
Microsoft regularly releases server or software updates to fix security problems, bugs in the software, and performance issues, or to add new features. These patches or updates are available on the Microsoft website. Microsoft regularly releases SQL server or software updates to fix security problems, bugs in the software, and performance issues, or to add... » read more
When running a validation test on a Windows Failover Cluster, drives may disappear from the cluster and file explorer if the cluster is hosting an Availability Group with iSCSI-backed disks. When you choose the default options in Validation – any storage that could be possibly shared storage is taken offline and brought into the cluster’s available... » read more
Look into the following logs… Critical Events from Failover Cluster Manager Validate Cluster Report Windows Event Viewer Quick Action: Update SQL Server to Latest Patch. Reboot server on all nodes. Critical Events from Failover Cluster Manager Cluster -> Nodes -> Show Critical Events Validate Cluster Report Cluster -> Validate Cluster -> Run all test Windows... » read more
Issue: Unable to get AlwaysOn database back online. The local availability replica is not in a state that could process the command. Verify that the availability group is online and that the local availability replica is the primary replica, then retry the command. (Microsoft SQL Server, Error: 41190) Fix: Drop AlwaysOn and re-create it. Steps:... » read more
This is one of the common errors I have seen while working with customers who are using SQL Server AlwaysOn availability groups. Once this error comes, the resource in the cluster goes to failed state and in SQL Server Management Studio, we should be an availability group in resolving state. Resolving state essentially means that... » read more
Error: When using Git, getting the following error when trying to link to a Git repository… Fix: Open up command prompt and run The above should add the safe directory to the .gitconfig file Reference: https://stackoverflow.com/questions/72978485/git-submodule-update-failed-with-fatal-detected-dubious-ownership-in-reposit
Error: Getting the following error when trying to clone a project in TortoiseGit or Visual Studio… error: unable to create file xxxxxxx: Filename too long Fix: Location your .gitconfig file Open up the .gitconfig file and add “longpaths = true”
Issue: All – Visual Studio has an issue where it saves SQL files as UTF-8-BOM as default, which causes errors when concatenating for our DBAs. Please follow the attached instructions to install the “Fix File Encoding” Extension for Visual Studio. This will fix the issue by saving your SQL files as UTF-8 (without BOM) by... » read more