> For the complete documentation index, see [llms.txt](https://docs.lithnet.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lithnet.io/ams/v3.0/help-and-support/troubleshooting.md). # Troubleshooting ## Logs The first step of any troubleshooting endeavor is check in the Access Manager log files. These contain information about errors and other important events. ### Access Manager Service The Access Manager Service has several log files. `access-manager-webapp.log` Contains events from the Access Manager web app, including information on access requests and authorization results. `access-manager-api.log` Contains events from the Access Manager API, including things like device authentication, registration and password updates. `access-manager-service.log` Contains events from the core access manager service, the scheduler, RPC interface, and worker services. `access-manager-jitworker.log` Contains events from the JIT worker service, which is responsible for creating and deleting JIT groups for computer objects when this feature is enabled. These logs are located in `%ProgramFiles%\Lithnet\Access Manager Service\Logs` ### Access Manager Agent The Access Manager Agent log files are located in `%ProgramFiles%\Lithnet\Access Manager Agent\Logs` ### Configuration Tool The configuration UI also has a log file to keep track of any issues encountered in the tool itself. The log file is called `access-manager-ui.log` and is located in `%ProgramFiles%\Lithnet\Access Manager Service\Logs` --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.lithnet.io/ams/v3.0/help-and-support/troubleshooting.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.