ImageGear SDK FAQs

Discover the answers to Frequently Asked Questions about ImageGear Below

General FAQ’s

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.
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
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.
In all cases, you’ll want to have your images as clear and as clean as possible. For any particular procedure, please consider the following: OCR and ICR: Capture images in at least 300 DPI resolution. Ideally, working in black and white will allow the objects of interest on your image to be better defined and recognized. Free the image form all noise as much as possible. As if a human was reading it, you’ll want the text objects on the image to be as legible as possible. For ICR, make sure that the characters are printed (no cursive text, etc). Barcode recognition: As with OCR and ICR, capture images in at least 300 DPI and working with black and white content can provide excellent results. You’ll also want to make sure that the bars in the barcodes are clearly defined on the image and are not mal-formed (for example, the barcodes should have the proper start and stop sequence, etc). As always, clear as much noise from the image as possible. Forms matching and registration: As with the prior 2 items above, capture your documents in at least 300 DPI. Make sure that your resolution is consistent between your form templates and incoming batch images as well. Form templates should only contain data that is common to every image that is being processed (i.e. – Form fields, the text that appears on the blank form itself, etc). The template should not have filled-in field information as this will affect the forms matching process.
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.
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.
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.
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 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 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.

.NET SDK FAQ’s

Please check the Windows Features to ensure that you have WCF and HTTP Activation installed for ImageGear Services to work.
This issue is known to be caused by older versions of the Microsoft Visual C++ Redistributable Packages being installed. To resolve the issue, follow these steps:
  • Navigate to the "Add or remove programs" window to see which versions of the Redistributable are currently installed.
  • Ensure you do NOT have the Microsoft Visual C++ 2005 Redistributable Package installed, this version is known to cause the problem. Any versions 2008 and above are okay.
  • Also be sure to run the SDK installer as an administrator. You may also want to close any other applications that are running.
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
To improve performance when zooming in or scrolling on PDF documents you can change the DrawMode ImGearControlParameter to the enumerated value ImGearPDFPageDrawMode.VISIBLE_AREA. By default, DrawMode is set to ImGearPDFPageDrawMode.ENTIRE_PAGE.
ImGearFileFormats.Filters.Get(ImGearFormats.PDF).Parameters.GetByName("DrawMode").Value = 2; //VISIBLE_AREA
Call the SetSolutionName method in the ImGearLicense Class. For example: //Win32 ImGearLicense.SetSolutionName("AccuSoft 5-40-20"); //Win 64 ImGearLicense.SetSolutionName("AccuSoft 5-41-20");
We have two pages in our documentation that explain how to use our Recognition API in a multi-threaded environment:
  • Recognition API and Multi-Threading
  • Walkthrough: Multi-Threaded Recognition
  • Some tips:
  • When initializing the ImGearRecognition object, make sure to use the constructor with the createUnique parameter set to true: using (var igRecognition = new ImGearRecognition(true)) This ensures that each ImGearRecognition object has its own settings collection and does not share one with other ImGearRecognition objects. Setting the createUnique parameter will help avoid System.AccessViolationExceptions.
  • Using the Dispose methods of the recognition objects should be done as soon as possible.
  • All PDF objects are based on underlying low-level PDF objects that are not controlled by .NET  resource manager and garbage collector. Because of this, each PDF object that is created from scratch should be explicitly disposed of using that objects Dispose() method.   Also, any ImGearPDEContent object obtained from ImGearPDFPage should be released using the ImGearPDFPage.ReleaseContent() in all cases.   This should cause all temp files to be cleared when the application is closed.
    1. Open our JQuiery Plugin Sample in Visual Studio 2010.
    2. Right-click on the ImGearPluginSample project and select "Use IIS Express ..." in the context menu. If this menu item cannot be found in menu, then IIS Express is already used as a development server.
    3. In the Properties Windows of project set SSL Enabled as true.
    4. Modify the system.ServiceModel section of Web.config file as follow:
    5. <behaviors>
        <servicebehaviors>
          <behavior name="simpleBehavior">
            <servicemetadata httpgetenabled="true" httpsgetenabled="true"></servicemetadata>
            <servicedebug includeexceptiondetailinfaults="true"></servicedebug>
          </behavior>
        </servicebehaviors>
        <endpointbehaviors>
          <behavior name="webHttpBehavior">
            <webhttp></webhttp>
          </behavior>
        </endpointbehaviors>
      </behaviors>
      <bindings>
        <webhttpbinding>
          <binding name="webHttpTransportSecurity">
            <security mode="Transport"></security>
          </binding>
        </webhttpbinding>
      </bindings>
      <services>
        <service name="ImageGear.Web.ImGearService" behaviorconfiguration="simpleBehavior">
          <endpoint binding="webHttpBinding" contract="ImageGear.Web.IImGearService" behaviorconfiguration="webHttpBehavior" bindingconfiguration="webHttpTransportSecurity"></endpoint>
        </service>
      </services>
      <servicehostingenvironment aspnetcompatibilityenabled="true"></servicehostingenvironment>
      
    6. Remember the port value in Properties Window of project in field "SSL URL"
    7. Build and run project.
    8. In the browser, starts the same webpage with HTTPS protocol and port from "SSL URL" field of project.
    9. Check the "Network" window of the "Developer Tool" in the browser to verify that all requests to the service are passing via HTTPS protocol.
    In an ImageGear.NET web application, you will need to define the location of the images and annotations directory in the "storageRootPath" and "artStorageRootPath" configuration property.
    In current version of ImageGear.NET, the "storageRootPath" and "artStorageRootPath" do not work with a network drive path "\\SERVER-NAME\sharefilename".
    The workaround for this would be creating a Symbolic link from a local directory to the network drive directory.

    To create a symbolic link:
      Open “Command Prompt” as Administrator Type in > mklink /d “local path” \\SERVER-NAME\sharefilename

    Pass in the path of the symbolic link as image or art storage root path in your web.config: storageRootPath="local path" artStorageRootPath="local path"

    Occasionally, permissions issues can prevent ImageGear from writing to a log file.
    • If one is using Microsoft Visual Studio, watch the output tab from the Debug view and see if any ImageGear.Web messages appear. If not, reconfigure the web.config file as outlined in the Error Logging Configuration Settings section of the ImageGear help file. Try enabling verbose logging by setting the switch named imageGearSwitch value to "Verbose". For example:

      <switches>
          <add name="imageGearSwitch" value="Verbose" />
      </switches>
      
    • When using Visual Studio, you have have a process of IIS Express running in your system tray:

      Sometimes it is necessary to stop that server and then restart the debugging process again.

    • The initializeData parameter in your web.config file must be set to a proper file name. The path is relative to the web.config file and the directory must have writable permissions and have the appropriate security permissions for the user debugging the application. Paths may be fully qualified specified locations if they begin with a hard drive location.

    • If the log file can be generated using Visual Studio debugging but fails to show when the application is deployed under IIS, it is most likely a security issue. Be sure that the directory picked has NETWORK SERVICE user name Read and Write permissions set.

    If there are files in the %TEMP% directory created by ImageGear that are not getting deleted, the most likely cause is that there are ImageGear objects in your code that are not being disposed of. The most common culprit is the ImGearPage object. This object has no Dipose method, but it does implement the IDisposable interface, so it can be disposed of. You can do so like this:
    if (igPage is IDisposable)
    {
        (igPage as IDisposable).Dispose();
    }
    The other ImageGear objects can safely be disposed of using their Dispose methods.
    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  
    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.
    When trying to use ImageGear PDF support, you may not be able to load igPDFxxnu.dll, where "xx" is the version number of ImageGear.
    • Ensure the .dll is the same architecture as your application (x86, x64).

    • Ensure the Microsoft Visual C++ Redistributable 2010 is installed: 32-bit 64-bit

    • If you are using an ASP.NET project, ensure IIS Express is set to your installed architecture:
      Go to Tools > Options > Projects and Solutions > Web Projects > Use the 64 bit version of IIS Express

    • Make sure you are initializing the PDF component to the path with the .dll. Try pointing this to the ImageGear Public Bin folder
      string libraryPath = @"C:\Users\Public\Documents\Accusoft\ImageGear.NET v22 64-bit\Bin";
      
      ImGearEvaluationManager.Initialize();
      ImGearCommonFormats.Initialize();
      ImGearFileFormats.Filters.Insert(0, ImGearPDF.CreatePDFFormat(libraryPath));
      ImGearPDF.Initialize(libraryPath);
      

      See Getting Started with PDF
    • Ensure that your project can access the bin folder that contains the DLL.

    • If you are using the .dlls in another folder, run the Deployment Packaging Wizard located in the Deployment Kit folder to copy all needed dependencies. Refer to the Help File under Deployment Packaging Wizard for more information.

    This is likely because you have not specified that the Recognition engine should be using its own unique collection of Recognition settings. When you create the ImGearRecognition object, simply pass in the boolean "true" to ensure that each thread uses its own Recognition setting collection. Like this: using (var igRecognition = new ImGearRecognition(true)) For more help with Recognition and Multi-Threading, take a look at the following pages:
  • Recognition API and Multi-Threading
  • Walkthrough: Multi-Threaded Recognition
  • There are numerous reasons why an image may not appear.
    • Try using a common web debugger, such as the F12 console in Chrome and Firefox. Inspect the Network tab for any 404, 500, or other bad requests.

    • the ASP.NET controls are designed to generate logs. See the Error Logging Configuration Settings found in the Using ImageGear.Web.UI Namespace section of the ImageGear help file for setting up logging.

    • Please Contact Accusoft for assistance in analyzing your log files.
    Typically this error occurs when "Any CPU" is selected as the target in Microsoft Visual Studio when running an ImageGear.NET project. Simply update the target to x86 or x64 depending on your ImageGear.NET version to resolve this issue.
    You will need to set up your project to include PDF support if you want to work with PDF documents. Add a reference to ImageGear21.Formats.Pdf (If you're using another version, make sure you're adding the correct reference). Add the following line of code where you specify other resources:
    • using ImageGear.Formats.PDF;
    Add the following lines of code before you begin working with PDFs
    • ImGearFileFormats.Filters.Insert(0, ImGearPDF.CreatePDFFormat());
    • ImGearPDF.Initialize();
      Here is a link that shows how to add PDF support to a project
    The application is missing the ImageDataProcessor.dll. Changing the output path or copying all the required .dlls from the deployment wizard to the project/bin folder will address the issue.
    This is done to give the web browser user a more responsive feel. A low resolution full sized image is first loaded which is fairly quick and responsive. Then, a higher resolution image will typically follow for the portion of the image being viewed in the client viewer. This higher quality image can be the one showing a full image at better resolution or one or more tiles showing a portion of the image depending on how far zoomed in the image may be. When you scroll around or zoom into the client viewer, you may see the previously loaded low resolution view for a moment while a better quality image gets requested and then subsequently displayed.
    Please be sure to copy the license strings exactly. Even trailing spaces in quoted strings must be applied. Also, with IIS services, it sometimes is necessary to restart or recycle the Application Pool for which the hosted ASP.Net application resides and not just the IIS service itself.
    Interactive applications are much better at printing documents than web browsers. As browsers improve their ability to print application-generated content, Accusoft will expand the printing support in ImageGear ASP.NET.
    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

    C and C++ SDK FAQs

    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): licensingerror 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.
    In order to print a series of images, PDF, or other multi-page document, use the IG_dspl_document_print. By using this function, IG Pro will print as a document rather than a single image, which will enable duplex support. Follow these steps to get started:
    1. Create a array of HIGEAR handles
    2. Load images or documents into each position
    3. Call the IG_dspl_document_print function on the array, using PRINTDLG normally.
    4. You may need to enable Duplex printing on the DEVMODE pointer in the PRINTDLG structure.
    The following sample code will outline this process.
    HIGEAR document[32]; //Document holding all the images
    
    //Get page count and load pages into array
    //"fd" a handle to the multi-page-document.pdf
    int pageCount = 0;
    IG_fltr_pagecount_file_format(IG_FORMAT_UNKNOWN, "multi-page-document.pdf", &pageCount);
    for(int i = 0; i < pageCount; ++i) {
        IG_fltr_load_FD_format(IG_FORMAT_UNKNOWN, (AT_INT)fd, 0, i + 1, 1, &document[i]);
    }
    
    PRINTDLG pd;
    if (PrintDlg(&pd)) {
        /* Try to enable Duplex printing via the DEVMODE pointer */
        LPDEVMODE dev = (LPDEVMODE)GlobalLock(pd.hDevMode);
        dev->dmDuplex = DMDUP_VERTICAL;
        GlobalUnlock(pd.hDevMode);
    
        //Print the document
        IG_dspl_document_print(document, pageCount, IG_GRP_DEFAULT_PRINT, pd.hDC, 1, 1, 0, 0, TRUE, NULL, NULL);
    }
    
    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
    By using the Deployment Packaging Wizard you can transfer all required ImageGear files, resources and dependencies needed for your application.
    The location of the Licensing Service has been moved and you will need to download a particular version of the License Manager from the appropriate link below. Once you download, please run the License Manager as you normally would and this should resolve your issue: 32 bit: http://ftp2.accusoft.com/ImageGear/ALM_IG.NET32.exe 64 bit: http://ftp2.accusoft.com/ImageGear/ALM_IG.NET64.exe
    This error can occur when attempting to code sign a Mac OS application.   To correct this issue follow the steps below: 1) Move any resource files located in the frameworks root directory to the Resource folder ( ig_cmyk_profile.icm, ig_rgb_profile.icm, IGLZW18, IGMED18, IGPDF18 etc... ) 2) Then specify the path to the Resource folder which contains the ImageGear component modules using the following function:
    static char* path = "/Resource/";
    IG_gctrl_item_set("COMM.PATH", AM_TID_MAKELP(AM_TID_CHAR), (LPVOID)path, strlen(path) + 1, NULL);
    
    
    If you require assistance please contact us at support@accusoft.com
    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  
    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.
    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.



    © 1991 - 2017 Accusoft Corporation. All Rights Reserved. | privacy statement