Troubleshooting Licensing

This section reviews potential issues you may experience during the licensing process:

General Notes
End User Has No Internet Connection
Internet Connection Is Temporarily Broken During Installation
Transferring ImageGear License onto a New Hardware System
Reinstallation of ImageGear-Based Application onto the Same Hardware System
The End User's Windows Registry Changed (Licensing Info Lost)
Unable to Obtain a License Using the License Manager
Trying to Run the SLU, I get a ”Component ‘COMDLG32.OCX’ or one of its dependencies not correctly registered” error
“80040154 Class Not Registered” Error when Using the License Development Kit on IIS

General Notes

Some general notes about licensing you should be aware of:

This was designed as an Internet-based licensing process. It is best if your end users have an Internet connection to get a License Key. The only exceptions are if you are a User License Licensee, or if you are distributing licenses manually on a very limited basis.
Once an application is licensed, no further Internet connection or interaction is required until you re-install the system or restore a previously backed-up system onto new hardware.
End Users are blocked from using the same Access Key to install the same application on different hardware. This is to prevent piracy.
A lightweight Licensing Component will grant a grace period to your end user whenever there is a licensing issue for any reason. You can modify the end user instructions to solve the problem.

End User Has No Internet Connection

User License level licensing or manual licensing is required if applications are going to be deployed to end users who will never have an Internet connection. Please be advised that manual licensing requires interaction on your part when installing the application on the end-user system.

Internet Connection Is Temporarily Broken During Installation

In this case, the auto-licensing method will return an error, and the grace period will be activated. The grace period will allow your application to function normally during a limited period of time, and you will need to repeat the licensing process (either manual, or automatic after connection is restored).

Transferring ImageGear License onto a New Hardware System

Currently there is no way to move a license key from one machine to another. Once a license key is tied to a machine, you can remove it from the machine (using the License Manager or manually deleting it from the registry), but that will not credit a license to your account. That said, if you run into an issue where you have licensed a machine by mistake, please contact sales@accusoft.com, as they will work with you. We understand this is a current limitation of our licensing system, and don't want you to be adversely affected.

Also, typically a development license comes with three “keys”, so if you want to license an additional machine, you most likely can. Run and log in to the License Manager and you can see the number of license keys remaining.

Reinstallation of ImageGear-Based Application onto the Same Hardware System

In this case, the license will be either found in the registry, or obtained from Deployment Licensing Service, regardless of when it was last requested.

The End User's Windows Registry Changed (Licensing Info Lost)

In general, if the registry is corrupted it might make sense to reinstall the application or even the entire system. But if the licensing info is the only data deleted from the registry, the licensing process that is executed as a part of the installation/registration can be repeated to retrieve a License Key from the Deployment Licensing Service.

Unable to Obtain a License Using the License Manager

One possibility is that you have strict firewall settings that are preventing our License Manager from connecting with licensing.accusoft.com, our licensing server. In order to connect with licensing.accusoft.com you'll have to make an exception in your firewall for our License Manager so that it can connect to licensing.accusoft.com on port 80 for http and port 443 for https.

Trying to Run the SLU, I get a ”Component ‘COMDLG32.OCX’ or one of its dependencies not correctly registered” error

This error happens if a particular deployment machine doesn't have the COMDLG32.OCX file registered. To fix this:

Install the comdlg32.ocx dependency, if not available on the target machine. If the comdlg32.ocx is not present on the system than it will need to be obtained from a system that has it (it should be available on your development machine in the directory mentioned in step 2).
Place the file in the C:\Windows\System32 folder. (C:\Windows\SysWOW64 on a 64-bit machine).
Register the DLL via the regsvr32.exe command.
You should see a successful message and then be able to proceed with the licensing installation.

“80040154 Class Not Registered” Error when Using the License Development Kit on IIS

If you are receiving an "80040154 Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG))." error while trying to use the LDK on a website created through IIS, it is likely because of a platform conflict (x32 vs x64). To fix it, try checking (or unchecking) "Enable 32-Bit Applications" for the App Pool associated with the website.