Posts Tagged ‘server’

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

Hey Folks,
here is an example to easy set ACLs on a Windows fileserver by importing path an permissions from a CSV file:

$Permissions = Import-Csv e:\permissions.csv -delimiter '|'
ForEach ($line in $Permissions)
 $acl = Get-Acl $line.Path
 $acl.SetAccessRuleProtection($True, $False)
 $rule = New-Object System.Security.AccessControl.
FileSystemAccessRule($line.Group,"Modify","ContainerInherit, ObjectInherit",
 "None", "Allow")
# The above line can be edited like the reference at the end.
 Set-Acl $line.Path $acl

The CSV has to look like this:


Reference Table:

Subfolders and Files only InheritanceFlags.ContainerInherit, InheritanceFlags.ObjectInherit, PropagationFlags.InheritOnly
This Folder, Subfolders and Files    InheritanceFlags.ContainerInherit, InheritanceFlags.ObjectInherit, PropagationFlags.None
This Folder, Subfolders and Files InheritanceFlags.ContainerInherit, InheritanceFlags.ObjectInherit, PropagationFlags.NoPropagateInherit
This folder and subfolders InheritanceFlags.ContainerInherit, PropagationFlags.None
Subfolders only InheritanceFlags.ContainerInherit, PropagationFlags.InheritOnly
This folder and files InheritanceFlags.ObjectInherit, PropagationFlags.None
This folder and files InheritanceFlags.ObjectInherit, PropagationFlags.NoPropagateInherit


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.



Hi folks,

I wrote less in the past month because I focused on work and Microsoft certification.The certification path was very straight – upgrading skills from MCITP to MCAS Server 2012 followed by the two Server Infrastructure exams 70-413 and 70-414.


In the next monts I’ll go forward to MCSE Messaging and Communications with Exchange 2013 and Lync 2013 and I’ll keep blogging about infrastructure and messaging topics.

Next week I’ll post some experiences I made with my new Nokia Lumia 920 with Windows Phone 8.



The Exchange Team is pleased to announce that in the first half of calendar year 2013 we will be releasing Exchange Server 2010 Service Pack 3 (SP3) to our customers. With SP3, the following new features and capabilities will be included:

Coexistence with Exchange 2013: Customers that want to introduce Exchange Server 2013 into their existing Exchange 2010 infrastructure will need the coexistence changes shipping in SP3.

Support for Windows Server 2012: With Service Pack 3, you will have the ability to install and deploy Exchange Server 2010 on machines running Windows Server 2012.

Customer Requested Fixes: All fixes contained within update rollups released prior to Service Pack 3 will also be contained within SP3. Details of our regular Exchange 2010 release rhythm can be found in Exchange 2010 Servicing.

In order to support these newly added features, there will be a requirement for customers to update their Active Directory schema. We are communicating the required changes ahead of the release date in order to assist our customers with planning their upgrade path ahead of time.

We hope these announcements come as welcome news to you. It is our custom to provide ongoing improvements to features, functionality and security of Exchange Server, based largely on customer feedback, and to provide continual innovation on an already great messaging product. We look forward to receiving your comments and announcing more detailed information as we continue to develop the features that will be included in SP3.

Kevin Allison
General Manager
Exchange Customer Experience

(Source:  EHLO Blog)

Today I got faced with a problem concerning a Windows Printserver. After a new printer was installed, the spooler services crashed again and again and generating registry events with ID 4097 and the source HpTcpMon (hptcpmon.dll).

After looking for changes made by the new printer, i figured out, that a new local port (HpTcpMon) was installed. To resolve this issue, I deleted the value in the registry.
1.Start Registry Editor

2. Locate  following key in the registry:

3. Check the following registry key for third-party port monitors, and remove the monitor mentioned in the event ID.

The Windows default port monitors should not be deleted. The default ports are:

AppleTalk Printing Devices (if services for Macintosh is installed)
BJ Language Monitor
Local Port
PJL Language Monitor
Standard TCP/IP Port
USB Monitor
Windows NT Fax Monitor

5. Expand Computer Management, expand Services and Applications, and then click services.

6. Right-Click Print Spooler, and then click Restart.