Fix: Exchange Server 2010 SP update errors

 

Are you trying to install Microsoft Exchange 2010 SP 2 (or 1) or any Roll up dates and getting the below error messages ?

This post has 3 different error fix which stop my installation, if you lucky enough to not have one of them , just skip that section, and move to the section of the post which is related  to you

1) Admin Tools Role is not current / Mailbox , Client Access , Hub Transport Role is not current error

2) Mailbox Role Failed, error indicates “Public Folder Database” Cannot bind argument to parameter 'Identity' because it is null. Even though Admin Tools issues has been fixed!

3) beremote has open files error

 

imageimage

This server role can’t be installed because the following roles aren’t current: MailboxRole , or

This server role can’t be installed because the following roles aren’t current: ClientAccessRole , or

This server role can’t be installed because the following roles aren’t current: HubTransportRole, or

This server role can’t be installed because the following roles aren’t current: Admin Tools R

 

Does your installation stop with this errors and “click here for help” is not giving you a specific answer ?

Here is the steps on how I did fix the issue.

 

Admin Tools Role is not current:

To fix this error you have to open the registry in your Exchange Server and check the “ConfiguredVersion” and “UnpackedVersion” keys , they should be all same

For Microsoft Exchange Server SP1: 14.1.218.15

For Microsoft Exchange Server SP2: 14.2.247.5

STEPS to fix this issue

1) Open Exchange Management Shell , enter the below cmd to check and verify the Admin Tools version

   Get-ExchangeServer | FL

SNAGHTMLc823746

 

Write the Admin Display Version [This screenshot has the “correct” settings ]

AdminDisplayVersion: Version 14.2 (Build 247.5)

2) Open the registry editor, navigate to :

  HKLM\SOFTWARE\Microsoft\ExchangeServer\v14\ 

and compare the registry entries for the below keys: and make sure they are same ,

image

HKLM\SOFTWARE\Microsoft\ExchangeServer\v14\MailboxRole

HKLM\SOFTWARE\Microsoft\ExchangeServer\v14\ClientAccessRole

HKLM\SOFTWARE\Microsoft\ExchangeServer\v14\HubTransportRole

They have to be all same, if not modify the keys based on your Service Pack .

In my case the values where : 14.1.218.15 for ConfiguredVersion in the MailboxRole,ClientAccessRole & HubTransportRole. I did modify them to be same as in the above screenshot 14.2.247.5 which fixed the

3) Delete the “action” and “watermark keys” from the registry.

4) Reboot your Server , restart the Service Pack installation process.

Good luck

 

Mailbox Role Failed, error indicates PublicFolderDatabase Cannot bind argument to parameter 'Identity' because it is null.

 

You did fix the Admin Tools issue, rebooted your server, restarted your Service Pack installation process, and let me  guess , you still cannot see the “installation completed successfully” message, instead:

 

Mailbox Role
Failed

Error:
The following error was generated when "$error.Clear();
if ($RoleCreatePublicFolderDatabase)
{
$publicDB = get-PublicFolderDatabase -Server:$RoleFqdnOrName -ErrorAction SilentlyContinue;
$DB = get-MailboxDatabase -Server:$RoleFqdnOrName -ErrorAction SilentlyContinue;
if ($publicDB -and $DB)
{
set-mailboxdatabase `
-Identity:$DB.Identity `
-publicFolderDatabase:$publicDB.Identity `
-DomainController $RoleDomainController
}
}
" was run: "Cannot bind argument to parameter 'Identity' because it is null.".

Cannot bind argument to parameter 'Identity' because it is null.
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:16:44

 

If you really don’t have any public folder, Don’t worry, I have a solution for you Smile If you do have a public folder database then make sure to take a backup , before you do the steps.

1)  Open the registry editor, navigate to :

HKLM\SOFTWARE\Microsoft\ExchangeServer\v14\MailboxRole

2)  Delete the Watermark key

3) Check the UnpackedVersion Data value and make sure its same with the AdminTool Value

SNAGHTMLca97ea3


4) As you may have noticed , I am missing the ConfiguredVersion key, go ahead and create the key, and make sure to add the data as:

image

 

ConfiguredVersion should have Data value as:  14.2.247.5

5) Reboot the Server

6) Restart the Service Pack Installation

Good luck

 

beremote() Error Fix Steps

Error: Setup cannot continue with the upgrade because the “beremote()” process has open files

image

 

This error will happen if you have a third party backup software installed in your Exchange Server environment. In my case I had Symantec Backup Exec 2012 installed, so the solution was , the stop the Backup Exec services via services.msc

image

image

 

I hope you will see the below screenshot when you done Smile

image

Good luck

Erdal

Comments (8) -

Thadeus
Thadeus
9/14/2012 12:00:33 AM #

Thank you for figure this out, & sharing it with us  I tried this and it worked like a charm.  Thanks a million.

Jim Robert
Jim Robert
1/19/2013 9:06:07 AM #

Useful post to fix the Exchange server. Here are few more methods:

1) Restore database from the most recent backup.
2) Run eseutil.exe tools if you don't have the backup.

3)If above solution does not work, try a third party tool like this: http://www.serversdatarecovery.com/exchange.html

Thanks
Jim

Don McEachern
Don McEachern
1/25/2013 8:39:31 AM #

First off - Thank you VRY much (Mailbox role error), so anyone else out there knows, I also deleted the action string, and I think you meant create the string value "ConfiguredVersion"
with the value of 14.2.247.5
Once those two strings (action and watermark) were deleted and I created the new string value - ConfiguredVersion it, rebooted and started the service pack again - bingo!
Thanks for the post.

Kimmo J
Kimmo J
2/16/2013 8:32:01 PM #

Thanks for this post. Saved my butt when my SP install bounced off these errors.

Jon Maxim
Jon Maxim
2/22/2013 3:43:21 PM #

You may go to programming way of repairing. It's recover .edb files crashed by malwares, system errors, hard drive failures and etc. Next tool must be useful exchange database fix it provides restoring contacts, messages, calendars, tasks and other items of .edb file. Tool repairs databases from MS Exchange Server 2000 up to 2013.

www.recoverfilesdata.com/...edb-pst-converter.html

Andrew Smith
Andrew Smith
3/12/2013 6:39:59 PM #

If you have any type of doubt about mailbox error fixing and interested to apply third party solution then you can Try SysTools Exchange Recovery. More:http://edb-file-repair.devhub.com/

Jassi
Jassi
4/13/2013 4:57:17 PM #

Thanks

Jose Ortega
Jose Ortega
4/21/2013 8:22:18 PM #

Excelent!, It works for me while updating to exchange server 2010 SP3. Thanks!

Add comment

  Country flag

biuquote
  • Comment
  • Preview
Loading