sXmont1j6
asked on
Exchange 2010 Setup Failed...
I have no idea why the mailbox rule failed on my new Exchange 2010 setup on a 2008 Server.. Someone please help me with this.
Mailbox Role
Failed
Error:
The following error was generated when "$error.Clear();
if ($RoleIsDatacenter -ne $true)
{
if (test-ExchangeServersWrite Access -DomainController $RoleDomainController -ErrorAction SilentlyContinue)
{
# upgrade the discovery mailboxes to R5 version, this will fix the RecipientDisplayType property of the discovery mailbox which was wrong in R4.
get-mailbox -RecipientTypeDetails DiscoveryMailbox -DomainController $RoleDomainController | where {$_.IsValid -eq $false} | set-mailbox -DomainController $RoleDomainController
$name = [Microsoft.Exchange.Manage ment.Recip ientTasks. EnableMail box]::Disc overyMailb oxUniqueNa me;
$dispname = [Microsoft.Exchange.Manage ment.Recip ientTasks. EnableMail box]::Disc overyMailb oxDisplayN ame;
$mbxs = @( get-mailbox -Filter {name -eq $name} -IgnoreDefaultScope -resultSize 1 );
if ( $mbxs.length -eq 0)
{
$dbs = @(get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
if($dbs.Length -ne 0)
{
$mbxUser = @(get-user -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
if ($mbxUser.Length -ne 0)
{
enable-mailbox -Discovery -identity $mbxUser[0] -DisplayName $dispname -database $dbs[0].Identity;
}
}
}
}
else
{
write-exchangesetuplog -info "Skipping creating Discovery Search Mailbox because of insufficient permission."
}
}
" was run: "Database is mandatory on UserMailbox. Property Name: Database".
Database is mandatory on UserMailbox. Property Name: Database
Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.1.218.11&e=ms.exch.err.Ex88D115&l=0&cl=cp
Error:
The following error was generated when "$error.Clear();
if ($RoleIsDatacenter -ne $true)
{
if (test-ExchangeServersWrite Access -DomainController $RoleDomainController -ErrorAction SilentlyContinue)
{
# upgrade the discovery mailboxes to R5 version, this will fix the RecipientDisplayType property of the discovery mailbox which was wrong in R4.
get-mailbox -RecipientTypeDetails DiscoveryMailbox -DomainController $RoleDomainController | where {$_.IsValid -eq $false} | set-mailbox -DomainController $RoleDomainController
$name = [Microsoft.Exchange.Manage ment.Recip ientTasks. EnableMail box]::Disc overyMailb oxUniqueNa me;
$dispname = [Microsoft.Exchange.Manage ment.Recip ientTasks. EnableMail box]::Disc overyMailb oxDisplayN ame;
$mbxs = @( get-mailbox -Filter {name -eq $name} -IgnoreDefaultScope -resultSize 1 );
if ( $mbxs.length -eq 0)
{
$dbs = @(get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
if($dbs.Length -ne 0)
{
$mbxUser = @(get-user -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
if ($mbxUser.Length -ne 0)
{
enable-mailbox -Discovery -identity $mbxUser[0] -DisplayName $dispname -database $dbs[0].Identity;
}
}
}
}
else
{
write-exchangesetuplog -info "Skipping creating Discovery Search Mailbox because of insufficient permission."
}
}
" was run: "Database is mandatory on UserMailbox. Property Name: Database".
Database is mandatory on UserMailbox. Property Name: Database
Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.1.218.11&e=ms.exch.err.Ex88D115&l=0&cl=cp
Elapsed Time: 00:02:06
Mailbox Role
Failed
Error:
The following error was generated when "$error.Clear();
if ($RoleIsDatacenter -ne $true)
{
if (test-ExchangeServersWrite
{
# upgrade the discovery mailboxes to R5 version, this will fix the RecipientDisplayType property of the discovery mailbox which was wrong in R4.
get-mailbox -RecipientTypeDetails DiscoveryMailbox -DomainController $RoleDomainController | where {$_.IsValid -eq $false} | set-mailbox -DomainController $RoleDomainController
$name = [Microsoft.Exchange.Manage
$dispname = [Microsoft.Exchange.Manage
$mbxs = @( get-mailbox -Filter {name -eq $name} -IgnoreDefaultScope -resultSize 1 );
if ( $mbxs.length -eq 0)
{
$dbs = @(get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
if($dbs.Length -ne 0)
{
$mbxUser = @(get-user -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
if ($mbxUser.Length -ne 0)
{
enable-mailbox -Discovery -identity $mbxUser[0] -DisplayName $dispname -database $dbs[0].Identity;
}
}
}
}
else
{
write-exchangesetuplog -info "Skipping creating Discovery Search Mailbox because of insufficient permission."
}
}
" was run: "Database is mandatory on UserMailbox. Property Name: Database".
Database is mandatory on UserMailbox. Property Name: Database
Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.1.218.11&e=ms.exch.err.Ex88D115&l=0&cl=cp
Error:
The following error was generated when "$error.Clear();
if ($RoleIsDatacenter -ne $true)
{
if (test-ExchangeServersWrite
{
# upgrade the discovery mailboxes to R5 version, this will fix the RecipientDisplayType property of the discovery mailbox which was wrong in R4.
get-mailbox -RecipientTypeDetails DiscoveryMailbox -DomainController $RoleDomainController | where {$_.IsValid -eq $false} | set-mailbox -DomainController $RoleDomainController
$name = [Microsoft.Exchange.Manage
$dispname = [Microsoft.Exchange.Manage
$mbxs = @( get-mailbox -Filter {name -eq $name} -IgnoreDefaultScope -resultSize 1 );
if ( $mbxs.length -eq 0)
{
$dbs = @(get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
if($dbs.Length -ne 0)
{
$mbxUser = @(get-user -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
if ($mbxUser.Length -ne 0)
{
enable-mailbox -Discovery -identity $mbxUser[0] -DisplayName $dispname -database $dbs[0].Identity;
}
}
}
}
else
{
write-exchangesetuplog -info "Skipping creating Discovery Search Mailbox because of insufficient permission."
}
}
" was run: "Database is mandatory on UserMailbox. Property Name: Database".
Database is mandatory on UserMailbox. Property Name: Database
Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.1.218.11&e=ms.exch.err.Ex88D115&l=0&cl=cp
Elapsed Time: 00:02:06
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Closing ticket.
Looks to me like it is a permission issue based on the out-put above. Make sure that you have Exchange Organizational Permissions and try again.
Will.