Have you ever noticed when looking at the Job Log of a To/From LDAP task that the HTML and XML views of the log are empty, but the text views works fine? I know I have and it bugged the $#@* out of me.
I asked around at TechEd about this and got a good answer: This happens where there is binary data in the log file that has not been converted. Unfortunately this seems to happen when you most need a nicely formatted log during the troubleshooting process.
Well at least we don't need to worry any more why we are only getting 1/3 of the log content we were expecting!
5 comments:
Hi Matt - I can't remember what made us try this, but a colleague did the save As from the xml screen even though it was blank, and it does save with content. of course it then needs to be parsed, but a good discovery nonetheless.
Excellent point. Thanks!
To read the ADS logs we still can manage with the work area folders, But did someone figure out how can we not loose the 3/4 of the content?
Not exactly sure what you're asking about here, but if you're referring to errors/warnings not in log, you can change the number of items to be included, check the logging settings for the job or pass in question.
Yes that is what I meant. thanks
Post a Comment