Security Compliance
ARM SQL database crash during large fileserver scan
This article explains how to resolve an issue where the ARM SQL database can crash or become unavailable during a large file server scan
First published date
3/2/2026 2:14 PM
Last published date
3/2/2026 2:14 PM
Overview
During file server scans, ARM writes large amounts of permission and structure data into the database. In large environments, using a very high number of parallel requests can overload SQL Server, causing instability or crashes during the scan
Product section
Access Rights Manager
Cause
- The problem can be caused by excessive parallel requests configured for the file server scan, which generates more simultaneous database load than the SQL Server instance can reliably handle
- Not enough resources on the SQL Server
Resolution
Resolution 1: Reduce parallel requests for the file server scan
-
Open the ARM Configuration.
-
Go to Scans and edit the affected File server scan.
-
Locate the setting that controls parallel requests
-
If the value is high (for example, 32), lower it significantly (to about 12).
-
Save the configuration and run the scan again, confirming that:
-
The scan completes, and
-
SQL Server remains stable (no crash/time outs).
-
Resolution 2: Verify SQL Server meets ARM SQL requirements
-
Confirm that the SQL Server hosting the ARM database meets the ARM SQL Server requirements (supported SQL versions, CPU, memory, storage, collation, and required roles such as
dbcreator/dbowner). -
Adjust resources or move the database to a server that fulfills these requirements if needed.
-
Re‑run the file server scan with the reduced parallel requests from Resolution 1.