January 22, 2009 at 2:58 pm
Warning: Null value is eliminated by an aggregate or other SET operation.
Msg 6603, Level 16, State 1, Server VBSA, Procedure sp_xml_preparedocument, Line 28
XML parsing error: Invalid at the top level of the document.
I am constantly getting the above error message whenever I try to run a script setup to change settings in a program. There appears to be nothing wrong with the code, and I've had it reviewed by others and I've looked it over myself, but noboyd hasenough experience to really debug it.
Is there any general fixes or checks I could use for this? Could anyone give me a betetr description on how to get this cleaned up? I know how to fix the null value I believe, but I'm unable to debug the bottom two. Even if someone could describe a general case in which these error messages would occur, it would be greatly appreciated. If it's something that not so general, I can post the code here as well.
January 22, 2009 at 3:33 pm
You have 2 messages. The first message is a warning which means that you have some aggregation function, but the server encountered null value. Since null is an unknown value, the server ignored it and. This shouldn’t bother you, but if you don’t want to get this warning you turn the set option ansi_warnings off. Notice that this has other effects, so I suggest that before taking this decision read about it in BOL (look for the article SET ANSI_WARNINGS).
The second error seems to be with an XML string that you pass to the procedure sp_xml_preparedocument. It seems that this string can not be parsed as XML. Make sure that it is a valid XML.
Adi
--------------------------------------------------------------
To know how to ask questions and increase the chances of getting asnwers:
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
January 23, 2009 at 7:28 am
could the problem with the xml be the encoding? I've bee using ansi right now. From what I can tell though, it should work with ANSI.
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply