> For the complete documentation index, see [llms.txt](https://docs.apryse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apryse.com/support/faq/eval-error.md).

# I get a system configuration error

Examples of this error are `Process does not have permission to Read the Windows Registry`.

Using PDFNet in demo/trial mode on development machines is usually not a problem because they are typically configured to have a loose security policy.

However, in case you are using the evaluation version on a production IIS server, you need to grant full permissions to the assembly - or loosen your global security policy.

{% hint style="info" %}
Please note that once you purchase a license this requirement no longer applies. Licensed Apryse products do not require elevated permissions.
{% endhint %}

Some of our customers were able to use the demo on servers with tight security by modifying a config xml file that controls security settings or using \`Code Access Security Policy\` tool. For more info please see:

* <http://msdn.microsoft.com/en-us/library/ff648243.aspx>
* <http://msdn.microsoft.com/en-us/library/cb6t8dtz(VS.80).aspx>
* <http://msdn.microsoft.com/en-us/library/a0ke3k86.aspx>

Because there are many different machine configurations and because the demo is not intended to be run in the production environment, we are not actively supporting this use case scenario.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.apryse.com/support/faq/eval-error.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.