> For the complete documentation index, see [llms.txt](https://documentation.2pintsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.2pintsoftware.com/ipxe-ws/4.0/troubleshooting/web-service-diagnostics.md).

# Web Service Diagnostics

### Logs and events

iPXE Anywhere Web Service 4.0 writes its logs to Windows event logs instead of a log file. In Event Viewer, they are under **Applications and Services Logs** > **TwoPintSoftware** > **iPXEAnywhere.WS**:

| Log                          | Contents                                                                                                                                 |
| ---------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
| **Main** > **Operational**   | Service startup, configuration, licensing, certificate, database and request handling events, including errors and warnings. Start here. |
| **Main** > **Debug**         | Additional detailed events. Turned off by default.                                                                                       |
| **Audit** > **Operational**  | Events about each boot request, such as device approvals and missing scripts.                                                            |
| **Logger** > **Operational** | Messages from the built-in web service and the .NET components it uses.                                                                  |

To turn on the Debug log, in Event Viewer select **View** > **Show Analytic and Debug Logs**, then right-click **Main** > **Debug** and select **Enable Log**. Or, from an elevated command prompt:

```
wevtutil sl "TwoPintSoftware-iPXEAnywhere.WS-Main/Debug" /e:true
```

### Running the Service Interactively

> NOTE: Ensure that the service is stopped before attempting to run it interactively.

You can run the service directly from a console, or by double-clicking the executable (**TwoPint.iPXEAnywhere.Service.exe** in the installation folder) in Windows Explorer. This starts the service in a command prompt window, which makes troubleshooting simple, because you can see the iPXE Anywhere workflow roll through the window.

When running in interactive mode, all logging is sent to the console window, and also written to a log file in the folder set by the **Debug log path** setting. This helps greatly when you run into issues, or when showcasing the technology. Note that the console runs under the account of the user running it, rather than the service account (SYSTEM by default), which can lead to access violations.

### Errors & Issues

Sometimes, things can go a little pear-shaped! If a machine is not booting as you would like it to, it is likely that a setting is invalid. Open **Configure iPXE WS** and click **Verify** to check the settings (see [Configuring the iPXE Web Service](/ipxe-ws/4.0/configuration/configuring-the-ipxe-web-service.md)). If you cannot find the issue, turn on the Debug log, try to boot the machine again, and then send the logs to 2Pint Software support. Include any PowerShell scripts that you have changed, and an export of the event logs. Email the files to <support@2pintsoftware.com>, or use the 2Pint Software online forums.

Note: Add all the files to a .zip file, otherwise the email might get caught in a spam filter.


---

# 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://documentation.2pintsoftware.com/ipxe-ws/4.0/troubleshooting/web-service-diagnostics.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.
