Fixing the “No Token” Error in Eclipse ECM

🚫 Fixing the “No Token” Error in Eclipse ECM

---

🚨 What causes the No Token error?

The No Token error in Eclipse ECM happens when the MachineKey validationKey values don’t match between the Eclipse Server and the Eclipse WebUI configurations. This mismatch breaks authentication.

---

✅ Step-by-step guide to fix the No Token error:

1. Locate the Eclipse Server web.config file:

📂 Path:
C:\Program Files\Astria Solutions Group\Eclipse Server\web.config

2. Open the file in Notepad and find the <machineKey> entry. Example:

xmlCopyEdit<machineKey validationKey="517ACDB5D9A2B03EB61DDC0A7EAA33F24C5C17C2122CA7EDB55EC7425A239F83496AEADE2BADBD15C0810EEF4FAF6EC36757C9643D5FB1CF050498231EA0B1D9" />

3. Locate the Eclipse WebUI web.config file:

📂 Path:
C:\Program Files\Astria Solutions Group\Eclipse WebUI\web.config

4. Compare both machineKey validation keys:

✅ If they do not match, copy the validationKey from the Eclipse Server config and paste it into the Eclipse WebUI config.

5. Save the changes to the Eclipse WebUI web.config file.
6. Restart ECM app pools in IIS:

• Open IIS Manager
• Go to Application Pools
• Restart both Eclipse3Server and Eclipse3WebUI
• You can also run iisreset from command prompt for a full reset.

7. Test logging in again.

---

✅ Summary:
The “No Token” error is almost always caused by a mismatch in the machineKey values between the two configs. Keeping these keys synchronized and restarting IIS resolves the error quickly.

Was this article helpful?

0 out of 5 stars

5 Stars		0%
4 Stars		0%
3 Stars		0%
2 Stars		0%
1 Stars		0%

5 Submit

Please Share Your Feedback

How Can We Improve This Article?

Name

Email

Submit