Tag: Windows Small Business Server 2011

SBS2011 – MoveData.exe – CLR20r3 Crash (Moving WSUS Database)

SBS2011 – MoveData.exe – CLR20r3 Crash (Moving WSUS Database)

I’ve come across a few issues over the years with the Move Data wizard in the SBS Console.

I decided to write about this one specifically because its a common issue I have when taking over Server Support from another provider.


Space on the Servers C:\ partition is running out. SBS2008/SBS2011 have a few useful wizards in the SBS Console which allows the Administrator to move large items like the Exchange Database, WSUS and User folders with ease. This is called the MoveData Wizard.


When trying to move data like the WSUS Content to another Drive via the SBS Console, you get the following error:

Windows SBS 2011 Standard Console has stopped working

Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: MoveData.exe
Problem Signature 02: 6.1.7900.0
Problem Signature 03: 4cd854e7
Problem Signature 04: StorageCommon
Problem Signature 05: 6.1.7900.6
Problem Signature 06: 52547e02
Problem Signature 07: 174
Problem Signature 08: 6f
OS Version: 6.1.7601.
Locale ID: 2057
Additional Information 1: 4323
Additional Information 2: 43239e9fc32d5958d879af5d68b14cad
Additional Information 3: ad0b
Additional Information 4: ad0b47be9336c61ea7f4be913ec84e32



To get to the bottom of the problem you need to find out why the MoveData.exe process has crashed. Forunatly Microsoft have given you a log for this which can be found here:
C:\Program Files\Windows Small Business Server\Logs\movedata.log

In my case, the log information gave me this:

[25944] 170526.082631.4406: General: Initializing…C:\Program Files\Windows Small Business Server\Bin\MoveData.exe
[25944] 170526.082631.6066: Storage: Data Store to be moved: WSUS
[25944] 170526.082634.1439: Storage: An error occured during the execution: System.Runtime.InteropServices.COMException (0x80070422): The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. (Exception from HRESULT: 0x80070422)
at WindowsUpdateAgent.IUpdateInstaller.get_IsBusy()
at Microsoft.WindowsServerSolutions.Storage.Common.MoveDataUtil.IsSystemPerformingCriticalMaintenance()
at Microsoft.WindowsServerSolutions.Storage.MoveData.MainClass.Main(String[] args)

Yup, it was as simple as the Windows Update Service was not started. The last administrator had disabled the service for some stupid reason… 

I checked the service via services.msc, changed it to Automatic, started it and re-run the Move Data wizard from the console.

Job done.

I then spent a few hours updating the server.

Related Links:

If you’re having a similar but not exact problem to this, it would be worth checking the below Question which I answered on the Experts-Exchange forum. This may help you further:


For further information about how to cleanup disk space on Small Business Server, see here:
Free up disk space in SBS2008 and SBS2011

For more of my Articles on SBS click here:
SBS Articles

Server 2008 R2 (SBS2011) – DNS Access Denied – Network (Unauthenticated)

Server 2008 R2 (SBS2011) – DNS Access Denied – Network (Unauthenticated)

Recently I had a client with an SBS2011 who lost power to the server. Client PCs were unable to access the server resources and errored saying that the PC may have been compromised.

When the server had rebooted the network location had changed to Unauthenticated. When trying to access the DNS console I was getting an error saying Access Denied.

See below for reference:

DNS Access Denied

DCDiag was failing on connectivity but Active Directory Users and Computers was accessible.

After a while I managed to resolved the error by running the below command followed by a reboot:

nltest /sc_change_pwd:domainname.local

Command Description:
Changes the password for the trust account of a domain that you specify. If you run nltest on a domain controller, and an explicit trust relationship exists, then nltest resets the password for the interdomain trust account. Otherwise, nltest changes the computer account password for the domain that you specify. You can use this parameter only for computers that are running Windows 2000 and later.

Once the server had rebooted the network location changed back to ‘Domain’ and DNS was accessible. All client machines was then able to access the server.

Comments on my blog have indicated that this fix also works with Server 2012 R2.

[amazon_link asins=’B01EZU2RLA,B00JLPEL2I,B01M1VAONS’ template=’ProductGrid’ store=’412294wp-21′ marketplace=’UK’ link_id=’4aa94d1d-578b-11e8-8999-a31504c592b5′]