We have a weird issue that I have been working with support on for a while that we can't seem to resolve.
For some reason, out of the blue, we are now getting a System Error when trying to login to the CSA.
We have tried removing the .password file and creating a new CSA password which results in the same thing.
The logs sort of claim that the properties.xml file was somehow corrupted - yet the Clarity app works just fine.
Support ultimately had me create a new properties.xml using the template in the .setup folder as the base and copying the values from the old file into the new one.
We loaded the new file on the server and restarted all services, but still we are getting the System Error when trying to login to CSA.
The logs pretty much don't say anything about this event, which has me baffled.
Anyone else encounter this and figure out how to resolve?
This is on v 126.96.36.1996 09 3
Can you check in which charset the properties.xml is saved? (UTF-8, Windows-1252, etc).
If you open the file with notepad and then choose 'Save As...', you will be able to see the charset guess n the combobox 'Encoding'.
If it´s not UTF-8, try to change it to UTF-8.
If you do that, check the first line of the XML. If it starts with '<?xml', then you must change the property encoding to UTF-8, like the example below:
<?xml version="1.0" encoding="UTF-8"?>
It is UTF-8.
Can you try removing the csa and redeploying to.see if that helps
Tried that. Still didn’t work.
Strange.... Try this step up from possible. Back up the Clarity directory and install clarity from iso and point that csa to the database and see if you are able to login to csa.
Hum, maybe the file is UTF-8 + BOM, or maybe JVM is using a different default charset when reading files.
Do you have any special character in the XML? Something like : á, ã, ç, etc. If so, try to replace them by an ASCII character, and save the file using ASCII charset.
Try restart CSA and check if the error persist.
we are now experiencing the same issue. Did you find a resolution.