XML errors when running specific reports in SCCM 2012.

Question

I'm having almost exactly the same problem as is referenced in this article:  http://social.msdn.microsoft.com/Forums/uk/sqlreportingservices/thread/587a3319-bc54-4d30-bb3f-bb90a0c6ec50.  When I try to run either of these reports (Computers with
specific software registered in Add Remove Programs; Count of instances of specific software registered with Add or Remove Programs) I receive the XML error shown in the attached screenshot.  I'm fairly sure the problem is the same as the other admin
was experiencing and I just need to remove the unprintable characters from the dbo.v_Add_Remove_Program column.  However, I have not been able to figure that part out yet.  In addition, will this be a potentially reoccurring issue?  I'm assuming
it is being caused by an application with a strange name being listed in the SQL table.  Thank you in advance.
Über Random

Answer 1

Torsten,  thank you for your response, I do appreciate it.  However, I had already seen the information from Garth and so had run the following SQL query: 
use CM_UV2
Select distinct
 CHARINDEX(cast(0xFFFF as varchar(1)),DisplayName0),
 DisplayName0
from
 dbo.v_Add_Remove_Programs
Where
 CHARINDEX(cast(0xFFFF as varchar(1)),DisplayName0) > 0
When I run that query, plugging in 0xFFFF from my error, it executes successfully, but I get nothing in the way of results.  When I use Garth's 0x28 I receive the expected results of any software that has a "(" in it.  Can anyone tell me why
the 0xFFFF cannot be found or what 0xFFFF resolves to?
Are there any other methods from MS for resolving this issue other than hacking their databases??  In one of the articles I was looking at the MS MVP was quick to state that finding and deleting any offending values in order to make the reports run
correctly was definitely in no way supported.  Now, I understand that MS can't have people just going around and hacking up their reports and still expect to be supported, but at this point I REALLY must call BS!  Microsoft really
needs to come up with a permanent solution to this problem that doesn't involve hacking the database. 
Über Random