Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3600
  • Last Modified:

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

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
caronimsguy
Asked:
caronimsguy
  • 4
1 Solution
 
Glen KnightCommented:
Sounds like possibly a space in an alias for a user? Be worth checking.
0
 
caronimsguyAuthor Commented:
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
 
caronimsguyAuthor Commented:
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
 
caronimsguyAuthor Commented:
Accepted
0
 
caronimsguyAuthor Commented:
Resolved the problem via support call to Microsoft.
0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now