Exchange backup failed and getting IDs 2112 and 2024 in Application Log.

When started the backup job, I got failure report only on one database however the other databases backup was successful. The error as the following

V-79-57344-65233 – Snapshot Technology: Initialization failure on: “\\DAG.XYZ.com\Microsoft Information Store\Tier1-DB1”. Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS).

Snapshot technology error (0xE000FED1): A failure occurred querying the Writer status.

Check the Windows Event Viewer for details.

Writer Name: Exchange Server, Writer ID: {76FE1AC4-15F7-4BCD-987E-8E1ACB462FB7}, Last error: The VSS Writer failed, but the operation can be retried (0x800423f3), State: Stable (1).

The only changes happened on this database was enabling circular logging and then disabling it again. For more troubleshooting I Run the command VSSADMIN LIST WRITERS on the passive node where I am running the backup job and I got the following writer error

Retryable error is the reason the backup job did not completed successfully. But still why???

My assumption that after disabling the circular logging still the passive node feels that circular logging is still disabled (considering that I am running backup on the passive node).

The solution for that is only restarting Microsoft Exchange Replication Service on the passive node and then run VSSADMIN LIST WRITERS and the status was stable now.

Ref: http://blogs.technet.com/b/timmcmic/archive/2012/03/11/exchange-and-vss-my-exchange-writer-is-in-a-failed-retryable-state.aspx

Hope this post saved some time to some administrators troubleshooting this error.

Regards,

Haytham

An Active Manager operation failed with a transient error. Please retry the operation. Error: The fully qualified domain name for node ‘DAG 1’ could not be found

I got this error while adding a member to my newly created DAG, the Windows was 2012 and Exchange is 2013. it was some how strange because with Exchange 2010 I did not face such error before. after searching I found that I need to manually add the first member of the DAG the full control allow permission on the DAG1 object in Active Directory. then I have to disable the object. when adding the new DAG member the DAG object will be enabled by itself again.

note that you do not have to repeat the same steps while adding addition DAG members

Ref: http://blogs.technet.com/b/justin_gao/archive/2012/12/30/you-need-to-know-pre-stage-cluster-name-object-when-your-create-exchange-server-2013-dag.aspx 

Regards,

Haytham

Corrupted installation of Exchange 2007 Service Pack happen and services could not be started

I was upgrading my Exchange 2007 SP2 to SP3, I have high available and site resilience server soles. My main issue occurred on Exchange Mailbox at DR site that is standby server (Standby Continuous Replication applied). The installation went fine and exchange setup log file did not report errors, however all exchange services was stopped and could not be successfully started. I have checked msi log file and it seems that many files of exchange are missed for example MSExchangeADTopolgyService.exe. I got the path from the service properties as snapshot below and I found that the file is missed, majority of other services were missing too.

My main concern is that I have 2 TB of exchange database that will need to be replicated from scratch again if I lost this server for ever. Thanks god the problem was limited to Mailbox at DR site only.

After searching I found that the solution is just re-install Exchange Service Pack (you need to remove rollup in case you installed it after SP installation).

The problem was resolved by run Setup again from the command line in the installation mode and installs the same roles that we were previously installing. The command used is Setup.com /m:install /r:mb

References:  http://support.microsoft.com/kb/947281

Regards,

Haytham

Exchange Services are in starting mode and could not be successfully started due to error ID 2080

It was a rear situation, some Exchange services could not be started on the majority of Exchange Servers. After initial investigation it was definitely that it is related to connectivity with domain Controllers. But how? I can successfully ping DCs, Ran dcdiag test against the DC. Found the dcdiag report looked good. But in the application Log I found error ID 2080 was repeated with description: Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=6660). Exchange Active Directory Provider has discovered the following servers with the following characteristics:

(Server name | Roles | Enabled | Reachability | Synchronized | GC capable | PDC | SACL right | Critical Data | Netlogon | OS Version)

Also IDs: 2114 and 2501 were logged many times

After more investigation and check Default Domain Controllers Security Policy Found “Exchange Servers” was not listed in “Manage auditing and security log” right

I added the “Exchange Servers” group to “Manage auditing and security log” right

And restarting Exchange Servers and everything went right

If you are looking for more details check this link http://blogs.technet.com/b/richardroddy/archive/2010/06/16/msexchange-adaccess-dsaccess-errors-and-the-manage-auditing-and-security-right.aspx

Regards,

Haytham

Hyper-V Replica Broker role could not be brought online and give error ID: 1069

