1) Open the Microsoft SQL Server Management Studio (As Administrator)
2) In the Database field Enter the below:
\\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query
3) Click Connect
Done
–Resolve the CLR20r3 MoveData.exe Crash
–Property Owner is not available for database SUSDB
–Free up Disk Space in Small Business Server (SBS2008 / SBS2011)
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.
Situation:
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
Problem Signature 09: PSZQOADHX1U5ZAHBHOHGHLDGIY4QIXHX
OS Version: 6.1.7601.2.1.0.305.9
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
Sometimes it is more practical to create a new Mailbox Database and move the mailboxes opposed to moving the Database via the SBS Wizard. The problem is, when you’ve done this and deleted the original Database it stops the SBS Console from creating any new mailboxes when creating a user, this is due to it trying to create the mailbox on the old (now removed) mailbox database.
The warnings received in the SBS Console are:
‘Unable to find the default mailbox database. Make sure mailboxes database exists and you have access to view the database’
‘Mailbox does not exist for reciepient of welcome mail.’
How to update the default mailbox database:
– Open the Exchange Powershell as Administrator
– Run the following command to get the mailbox Database name:
‘Get-MailboxDatabase’
The outcome will look a little something like this:
– Open the registry (regedit) and browse to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SmallBusinessServer\Messaging
– Update the String value of MailboxDatabaseName to the name of the new mailbox database name
Link to Microsoft KB:
https://support.microsoft.com/en-us/help/2500559/-add-a-new-user-wizard-fails-to-create-a-user-mailbox-on-windows-small-business-server-2011
Problem:
The Windows Server Backup fails with error 2155348129 on SBS2011.
Application Error ID 70:
Log Name: Application
Source: Microsoft-SharePoint Products-SharePoint Foundation Search
Event ID: 70
Task Category: Gatherer
Level: Error
User: DOMAIN\spsearch
Computer: SERVER.DOMAIN.local
Description:
The mount operation for the gatherer application 37ad8233-57f1-47b1-873e-6a91d0f1bc36 has failed because the schema version of the search administration database is less than the minimum backwards compatibility schema version supported for this gatherer application. The database might not have been upgraded.
Log Name: Application
Source: Microsoft-Windows-Backup
Event ID: 521
Level: Error
User: SYSTEM
Description:
The backup operation that started at ‘?2011?-?07?-?06T02:12:07.198000000Z’ has failed because the Volume Shadow Copy Service operation to create a shadow copy of the volumes being backed up failed with following error code ‘2155348129’. Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.
Cause:
In SBS 2011 the above issue is normally caused due to a MS SharePoint update that has not been completed. Patching SharePoint Foundation 2010 in SBS2011 is a two-step process. The updated binaries are installed automatically but PSCONFIG must be run manually in order to update the Sharepoint databases.
Resolution:
Check to see if the Sharepoint databases requires an update:
• Launch an elevated SharePoint 2010 Management Shell –
Click Start> All Programs> Microsoft SharePoint 2010 Products> Right click SharePoint 2010 Management Shell and select Run as Administrator.
• Once the shell opens, type the following command followed by enter:
(get-spserver $env:computername).NeedsUpgrade
If the result of this command is True, then you need to complete the following steps in order to update the database. If the result is False then the below probably won’t resolved the issue.
1. Launch an elevated SharePoint 2010 Management Shell –
Click Start> All Programs> Microsoft SharePoint 2010 Products> Right click SharePoint 2010 Management Shell and select Run as Administrator.
2. Type the following followed by enter:
PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures
Note: The Companyweb site will be inaccessible while the command is running. It is best to run the command after business hours. The amount of time the command takes to run will vary on the size of the database and the speed of the server. On a reference machine with 8 logical processors, 32GB of RAM and a 2GB content database, the command took approximately 5 minutes to execute.
Results:
The credit and the original post for this problem can be found here:
https://social.technet.microsoft.com/Forums/en-US/94c5f178-f020-4d0f-ba7c-11c415d0d862/manually-running-psconfig-is-required-after-installing-sharepoint-foundation-2010-updates?forum=smallbusinessserver
For more of my Articles on Windows Small Business Server, please see here:
I’ve written the below article as an overview on how to Free up disk space in SBS2008 and SBS2011.
Reclaiming Disk Space in SBS 2008 / SBS 2011.
The IIS Logs:
IIS logs in SBS 2008/2011 can grow pretty big. Check the following folder and sub directories:
C:\inetpub\logs\LogFiles
Delete the *.log files but do NOT delete the actual folders:
Top TIP:
Unless there is no other option, leave the last one month of logs so that they can be reviewed if ever required. They can always be moved to another volume if you don’t won’t to delete them.
The Windows Small Business Server logs folder:
Windows SBS generates a number of log files when utilising the SBS Console. These logs can become very large over time.
The SBS Log files can be found here:
C:\Program Files\Windows Small Business Server\Logs\
These logs can be moved or deleted if required to free up additional disk space. I’d always suggest moving a log file opposed to deleting it.
Console.log –
Console.log can become particularly big in some instances if you use the SBS Console. This log will continue to grow while the SBS Console is running and as you use the SBS wizards. The Windows SBS Manager service will need to be stopped in order to delete this log. The SBS Console will also need to be closed. Once the log has been moved/deleted, remember to restart the Windows SBS Manager Service.
Top TIP:
When using the SBS Console, make sure that it is closed afterwards. The console.exe process can sap server resources.
*.evtx files –
These are the event logs before the setup of the server completed, they can be safely removed if the server has been in production and had no setup issues.
W3wp.log –
Located in the C:\Program Files\Windows Small Business Server\Logs\WebWorkplace folder. This is the log for Remote Web Workplace (RWA).
MonitoringServiceLogs –
The C:\Program Files\Windows Small Business Server\Logs\MonitoringServiceLogs folder.
These are the logs for the Windows SBS Manager service. As such the service will need to be stopped prior to the logs deletion.
POP Connector Logs –
The POP3 connector log located in C:\Program Files\Windows Small Business Server\Logs\POP3Connector monitors the POP3 Service and keeps a log of the connections made to the POP Server. This log is typically only large if the POP Connector is being used. You will need to stop the Windows SBS POP3 Connector Service in order to delete these logs.
POP Connector Badmail –
If you the POP3 Connector is being used, you may end up with emails that failed to be delivered (rejected by the local Exchange server) in C:\Program Files\Windows Small Business Server\Data\badmail.
WSUS Cleanup Wizard:
Windows SBS 2008/2011 comes with Windows Server Update Services (WSUS) pre-installed. The database and content for this feature can grow massively over time. To help reduce this space, you can run the WSUS Cleanup Wizard:
To run the Server Cleanup Wizard :
1. Click Start>Administrative Tools> Windows Server Update Services
2. The WSUS Administration Console will open > Expand the server name> Select Options, and then Server Cleanup Wizard.
3. Select one option at a time and click next.
4. The wizard will begin the cleanup process and will present a summary when it has completed. Click Finish to complete the process.
5. Repeat steps 2-4 until you’ve gone through all the cleaned up options.
Note:
If the cleanup wizard has not been run in a while (or ever) it can take several attempts for the wizard to succeed. The wizard can crash so don’t be alarmed if you’re given an error. If the wizard crashes and you’re unable to open the WSUS Console then restart the following services and try again:
Windows Update / Windows Internal Database.
The SBS Move Data Wizards:
The SBS Console comes with a number of Wizards that allows the admin to move certain files and folders to other partitions. It is suggested that a good backup always be taken prior to the wizards being run. The Wizards can be accessed from the SBS Console> Backup and Server Storage> Server Storage. See the wizards on the right hand side.
– Move Exchange Server Data:
This moves both the exchange database file as well as your exchange transaction logs for all storage groups.
– Move Windows SharePoint Services Data:
This moves the SharePoint Content and Configuration databases.
– Move Users’ Shared Data:
This moves C:\Users\Shares\ directory and all sub directories
– Move Users’ Redirected Documents Data:
This moves C:\Users\FolderRedirections\ directory and all sub directories
– Move Windows Update Repository Data:
This moves the Windows Update repository data from C:\WSUS\WSUSContent and C:\WSUS\UpdateServicePackages. Please note it does NOT move the actual WSUS Database (SUSDB).
Move Wizards location:
Moving the WSUS Database:
The Windows Server Update Services Database can be relocated by doing the below. Again a good backup is recommended prior to proceeding:
– Launch SQL Server Management Studio Express console as an administrator. It is located under Start > Programs >Microsoft SQL Server 2008 R2 > SQL Server Management Studio Express.
– Fill in the following information and then click Connect
– Server type: Database Engine
– Servername: \\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query
– Authentication: Windows Authentication
– Expand Databases and right-click on SUSDB and select Tasks > Detach… from the context menu.
– Select the “Drop Connection” checkbox and click OK.
– Open Windows explorer and COPY the C:\WSUS\SUSDB folder to the new location on another partition.
– To reattach the database, right-click on Database and select Attach… from the context menu.
– On the Attach Databases page select the Add button.
– Browse to the new location of the SUSDB.mdf database and select OK twice to complete the move
– Delete the old Database folder once you’re happy that it is working correctly.
Still running low on disk space?
Download and install TreeSize Free (http://www.jam-software.com/freeware/)
Run a scan on the drive and it will display all the folders on that drive as well as their file sizes. You can then see where the largest folders are and determine what else is taking up space.
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:
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.