How to fix Error 1814 on Windows Server 2025 / Windows 11

by

Troubleshooting Guide: SQL Server Error 1814 – Could Not Create tempdb

Why This Error Happens

This error occurs when SQL Server 2025 cannot allocate space for the tempdb data or log files during service startup, most commonly due to insufficient free disk space on the volume hosting tempdb. It can also be triggered by incorrect file path configurations (pointing to a drive that no longer exists or is unreachable), restrictive NTFS permissions on the target folder, or underlying disk-level issues such as corruption or a misconfigured storage pool in Windows Server 2025. Since tempdb is recreated fresh on every service start, any obstruction to its physical creation will halt the entire SQL Server instance from starting.

Step-by-Step Resolution Guide

Step 1: Verify Available Disk Space

  • Open File Explorer or run Get-PSDrive in PowerShell to check free space on the drive specified for tempdb (commonly T:\ or C:\).
  • If space is low, delete unnecessary files, old log files, or move other databases off the drive.
  • Check for Volume Shadow Copy (VSS) snapshots or Windows Update cache consuming unexpected space using cleanmgr.exe.

Step 2: Confirm tempdb File Path Configuration

  • Open SQL Server Configuration Manager and check the SQL Server service startup parameters (-d, -l, -e flags) for correct file paths.
  • Alternatively, start SQL Server in single-user mode via command line: sqlservr.exe -c -m -T3608 to inspect configuration without full tempdb dependency.
  • Ensure the referenced drive letter or mount point actually exists and is online in Disk Management.

Step 3: Check NTFS Permissions and Service Account Rights

  • Right-click the tempdb folder (e.g., C:\Program Files\Microsoft SQL Server\MSSQL17.MSSQLSERVER\MSSQL\DATA) and verify “Security” tab permissions.
  • Ensure the SQL Server service account (e.g., NT Service\MSSQLSERVER) has Full Control on the folder.
  • Reapply permissions if needed: icacls "D:\TempDB" /grant "NT SERVICE\MSSQLSERVER":(OI)(CI)F.

Step 4: Review Windows Event Viewer for Disk Errors

  • Open Event Viewer and navigate to Windows Logs > System and Application.
  • Look for Disk, Ntfs, or VDS Basic Provider errors occurring at the same timestamp as Error 1814.
  • Run chkdsk D: /f (replace D: with your tempdb drive) during a maintenance window if corruption is suspected.

Step 5: Relocate tempdb to a Healthy Drive

  • If the original drive is failing or full, modify the startup parameter -d and -l in SQL Server Configuration Manager to point to a new, healthy volume with sufficient space.
  • Restart the SQL Server service to force tempdb recreation at the new location.

Alternative or Verification Steps

  • After applying fixes, restart the SQL Server service and confirm it starts without Error 1814; check SQL Server Error Log (ERRORLOG file) for the line “tempdb was successfully created.”
  • As an alternative, if permissions or paths cannot be immediately fixed, temporarily point tempdb to a different drive with ample free space using startup parameters, then correct the permanent location once the underlying disk issue is resolved.