xml rpc client error illegal character d83d

#Xml rpc client error illegal character d83d how to#

OR, you can just highlight and run the inner-most SELECT (i.e. If the error still happens, it is coming from the CAST(target_data part, else it really is the outer part. Remove the CAST( and AS XML) parts of the outer SELECT. Most likely the error line number that is leading you to the outer select is simply referencing the query, not a particular part of the query. And, if it was the outer CAST, that would mean that an individual deadlock graph would have at least 22,203 lines it. I doubt it is the outer SELECT since that is just taking a subset of the data that is already valid XML. There are two places in your query that cast to XML, so start with confirming which one is throwing the error.

#Xml rpc client error illegal character d83d how to#

Here is how to find the 'illegal' character: 0 (X64) 16:07:19 Copyright (c) 1988-2008 Microsoft Corporation Standard Edition (64-bit) on Windows NT 6.1 (Build 7601: Service Pack 1) (VM) Here is the SQL version for both DB Microsoft SQL Server 2008 (SP3). Sample XML result from the working database: Though this same script was running fine and without any issue in another server with the same version & collation.

XML parsing: line 22203, character 102, illegal xml characterĮven if I changed it to VARCHAR(max) it remains the same. 'NVARCHAR(max)') AS XML) AS DeadlockGraphĪND target_name = 'ring_buffer' ) AS Data - Split out the Event Nodes CROSS APPLY TargetData.nodes('RingBufferTarget/ AS XEventData ( XEvent ) ) AS tab ( event_data )īut it was always ended with the following error: Msg 9420, Level 16, State 1, Line 1 I was running this query in SQL Server 2008 (),Ĭollation: SQL_Latin1_General_CP1_CI_AS SELECTĬAST(event_data.value('(event/data/value)',