ByteScout Extractor SDK fails with ASP.NET on a specific server but works on another
When encountering issues with the Extractor SDK on different servers, consider the following recommendations:
Ensure all required files are in place: Your
.NETapplication should contain all the files located in the
VBScriptsample script: If the full version installer for the Extractor SDK has been run on your server, download, unpack, and execute this
VBScriptsample script: PDF Extractor SDK - PDF OCR To Text. If this sample fails, a full version reinstall of the SDK may be necessary.
If the previous test fails, Try an isolated
.NETsample: Compile and run an isolated
C#, then copy it onto the server's Desktop and run it from the command line: PDF Extractor SDK. If this step fails, some required files might be missing on this server.
Check for necessary runtime files: Confirm the presence of necessary runtime files on the server: .NET Framework 4.5 or .NET Framework 4.7 and Microsoft C++ Runtime (required for OCR in PDF Extractor). Choose the
x64version, or install both.
Test standalone compiled
C#sample: If the standalone compiled
C#sample functions, but your app does not, try running this isolated
.NETweb application: ASP.NET sample for Scanned PDF to CSV.
Consider additional actions for
ASP.NET issues: If the isolated
C# compiled application does not function, consider implementing the following solutions:
- Please adjust the IIS Application Pool for your app to use
.NET 4.7.2(a restart may be necessary).
- Make sure that your IIS is configured correctly to host
.NETapplications. The problem could be due to a misconfiguration. You can refer to the official Microsoft guide on how to host
ASP.NETapps on IIS for assistance.
- Verify that your web app has the required permissions to access and execute the DLL files from the ByteScout SDKs.
- Consider running the app under a different user account in the IIS Application Pool. Sometimes, issues can occur due to permissions or restrictions associated with the user account.
- Check if your IIS worker process (
w3wp.exe) has sufficient allocated memory. Insufficient memory could lead to app failures.
- Take a look at any server security software or firewall settings. These settings might be blocking certain operations of the SDK, causing potential issues.