EXCHANGE RANGER

Archive for December 2012

"There are no more endpoints available from the endpoint mapper. (Exception from HRESULT: 0x800706D9)".

By Gulab Prasad | Sunday, December 30, 2012 | Exchange 2010 1 Comment

My last article of year 2012.
I was installing exchange server 2010 SP2 and ran into this error/issue. The server is updated with windows update and prerequisite is installed.

While Hub Transport installation was going on, it failed with the below error message.

Hub Transport Role
Failed

Error:
The following error was generated when "$error.Clear();
          if (!(get-service MSExchangeADTopology* | where {$_.name -eq "MSExchangeADTopology"}))
          {
            install-ADTopologyService
          }
        " was run: "There are no more endpoints available from the endpoint mapper. (Exception from HRESULT: 0x800706D9)".

There are no more endpoints available from the endpoint mapper. (Exception from HRESULT: 0x800706D9)
Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.2.247.1&e=ms.exch.err.Ex88D115&l=0&cl=cp

Elapsed Time: 00:00:18

Client Access Role
Cancelled

Finalizing Setup
Cancelled

I checked the windows firewall service and found that it was disabled. Set the service to Automatic and started the service. Started the installation again it completed successfully. As exchange server 2010 is getting installed on Windows Server 2008R2, you make sure that Windows Firewall is not disabled. You should never disable the Windows Firewall on Windows Server 2008R2.

I thought of writing it as my last article of year 2012. I will begin New Year 2013 with Exchange Server 2013 and Unified Communication technologies and try to write as many as helpful, knowledgeable articles I can.

Happy and Prosperous New Year To All of You.

Cheers,

Error: An error occurred while trying to validate the specified database copy for possible activation. Error: Database copy 'DB01' has been blocked from activation on server 'SERVER.DOMAIN.com' by an administrative action.

By Gulab Prasad | Sunday, December 23, 2012 | Exchange 2010 2 Comments

I came across with this "weird" issue while upgrading DAG from exchange server 2010 SP1 to SP2. The environment had Windows NLB with 2 servers.
Here is how DAG looks like...

As per the procedure, I upgraded the Network Load Balancer first and then Mailbox Servers. Network Load Balancer upgrade went fine without any issues. Installed Update RollUp 4 as well after upgrading it to SP2. Started upgrading Member server of DAG, you can refer to this Tech Net article to upgrade DAG member servers.

Both the member server MBX02 and MCSHT got upgraded as expected, while upgrading the MBX01 it failed on stopping Microsoft Exchange RPC Client Access Service twice.
Restarted the server and upgrade completed successfully. Installed Update Rollup 4 as well on all the servers. After upgrade now it's time to move the everything back as it was before upgrade. So ran the below command:
Move-ActiveMailboxDatabase "DB01" -ActivateOnServer MBX01 and it failed with below error.

Checked the status of the server by running the command:
Get-MailboxServer MBX01 | fl Name,DatabaseCopyAutoActivationPolicy and it says Unrestricted, hence it's not blocked. Ran the command again and it failed with the same error message. Tried from GUI and as expected, it had to failed.
Friend of mine with whom I was working with, suggested that we should try to Suspend the copy of database residing on MBX01 and resume the DatabaseCopy than try to move.