Discover the answers to Frequently Asked Questions about ImageGear Medical below.
If you get a "AccuSoft License Manager couldn't communicate with the licensing Web Service." error (it doesn't have to look exactly like this): when licensing versions 12-16 of ImageGear Pro, you will need to use a modified version of our License Manager. The older versions of our products pointed to our older licensing server. Use our updated Legacy License Manager.
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 email@example.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.
No, although if you run an Accusoft licensing utility (as opposed to an OEM key) that will communicate with the Accusoft servers to place a license on your machine. That's it. When you run your code, network access to Accusoft servers is not necessary.
Using the link below, login using the email address and password you used to register the product. The earlier installers are here: http://support.accusoft.com/support/UpdateCenter/s_Product_Archive.aspx
- Open Windows Explorer and type ftp://ftp.jpg.com/ into the Navigation Bar.
- Right Click inside Windows Explorer to bring up the standard context menu.
- Find "Login As" and click it to login to FTP Server.
- Provide the user name: support and the password: 853ae90f
The Tagged Image File Format (TIFF) is widely popular, and is particularly used in document imaging. It can support a number of compression types:
- Packbits - Created by Apple, this lossless compression type is used for run-length encoding (RLE). Baseline TIFF readers must support this compression. Use this compression for higher compatibility with various applications.
- CCITT (Huffman encoding) - Used particularly for encoding bitonal (or bi-level) images. "Group 3" and "Group 4" are particularly known for its use with fax transmission of images. Using this compression type will help keep smaller file sizes.
- LZW - A lossless compression type that supports multiple bit depths. Because it's lossless, it produces files that are generally larger than other compressions. Use this compression if you want to retain the exact visual quality of the image without data loss or artifacts.
- JPEG - Very popular compression, used for color and grayscale images and can produce high compression ratios. JPEG allows a good amount of control over how the image in question should be compressed. Use this compression for general color or grayscale images.
- Deflate - A lossless compression using Huffman and LZ77 techniques and also supports different bit depths.
While using our Server Licensing Utility (SLU) to register runtime licenses with machines using your applications you will be asked for a License Configuration file. This file can be obtained by following these instructions:
- Log in.
- Go to your Products tab.
- Click the product/version you want to license.
- Click deployment.
- Click License.
- Click License pools.
- Click “Generate Config File” for the product you would like a config file for.
To find your license for any of our SDK products (on Windows), navigate to the Registry Editor. You can reach this by visiting the Start Search bar and typing “regedit”. From there, navigate to: HKEY_LOCAL_MACHINE -> SOFTWARE -> ACCUSOFT -> Licensing -> Accusoft You will see several keys that look something like this: 5-43-22 If you double click on these values, you will get a dialog box with the Value Data already selected for you. This data is useful for Support Engineers when diagnosing SDK Licensing Issues. Each license stored in the registry is located in a key with a unique name. The name identifies key attributes of the license (Product, Version, Features) in the format ***-***-***. The first number specifies the product, the second number specifies the platform, and the third specifies the version. Below is a breakdown of each Product, and its corresponding product ID: 1 – IMAGE_GEAR 2 – VISIQUEST 3 – IMAGE_GEAR_DOT_NET 4 – NETVUE 5 – IMAGE_GET_DOT_NET_MFA 6 – BARCODEXPRESS 7 – IMAGXPRESS 8 – TWAINPRO 9 – PRINTPRO 10 – THUMBNAILXPRESS 11 – NOTATEXPRESS 12 – PDFXPRESS 13 – OCRXPRESS 14 – MICRXPRESS 15 – SMARTZONE_ICR 16 – FORMFIX 17 – SCANFIX 18 – ISISXPRESS 21 – IMAGE_GEAR_JAVA 22 – FORMDIRECTOR 23 – SMARTZONE_OCR So, using the same example as above, 5-43-22: 5 corresponds to ImageGear.NET , 43 is what type of Platform you’re on (Win32, Win64, Linux, etc.). 43 specifies that this license is for any CPU. 22 is what version of the product the license is for. In this case, it’s ImageGear.NET v22.
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.
Currently, our only product that supports XFA PDF content is ImageGear Professional for Windows DLL.
There are a couple reasons why a license might stop working. The most common would be if the MAC addresses changed (on a virtual machine, or after significant hardware change). Additionally, a temporary two week license can be put on a machine via the Server Licensing Utility if there are no licenses available when you license a machine. Feel free to contact support at firstname.lastname@example.org if you have additional questions. If you want a new license please contact email@example.com.
If you are receiving a "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.
This error happens if a particular deployment machine doesn't have the COMDLG32.OCX file registered. To fix this: 1. Install the comdlg.ocx dependency, if not available on the target machine. If the comdlg.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). 2. Place the file in the C:\Windows\System32 folder. (C:\Windows\SysWOW64 on a 64 bit machine) 3. Register the DLL via the regsvr32.exe command. 4. You should see a successful message and then be able to proceed with the licensing installation.