> For the complete documentation index, see [llms.txt](https://docs.blockyforveeam.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.blockyforveeam.com/administration-guide/chapter-6-diagnostics.md).

# Chapter 6: Diagnostics

## **Chapter 6: Diagnostics**

### 6.1 Service Report

To help our service analyze unexpected behavior of our software, you can generate a service report by selecting the menu item “File >> Generate Service Report." All service information is stored in the file <mark style="color:red;">"C:ProgramDataGrauDataBlockyBlockyforVeeam®\_Diag.zip."</mark> Generating a service report is also available via the BlockyCLI.

When using the Central GUI, the service report is generated on the active connected target server and must be collected from there once finished.

### 6.2 Missing privileges

The Blocky GUI requires certain privileges to run properly, so you have to make sure the user is able to gain such privileges.

The required privileges are:

* SE\_BACKUP (SeBackupPrivilege)
* SE\_RESTORE (SeRestorePrivilege)
* SE\_TAKE\_OWNERSHIP (SeTakeOwnershipPrivilege)
* SE\_LOAD\_DRIVER (SeLoadDriverPrivilege)
* SE\_SECURITY\_NAME (SeSecurityPrivilege)

In standard installations, any local or domain admin user is allowed to gain these privileges by default. It is possible to restrict these privileges via local security policies or domain group policies. Please make sure to **not** restrict these policies for users who need to run the Blocky GUI.

### 6.3 System clock tampering

BlockyforVeeam® monitors the system clock and detects backward time manipulations. Once such system clock tampering is detected, it will be reported in the Windows event log, and access control will refuse any write access, even from whitelisted applications.


---

# 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.blockyforveeam.com/administration-guide/chapter-6-diagnostics.md?ask=<question>&goal=<endgoal>
```

`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.