Thought prompt: if a seemingly unrelated component (antivirus, network mount) occasionally blocks writes, what failure modes could produce a numeric error like 6007?
If none of the above resolves error 6007, provide the following to Hexagon PPM Support (formerly Intergraph):
Note: Do not attempt to manually edit the CADWorx database using Access or SQL editors unless explicitly guided by Hexagon support, as this may permanently corrupt the project.
If CADWorx crashed previously, it may have left behind an .MDW file, which acts as a lock.
If you have tried all the above steps and still see error 6007, gather the following and submit a support ticket:
Hexagon (formerly Intergraph) has dedicated tools like CADWorx Database Validator not publicly available – support engineers can run remote diagnostics.
CADWorx relies on a centralized project database (Microsoft Access or SQL Server) to store line numbers, component properties, and specifications. If this database gets corrupted due to a sudden power loss, network interruption, or improper shutdown, CADWorx throws Error 6007.
If none work, check the CADWorx.log file (in the project folder or temp folder) — it often gives more detail after error 6007.
Would you like a step-by-step guide for a specific CADWorx version (e.g., 2018, 2020, 2023)?
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.
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) error number 6007 cadworx
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.
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.
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 number 6007 in CADWorx is a licensing-related issue typically triggered when the software fails to communicate with the license server or hardware lock. This specific code often appears alongside other "6000-series" errors (like 6050) when using a network key, such as the HASP HL. Primary Causes of Error 6007
The error most commonly stems from a failure in the client-server handshake for license verification. Common triggers include:
Server Unavailability: The license server is offline or unreachable due to network outages.
Network Configuration Issues: The workstation cannot resolve the server's location or IP address.
License Path Ambiguity: CADWorx is searching for a local hardware lock instead of a network license, or vice versa.
Missing or Incorrect Configuration Files: The nethasp.ini file, which directs CADWorx to the correct license manager, is either missing, misconfigured, or not in the proper directory. Steps to Resolve the Error Resource constraints: Check disk space, file locks, and
To fix Error 6007, technicians generally follow these structured troubleshooting steps as outlined in the Intergraph HASP Support Guide:
Modify the nethasp.ini FileThe most effective fix is to force the client machine to point directly to the server by editing the nethasp.ini file.
Location: For CADWorx users, this file is usually found in the Utilities folder (e.g., C:\CADWorx 20xx\Utilities).
Modification: Ensure the following parameters are correctly set under the [NH_TCPIP] section: NH_TCPIP = Enabled NH_SERVER_ADDR = [Server IP Address]
NH_USE_BROADCAST = Disabled (this forces a direct connection rather than a broad search).
Deployment: Copy the modified nethasp.ini file into the AutoCAD root folder to ensure it is prioritized during startup. Verify Network Connection
Open a command prompt on the workstation and ping the server’s IP address to ensure a physical connection exists.
Ensure the workstation and server are on the same network or subnet if broadcast searching is still active. Check Hardware Lock (ESL) Data
Use the HASP ESL Maintenance Utility found in the CADWorx Program Group to check module authorization.
If you use both local and network locks, remember that CADWorx prioritizes local locks first. If a local lock is present but lacks the necessary module authorization, the software will trigger an error instead of checking the network lock. Remove any unauthorized local hardware keys before launching. License Manager Update
Run the HASP SRM or Sentinel Runtime utility (often included in the CADWorx installation media) on the server to ensure the license manager is running the latest version. Alternative Interpretations
While largely a licensing issue in the CADWorx/Intergraph ecosystem, similar "6007" codes in other software (like Backendless) refer to missing resources. In CADWorx, however, if your licensing is confirmed as healthy but you still see errors when placing components, it may instead indicate a missing or corrupted specification (.SPC) file or a broken path to the project's support folders.
AI responses may include mistakes. For financial advice, consult a professional. Learn more
Error Code 6007 returned when requesting a file - File Service - Backendless Support
Understanding and Resolving Error Number 6007 in CADWorx In the specialized field of plant design and engineering, CADWorx stands as a cornerstone for 3D modeling and intelligent drawing production. However, like any sophisticated software, it is prone to technical interruptions that can stall a project's momentum. One such disruption is Error Number 6007, an error typically encountered during the startup or operation of CADWorx Plant. This error primarily signals a failure in the software’s ability to communicate with its licensing system or an underlying database configuration. The Technical Nature of Error 6007
At its core, Error 6007 is often a licensing or initialization error. When CADWorx launches, it performs a "handshake" with the Hexagon (formerly Intergraph) Licensing Service to verify that the user has a valid seat or network license. If this handshake is interrupted—due to network latency, a hung license process, or incorrect environment variables—the software throws Error 6007.
In some contexts, this error can also point to a mismatch in project configuration files. If CADWorx is attempting to load a specification or a project database (.prj file) that is corrupted or resides on a server path that the user does not have permission to access, the initialization sequence fails, resulting in this specific numeric code. Primary Causes Several factors can trigger this interruption:
License Service Communication: The most common culprit is that the SPLM (SmartPlant License Manager) or the newer Intergraph Licensing Service is not running or is blocked by a firewall. If none of the above resolves error 6007,
Configuration Pathing: CADWorx relies heavily on defined paths for its libraries. If the Support or Library folders are moved or mapped to an unavailable network drive, the system triggers 6007.
Administrative Permissions: CADWorx requires specific read/write access to registry keys and local folders. Without "Run as Administrator" privileges or proper Windows permissions, the software cannot complete its startup routine. Strategies for Resolution
To resolve Error 6007, users should follow a tiered troubleshooting approach:
Restart Licensing Services: Access the Windows Services panel and ensure the Intergraph Licensing Service is active. Often, simply stopping and restarting this service clears "stuck" license heartbeats.
Verify Data Paths: Using the CADWorx Plant Setup tool, verify that all paths for the Specification Directory and the Library Directory are valid and accessible.
Clean Registry Entries: In persistent cases, the CADWorx profile in the Windows Registry may become corrupted. Clearing the user profile (after a backup) and allowing CADWorx to rebuild it upon the next launch often solves deep-seated initialization errors.
Firewall Exceptions: Ensure that the ports used by the license server (typically 5093 or 5099) are open for both inbound and outbound traffic. Conclusion
While Error Number 6007 can be a frustrating bottleneck for designers, it is rarely a sign of permanent data loss. It is a diagnostic signal that the bridge between the software and its essential resources—be it a license or a configuration file—has been severed. By systematically checking the licensing environment and file pathing, CADWorx users can quickly restore their modeling environment and maintain project schedules.
In CADWorx, Error 6007 is a licensing and hardware lock error that occurs when the software fails to pull a valid license from the designated server or local hardware key. It is categorized within the 6000-series of licensing errors, often appearing alongside similar codes like 6050. Root Causes of Error 6007
The primary cause is a communication failure between the CADWorx client machine and the HASP (Hardware Against Software Piracy) license manager. This typically happens for several reasons:
Network Disconnection: The client machine is not on the same network as the license server.
Remote License Search Failure: The software cannot automatically locate the network key across subnets.
Module Authorization Conflict: If a local hardware lock is plugged in but doesn't have the required module authorized, CADWorx may fail to check the network lock, leading to a licensing error.
Incorrect Setup: The software is pointing to the wrong IP address or server for its licensing data. Resolution Strategies
To resolve Error 6007, users should follow a systematic troubleshooting process:
Verify Network Connectivity: Use the command prompt to ping the license server to ensure the client machine has a stable connection.
Configure nethasp.ini: If the software still fails to find the license, you must manually force the connection. Locate the nethasp.ini file (typically found in the Assidrv folder) and modify it to point directly to the Server IP Address. Adjust Sentinel Admin Control Center Settings: Access the Sentinel keys management page. Navigate to the Access to Remote License Managers tab.
Check Aggressive Search for Remote Licenses and enter the specific Server IP.
Hardware Lock Audit: Use the HASP ESL Maintenance Utility or Pulse (found in the CADWorx Program Group or Support folder) to check which modules are active on your hardware lock. Ensure that multiple local hardware locks are not plugged into the same machine, as this can cause reading conflicts.
For more specific guidance, you can refer to the official Hexagon PPM Documentation on error numbers. HASP Support Guide - Green and Red Network Key - Intergraph