This log file (MalformedXml.errorLog) is huge in all three of our tenants. Everything seems to be working fine, so I haven't been too concerned with the contents. I periodically delete them, and the systems create new ones, but the get extremely large. Can anyone shed some light on this log?
Does anyone from Ivanti have an answer?
Thanks for posting to the Ivanti Community.
Sorry that it seems no one has the answer to be able to assist you on this yet. Please do consider the other ways to engage with us to get assistance:
Thanks for responding Michael.
So, can I infer from your comment that this is not a 'normal' thing and other users are not seeing the same issue?
I think this is "normal" behaviour: In our environments, these files get extremely large, too, although everything is working fine. Therefore, we just delete them from time to time.
I would log a support ticket and find out what the log is for. Personally I havens investigated it.
2 of 2 people found this helpful
Logging Service writes an entry to this file when it runs into an XmlException in a method called ReadNextLogEntry(). The exception is apparently raised when a logfile entry is somewhat malformed.
You can check your Windows Application Event Log for a corresponding entry. On my system Logging Service frequently complains about 'log4net' being an undeclared prefix.
Those malformed entries probably do not make it to the Logs table in ISM.
We have the same problem, logfiles are growing +/- 4GB a day.
Is there a setting we can adjust to stop this logging
Usually we got such file after push operations or after direct SQL backup/restore DB from one tenant to another.
After that we need to delete this file and restart Logging service.