MOSS: Observations on InfoPath debugging

InfoPath form server error messages are misleading.


During development of an InfoPath form, I would post it to MOSS server and access the form. The form would start to load and then generate a misleading error message pointing me to the windows event log for details. In fact, no message was written to the windows event log. Rather, the message was sent to the MOSS ascii diagnostic log. You can track that down via central services administration.


You need to be quick on your feet. MOSS likes to write to the log file, frequently and verbosely. This can be trimmed but the default log writing behavior is "everything as quickly as possible".

One thought on “MOSS: Observations on InfoPath debugging

  1. No name

    Hi Paul and thank you for all your useful posts.
    I was wondering if there is any alternative for not promoting field while publishing your infopath form. Promoted column approach, not olny causes issue for publishing complex forms, also it is not maintainable. and you end up with having massive number of columns under your column list.
    Do you suggest any idea???
    Thank you


Leave a Reply

Your email address will not be published. Required fields are marked *