- General Information (1)
- Guides (11)
- Assemblage
- Trumpet Publisher for Sharefile
- Attach Plus
- SignatureBridge for DocuSign
- Symphony OCR
- 1. Background Information
- 2. Installation and Basic Configuration Guide
- 3. Configuration Guide - Worldox
- 4. Configuration Guide - NetDocuments
- 5. Configuration Guide - Sharefile
- 6. Configuration Guide - OpenText
- 7. Configuration Guide - PracticeMaster
- 8. Configuration Guide - LSSe64
- 9. Configuration Guide - Folders
- 10. Configuration Guide - Box
- 11. Configuration Guide - Dropbox
- 12. Configuration Guide - Google Drive
- 13. Configuration Guide - Microsoft One Drive
- 14. Configuration Guide - SharePoint
- 15. Administrator Guide
- 16. Enabling Functionality in Symphony OCR
- 17. Advanced Reporting Features
- 18. FAQs
- 19. Troubleshooting Tips and Tricks
- 19.1. Troubleshooting Procedures
- 19.2. There was a problem downloading the Symphony OCR Engine
- 19.3. Insufficient Disk Space Warning
- 19.4. Unable to determine number of Worldox users
- 19.5. Unable to Determine number of Netdocuments users
- 19.6. You have more users on your Worldox licensing than you have on your Symphony Licensing
- 19.7. License Update Check Failed - Error Checking for License Updates
- 19.8. Migrating Symphony OCR to a new workstation
- 19.9. The Program Can't Start Because MSVCR71.dll is Missing Error
- 19.10. Compact, repair or reset the Symphony OCR database
- 19.11. Backlog Processing is Throttled
- 19.12. Removing many documents from the Symphony OCR database
- 19.13. Explicitly adding documents for processing
- 19.14. Needs Attention file - Adding text to image failed — null
- 19.15. Symphony OCR is consuming lots of disk space on our indexer's local disk
- 19.16. Performing Maintenance screen never updates
- 19.17. OCRed documents not text searchable
- 19.18. Java.io.IOException: StringLong keys can't be longer than 300K error
- 19.19. Documents in Inaccessible list are not OCRed - Security prevents manipulation of document
- 19.20. Documents in Inaccessible list are not OCRed - File system or DMS security settings block processing (Worldox sites only)
- 19.21. Documents in the Inaccessible List when security not applied
- 19.22. Worldox API (WDAPI32, WBAPI) crashing
- 19.23. Very Large Documents Preventing others from Processing
- 19.24. ABBYY is probably not installed
- 19.25. "Unable to process msg request" or "Outlook has not been launched one time on this machine" error during MSG processing
- 19.26. Unable to bring up Symphony OCR interface
- 19.27. Documents aren't searchable with NetDocument's ECHO turned on
- 19.28. Symphony OCR doesn't automatically redirect to home page
- 19.29. Symphony fails sending email: PKIX path building failed
- 19.30. Symphony OCR crashes during analysis
- 19.31. Handwritten pages are rotated by Symphony OCR when they shouldn't be
- 20. Not Processed List Description
- Configuration Guide
- Updates & Licensing
- Release Notes
- Symphony Analyzer Tool
- Symphony Profiler
- Symphony Profiler Troubleshooting
- Virtuoso
- Worldox Autofiler
- AuditSync
- Training Manuals- Symphony Suite (2)
- Guide Archives (3)
Home → Guides :: Symphony OCR → Troubleshooting Tips and Tricks → Needs Attention file - Adding text to image failed — null
19.14. Needs Attention file - Adding text to image failed — null
Background
After updating Symphony OCR to version 8.0.7 or higher, some files appear in the 'Needs Attention' list with the reason being "Adding text to image failed — null". When the files are reanalyzed, they are not processed and they return to the 'Needs Attention' list.
Resolution Updated
We have an update available that resolved the error. Update SymphonyOCR to version 8.1.3 or higher.
Symphony will automatically reanalyze any files in the Needs Attention list after the update. If you have Ignored files related to this error you can manually tell Symphony to reanalyze them.
This page was: Helpful |
Not Helpful