Discover the answers to Frequently Asked Questions about ImagXpress below.

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. 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.
In order to determine which operating systems and versions of Visual Studio are supported in your application, please visit the documentation for your product and go to Getting Started -> System Requirements or Operating Requirements
If your ImageGear application does not initialize in a browser, the following may help to solve the issue. For ImageXpress ActiveX applications, the same general troubleshooting steps apply.
The most common cause of ActiveX controls not loading is missing dependencies.
  • Dependency Analyzer

  • Use the Dependency Analyzer to determine which JavaScript components must be associated with your IGCoreCtrl before use. Select the features of ImageGear that you are using.
    For example, to use the ART component, you must add the following associations.
    IGCoreCtl1.object.AssociateComponent( IGFormatsCtl1.object.ComponentInterface );
    IGCoreCtl1.object.AssociateComponent( IGDisplayCtl1.object.ComponentInterface );
    IGCoreCtl1.object.AssociateComponent( IGProcessingCtl1.object.ComponentInterface );
    IGCoreCtl1.object.AssociateComponent( IGArtCtl1.object.ComponentInterface );
    

  • Deployment Packaging Wizard

  • The Deployment Packaging Wizard will provide you with all required .ocx and .dll dependencies that you will need to include with your application.
    If you are using a .cab file, all of the dependencies from the wizard must be included in your .cab, and referenced inside an .INF file. See a sample .INF file.
    For more information, see Using INF Files on MSDN
  • Registering Domain-tied OEM keys
    In order to licence your product to run on a web page, your OEM licence key is added to a JavaScript file and tied to a number of domains of your choice. Log into the Web Licence Key Generator with your Accusoft username and password and follow the instructions.
    For more information, see the documentation: ActiveX Website Runtime Licensing

If you are in Visual Basic 6, set the NotateXpress Client property to the name of the ImagXpress control (example in VB6):

NotateXpress1.Client = "ImagXpress1"

If you are in another development environment, call the NotateXpress SetClientWindow method, passing the window handle of the ImagXpress control via the Hwnd property on the ImagXpress control (example in Delphi).

NotateXpress1.SetClientWindow(ImagXpress1.hWnd);

If you are using NotateXpress by reference in Visual Basic, you can call the SetClientWindow method also.

If neither of these methods are available, use the InterfaceConnect method.

(For more information, please see the page Connect to ImagXpress Client in the NotateXpress help documentation.)

Please note: You must have received unlock codes in order to distribute applications. These are received when runtimes are purchased. If you have not received them please Contact Sales.

1) If you are using the .NET interface you must call the UnlockRuntime method in the Licensing class where the application begins and pass the unlock codes as the parameters. For example:
imagXpress1.Licensing.UnlockRunTime (1234,1234,1234,1234);
2) If you are using the ActiveX control you must call the UnlockRuntime method where your application begins and pass the unlock codes as the parameters. For example:
ImagXpress1.UnlockRuntime 1234,1234,1234,1234

To copy an image from the ImagXpress 8 .NET control, you can use the ToHdib method of the ImageX class as outlined in the code samples below. The sample code assumes the image data is in 1 bit per pixel format.

For C# Developers:
PegasusImaging.WinForms.ImagXpress8.ImagXpress ix = new PegasusImaging.WinForms.ImagXpress8.ImagXpress(); PegasusImaging.WinForms.ImagXpress8.ImageX theImageX = PegasusImaging.WinForms.ImagXpress8.ImageX.FromFile("c:\\Pegasus.tif"); scanFix1.FromHdib((System.IntPtr) theImageX.ToHdib(false));
For Visual Basic. NET Developers:
Dim ix As New PegasusImaging.WinForms.ImagXpress8.ImagXpress() Dim theImageX As PegasusImaging.WinForms.ImagXpress8.ImageX theImageX = PegasusImaging.WinForms.ImagXpress8.ImageX.FromFile("c:\Pegasus.tif") ScanFix1.FromHdib(theImageX.ToHdib(False))
On Windows:
  • 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
