---
title: "Enterprise Node Token Issues"
slug: "enterprise-node-token-issues"
updated: 2025-03-07T17:48:47Z
published: 2025-03-07T17:48:47Z
canonical: "docs.catchpoint.com/enterprise-node-token-issues"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.catchpoint.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Enterprise Node Token Issues

If the enterprise nodes are giving following errors under logs:

"CPS Status: The token was invalid for the given Synthetic-Node, likely because the token data wasn't in cache, no tokens assigned for the machine or the token is not assigned to the machine."

Please follow the below steps:

Clear the token values.xml file- Stop catchpoint service `> rm /opt/3genlabs/registry/LocalMachine/software/3genlabs/hawk/syntheticnode/service/\*` `> rm /opt/3genlabs/registry/LocalMachine/software/3genlabs/security/mostrecentschedulertoken/\*` Start catchpoint service.

If still the token issue not resolved- Stop the service again; and remove the entire registry folder and restart Catchpoint services. `> rm -rf /var/3genlabs/registry`

OR

1 - Stop catchpoint. 2 - Delete `/var/3genlabs/hawk/syntheticnode/synthetic_node_configuration.dat\*` 3 - Delete `/var/CatchPoint/Agent/Services/CommEng/Cache/\*` 4 - Start the node

You can flush the token using below:

`http://s.3gl.net/hawkscheduleserver/monitorservice.svc/web/query?name=synthetic-location&parameters=mrum=<hostname>|flush_machine=1`