Solved

Exchange 2010 SP1 update fails (Cannot bind argument to parameter 'Identity' because it is null.)

Posted on 2011-02-25
5
3,153 Views
Last Modified: 2012-05-11
When I attempted to upgrade my Exchange 2010 box to SP1, the Mailbox role fails to install. I am using an administrator account with all relevent permissions and groups.  I've tried the procedure to remove white space from my public folder names but this did not help.   The error message is below.  Any help would be appreciated.

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.

0
Comment
Question by:caronimsguy
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
5 Comments
 
LVL 74

Expert Comment

by:Glen Knight
ID: 34981083
Sounds like possibly a space in an alias for a user? Be worth checking.
0
 

Author Comment

by:caronimsguy
ID: 34982438
Thanks dematzer for your comment.

I checked but I didn't find any spaces in any user alias.  I did find one user that had a corrupt
mailbox.  I fixed the mailbox but the problem still exists.
0
 

Accepted Solution

by:
caronimsguy earned 0 total points
ID: 35021935
After 7 hrs. on the phone with Microsoft this case has been resolved.

The error message actually points in the wrong direction.  The problem is not with the Public Folders, mailboxes or user alias.  The issue is a missing registry key.  Please note editing the registry incorrectly can get you into trouble.  Proceed at your own risk.  In my case the following Registry value was missing

Under the key HKLM\Software\Microsoft\ExchangeServer\v14\MailboxRole, the REG_SZ  value ConfiguredVersion should be set to the current version of Exchange, in my case 14.0.639.21
0
 

Author Comment

by:caronimsguy
ID: 35021979
Accepted
0
 

Author Closing Comment

by:caronimsguy
ID: 35067690
Resolved the problem via support call to Microsoft.
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
exchange 2007, exchange 2013, active sync 3 35
Exchange Cross-Forest Migation 6 32
Exchange OWA website Redirection 7 46
Restrict Mailbox size in Exchange 2 25
How to resolve IMCEAEX NDRs in Exchange or Exchange Online related to invalid X500 addresses.
In-place Upgrading Dirsync to Azure AD Connect
how to add IIS SMTP to handle application/Scanner relays into office 365.
This video discusses moving either the default database or any database to a new volume.

733 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question