Has anyone run across this issue in 2024.1 and the latest version of the PDT off EpicWeb. When trying to analyze a server log it says the file format is not valid. It does not give an error, it just does not load the file.
Thanks
Greg
I feel like I have this from time to time, but I’ve never endeavored to figure it out. Try a different log file and see if there’s an issue.
Usually it’s one of the log files that’s corrupt for some unknown reason… at least for me anyway.
Well I don’t know if I’ll be any help, but when I hit a snag with PDT a few months ago, it was these settings:
This was not for the log file thing. It was for the Config Check, and the error was about net.tcp. I found that advice on here somewhere…
But I’ve never used the log file in the PDT.
Thanks all. I believe the problem was an issue with some of the xml not closed out correctly in file. It used to give a better error when this happen in older versions of the PDT.
2 Likes
That’s what I thought too, I wish there was a way to identify where
Perhaps just running the xml through a validation tool?
It is what it is. sighs and shakes head in Epicor
It failed using a validation tool for XML. I don’t have the fight for me to go through a sizable log file to find a missing “/>”
3 Likes
Right, does the validation tool tell you where to fix it?