Troubleshooting

What to check when MTConnect Server doesn't start, a Device isn't collected, or data doesn't arrive.
MTConnect Server Docs Menu

Start with System > Logs and System > Workers in the App (see Administration), and the Tools for connections to machines. Every check is made from the computer MTConnect Server is installed on.

Installing and Starting

ProblemWhat to Check
Setup says the Service didn't startCheck 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 openMake 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 computerAllow the HTTP Port through the Windows Firewall
The password doesn't workReset it with TrakHound.MTConnectServer.exe set-admin <username> (see Admin Account)
The header's Status isn't RunningHover over the Status to see each Worker's status, and check System > Workers and System > Logs

Connecting to Machines

ProblemWhat to Check
Find Devices finds no DevicesCheck the Agent's Address and Port, and that the Agent can be reached from this computer with a Port Check, or by opening http://{address}:{port}/probe in a browser on the server
A Device shows DISCONNECTED or ERRORSee the message on Collection > Connections > Status, and Connections > History. Check what the Agent serves with the Request Browser
An SHDR Device has no dataCheck the Adapter with the 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 AdapterSome 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 validCheck it with Device Validation

Collection

ProblemWhat to Check
A Device isn't collectedMake 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 ProfileIts data isn't stored or published anywhere. Select a Profile on its Collection tab, or give its Group a Profile (see Profiles)
Nothing is stored in the databaseMake 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 LoadedCheck its settings (Edit) and the logs
Items build up in Statistics > BuffersThe 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 growingAdd Data Retention rules, and leave out constantly changing values with a Filter. Check Statistics > Retention for errors
The API's WebSocket stream sends nothingThe stream needs a Messages Profile with the default Base Topic, and an MQTT Service on the default Router (see Streaming)

Licenses

ProblemWhat to Check
A License Code isn't validLicense Codes are issued for a specific computer. Request one with Request License in the App on this computer
No Licenses AvailableEvery 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)
Devices stopped being collectedTheir License expired. Add the renewed License Code and use Replace to move the Devices to it

Agent Hub

ProblemWhat to Check
The endpoints can't be reached from another computerAllow the Hub port (default 5001) through the Windows Firewall
A request returns NO_DEVICECheck the Device UUID in the path. GET http://{server}:5001/ lists the running Devices and their probe paths
A Device has no URLs yetIt'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 RejectedThe 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 with the version from the App's header and the relevant entries from System > Logs.