WSUS SP1 Upgrade and now hexadecimal error

Discussion in 'Update Services' started by Mark Wiseley, Jun 2, 2006.

  1. Mark Wiseley

    Mark Wiseley Guest

    Ok, so things were working great, then I installed SP1 for WSUS. Everything
    still looked good, so I set WSUS to point to the Microsoft Beta update site
    to get the updates for Vista
    (http://technet2.microsoft.com/Windo...70c3aea9-4dc2-49ad-a085-dc1b59f1af7d1033.mspx).
    Did a sync and tons of updates came in. So I click on critical updates and
    approve. So far so good. Then I click on Review Other updates. That's
    when I get this weird hexadecimal value 0x1A, is an invalid character.
    Line1, position 11710. Show details below:
    System.Xml.XmlException: '', hexadecimal value 0x1A, is an invalid
    character. Line 1, position 11710.
    at System.Xml.XmlScanner.ScanContent()
    at System.Xml.XmlTextReader.ParseBeginTagExpandCharEntities()
    at System.Xml.XmlTextReader.Read()
    at System.Xml.XmlValidatingReader.ReadNoCollectTextToken()
    at System.Xml.XmlValidatingReader.Read()
    at System.Xml.XmlLoader.LoadCurrentNode()
    at System.Xml.XmlLoader.LoadDocSequence(XmlDocument parentDoc)
    at System.Xml.XmlLoader.Load(XmlDocument doc, XmlReader reader, Boolean
    preserveWhitespace)
    at System.Xml.XmlDocument.Load(XmlReader reader)
    at System.Xml.XmlDocument.LoadXml(String xml)
    at AdminControls.TableCustomControl.Display(String tableXmlString)
    at Administration.Updates.List.Page_Load(Object sender, EventArgs e)

    at System.Xml.XmlScanner.ScanContent()
    at System.Xml.XmlTextReader.ParseBeginTagExpandCharEntities()
    at System.Xml.XmlTextReader.Read()
    at System.Xml.XmlValidatingReader.ReadNoCollectTextToken()
    at System.Xml.XmlValidatingReader.Read()
    at System.Xml.XmlLoader.LoadCurrentNode()
    at System.Xml.XmlLoader.LoadDocSequence(XmlDocument parentDoc)
    at System.Xml.XmlLoader.Load(XmlDocument doc, XmlReader reader, Boolean
    preserveWhitespace)
    at System.Xml.XmlDocument.Load(XmlReader reader)
    at System.Xml.XmlDocument.LoadXml(String xml)
    at AdminControls.TableCustomControl.Display(String tableXmlString)
    at Administration.Updates.List.Page_Load(Object sender, EventArgs

    Anyone have any idea how to fix this?

    Thanks,
    Mark
     
    Mark Wiseley, Jun 2, 2006
    #1
    1. Advertisements

  2. Mark Wiseley

    Mark Wiseley Guest

     
    Mark Wiseley, Jun 2, 2006
    #2
    1. Advertisements

  3. Can't repro on my WSUS test box. I do see some errors in my
    SoftwareDistribution.log file about updates not inserting correctly - but
    these were silent failures. Check your log file -- C:\Program Files\Update
    Services\LogFiles\SoftwareDistribution.log and see if anything in your most
    recent 'beta' sync looks odd.

    Also - something else that is strange about your situation is that you got a
    bunch of new updates after you ran the script and synchronized. I didn't
    get any new updates myself... so maybe you caught one of the beta servers at
    a bad time :(

    Report back any additional findings and we'll all see what we can do to
    help.

    Thanks,
     
    Jeff Centimano [MVP - Windows Server], Jun 2, 2006
    #3
  4. Mark Wiseley

    Mark Wiseley Guest

    Ok, so I have limited it down to being a Vista Driver download issue. Here
    is what I have done. Reset the database, changed the synch option to not
    download and to pull update from MSUS. Now when I look at the updates, I
    still get the error, so I started customizing the view, and if I select
    Vista, and drivers, I get the hexadecimal error. If I select everything
    else, except that, then I can approve and deny my updates. How can I get
    this cleared out or reset???

    Thanks,
    Mark Wiseley
     
    Mark Wiseley, Jun 5, 2006
    #4
  5. Mark - interesting. This would also make sense why I'm not able to repro...
    I never sync drivers (just a personal preference). I'll reconfigure my test
    environment to include Vista drivers and see what happens.

    Back w/ you shortly.

    --Jeff
     
    Jeff Centimano [MVP - Windows Server], Jun 5, 2006
    #5
  6. Mark Wiseley

    Mark Wiseley Guest

    Ok, so before I waste one of my PSS calls, one question. I have changed my
    synch settings to not sych Drivers. However, the drivers are already
    downloaded and waiting to be approved or denied, but I can't get that view
    to display to be able to approve or deny. Is there any way to reset the
    updates, or force a new synch or something to get past this??? Thanks for
    your help.

    Mark
     
    Mark Wiseley, Jun 6, 2006
    #6
  7. Unfortunately, once they're in the DB there's not much you can do about it -
    except roll back to a previous backup before this issue. You can remove the
    updates themselves from the file system (see the Mowing the Grass page on
    the WSUS Wiki for info), but the metadata will still be there. In fact, you
    can't even mow the grass since you have to first decline the updates for the
    'purgeunneededfiles' to do anything. So... as painful as it sounds a PSS
    call is probably in order. If you can hold off 24 more hours I've put an
    e-mail in to the WSUS PM to get her thoughts on the subject. I'll follow up
    once I hear something from her.

    Thanks,

    Jeff
     
    Jeff Centimano [MVP - Windows Server], Jun 6, 2006
    #7
  8. Mark Wiseley

    Mark Wiseley Guest

    As of right now, I have created a new WSUS server with SP1, and downloading
    the updates. I have modified my GPO so the clients point to the new WSUS,
    and basically I am going to blow away the old WSUS Server. Not the best
    option, but I have spent too much time on this already and need to get WSUS
    back up and running so I can move on.

    Mark
     
    Mark Wiseley, Jun 8, 2006
    #8
  9. From what I understood, Bobbie (WSUS PM) was going to get involved in this
    thread - but it looks like she posted a new thread above. See her message,
    dated 6/7 - titled 'Vista Beta Driver Update Revisions' for an overview of
    the situation. Bottom line - this is a known issue that you guys bumped
    into. Wish we could have found this during the SP1 beta, but the MU
    back-end wasn't ready w/ Vista drivers... so us testers never got the chance
    to sync the beta catalog.

    Hope you all get back on track soon!


    --
    Jeff Centimano
    MVP - Windows Server
    http://windowsconnected.com/blogs/jeff
     
    Jeff Centimano [MVP - Windows Server], Jun 8, 2006
    #9
  10. I am so sorry folks for not posting to this thread. The jist is Hi - I
    wanted to get back to folks who had the issue with the Vista Beta
    driver downloaded from the beta MU site or what we call "BUMC".
    If you had deployed a WSUS with SP1 server and pointed it to BUMC server to
    download Vista updates to service your Vista Beta 2 clients and had elected
    to synch drivers for Windows Vista, read on.

    The Vista driver update (ID number: e1e8fe52-062c-4f6e-9a30-47c2db9d8207)
    contained malformed metadata that caused problems with the WSUS UI. A new
    revision has been published to minimize the impact of this issue.
    Re-synching with the BUMC server will mark this update as expired and hide
    it from the default views for Updates. You will be unblocked from working
    with normal updates and approval types, but it should be noted that viewing
    the list of "declined" updates on the server will still cause a failure in
    the UI. The packages were not ready for testing before we went out with
    SP1 - so apologies this was not caught.

    We have gone thru all the other driver metadata and do not find this
    occuring in anyother updates. thnx - bobbie

    --
    Bobbie Harder
    Program Manager, WSUS
    Microsoft

    This posting is provided "As Is" with no warranties, and confers no rights.
    Use of included script samples are subject to the terms specified at
    http://www.microsoft.com/info/cpyright.htm


    --
    Bobbie Harder
    Program Manager, WSUS
    Microsoft

    This posting is provided "As Is" with no warranties, and confers no rights.
    Use of included script samples are subject to the terms specified at
    http://www.microsoft.com/info/cpyright.htm
     
    Bobbie Harder \(MSFT\), Jun 9, 2006
    #10
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.