> For the complete documentation index, see [llms.txt](https://docs.swingsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.swingsoftware.com/integrator-for-notes/error-messages/web-500-internal-server-error.md). # \[Web] - 500 Internal server error **Description** When working in the web client, on creation or detach of an attachment appears error: Error executing agent SwGetGlobalVariable 500 – internal server error **Solution** This behavior is pointing to the non-signed database. Please check is database signed with the server ID or the Id of the user that has enough rights to run unrestricted agents? If this is not the case, please sign the database and check this issue once again. Please follow these steps to sign the database: 1\. Copy database on to server (or on to local). 2\. Open Lotus Domino Administrator, navigate to "Files" tab and select the database there. 3\. Choose Files –> Sign... 4\. Choose the following: Active User’s ID to sign using with your ID. 5\. Choose the following option to specify which elements to sign: All design documents to sign every design element. 6\. Select “Update existing signatures (faster)” 7\. Click OK. --- # 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.swingsoftware.com/integrator-for-notes/error-messages/web-500-internal-server-error.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.