Policy Server Guides › Policy Server Configuration Guide › Troubleshooting

Troubleshooting

Non-english Input Characters Contain Junk Characters

Symptom:

When I install or configure SiteMinder components in the console mode on UNIX machines, few non-English input characters are not displayed correctly in the console window.

Solution:

Verify terminal settings of your console window and confirm that the console does not clear high (8th) bit of input characters by executing the following command:

stty -istrip

Error Message from Advanced Authentication Server

Symptom:

My users are seeing the following browser error:

An internal error has occurred. Please close and re‑open your browser. If the problem persists, please contact your helpdesk.

Solution:

Check the following items:

• Verify that the RiskMinder service is up and running on the Policy Server.
• Verify that RiskMinder is in the READY state by checking the following log file:

  siteminder_installation_directory\..\aas\logs\cariskminderstartup.log
  

• Restart the CA SiteMinder® SPS.
• If the DeviceDNA™ is not being collected, do the following steps:
  1. Configure the JVM with the JSafeJCE Security Provider.
  2. Restart the CA SiteMinder® SPS.

More information:

Configure your CA SiteMinder® SPS Environment for Enhanced Session Assurance with DeviceDNA™

"Token not Found" Error

Symptom:

The Flow Application log file from my CA SiteMinder® SPS shows the following error:

Token is not found...

Solution:

Verify the following items:

• Verify that your agent is enabled.
• Verify that your Policy Server is connected to your session store.