Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

COM Class Factory Errors may appear in Batch Manager when running workflows using text-recognition.  Typical symptoms of this are blank text layers or keyfree not recognizing any text on a text searchable document in GS LAN. COM Errors (Component Object Model) can be responsible for this. If these errors reside on the server, we're typically dealing with a DCOM issue, whereas client issues tend to be simple COM issues. 

As far as GlobalSearch is concerned, COM issues tend to be very simple permissions errors.

Fixing DCOM & COM Permissions isn’t difficult. Follow the steps below:

Set DCOM/COM Permissions Manually

  1. Open CMD prompt as an administrator
  2. Run: cd C:\WINDOWS\System32
  3. Run: regsvr32 /n /i:”c:\getsmart\inc” “c:\getsmart\ocr\frengine.dll”  ***
  4. Run: mmc comexp.msc /64
  5. Open “Computers” – “My Computer” – “DCOM Config” – “ABBY Finereader Engine Loader”
  6. Right click on “ABBY Finereader Engine Loader” and select properties
  7. Select customize for all 3 options and add the SSAdministrator to the security with full permissions

To Set COM on a client:

  1. Open CMD prompt as an administrator
  2. Run: cd C:\WINDOWS\System32
  3. Run: regsvr32 /n /i: "YOURCLIENTSDRIVE:\Program Files\Common Files\Square9\GetSmart\inc" "YOURCLIENTSDRIVE:\Program Files\Common Files\Square9\GetSmart\ocr\frengine.dll" ***
  4. Run: mmc comexp.msc /64
  5. Open “Computers” – “My Computer” – “DCOM Config” – “ABBY Finereader Engine Loader”
  6. Right click on “ABBY Finereader Engine Loader” and select properties
  7. Select customize for all 3 options and add the SSAdministrator to the security with full permissions

Make sure to test the workflow once you are done. If one way doesn’t work, trying setting the permissions using the other method.

Info
titlePlease Be Advised

x86 Servers and Clients are not supported.


Info
titleExternal Link to Microsoft Developer Network Website

For more on COM and DCOM see the MSDN article HERE.

*** Make sure you change the drive letter according to where GetSmart is stored. Additionally DO NOT copy and paste this from the KB article, the quotations are a different ASCII character from what CMD sees as valid.