Cannot use file because it was originally formatted with sector size 4096 and is now on a volume with sector size 8192

Error: Error details:Error installing SQL Server Database Engine Services Instance FeaturesCould not find the Database Engine startup handle.Error code: 0x851A0019 Getting the following error in Event Viewer when trying to install SQL Server… Cannot use file ‘D:\Program Files\Microsoft SQL Server\MSSQL16.MSSQLSERVER\MSSQL\DATA\mastlog.ldf’ because it was originally formatted with sector size 4096 and is now on a volume... » read more

0
Read
echiang
Could not find the Database Engine startup handle

Error: TITLE: Microsoft SQL Server 2022 Setup —————————— The following error has occurred: Could not find the Database Engine startup handle. For help, click: https://go.microsoft.com/fwlink?LinkID=2209051&ProdName=Microsoft%20SQL%20Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=16.0.1000.6&EvtType=0xD15B4EB2%25400x4BDAF9BA%25401306%254025 Issue: Unable to start SQL services. Check Windows “Event Viewer” for errors. Event Viewer Log: Cannot use file ‘D:\Program Files\Microsoft SQL Server\MSSQL16.MSSQLSERVER\MSSQL\DATA\master.mdf’ because it was originally formatted with sector size... » read more

0
Read
echiang
PowerShell to move specific files after x days

Explanation: Set the directories: Replace "C:\SourceDirectory" and "C:\DestinationDirectory" with the actual source and destination paths. Set file types: Replace ` “.txt”, “.log”` with the desired file extensions. Set the number of days: Modify $days to specify the age threshold for moving files. Get the current date: The script calculates the cutoff date by subtracting the specified number of days from the current date. Get the... » read more

0
Read
echiang
Windows Failover Cluster – Designate all nodes as possible owners

Task: Designate all nodes as possible owners for DB01 and DB02 to ensure the cluster resource comes online automatically after a failover. Steps: To designate all nodes as possible owners for resources like DB01 and DB02 in a Windows Server Failover Cluster (WSFC), you can follow these steps. This ensures that the cluster resource comes... » read more

0
Read
echiang
Apply Latest CU Update for SQL Server 2019

Note: Run the SQLServer2019-KB5039747-x64.exe file to start the patch. An GUI similar to the SQL Server Install will popup to guide you through the patch process. Make sure SQL Server services has been stopped. Make sure to restart the server after the patch has completed. After the restart, the SQL Server version should reflect what... » read more

0
Read
echiang
Windows Failover Cluster – Configure a File Share Witness

Create a Witness This sections shows how to  create a witness. In the Failover Cluster Manager, locate the new cluster resource, right click, More Actions, Configure Cluster Quorum Settings. You Begin page of the Configure Quorum Wizard Choose “Select the quorum witness” Quorum Configuration Option page. This is where you will inform the Wizard which... » read more

0
Read
echiang
Troubleshoot SQL Server AlwaysOn Failures

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

0
Read
echiang
Screen Capture on Windows

Press Windows logo key  + Shift + S for a static image snip. https://support.microsoft.com/en-us/windows/use-snipping-tool-to-capture-screenshots-00246869-1843-655f-f220-97299b865f6b

0
Read
echiang
The service did not start due to logon failure.

Error: Getting the following error when trying to set a network account to run SQL Server service. The service did not start due to logon failure. Fix: Make sure the network account has “logon as a service” permission. Enable service log on permission for Run As accounts Go to Administrative Tools and select Local Security... » read more

0
Read
echiang
MMC could not create the snap-in for Task Scheduler

Error: MMC could not create the snap-in. The snap-in might not have been installed correctly. Fix: Microsoft Management Console (MMC) is a built-in feature in Windows operating system that lets you manage snap-in on the go. Snap-ins are basic component of a console. Sometimes, snap-ins may not work properly, especially if the registry configuration of... » read more

0
Read
echiang