> 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/core/learn-more/demo.md). # Try the Apryse SDK Demo/Trial for Server/Desktop Get a free 40-day evaluation of Apryse SDK. Learn about common queries and solutions for errors during the trial period. Contact support for assistance. The Apryse Server SDK streamlines secure docume Apryse offers a free, 40-day evaluation of the Apryse SDK (active days only). Once the 40-day evaluation period expires, the library will start generating an exception/error indicating that the evaluation period has expired and the library will stop functioning. **Note:** Active days above refers to days of active use - this means that only the days that you use the product count towards the demo period. ## Common questions The most common query regarding the demo/trial mode, arises from errors arising due to insufficient rights. **Error:** When trying to run the application, the following error message is seen: > Please contact customer support at: [support@apryse.com](https://docs.apryse.com). No reg. write rights. **Solution:** Please use an account with sufficient privileges to write to the registry. Using PDFNet demo on development machines is usually not a problem because most development machines do not restrict writing to the registry. In case you are using the evaluation version on a production IIS server, you need to grant sufficient permissions to the assembly - or loosen your global security policy to allow registry writes. This restriction does not apply to the production version, which does not require registry access. Please see the topics under "server" in the [FAQ section](/core/get-started/faq.md) for more information on using the demo version in the context of a service or web server. --- # 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/core/learn-more/demo.md?ask=&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.