General Troubleshooting Tips for IronOCR
For general access and application issues, please try the following suggestions:
- Ensure you have the latest version 2015-2019 of Microsoft Visual C++ Redistributable for Visual Studio installed on your target machines, as Tesseract depends on this.
- x86 machines require only x86 versions.
- x64 machines require both x86 and x64 versions.
- For more information, refer to the Microsoft documentation.
Production servers are typically more locked down than development or testing machines. Please ensure that the server has internet access to download required components on the first run.
- Ensure Full Control permissions are applied for the following users on your system default temp folder (on Windows, this is normally
/windows/temp
) and the input files/location:- AppPool identity/IIS User (typically IUSR)
- NetworkService
- ASPNET (where applicable)
After updating the library version or changing license keys, it is advisable to redeploy a CLEAN version of your application to reduce the likelihood of DLL caching.
- Try downloading the library into a clean project, wiping all Windows temp files and cache folders on your servers.
- Manually delete IronOcr from the temp folder or the specified Installation Path.
- Uninstall the library, ensuring to tick the Remove dependencies checkbox.
- Manually remove the NuGet cache from this location:
%userprofile%\.nuget\packages
. - Clear the cache automatically through Visual Studio by choosing the following option: Go to Tools > NuGet Package Manager > General, and then click Clear All NuGet Cache(s).
- Set a new Installation Path in a new directory outside of Program Files, Temp, or Users per the instructions given here: IronOCR Installation Path Setting.
If these steps do not resolve the issue, please review our Engineering Request list for IronOCR. This provides the information needed by our engineers to provide the swiftest turnaround on a technical inquiry.