Initializer Error After Update to Latest version

Summary: After updating to the latest version of Aspose.PDF via the NuGet package, several dependencies were updated. Upon testing the API, the following error was encountered: “The type initializer for ‘#=z$NkvaymAmvW0jnfQR2Lrffo3ww9p’ threw an exception.” The issue is suspected to be related to dependencies, as the process works correctly during local debugging but fails on the actual server.

Environment Details:

  • Solution Deployment: Website API
  • Source Control: TFS
  • Target Framework: .NET Framework 4.6.1
  • Staging Server: Windows Webserver with IIS

Issue Description: The error occurs when attempting to execute the API on the staging server. The error message provided is not detailed enough to determine the exact cause, but based on the behavior (working locally but failing on the server), it is likely a dependency issue.

Steps Taken:

  • Verified that the error does not occur during local debugging.
  • Confirmed that all packages were updated via NuGet and dependencies were correctly restored.
  • Checked for any missing or incompatible assemblies on the server.
  • Reviewed server logs and exception details but did not find specific clues to identify the root cause.

Impact: The issue is currently preventing the API from functioning correctly on the staging server, which may delay the deployment of updates to production.

@DFWDimas
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.

Issue ID(s): PDFNET-58073

You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.