Mastercam – Pre-Packaged Appset Configuration and Troubleshooting

Overview

Mastercam is a commonly used CAD/CAM application that can present challenges when deployed in a virtualized environment due to its licensing dependencies.

To simplify deployment, we provide a Pre-Packaged Mastercam 2026 Appset through the Packaging Portal. This Appset has been created and tested in a clean environment and is designed to work for most customers.

However, because Mastercam relies on licensing components that may also be used by other applications, compatibility issues can occur depending on the configuration of your environment.

This article explains the licensing components, how they are configured within the Pre-Packaged Appset, and the troubleshooting steps to follow if you experience difficulties.

1. Mastercam Licensing Components

Mastercam requires two key components:

• CodeMeter – Provides licensing functionality and communication with the configured license server.

• Sentinel Driver – Provides additional licensing functionality required by Mastercam.

Our Pre-Packaged Appset handles these components as follows:

Potential Compatibility Issues

If other applications in your environment already use CodeMeter, conflicts may occur between the virtualized CodeMeter components and those installed directly on the device.

These conflicts can prevent Mastercam from launching, communicating with its license server, or functioning correctly.

Important: Successful virtualization cannot be guaranteed in every environment. We strongly recommend testing the Pre-Packaged Appset before deploying it to production.

2. Sentinel Licensing Configuration

The Pre-Packaged Appset configures Sentinel licensing using a file named nethasp.ini.

This file contains the licensing configuration required by Mastercam and must be present in the following locations:

Location 1

C:\Program Files\Common Files\Mastercam\MastercamLicensing\nethasp.ini

Location 2

C:\Program Files\Mastercam 2026\common\Editors\CIMCOEdit\nethasp.ini

Location 3

C:\Program Files\Mastercam 2026\nethasp.ini

Verifying the Configuration

If Mastercam virtualizes successfully but experiences licensing issues:

1. Check that nethasp.ini is present in all three locations.

2. Open each file and verify that it contains the correct licensing information for your environment.

3. Confirm that the configured license server is accessible from the device.

Missing or incorrect licensing information may prevent Mastercam from obtaining a valid license.

3. CodeMeter Licensing Configuration

CodeMeter licensing is configured by adding the license server address using the CodeMeter command-line utility.

The following command can be used to register the license server:

"C:\Program Files (x86)\CodeMeter\Runtime\bin\cmu32.exe" --add-server <IP_address_or_FQDN>

Replace <IP_address_or_FQDN> with the IP address or fully qualified domain name of your CodeMeter license server.

Example using an IP address:

"C:\Program Files (x86)\CodeMeter\Runtime\bin\cmu32.exe" --add-server 192.134.2.3

Example using a server hostname:

"C:\Program Files (x86)\CodeMeter\Runtime\bin\cmu32.exe" --add-server licenseserver.unv.myuniversity.edu

Ensure that the specified license server is reachable from the device running Mastercam.

4. Troubleshooting Licensing Issues

If Mastercam fails to launch, cannot obtain a license, or does not virtualize successfully, use the following checks to help identify the cause.

Step 1 – Verify the Required Windows Services

Open Windows Services (services.msc) and check the status of the following services:

If a required service is not running, investigate why it has stopped and attempt to start it where appropriate.

Note: The services available may vary depending on the installed licensing components and their configuration.

Step 2 – Check CodeMeter WebAdmin

CodeMeter provides a local web interface that can be used to inspect its configuration and licensing status.

Open a browser on the device running Mastercam and navigate to:

http://localhost:22352/dashboard.html

If the page opens successfully, check that the CodeMeter configuration contains the correct license server information.

If the page does not open, CodeMeter may not be running or its web interface may be unavailable.

Step 3 – Check Sentinel Admin Control Center

Sentinel also provides a local web interface for inspecting its licensing configuration.

Open a browser and navigate to:

http://localhost:1947/_int_/ACC_help_index.html

If the page opens, use the available information to check the Sentinel licensing configuration.

If the page cannot be accessed, verify that the Sentinel licensing components are installed and running correctly.

Important: Access to either web interface confirms that the relevant management interface is responding. It does not necessarily confirm that Mastercam can successfully obtain a license.

Step 4 – Verify License Server Connectivity

Confirm that:

• The configured license server address is correct.

• The device can communicate with the license server.

• Any required network ports are accessible.

• The license server is running and has the appropriate licenses available.

• No conflicting CodeMeter installation is interfering with the virtualized application.

5. What to Do if Mastercam Fails to Virtualize

If Mastercam continues to fail after completing the checks above:

1. Confirm that you are using the correct Pre-Packaged Appset from the Packaging Portal.

2. Verify the CodeMeter and Sentinel licensing configurations.

3. Check for existing installations of CodeMeter that may conflict with the virtualized components.

4. Test the Appset in a clean environment, where possible, to determine whether the issue is specific to your existing configuration.

5. If the issue persists, raise a support ticket for further investigation.

When contacting Support, please include:

• A description of the issue and any error messages displayed.

• The steps required to reproduce the problem.

• Details of any existing CodeMeter or Sentinel installations.

• The troubleshooting steps already completed.

• The relevant Streaming Core log file(s) to assist with diagnosis.

Providing this information will help our Support team investigate the issue more efficiently.

6. Deployment Recommendations

We recommend initially deploying the Pre-Packaged Mastercam Appset to a test environment before making it available to end users.

This allows you to confirm that:

• Mastercam launches and operates as expected.

• Both licensing components function correctly.

• The application can communicate with the required license servers.

• No conflicts occur with other applications installed on the device.

If Mastercam cannot be virtualized reliably in your environment, you may need to consider an alternative deployment method, such as a traditional local installation.

Summary

The Pre-Packaged Mastercam 2026 Appset is intended to simplify deployment and reduce the need for customers to package the application themselves.

However, due to its reliance on CodeMeter and Sentinel licensing components, successful virtualization may depend on your existing application and licensing configuration.

We recommend validating the Appset in a test environment before production deployment. If you encounter issues, follow the troubleshooting steps in this article and contact Support with the relevant Streaming Core logs if further assistance is required.