Unexpected UI errors in WSUS

Posted by bink on November 13 2007, 11:45 PM. Posted in WSUS.

WSUS Blog:

We have been hearing reports from some customers who use WSUS that they have been having trouble accessing their administration consoles. We have confirmed the cause of this issue and fixed it on our servers, which will automatically fix the issue for most customers on their next synchronization cycle.  This post will explain the issue in detail and provide steps customers can take to get WSUS working again even sooner.

<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /><o:p> </o:p>

The cause of this issue is that, on Sunday evening, Microsoft renamed a product category entry for Forefront to clarify the scope of updates that will be included in the future. Unfortunately the category name that was used included the word Nitrogen in double quotes (appearing as “Nitrogen”). A double quote is a restricted character within WSUS, which created an error condition on the administration console.  This issue occurred on many WSUS servers that synchronized with Microsoft servers between 5pm Sunday and 11am Monday Pacific Time.

<o:p> </o:p>

We renamed the category to eliminate the double quotes on Monday morning at 11am after investigating and validating the problem.  This will fix the issue for any impacted WSUS server the next time it synchronizes with Microsoft’s servers.  We are also improving our publishing tools to make sure that issues like this are caught during the publishing process, before they impact customers.

<o:p> </o:p>

It’s important to note that WSUS customers whose servers did not synchronize during this time, or end users connecting directly with Windows Update, Microsoft Update, or Automatic Updates are not impacted by this issue.