For any other operating system, use an FTP client, such as FileZilla, using the above FTP and login information. Once you've successfully logged in, you can drop your files into the folder.
Although ImagXpress may have limited ability to load PDFs, they are no longer supported. You may find this message around the documentation:
Note: PDF support is deprecated in ImagXpress, please use PDF Xpress instead for PDF support.
We strongly recommend using PDFXpress to load the wide range of PDFs documents.
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.
You can view which camera RAW formats are supported from the products' "Support File Formats" page:
This information can be found in the Distributing ImagXpress section of the help documentation. .NET Help. ActiveX Help.
Accusoft supports 3 primary license types: Evaluation, Toolkit, and Runtime licenses.

Evaluation License:

An Evaluation license is available upon download and will allow you to try our products and determine if they will suit your needs. Most downloads include free demo applications that demonstrate the core functionality of our product and will show you how to get up and running integrating Accusoft products with your solution. While the Evaluation license is free to download it does come with some restrictions. These restrictions may come in the form of water marked documents, pop-up dialogue boxes, or a time limit on the Evaluation license itself.

Toolkit License:

Should you decide that an Accusoft product is right for you, the next step should be to purchase one or more of our Toolkit licenses. Accusoft requires each developer using an Accusoft component to have a Toolkit license on their development machine. Once registered, the Toolkit license will unlock all restrictions of the Evaluation license. Please note, the Toolkit license is strictly to be used for development purposes, and when activated, it will be tied the specific development machine that it was registered on. Understandably, the occasion may arise where a Toolkit license needs to be moved from one development machine to another. In such a scenario, please contact sales@accusoft to see if this is feasible. For more information on how to register a Toolkit license on a development machine please see the 'Toolkit Licensing' section of your products Help documentation.

Runtime License:

Finally, once you have completed your solution and are ready for deployment, you will need to purchase a Runtime license. Accusoft offers 2 types of Runtime licenses. Most commonly, you will purchase an Automatically Reported Runtime (or Node-Locked) license, which requires a license for every machine your solution will be deployed to. It is very important to note that Runtime licenses are tied to the machine they are activated on and should not be used for development purposes. Doing so will quickly use up your Runtime licenses and cannot be refunded. For more information about how to activate an Automatically Reported Runtime license, please see the ‘Automatically Reported Runtime License’ section of your products Help documentation. In certain circumstances, Accusoft will issue a Manually Reported Runtime licenses that allow you to embed all of the licensing information directly into your application. These licenses are only distributed under certain circumstances and eligibility is determined by Accusoft sales. For more information on how to activate this type of license, please see the ‘Manually Reported Runtime License' section of your products Help documentation.
A possible cause for this is if the source image has a rectangular, or uneven, X and Y resolution (for example: 200 x 300 DPI). When you pass an image to one of PrintPRO's print functions, it's treating the source content with respect to its real pixel dimensions. So, in the case of images with uneven resolution values, they may appear warped - even when specifying to maintain the aspect. To resolve this, resize the incoming image content in such a way for it to be in a square resolution (for example: 300 x 300 DPI):
            System.Drawing.Image picture = System.Drawing.Image.FromFile(samplePicture);

            Accusoft.ImagXpressSdk.ImageX scaleImage = Accusoft.ImagXpressSdk.ImageX.FromBitmap(ix, (System.Drawing.Bitmap)picture);
            Accusoft.ImagXpressSdk.Processor theProc = new Accusoft.ImagXpressSdk.Processor(ix, scaleImage);
            float bestResolution = 0;
            float scaleFactor = 0;
            float resNumerator = 0, resDenominator = 0;

            bestResolution = picture.HorizontalResolution;

            if(picture.HorizontalResolution > picture.VerticalResolution)
            {
                resNumerator = (float)picture.HorizontalResolution;
                resDenominator = (float)picture.VerticalResolution;
                bestResolution = picture.HorizontalResolution;

                scaleFactor = resNumerator / resDenominator;

                theProc.Resize(new System.Drawing.Size(picture.Width, (int)(picture.Height * scaleFactor)), Accusoft.ImagXpressSdk.ResizeType.Quality);                
            }
            else if (picture.VerticalResolution > picture.HorizontalResolution)
            {
                resNumerator = (float)picture.VerticalResolution;
                resDenominator = (float)picture.HorizontalResolution;
                bestResolution = picture.VerticalResolution;

                scaleFactor = resNumerator / resDenominator;

                theProc.Resize(new System.Drawing.Size((int)(picture.Width * scaleFactor), picture.Height), Accusoft.ImagXpressSdk.ResizeType.Quality);                
            }

            theProc.Image.Resolution.Units = System.Drawing.GraphicsUnit.Inch;
            theProc.Image.Resolution.Dimensions = new System.Drawing.SizeF(bestResolution, bestResolution);
            picture = theProc.Image.ToBitmap(true);

            ...

            //Other parameters to this function call would be provided by your application
            job.PrintImage(picture, new System.Drawing.PointF(startXPoint, startYPoint), new System.Drawing.SizeF(printWidth, printHeight), true);
