Endpoint Protection

 View Only
  • 1.  Invalid XML Character

    Posted Jun 02, 2009 03:27 PM
    I have been receiving the following error message intermediately since we've had Endpoint Protection.

    We started with MR2 and now we are on MR4 MP1.

    The error is sent via the server system event notification condition with a severity rating of severe.

    Event Type: An unexpected exception has occurred.
    Description: An invalid XML character (Unicode: 0x0) was found in the CDATA section.



    This has been an annoyance since the start and I was looking for any suggestions/remedies on this.

    I tried calling support, however they said not to worry about it, that it should go away. However it'll pop-up a few times one week, and not show up for another 2, its very intermittent but it also comes back up.


    Any help would be appreciated.

    Thanks

    Current System

    Windows 2003 R2 SP2
    Symantec Endpoint Protection MR4 MP1
    Running with a SQL DB on SQL 2005 SP2 on Widows 2003 R2 SP2






  • 2.  RE: Invalid XML Character

    Posted Jun 03, 2009 12:13 PM
    Just getting this out there, loking for some feedback


  • 3.  RE: Invalid XML Character

    Posted Jun 03, 2009 12:22 PM
    Are u getting this error in client or in SEPM????


  • 4.  RE: Invalid XML Character
    Best Answer

    Posted Jun 03, 2009 01:01 PM
    The server side message "Invalid XML Character" is in response to a client side problem (not properly sending up event data). This defect was present in MR2 clients. This was fixed in MR3 clients.

    I suspect that you have an MR4-MP1 server with one or more MR2 clients still in your evironment. If this is indeed the case, once you upgrade all of the clients, the error should go away.


  • 5.  RE: Invalid XML Character

    Posted Jun 03, 2009 01:32 PM
    Good solution Mr. Landon. It can also be a cause.
    Just to get some idea .....Does this error has any relation with the JRE ???


  • 6.  RE: Invalid XML Character

    Posted Jun 03, 2009 06:50 PM
    I thought we had gotten all the MR2 Clients.

    I looked into this using the computer status logs and in the filters selected the MR2 product version and I found the client that was still on MR2

    Thanks