Error Number 6007 Cadworx May 2026

Error number 6007 in CADWorx is almost always solvable without reinstalling the software. In most cases, the cause is a leftover lock file (.ldb/.laccdb) or a spec database in need of compaction. By following the structured approach above—deleting lock files, compacting the database, checking permissions, and adjusting security software—you can return to productive piping design within minutes.

Remember: when error 6007 appears, the database is not permanently broken. Stay calm, work through the solutions methodically, and you will recover your workflow. Implement the preventive measures, and this error will become a rare nuisance rather than a daily roadblock.

Keywords used: error number 6007 cadworx, CADWorx database error, fix error 6007, CADWorx spec file corruption, CADWorx lock file, compact and repair CADWorx spec.

The CADWorx Error Number 6007 is a critical licensing error indicating that a valid Intergraph CAS hardware lock (ESL/HASP key) cannot be found. This typically prevents the software from launching or causes it to crash during initialization. What Causes Error 6007?

This error occurs when the CADWorx application attempts to verify your authorization but fails for one of the following reasons:

Missing Hardware Lock: The physical USB dongle (HASP HL) is not plugged into the computer.

Network Connection Issues: For floating licenses, the client machine cannot reach the license server.

Driver Failure: The HASP driver is outdated, corrupted, or not running. error number 6007 cadworx

Conflicting Locks: Multiple local locks are attached, or a local lock is present without the necessary module authorization, causing CADWorx to ignore the network lock. How to Fix CADWorx Error 6007 1. Verify Physical Connections If you use a standalone local lock:

Ensure the Intergraph CAS HL is firmly plugged into a working USB port.

Remove any secondary local hardware locks; CADWorx only reads from one local lock at a time. 2. Update the HASP Driver Outdated drivers are a frequent culprit.

Download and install the latest HASP HL driver from the Hexagon Smart Support portal.

Restart your computer after installation to ensure the driver service starts correctly. 3. Force Network Connection (For Network Licenses)

If your license is on a server, you may need to manually point the software to it:

Locate the nethasp.ini file in the CADWorx Assidrv or Support folder. Error number 6007 in CADWorx is almost always

Edit the [NH_TCPIP] section to set NH_SERVER_ADDR = [Your_Server_IP] and set NH_USE_BROADCAST = Disabled.

Copy this modified file into your CAD platform's root folder (e.g., the AutoCAD folder) to ensure it is prioritized. 4. Run the ESL Maintenance Utility

Use this tool to check what modules are actually authorized on your key:

Run Pulse.exe (found in the CADWorx Support folder) or the HASP ESL Maintenance Utility.

Click Show ESL Data to confirm your specific CADWorx module (e.g., Plant Professional) is active. 5. Check Firewall and Antivirus

Firewalls often block the communication port used by the license manager (typically Port 1947).

Add an exception for the HASP License Manager in your Windows Firewall settings. Keywords used: error number 6007 cadworx, CADWorx database

Temporarily disable antivirus software to see if it is interfering with the HASP service. Still seeing the error?

If these steps don't work, verify that your license has not expired or been moved to the newer Intergraph Smart License (ISL) system, which replaced many older hardware locks after August 2020.

Are you using a standalone USB dongle or a floating network license for your CADWorx installation? HASP Support Guide - Green and Red Network Key - Intergraph

Error 6007 often appears when a drawing cannot find its assigned spec.

Procedure:

If your CADWorx project and specs reside on a network drive (common in multi-user environments), high latency, intermittent disconnections, or insufficient read/write permissions will produce error 6007.

In multi-user environments, if a user’s session ends unexpectedly (e.g., power loss), a "lock" file or a pending transaction might remain in the project database (SQL or Access backend), preventing subsequent access to that record and generating the 6007 error.