There are a number of cleanup operations that you can use to make an image more suitable for a particular application. What you observe visually on the image and how you perceive its impact on your project is the most important. For example, if you’re noticing very many random specks on your image, and you’re planning to use OCR, then you may want to try a depseckle or blob removal operation first. If the content in your image looks a bit slanted, you could try a deskew or rotate operation. In some cases, using a line removal operation on forms that have grid fields could be helpful also. The amount of image cleaning you may need to do can very from project to project. There’s not a one shot cleaning operation that will always work for all images. But, observe the nature of the noise and interference in your images to determine what general parameters appear to provide the best results.
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:
  1. Log in.
  2. Go to your Products tab.
  3. Click the product/version you want to license.
  4. Click deployment.
  5. Click License.
  6. Click License pools.
  7. Click “Generate Config File” for the product you would like a config file for.
Information on the SLU can be found here: http://help.accusoft.com/ImagXpress/v13.0/dotnet/webframe.html#Server%20Licensing%20Utility.html Information on the Licensing Configuration File can be found here: http://help.accusoft.com/ImagXpress/v13.0/dotnet/webframe.html#License%20Configuration%20Files.html  
The downloaded development kit includes code samples for supported platforms. Samples are available through the Start > Programs > Accusoft > ImagXpress menu.
Please refer to the "How To" section in the User Guide section of the appropriate Help File (.NET or ActiveX) for sample code showing the use of the control.
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.
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 support@accusoft.com if you have additional questions. If you want a new license please contact sales@accusoft.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. enable32
There are a few reasons why this might happen:
  1. You have licensed your machine with a runtime/deployment license and you are not calling the SetSolutionName and SetSolutionKey methods in your code. By default, Accusoft products will look for a license in the registry at this path: HKEY_LOCAL_MACHINE\SOFTWARE\Accusoft\Licensing\Accusoft. However, for runtime licenses, they are stored at HKEY_LOCAL_MACHINE\SOFTWARE\Accusoft\Licensing\YourSolutionName. So, when you call SetSolutionName, that tells your application to look in the correct directory to find the runtime license. You can find the necessary parameters for these methods on the customer portal customer portal.
  2.  You did not successfully install a license on your machine and the temporary license installed has expired. If you use the SLU (Server License Utility) or the LDK (License Deployment Kit) to license your machine and it fails, a temporary 14 day license will be placed on your machine. When that expires, you'll no longer be able to use the product. If this happens, you'll need to run the SLU or try using the LDK again. If that doesn't work, you might want to try licensing your machine in offline mode.
  3.  You are trying to use a development license and you are calling SetSolutionName and SetSolutionKey in your code. You should only call SetSolutionName and SetSolutionKey in your code when you are deploying your application and using a deployment license. When you install a development license on your machine, it is placed into the registry at the following path: "HKEY_LOCAL_MACHINE\SOFTWARE\Accusoft\Licensing\Accusoft". When you call SetSolutionName in your code, you are telling the control to look for a license at a different path: HKEY_LOCAL_MACHINE\SOFTWARE\Accusoft\Licensing\YourSolutionName. If you are calling SetSolutionName and SetSolutionKey while trying to use a development license, simply comment out those lines for now.
  4. The license information you've entered might be wrong. Check on the customer portal to make sure you've got the values parameters for the SetSolutionKey and SetSolutionName correct.
This issue can arise with multiple IIS app pools writing to the same folder and ASP temp directory. When one website creates files inside, others may not be able to read them. Try the following:
  • Give explicit permissions for each app pool user (e.g, IIS AppPool\[name]) on C:\Windows\Temp\Accusoft.
  • Do the same for C:\Windows\Microsoft.NET\Framework\[version]\Temporary ASP.NET Files
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.
Don't see your question answered here?

Fill out the short form below and we will get back to you as soon as possible.

Please be as specific as possible when writing your question.