How to diagnose and resolve Save errors in BricsCAD

Save failures in BricsCAD can be diagnosed and resolved by determining whether the problem is caused by file integrity, permissions, security software, network mapping, or OS level restrictions.

Understanding how BricsCAD saves a DWG file

BricsCAD does not overwrite an existing DWG file directly. It uses the following process:

  1. Create a temporary file in the destination folder.
  2. Rename the existing .dwg to .bak.
  3. Rename the temporary file to .dwg.
Note: If any step is blocked, the save operation fails. In most cases, this indicates an external file system restriction, not drawing corruption.

Common causes

  • Security software restrictions
    • Windows Controlled Folder Access or third-party security software can block create, write, or rename operations. This causes save failures in protected folders, such as Documents, while saving to the Desktop or other local test folders succeeds.
    • Possible error: "File not found. Check the file name and try again."
  • Directory or file permissions
    • You have read rights but lack create, write, delete or rename rights.
    • Target file or folder is marked read-only.
  • Network and mapped-drive instability
    • Non-native drive mapping (synchronization clients, VPN utilities) interferes with locking and renaming behavior.
    • An intermittent connection drop interrupts the transaction sequence.
    • The file appears temporarily locked during the rename phase.
  • Path length limits
    • The effective path exceeds Windows limits (commonly 260 characters in constrained environments).
    • Deep nesting or a long filename causes the save operation to fail.
  • Add-on, module or lock file interference
    • Third-party plugins or LISP interfere with save calls.
    • Stale .dwl lock files after crash or session interruption.
    • Optional module loading overhead causes conflicts in specific environments.
  • Drawing database issues
    • Corruption or invalid objects can fail save transaction late in the process.

How to troubleshoot

BricsCAD checks
  • Create a new blank DWG file and save it to the same destination (for file and location isolation).
  • Open the original file from network, then use the Save As option to specify a local path (for network and local isolation).
  • Save the file to a short local path, such as C:\Test\, to test the path length impact.
  • Set the CHECKDWLPRESENCE system variable to 1 to validate active and stale lock files.
  • Set the LOADMECHANICAL2D and DEMANDLOAD system variables to 0, then retest.
  • Start BricsCAD in Safe Mode without plugins or LISP.
  • Run _AUDIT and _PURGE commands, fix any errors and retest the save operation.

System checks
  • In Windows Security, go to Virus & threat protection, then Ransomware protection, and allow bricscad.exe through Controlled folder access.
  • Add BricsCAD exclusions in third-party antivirus and security tools for write and rename operations.
  • Verify if you have create, write, delete and rename permissions in the target folder.
  • Confirm that the target DWG file and its parent folder are not read-only.
  • Remap the shared location using native Windows SMB (avoid third-party mapped-drive methods).
  • Test by saving locally to rule out network drops.
  • Boot Windows in Safe Mode to isolate OS level and background interference.

How to gather data for a support request

If the issue persists, create a support request including the following information:

  • The exact error message and the full destination path.
  • Set the QAFLAGS system variable to 256, reproduce the error, press the F2 key, and copy the full command history.
  • The result of the short local path test (C:\Test\).
  • The network mapping method and the result of the native SMB remap test.
  • The permission validation results for create, write, rename and delete.
  • The Crash_report.txt file (if a crash occurred).
  • The source DWG file (if the issue is specific to the file).