Expected hex 0x in '{0xdddddddd, etc}' in XsltListViewWebPart

Question

I have a slight glitch in a webpart. On the webpart, after the page loads, the first time you click on a row, this error pops up. You can navigate to a different tab on the same page or click another row or use the select all checkbox and it will no longer do this. However, if you then refresh the page, it will do it again. I have seen a few others have this issue and they had to rebuild the whole page. The webpart works fine however, and you can do whatever you want, its just annoying so I want to get rid of it. Any thoughts??!

Update: 10/13 - It seems that in some cases, rebuilding the page exactly the same way corrects the issue. This is okay for smaller pages, but it is very tedious for larger more complex pages.

Answer 1

Might be a bug. Two posts that might help: http://chrissyblanco.blogspot.com/2007/12/bug-with-customaction-in-actions-menu.html and a solution here http://stephenkaye.blogspot.com/2008/02/bug-with-customactions.html

Answer 2

I too had this problem on an application page I deployed from visual studio to a publishing webs Pages catalog. When I declared the XsltListViewWebPart only in the aspx it almost worked but with mentioned error (expected hex 0x...) and my document tools in the ribbon could not be found.

I had to declare the parameters codebehind and it needs to be done before Page_Load() or OnLoad(). Not sure if OnInit() is right but it works for me :) Otherwise you get an error message saying that your view is invalid (don't know exact message since my error is in Swedish). The code I use is in a usercontrol:

    protected override void OnInit(EventArgs e)
    {
        base.OnInit(e);

        // This code must be run early or an error saying "Choosen view is invalid" will be displayed
        SPList list = SPContext.Current.Web.Lists.TryGetList("Documents");
        SPView view = list.DefaultView;
        mXsltListViewWebPart.Title = "Document library";
        mXsltListViewWebPart.ListId = list.ID;
        mXsltListViewWebPart.ViewGuid = view.ID.ToString("B");
        mXsltListViewWebPart.XmlDefinition = view.GetViewXml();
    }

Answer 3

I also think it is a bug....This seems to be the fix. Worked for me: http://developz.blogspot.com/2012/02/expected-hex-0x-in-0xdddddddd-etc.html