> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/products/cc-software/troubleshoot/command-centre-connection-issues/scheduled-reports-do-not-use-the-servers-date-format.md).

# Scheduled reports do not use the server's date format

Resolve scheduled reports that show dates in a different format from the one set on the server.

A report generated automatically by the server shows dates in a different format from the one set on the server.

**Cause:** the usual cause is that the service accounts do not use the server's regional format. A scheduled report is generated by the server, not by a logged-in operator.

### Copy the server's regional settings to the system accounts

1. Open **Control Panel** and go to **Clock and Region**.

   ![Control Panel, Category view, with Clock and Region highlighted](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-138f03bf847ca27daa32743be7c81f9a060532da%2FSECHUB-TS-REPORT-DATE-FORMAT-01-control-panel-clock-and-region.png?alt=media)
2. Go to **Region**.

   ![Clock and Region with Region highlighted](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-49b632a594553500107746ac9ca7cebb0eb3fb02%2FSECHUB-TS-REPORT-DATE-FORMAT-02-region.png?alt=media)
3. Go to the **Administrative** tab.

   ![Region dialog, Formats tab showing the date and time formats, with the Administrative tab highlighted](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-1c8e21d9d648162ce43628e7ced75bfca6050c62%2FSECHUB-TS-REPORT-DATE-FORMAT-03-administrative-tab.png?alt=media)
4. Click **Copy settings**.

   ![Region dialog, Administrative tab, with the Copy settings button highlighted under Welcome screen and new user accounts](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-52a863f4a56bab68b950d17a96b487ad520ecdab%2FSECHUB-TS-REPORT-DATE-FORMAT-04-copy-settings.png?alt=media)
5. Check **Welcome screen and system accounts** and **New user accounts**.

   ![Welcome screen and new user accounts settings, with both Copy your current settings to boxes ticked](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-689aab6d43d234d3328b6abe95f8afe2984dc68a%2FSECHUB-CCS-ERR-CC-CLIENT-NO-LOGIN-03.jpg?alt=media)
6. Click **OK**.

The service accounts now use the server's locale format, so the reports should be in the correct format. All new user accounts created on the server will use this format as well.

The same Windows setting is the fix for a client login fault: see [Unable to log into Command Centre Client on a workstation, but Configuration Client works fine](https://help.security.gallagher.com/knowledge-hub/products/cc-software/troubleshoot/command-centre-errors/unable-to-log-into-command-centre-clie.md).


---

# 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://help.security.gallagher.com/knowledge-hub/products/cc-software/troubleshoot/command-centre-connection-issues/scheduled-reports-do-not-use-the-servers-date-format.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.
