# Troubleshooting

> What to check when MTConnect Server doesn't start, a Device isn't collected, or data doesn't arrive.

URL: https://www.trakhound.com/docs/mtconnect-server/troubleshooting

Start with **System > Logs** and **System > Workers** in the App (see [Administration](https://www.trakhound.com/docs/mtconnect-server/administration)), and the [Tools](https://www.trakhound.com/docs/mtconnect-server/tools) for connections to machines. Every check is made from the computer MTConnect Server is installed on.

## Installing and Starting

| Problem | What to Check |
| --- | --- |
| Setup says the Service didn't start | Check the logs in the install directory's `logs` folder and the Windows Event Viewer (Application and System logs). Make sure the ASP.NET Core Runtime 10 (x64) is installed. Setup writes its own log to `%TEMP%` (`Setup Log {date} #{n}.txt`) |
| The App doesn't open | Make sure the **TrakHound MTConnect Server** Windows Service is running (`services.msc`), and that you're using the HTTP Port entered during install (default `8490`) |
| The App can't be opened from another computer | Allow the HTTP Port through the Windows Firewall |
| The password doesn't work | Reset it with `TrakHound.MTConnectServer.exe set-admin <username>` (see [Admin Account](https://www.trakhound.com/docs/mtconnect-server/administration#admin-account)) |
| The header's Status isn't **Running** | Hover over the Status to see each Worker's status, and check **System > Workers** and **System > Logs** |

## Connecting to Machines

| Problem | What to Check |
| --- | --- |
| **Find Devices** finds no Devices | Check the Agent's Address and Port, and that the Agent can be reached from this computer with a [Port Check](https://www.trakhound.com/docs/mtconnect-server/tools#network), or by opening `http://{address}:{port}/probe` in a browser on the server |
| A Device shows **DISCONNECTED** or **ERROR** | See the message on **Collection > Connections > Status**, and **Connections > History**. Check what the Agent serves with the [Request Browser](https://www.trakhound.com/docs/mtconnect-server/tools#request-browser) |
| An SHDR Device has no data | Check the Adapter with the [SHDR Browser](https://www.trakhound.com/docs/mtconnect-server/tools#shdr-browser). On the Device's **AgentHub** tab, **Keys Not in Model** counts keys with no DataItem in the Device model, whose data is ignored |
| An Agent stops getting data from an Adapter | Some Adapters only accept one client. Serving the Adapter through the Agent Hub, or connecting with the SHDR Browser or a Port Check, can disconnect another Agent reading from it |
| A Device model isn't valid | Check it with [Device Validation](https://www.trakhound.com/docs/mtconnect-server/tools#device-validation) |

## Collection

| Problem | What to Check |
| --- | --- |
| A Device isn't collected | Make sure Collection is turned on for the Device and it has a License. A new License is noticed within about 30 seconds. The App's **Quick Start** lists what's left to set up |
| A Device shows **No Profile** | Its data isn't stored or published anywhere. Select a Profile on its **Collection** tab, or give its Group a Profile (see [Profiles](https://www.trakhound.com/docs/mtconnect-server/profiles)) |
| Nothing is stored in the database | Make sure the Profile has a destination, and that its Service shows **Loaded** under **Collection > Configuration**. Check that the database user can create tables (and schemas) in the database |
| A Service shows **Not Loaded** | Check its settings (**Edit**) and the logs |
| Items build up in **Statistics > Buffers** | The Router's database can't keep up or can't be reached. The data is kept in the File Buffer until it can be written |
| The database keeps growing | Add [Data Retention](https://www.trakhound.com/docs/mtconnect-server/data-retention) rules, and leave out constantly changing values with a [Filter](https://www.trakhound.com/docs/mtconnect-server/filters). Check **Statistics > Retention** for errors |
| The API's WebSocket stream sends nothing | The stream needs a Messages Profile with the default Base Topic, and an MQTT Service on the **default** Router (see [Streaming](https://www.trakhound.com/docs/mtconnect-server/api#streaming)) |

## Licenses

| Problem | What to Check |
| --- | --- |
| A License Code isn't valid | License Codes are issued for a specific computer. Request one with **Request License** in the App on this computer |
| **No Licenses Available** | Every seat of the added License Codes is in use, or they've expired. Add or request another License Code, **Unassign** one from a Device that's no longer used, or **Release** seats of deleted Devices (see [Collection Licenses](https://www.trakhound.com/docs/mtconnect-server/licenses)) |
| Devices stopped being collected | Their License expired. Add the renewed License Code and use **Replace** to move the Devices to it |

## Agent Hub

| Problem | What to Check |
| --- | --- |
| The endpoints can't be reached from another computer | Allow the Hub port (default `5001`) through the Windows Firewall |
| A request returns `NO_DEVICE` | Check the Device UUID in the path. `GET http://{server}:5001/` lists the running Devices and their probe paths |
| A Device has no URLs yet | It's shown as **Waiting for its Source** until it's enabled and its source has been read. Check the source with a Port Check |
| Observations are **Rejected** | The Device's Agent rejected values that don't fit the Device model. Check the model with Device Validation, and the Device's logs |

> Still stuck? [Contact us](https://www.trakhound.com/contact?product=mtconnect-server&type=support) with the version from the App's header and the relevant entries from **System > Logs**.
