WSUS – Error: Unexpected Error

Posted by robd on May 16, 2017
WSUS / 4 Comments

Recently our WSUS console kept crashing either when opening certain computer folders or All Computers.

Error: Unexpected error

So after lots of frustration I rebuild WSUS on Server 2016 and using a proper SQL instance:

Uninstall WSUS PowerShell:

Then re-install with powershell:

Then set the SQL instance using a elevated CMD:

The servers all started populating, great.

Then FAIL again.

After some Googling I found the problem seems to be with a corrupt PC checking in, i.e. the PC checks in, then via WMI all the info is gathered on the PC and if that info is corrupt then WSUS crashes!!

To fix,

Copy the WSUS console error into Notepad++ (don’t use anything else) and look for:

Basically this means that the weird square symbol or SYM symbol is present in the WSUS database and causing WSUS to shit itself:

So we need to find it, open SQL Management Studio and open the SUSDB

Note: if you’re not using proper SQL then open the DB via:

Changed the default view setting by going to the Tools > Options > SQL Server Object Explorer settings, then adjusted the ‘Value for Edit Top <n> Rows command’ from 200 to 0, making the option display all rows.

Navigate down within the SUSDB database, to the dbo.tbComputerTargetDetail table, right-clicked it, and selected ‘Edit All Rows’.

Click the top left corner of the column/rows to select everything, then copy-pasted it into NotePad++

Then copy the SYM from the error and search for it in the info you’ve just copied:

As you can see the ID on the left is 525:

Lets now cross reference this against another table in the SUSDB database via SQL script:

Look for the ID:

Thats the PC!!!

Find it and update the BIOS and anything else you can, then get it to report in again to WSUS:


Credit to SterlingT, he’s a wonderful human being:

Tags: , , ,

Veeam – Unable to release guest. Error: Unfreeze error (over VIX): [Backup job failed.]

Posted by robd on February 06, 2013
Veeam / No Comments

If you’re a Veeam user you may feel the same way as I do when it comes to the product, that is:

“It’s absolutely brilliant and I really love it but when it goes wrong, it really goes wrong!”

So we recently we had a backup failure where were getting the following error:

Unable to release guest. Error: Unfreeze error (over VIX): [Backup job failed.]

On the exchange server we were seeing these kind of errors in the event log:

Information Store (3424) Shadow copy instance  freeze ended.


Volume Shadow Copy Service error: Unexpected error calling routine ConvertStringSidToSid (S-2-6-11-2001077031-0230750062-1115881885-1111.bak).


Also when I ran “vssadmin list writers” in a command prompt  I found:



So after some Googling, I found fixes such as:


Reboot the server,

Uninstall any Symantec backup exec agents on the machine,

Re-install VMware tools,

Run a batch script to re-register VSS DLL’s (I’ll post it below),

Make sure Windows firewalls are off.


Well none of these ended up being our issue, ours was down to our physical internal firewalls!!  A change had been made meaning the Exchange VSS writer couldn’t write directly to the SAN meaning by the time it routed there via an alternative path the default 20 seconds VSS Microsoft Exchange Writer had timed out!  Bugger.


So the firewall man, reverted his change and Bobs your uncle, successful backup!!

Script as promised:

Tags: , , , , ,

Copy Protected by Chetan's WP-Copyprotect.