Skip to main content

LevelBlue Completes Acquisition of Cybereason.  Learn More

LevelBlue Completes Acquisition of Cybereason.  Learn More

Services
Cyber Advisory
Managed Cloud Security
Data Security
Managed Detection & Response
Email Security
Managed Network Infrastructure Security
Exposure Management
Security Operations Platforms
Incident Readiness & Response
SpiderLabs Threat Intelligence
Solutions
BY TOPIC
Offensive Security
Solutions to maximize your security ROI
Operational Technology
End-to-end OT security
Microsoft Security
Unlock the full power of Microsoft Security
Securing the IoT Landscape
Test, monitor and secure network objects
Why LevelBlue
About Us
Awards and Accolades
LevelBlue SpiderLabs
LevelBlue Security Operations Platforms
Security Colony
Partners
Microsoft Security
Unlock the full power of Microsoft Security
Technology Alliance Partners
Key alliances who align and support our ecosystem of security offerings
Loading...
Loading...

ERRMSG: MailMarshal SQM failed to authenticate the user ‘Domain\User'

Expand / Collapse


This article applies to:

  • Trustwave MailMarshal (SEG) Spam Quarantine Management website
  • Trustwave ECM/MailMarshal Exchange 7.X Quarantine Management website

Symptoms:

  • If you rename an Active Directory user account, the user is unable to log into the MailMarshal SQM or QM website.
  • For example:
    • The Active Directory account 'Testuser1' is renamed to 'Testuser2'. 
    • When this user attempts to log on to the MailMarshal website they receive the following error: MailMarshal SQM failed to authenticate the user ‘Domain\Testuser1', if the problem persists contact your Administrator

Cause:

This issue is caused by caching of the Windows Authentication credential at the server.

  • Note: Changing the credential will also cause an issue with user aliases. The user will not see their personal content once logged on. To fix this separate issue, see Trustwave Knowledgebase article Q10003.

Resolution:

To clear the cached credentials, restart Windows on the web server.

Before restarting Windows, you can try the following actions which are less disruptive.

  • Wait for a period of time without attempting to use the account for this connection, to allow the cached credential to time out.
  • Clear the authentication cache at the client.
  • Restart IIS on the web server.

      To contact Trustwave about this article or to request support:


      Rate this Article:
           

      Add Your Comments


      Comment submission is disabled for anonymous users.
      Please send feedback to Trustwave Technical Support or the Webmaster
      .