Posts Tagged ‘error’

Hi Folks,

in the last days I had massive problems setting up the replication of a database in a DAG.
While executing the command Add-Database Copy” following error message was generated:

[PS] C:\>Get-MailboxDatabase -Server AD-ex01 | Add-MailboxDatabaseCopy -MailboxServer AD-ex11 -ActivationPreference 2
The seeding operation failed. Error: An error occurred while performing the seed operation. Error: Failed to notify source server
‘AD-EX01.AD.customer.local’ about the local truncation point. Hresult: 0xc8000713. Error: Unable to find the file.
[Database: ex00-mdb001, Server: AD-EX11.AD.customer.local]
+ CategoryInfo          : InvalidOperation: (:) [Add-MailboxDatabaseCopy], SeedInProgressException
+ FullyQualifiedErrorId : [Server=AD-EX01,RequestId=2e434125-4b73-4845-b42c-218aae43caf4,TimeStamp=07.10.2014 15:37:18] [FailureCategory=Cmdlet-SeedInPr
ogressException] 92042DF7,Microsoft.Exchange.Management.SystemConfigurationTasks.AddMailboxDatabaseCopy
+ PSComputerName        : AD-ex01.AD.customer.local

After trying to enable replication by turning on / off circular logging to replicate, we opened a case at Microsoft Support.

The solution provide from Microsoft Support worked:

1. Dismount database

2. Make sure the database is in “clean shutdown” state:
ESEutil /mh X:\Databases\Database.edb

If database isn’t in clean shutdown you’ve to repair it with eseutil:
Eseutil /r E00 /d: “Database Path” /l: “Log Folder Path” /s: “Log Folder Path” /a /i

3. Move away all data and folders within the Log Folder Path

4. Mount database

5. Update the Prior failed database copy

Update-MailboxDatabaseCopy database\AD-EX11 -DeleteExistingFiles

After this the replication worked!

Cheers, Chris

Recently I got an error while installing a second node in a SQL 2005 Cluster.

I installed from the customers’ installation eOpen ressources (with two CDs) and everything looked O.K.
While the installer tried to cleanup installation an misleading error occured.

“Can’t access cluster ressource”

I searched in many newsgroups, forums etc. but none of the answers matches my problem.
I asked my colleague Stefan L. and he remembered he had a similar problem.

The setup can’t handle the two Folders (CD1 and CD2) so you manually have to copy the files from CD1 into the CD2 folder. It’s important to do this in this direction because CD2 setup.exe would launch only the client setup.



Recently I had a problem while migrating a customers’  Exchange 2003 to MSX2010. The mailbox migration went well, and so we deleted all mailstorage groups on the Exchange 2003 Backend server.

After this we started to move the public folders on a Exchange 2003 Frontend server and triggered the “Move-All-Repicas” script on the Exchange 2010, too.

Nothing happened – no messages in the event log. After several attempts the customer tested to move the public folders on the original BE server and immediately appeared the error: “Error c1050000 MSexchangeIS – Profile is not configured”. (Thank you, Joerg;-))

After brief research, it turned out that this error occurs if on the public folders’ source server no mailbox storage group is configured.

After re-create a storage group and and information store mailbox replication worked as expected.



Yesterday I got a problem while migrating a fileserver cluster from Windows 2003 to Windows 2008 R2.

We wanted to migrate a big fileserver cluster with several volumes by mirroring the SAN LUNs, break the mirrors and mount them to the new Windows 2008 R2 fileserver.

After mounting the partitions to the new cluster we set up a new virtual fileserver and created some shares. With one partition/share we run in the following error:

The shared ressource is not available.

After some investigation we figured out that the SYSTEM group doesn’t had permissions on the partition at root level so the cluster service running with local system account can’t initialize the share.

After adding SYSTEM at root level with full access sharing of this partition was possible:



Here’s the PowerShell command to remove the last arbitration mailbox to prepare uninstall of Exchange 2010.

Get-Mailbox -Arbitration | Remove-Mailbox -RemoveLastArbitrationMailboxAllowed



Randy just released the Outlook Calendar Checking Tool, for short CalCheck.

It’s a very useful tool to solve those tricky calendar problems an Exchange admin is often confronted with.
My special thanks to Kottee, who informed me about the release.

CalCheck – The Outlook Calendar Checking Tool



Yesterday I ran into a problem which was often discussed before by my colleagues and me.

I wanted to prepare the AD schema update before installing Exchange 2010. The “setup /pad” and “setup /ps” commands ran without any errors so I started to install Exchange 2010 (SP2).

The Installation itself ran without any errors, too. After rebooting the freshly installed Exchange 2010 server I wanted to opend the EMC and the EMS – and got one of these annoying WinRM management startup failures.

So I did it as recommended by MS and used the articles provided by TechNet and EHLO Team Blog and finally used the Exchange Management Troubleshooter (EMTShooter) without any hint or solution – the EMTShooter only detected an unknown error.

I called my colleague Stephan H.  (A big thank you, Stephan, for the memory of this topic) and he put me on the right track. A virus scanner was installed and activated on the schema master. Several times he had this issue: The schema update seemed to run properly but after installing Exchange 2010 strange errors occured.

The solution was very easy. I deactivated the virus scanner on the schema master and rerun Exchange 2010’s “setup /ps”. After finishing the PrepareSchema I rebooted the Exchange 2010 server and everything worked fine. In this case the AntiVirus software blocked the “evil” remote PowerShell.