>I don't do much at all with XmlDocument, so I can't really tell you what the error message means without a little research. But is there any way you can figure out *what* changed in the XML? That might help pinpoint what the problem is.

This is our robot application which reads several blogs from our members and tries to identify the updated time of each one. So, the only other way for me to know what is causing this would be to save the XML I am trying to work with before the error happens. This is done at midnight. It happened again last night. So, I will try to isolate the code which is causing this or put a Try/Catch syntax at the XML class level to log more information in such situation.