Hyper-V Replica Broker could not be brought online and give error ID: 1069

However my Hyper-V cluster was fine and working without issues, I got this error when creating Hyper-V replica Broker role.

After investigating I found that virtual cluster computer object does not have required permissions on the Active Directory OU that contains Hyper-V cluster servers. I gave the cluster computer object full control on the OU and then successfully bring the resource online.

If you want to be more accurate you can give the cluster computer object “create computer object permission instead of full control”

Regards,

Haytham

Cluster Name failed registration of one or more associated DNS name(s) for the following reason

Sometimes people got confused while creating a cluster in Windows Server. They think they have to create a static record in DNS as they are doing in WNLB. The right thing is you do not have to create the record because it will be created automatically on condition that you have enabled dynamic update on DNS zone.

If you created the record manually you might get error 1196 that “Cluster network name resource ‘Cluster Name’ failed registration of one or more associated DNS name(s) for the following reason:

DNS operation refused.

 

 

Ensure that the network adapters associated with dependent IP address resources are configured with at least one accessible DNS server”

Any way you can solve this issue be deleting the record and it shall be created by itself again “try to start the cluster service if the record was not updated automatically”

Or go through the following steps

Go to DNS, find the record ( A & Pointer record) for the cluster name resource.

• Make a right click
• Go to properties
• In the security make sure the “Authenticated users” are included
• Make sure it has “Write: rights and Special permissions
• Click Advance, locate authenticated users, and click edit
• Make sure, Write all properties, Read permissions, All Validated Writes selected
• Click OK three times to exit.

Regards

Haytham

Checking WMI

RPC server is not available, Unable to connect to WMI on remote machine “”, error = 0x800706ba all this error you might have while can not connect to WMI service,

use this tool to check connectivity, in run type wbemtest then enter, you will get the following tool GUI, under name space replace sccmxp with your machine, then add your user name and password. then connect, you should be able to connect to know that WMI is accessible by the network

also below link link is so informative for further testing

http://blogs.technet.com/b/askperf/archive/2007/06/22/basic-wmi-testing.aspxand

below link for FW settings

http://msdn.microsoft.com/en-us/library/aa389286%28VS.85%29.aspx

Regards,

Haytham

Certificate enrollment fails giving (The RPC server is unavailable. 0x800706ba (WIN32: 1722))

I experienced this problem while trying to Autoenroll a certificate from a client. after searching I found that it is because of CA is installed on a Domain controller.

the problem solved by adding “Domain Controllers” security group to “CERTSVC_DCOM_ACCESS” Domain Local Security Group.

for further investigations and other troubleshooting steps review the following links

http://blogs.technet.com/b/instan/archive/2009/12/07/troubleshooting-autoenrollment.aspx

http://social.technet.microsoft.com/Forums/en/windowsserver2008r2general/thread/f3de8600-cf4e-4a39-a42e-7f929e1b8d6d

Regards,

Haytham

Setting a process exclusion in your network

while I was configuring exclusions in Forefront Client security, I was having to actions to do. first was set Files and Folders exclusions and the second is to exclude processes itself. for first action I had no problem however for the second one I found that there is no option in FCS GUI to exclude processes. after search I found to do this task you need to edit the registry or through GPO if you have a good numbers of servers.

As i had only one server I went to change the registry on that server to set exclusions. for the right steps do the following

1. go to the following registry Key HKLM\SOFTWARE\Microsoft\Microsoft Forefront\Client Security\1.0\AM\Exclusions\Processes
2. for each process add new DWORD entry with the complete listing name of the process (e.g. “C:\WINDOWS\system32\Process_Name.exe“) one puts on.

Note that you need to replace process_Name.exe or the entire path according to the process you want to exclude.

references: http://blogs.technet.com/b/clientsecurity/archive/2010/03/12/setting-a-process-exclusion-in-your-network.aspx

Best Regards,

Haytham

Setup TMG Failed while registering performance monitors

My installation to TMG failed for not able to register performance monitor. after investigation the problem I believed that the corruption of the performance was due to a group policy applied to the machine and mostly it was due to FCS policy.

to solve this issue you need to manually rebuild Performance Counter Library values. if you want to rebuild all Performance counters including extensible and third-party counters in Windows Server 2003, type the following commands at a command prompt. Press ENTER after each command.

cd\windows\system32

lodctr /R

however you can go step by step through the following link

http://support.microsoft.com/kb/300956

Regards,

Haytham