Mailbox database recovery to alternate location

Hi, i'm trying to write a script to automatically restore an exchange mailbox database to an alternate location
I am using
$pg = get-protectiongroup -dpmservername servername
$ds = get-datasource -protectiongroup $pg[2]; // 2's the index of the exchange protection group
$rp = get-recoverypoint -datasource $ds[2]; // 2's the index of the mailbox database
$gr = get-recoverableitem -recoverableitem $rp[rp.Length-2] -BrowseType child; // get second-last recovery point
$rop = New-RecoveryOption -targetserver lead.miningis.local -recoverylocation copytofolder -FileSystem -alternatelocation "C:\Ex2" -recoverytype restore -OverwriteType Overwrite
recover-recoverableitem -recoverableitem $gr -recoveryoption $rop
This results in powershell crashing.
Event Data:
1093201316
5
PowerShell
None
0
powershell.exe
6.0.6002.18111
System.NullReferenceException
System.Reflection.TargetInvocation
unknown
System.RuntimeMethodHandle._InvokeMethodFast
unknown
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Rport07d40efb
Seems like a value was null. What am I doing wrong?
Thanks

I seem to also encounter this issue. Basically I am trying to do the same thing, automate a restore of a mailbox database to an offsite storage location for DR purposes. Seems to fail with the null error too. The only difference is I am using DPM 2012 R2
with Exchange 2013.
Here is my script:
$pg = Get-ProtectionGroup -DPMServerName "blah"
$ds = Get-Datasource $pg[3]
$rp = Get-RecoveryPoint -DataSource $ds[1]
$gr = Get-RecoverableItem -RecoverableItem $rp[-1] -BrowseType child
$rop = New-RecoveryOption -TargetServer "server name here" -TargetLocation "c:\Restorations" -RecoveryLocation CopyToFolder -Exchange -ExchangeOperationType NoOperation -RecoveryType Restore
Recover-RecoverableItem -RecoverableItem $gr -RecoveryOption $rop
Any help would be greatly appreciated!
Thanks

Similar Messages

  • Best practice for default location of mailbox database(s) / logs

    Hello,
    I don't recall seeing any options during the Exchange 2013 install, to specify an alternate location for either the mailbox database or log files. I've reviewed the commands for moving the mailbox databases, but before reviewing the options for setting a
    location for the log files, I thought it best to see whether it's still advised to separate log/mailbox databases away from the OS, with our Exchange server being a virtualised instance?
    Also, I'm assuming that Exchange still requires the usual backup of transaction logs, for them to be cleared?
    Many thanks.

    Hi JH,
    here is a link to storage options and requirements for the Mailbox server :
    http://technet.microsoft.com/en-us/library/ee832792(v=exchg.150).aspx
    By default when installing New Exchange server With mailbox role,it will create default database and log path.
    Recomended is to have Database and Log files on seperate disks.You will have to attache those disk first,then you can create New database using ECP.
    Please look at my Gallery With full guide on how to setup New Exchange server.
    http://gallery.technet.microsoft.com/Install-Exchange-server-b5cce9e4
    Also for future use you might need to clean up log files to free up Space on Your Exchange server:
    http://gallery.technet.microsoft.com/Task-Scheduler-to-cleanup-25047622
    Hope this helps
    Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Off2work

  • Get folders in a mailbox in recovery database

    Hi,
    I want to get a list of folders in a mailbox in the recovery database without restoring the mailbox.
    How can I achieve that?
    Thanks,
    Gagan
    Gagan

    Old thread, but relevant to what I need to do right now.
    FYI, Get-MailboxFolderStatistics does not have a
    -database parameter in Exchange 2010 or 2013. 
    Get-Mailbox -database returns no results from a recovery database.
    I'm still working on trying to figure this out, but I'm thinking it may not be possible.

  • Litigation Hold, Single Item Recovery, & Mailbox Database Deleted Items Retention

    Hello
    I'm looking for a simple explanation of how the three features mentioned in the subject line interact and affect one another.
    Specifically, I'm after the answer to the following question:
    If a users mailbox has litigation hold enabled, and the mailbox database it lives on has a deleted items retention value of 365 days, does that users "Recoverable Items" get deleted after 365 days, or does litigation hold, as I supspect bypass the retention
    value?
    If Single Item Recovery is enabled for said user as well, and added to the scenario above - how does this affect the retention of the deleted items?
    I cannot find a definitive article that describes mailbox database deleted items retention, litigation hold and single item recovery and their behaviours when used together.
    Regards
    Matt
    Matt

    Hello again,
    Just wanted to open this thread up again, and gain some further clarification, specifically on the behaviour of items in "Recoverable Items\ Deletions" folder.
    In the following scenario how will items be processed:
    -SingleItemRecoveryEnabled -True
    -LitigationHoldEnabled - True
    -UseDatabaseRetentionDefaults -True
    -Items in the Deletions folder have passed the retention value date as specified on the database.
    Given the parameters above, when the I run the Managed Folder Assistant against a mailbox, I'm expecting to see the items in the Deletions folder move, and be placed in Purges folder.
    This is not happening however, items are only removed from the Deletions folder when LitigationHold is disabled. Then, items bypass the Purges folder altogether and are removed from the mailbox/database altogether.
    I referred to the article below for clarification:
    http://blogs.technet.com/b/exchange/archive/2009/09/25/3408389.aspx#_Short-Term_Preservation_of
    "...the message was not purged from the mailbox store. Instead the message was moved from the Recoverable
    Items\Deletions folder to the Recoverable Items\Purges folder. All store hard-deleted items end up in this folder when single item recovery is enabled. The Recoverable Items\Purges folder is not visible to the end user, meaning that they do not see data retained
    in this folder in the Recover Deleted Items tool.
    When the message deletion timestamp has exceeded the deleted item retention window, Records Management will purge the item."
    Can anyone assist in explaining the behaviour I'm observing?
    I'm in a transition period where by our organisation has been journalling all
    email to an Online service since 2008 and this service will continue to be used solely as our archiving and compliance mechanism.
    Since Exchange 2010 was adopted by the company around 18 months ago, the previous mail administrator had litigation hold enabled on all mailboxes
    from the outset, so I'm in the position now where by I have two retention methods running side by side.
    Long story short, the online archiving will be used moving forward and litigation hold will be disabled within Exchange. 
    What I want to do is transition from long term data
    preservation inside Exchange, to short term preservation - hence the reason for now enabling SIR.
    Currently I have mailboxes with 10's of GB's of mail sat in the "Recoverable Items\Deletions" folder, and very little, if anything in some
    cases, in the respective "Purges" folder.....
    Can anyone advise on a "correct" procedure for making this transition?
    Regards
    Matt
    Matt

  • Migration from Exchange 2007 to 2013 gives error "Failed to communicate with the mailbox database'

    I have been trying to migrate several databases from Exchange 2007 to Exchange 2013. The migration started successfully, and many of the mailboxes moved successfully (about 70). The remaining mailboxes, failed. Looking deeper, we found a few issues; The
    two 2013 Mailbox servers were on different versions. The Server had run out of disk space, and the NIC drivers needed to be updated.
    Now when we try to migrate a mailbox that had failed in the earlier batch, we get the following error:
    Data migrated:                        
    Migration rate:                        
    Error:                        
    MigrationTransientException: Failed to communicate with the mailbox database. --> Failed to communicate with the mailbox database. --> MapiExceptionNetworkError: Unable to make connection to the server. ‎(hr=0x80040115, ec=-2147221227)‎ Diagnostic
    context:    ......    Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 501    Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0    Lid: 11672   dwParam:
    0x0 Msg: EEInfo: NumberOfParameters: 4    Lid: 8856    dwParam: 0x0 Msg: EEInfo: prm[0]: Unicode  string: ncacn_ip_tcp    Lid: 8856    dwParam: 0x0 Msg: EEInfo: prm[1]: Unicode  string: <Server
    FQDN>    Lid: 12952   dwParam: 0x0 Msg: EEInfo: prm[2]: Long val: 3749909585    Lid: 12952   dwParam: 0x0 Msg: EEInfo: prm[3]: Long val: 382312662    Lid: 45169   StoreEc: 0x824        
    Lid: 50544   ClientVersion: 15.0.847.32    Lid: 52080   StoreEc: 0x824         Lid: 44273      Lid: 49064   dwParam: 0x1    Lid: 37288  
    StoreEc: 0x6AB         Lid: 49064   dwParam: 0x2    Lid: 59431   EMSMDB.EcDoConnectEx called [length=203]    Lid: 51239   EMSMDB.EcDoConnectEx exception [rpc_status=0x6D9][latency=0]   
    Lid: 62184      Lid: 16280   dwParam: 0x0 Msg: EEInfo: ComputerName: n/a    Lid: 8600    dwParam: 0x0 Msg: EEInfo: ProcessID: 3460    Lid: 12696   dwParam: 0x0 Msg: EEInfo:
    Generation Time: 0414-04-07T16:32:03.2100000Z    Lid: 10648   dwParam: 0x0 Msg: EEInfo: Generating component: 2    Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: 1753    Lid: 9624   
    dwParam: 0x0 Msg: EEInfo: Detection location: 501    Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0    Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 4    Lid: 8856   
    dwParam: 0x0 Msg: EEInfo: prm[0]: Unicode  string: ncacn_ip_tcp    Lid: 8856    dwParam: 0x0 Msg: EEInfo: prm[1]: Unicode  string: <Server FQDN>    Lid: 12952   dwParam: 0x0 Msg: EEInfo:
    prm[2]: Long val: 2767313664    Lid: 12952   dwParam: 0x0 Msg: EEInfo: prm[3]: Long val: 382312662    Lid: 59505   StoreEc: 0x824         Lid: 50544   ClientVersion:
    15.0.847.32    Lid: 52080   StoreEc: 0x824         Lid: 36081      Lid: 51152      Lid: 52465   StoreEc: 0x80040115   
    Lid: 60065      Lid: 33777   StoreEc: 0x80040115    Lid: 59805      Lid: 52487   StoreEc: 0x80040115    Lid: 19778      Lid: 27970  
    StoreEc: 0x80040115    Lid: 17730      Lid: 25922   StoreEc: 0x80040115
    All of the issues listed above have been corrected, and all of the databases are mounted. Users are able to send and receive mail, but I can not migrate mail using the Migration Batch utility.
    The destination server is a Hyper-V Guest running Server 2012, SP1, and Exchange 2013
    The Source Server is Running Exchange 2007.
    I have tried doing a test move to another destination server that is also Server 2012, and Exchange 2013, and the migration also failed.
    I would appreciate any help you can give me!
    Thanks,
    Jon

    Any update if you have resolved the issue.
    Not similar, but this thread can be helpful while you migrate the mailboxes from exchange 2007 to 2013. Please check :http://social.technet.microsoft.com/Forums/exchange/en-US/721f0ae4-623a-4b02-adaf-f561d86c0426/move-mailboxes-and-public-folders-from-exchange-2007-to-exchange-2013?forum=exchangesvrdeploy&prof=required

  • Restoring deleted emails from a mailbox database edb file.

    hello all.
    i have done some reading up on this subject and also covered it off in my MCSA 70-341 training. ( some time ago)
    i dont deal with the exchange server often and would like to be clear before i delve into the exchange server.
    a user has lost some emails, and they don't appear to be recoverable as there not in the recover deleted items either within outlook.
    i cant find any trace of them on the exchange server.
    sadly (1/2 my fault) the previous exchange admin never had audit logging or single item retention enabled on the mailbox so i am finding it hard to find much in the way of information to point me to the cause of the problem or recover the emails
     its their "sent items" folder and oddly its only the last 2 years worth of sent items that are gone as from 2012 previous are still there
    i do have an up-to-date full database backup that is currently downloading off our backup system.
    i am forgetting the best method to process the recovery, can anyone point me to a guide or give me a few steps on what to do? 
    it is only the emails form the sent items that need to be recovered so i am thinking i need some sort of granular restore method??
    many thanks
    gordon 

    Here you go
    http://exchangeserverpro.com/restore-exchange-server-2013-database-recovery-database/
    http://exchangeserverpro.com/restoring-mailbox-exchange-server-2013-recovery-database/
    Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline Exchange Mailbox and Public Folder EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e. 2003 -->
    2007 --> 2010 --> 2013 with Lucid8's
    DigiScope

  • Microsoft Exchange Mailbox Replication service was unable to process jobs in a mailbox database 1006.

    HI all,
    I ran into a problem with one of the servers in my DAG.  Due to a backup failure, the log partition filled up and the Exchange database went offline on this particular server.  The DAG continued to function on the other server.  So this particular
    DB01 had only some test accounts in it so I removed the database copy.  Unfortunately the removal must not have completed correctly. 
    After recovering the needed space in the partition, I tried to recopy the database and it failed.  So I deleted the entire database from the active server and it successfully removed it from the active server.  Now on both the servers the database
    is not showing, however I'm receiving the error below which indicates to me that the service still thinks the database exists.  I am also getting event 4113 Database redundancy health check failed for the database copy as it shows there is only one copy
    of the database (failed redundancy) but there should be zero copies.
    This database no longer exists in AD as I have verified this with ADSI so it must have something on the exchange server that is still telling the service the database exists. 
    Can you point me to the location to clean this up?
    Log Name:      Application
    Source:        MSExchange Mailbox Replication
    Date:          02/25/2011 2:00:07 PM
    Event ID:      1006
    Task Category: Service
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:      email1.domain.com
    Description:
    The Microsoft Exchange Mailbox Replication service was unable to process jobs in a mailbox database.
    Database: DB01
    Error: MapiExceptionUnknownUser: Unable to open message store. (hr=0x80004005, ec=1003)
    Diagnostic context:
        Lid: 55847   EMSMDBPOOL.EcPoolSessionDoRpc called [length=243]
        Lid: 43559   EMSMDBPOOL.EcPoolSessionDoRpc returned [ec=0x0][length=200][latency=0]
        Lid: 23226   --- ROP Parse Start ---
        Lid: 27962   ROP: ropLogon [254]
        Lid: 17082   ROP Error: 0x3EB    
        Lid: 26937 
        Lid: 21921   StoreEc: 0x3EB    
        Lid: 27962   ROP: ropExtendedError [250]
        Lid: 1494    ---- Remote Context Beg ----
        Lid: 26426   ROP: ropLogon [254]
        Lid: 22086 
        Lid: 27206 
        Lid: 17990 
        Lid: 16966   StoreEc: 0x8004010F
        Lid: 31433   StoreEc: 0x8004010F
        Lid: 8620    StoreEc: 0x3EB    
        Lid: 1750    ---- Remote Context End ----
        Lid: 26849 
        Lid: 21817   ROP Failure: 0x3EB    
        Lid: 26297 
        Lid: 16585   StoreEc: 0x3EB    
        Lid: 32441 
        Lid: 1706    StoreEc: 0x3EB    
        Lid: 24761 
        Lid: 20665   StoreEc: 0x3EB    
        Lid: 25785 
        Lid: 29881   StoreEc: 0x3EB    
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MSExchange Mailbox Replication" />
        <EventID Qualifiers="32772">1006</EventID>
        <Level>3</Level>
        <Task>1</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2011-02-25T22:00:07.000000000Z" />
        <EventRecordID>181576</EventRecordID>
        <Channel>Application</Channel>
        <Computer>email1.domain.com</Computer>
        <Security />
      </System>
      <EventData>
        <Data>DB01</Data>
        <Data>MapiExceptionUnknownUser: Unable to open message store. (hr=0x80004005, ec=1003)
    Diagnostic context:
        Lid: 55847   EMSMDBPOOL.EcPoolSessionDoRpc called [length=243]
        Lid: 43559   EMSMDBPOOL.EcPoolSessionDoRpc returned [ec=0x0][length=200][latency=0]
        Lid: 23226   --- ROP Parse Start ---
        Lid: 27962   ROP: ropLogon [254]
        Lid: 17082   ROP Error: 0x3EB    
        Lid: 26937 
        Lid: 21921   StoreEc: 0x3EB    
        Lid: 27962   ROP: ropExtendedError [250]
        Lid: 1494    ---- Remote Context Beg ----
        Lid: 26426   ROP: ropLogon [254]
        Lid: 22086 
        Lid: 27206 
        Lid: 17990 
        Lid: 16966   StoreEc: 0x8004010F
        Lid: 31433   StoreEc: 0x8004010F
        Lid: 8620    StoreEc: 0x3EB    
        Lid: 1750    ---- Remote Context End ----
        Lid: 26849 
        Lid: 21817   ROP Failure: 0x3EB    
        Lid: 26297 
        Lid: 16585   StoreEc: 0x3EB    
        Lid: 32441 
        Lid: 1706    StoreEc: 0x3EB    
        Lid: 24761 
        Lid: 20665   StoreEc: 0x3EB    
        Lid: 25785 
        Lid: 29881   StoreEc: 0x3EB     </Data>
      </EventData>
    </Event>

    Hi
    This error occurs because the MailboxReplicationService (MRS) currently caches Mailbox Database information past the lifetime of some databases. 
    Restarting the service will clear the cache.
    Maybe it is the simplest way to solve it.
    If it doesn’t work, you can try cmd to check it.
    Get-MailboxDatabase : Can you find the database which you delete?
    Remove-MailboxDatabase -Identity "MyDatabase": You can try to delete database if you can see the database.

  • Powershell command to migrate Exchange 2007 mailbox databases with a legacy name, & import them into a new 2007 instance, with a new name.

    Hi All. I am currently at the later stage of provisioning a new CCR Exchange 2007 migration (to
    virtualise old Exchange 2007 hardware) for 5,000 users & have a quick question.
    I have created around 15 newly named storage groups, & have named 1 new DB per group, with the same name (let's say New-DB-1), residing within them.  The problem I have, is the old legacy DB's have different names (let's say Old-DB-1) & I need
    to import them into the new storage groups, to match the new names. So far I can import/export between old & new OK if both old & new DB names\folders etc. names marry up perfectly, but are unable to if there not the same. Does anyone have any thoughts
    on how best to tackle this, as this is one of the final hurdles stopping the migration? Many Thanks, John 

    Hi All
    Many Thanks for the feedback.
    The terminology 'migrate' was used based around the fact I will be decommissioning the old 2007 physical environment. This is after moving all DB's over to the new newly created Virtual environment that will host all roles.
    The solution I ended up using yesterday, was the following:
    1) Dismounted the relevant named DB (NEWDB) in the new environment.
    2) I then ticked the 'This database can be overwritten by a restore option' box.
    3) Copied over the old named DB (OLDDB) to the same location, & overwrote using the new name (NEWDB).
    4) Re-mounted the (NEWDB).
    5) Ran the following 2 PowerShell commands:
     Get-mailbox –database OLDDB | move-mailbox –targetdatabase NEWDB -configurationonly:$true
     Get-MailboxDatabase NEWDB | ResetSearchIndex.ps1 -force
    6) Checked to make sure the clients were working ok, in the now the new (NEWDB) environment.
    Rich: Many thanks for your PS script, which I will test with future DB moves & provide feedback
    J
    John.

  • Exchange 11g connector : error with 2003 mailbox databases

    Hi,
    I have installed the Exchange 11g connector in a OIM 11g R2 server. I successfully ran the "Exchange User Mailbox Database Group Lookup Reconciliation" job and recon-ed a mailbox for a specific user (Exchange 2010 mailbox) account using the "Exchange Target Resource User Reconciliation".
    But the fun stops there, when I try the execute the "Exchange Target Resource Delete User Reconciliation" job, I get the following error (see #1) in the result. I don't have any new event in the Event viewer. When I check the connector server I see a similar error (see #2). I tried to manually run the powershell command with the connector server user and it works properly (see #3).
    The problem seems to be related the Exchange 2003 mailboxes, since when I try to recon a mailbox for a user with a 2003 mailbox, I get a similar "database not found" error. There again, if I check the same user using the service account, I can get it's mailbox.
    Any idea what might be the problem ? Any more debugging I can try ?
    Thanks
    h4. #1 - In the scheduled task result :
    org.identityconnectors.framework.common.exceptions.ConnectorException: Problem while PowerShell execution Org.IdentityConnectors.Framework.Common.Exceptions.ConnectorException: Couldn't find database "ORME-DE-COUR\Premier groupe de stockage\Banque de boîtes aux lettres (ORME-DE-COUR)". Make sure you have typed it correctly.
    at Org.IdentityConnectors.Exchange.RunSpaceInstance.CheckErrors(IList errors)
    at Org.IdentityConnectors.Exchange.RunSpaceInstance.InvokePipeline(Collection`1 commands)
    at Org.IdentityConnectors.Exchange.RunSpaceInstance.InvokePipeline(Command item)
    at Org.IdentityConnectors.Exchange.Service.Impl.PowerShellExchangeServiceImpl.InvokePipeline(Command cmd)
    h4. #2 - In the connector server log :
    30/05/2013 10:49:36 AM <INFORMATION>: Class-> ExchangeConnector, Method -> CreateFilterTranslator, Message -> Method Entered
    30/05/2013 10:49:36 AM <INFORMATION>: Class-> PowerShellExchangeServiceImpl, Method -> CreateFilterTranslator, Message -> Method Entered
    30/05/2013 10:49:36 AM <INFORMATION>: Class-> ExchangeConnector, Method -> ExecuteQuery, Message -> Method Entered
    30/05/2013 10:49:36 AM <INFORMATION>: Class-> PowerShellExchangeServiceImpl, Method -> ExecuteQuery, Message -> Method Entered
    30/05/2013 10:49:36 AM <INFORMATION>: Class-> ExchangeUtility, Method -> GetCommand, Message -> Method entered
    30/05/2013 10:49:36 AM <INFORMATION>: Class-> ExchangeUtility, Method -> GetCommand, Message -> Returning cmd Get-Mailbox
    30/05/2013 10:49:36 AM <INFORMATION>: Class-> ExchangeUtility, Method -> GetCommand, Message -> Exiting the method
    30/05/2013 10:49:36 AM <INFORMATION>: Class-> PowerShellExchangeServiceImpl, Method -> InvokePipeline, Message -> Method Entered
    30/05/2013 10:49:36 AM <INFORMATION>: Class-> PowerShellExchangeServiceImpl, Method -> InvokePipeline, Message -> PowerShell Command: Get-Mailbox
    30/05/2013 10:49:36 AM <INFORMATION>: Class-> PowerShellExchangeServiceImpl, Method -> InvokePipeline, Message -> Parameter: IgnoreDefaultScope Value:
    30/05/2013 10:49:36 AM <INFORMATION>: Class-> PowerShellExchangeServiceImpl, Method -> InvokePipeline, Message -> Parameter: ReadFromDomainController Value:
    30/05/2013 10:49:36 AM <INFORMATION>: Class-> PowerShellExchangeServiceImpl, Method -> InvokePipeline, Message -> Parameter: ResultSize Value:Unlimited
    ConnectorServer.exe Error: 0 : Org.IdentityConnectors.Framework.Common.Exceptions.ConnectorException: Problem while PowerShell execution Org.IdentityConnectors.Framework.Common.Exceptions.ConnectorException: Couldn't find database "ORME-DE-COUR\Premier groupe de stockage\Banque de boîtes aux lettres (ORME-DE-COUR)". Make sure you have typed it correctly.
    at Org.IdentityConnectors.Exchange.RunSpaceInstance.CheckErrors(IList errors)
    at Org.IdentityConnectors.Exchange.RunSpaceInstance.InvokePipeline(Collection`1 commands)
    at Org.IdentityConnectors.Exchange.RunSpaceInstance.InvokePipeline(Command item)
    at Org.IdentityConnectors.Exchange.Service.Impl.PowerShellExchangeServiceImpl.InvokePipeline(Command cmd)
    at Org.IdentityConnectors.Exchange.Service.Impl.PowerShellExchangeServiceImpl.InvokePipeline(Command cmd)
    at Org.IdentityConnectors.Exchange.Service.Impl.PowerShellExchangeServiceImpl.SearchUser(ObjectClass oclass, String query, ResultsHandler handler, OperationOptions options, ObjectClassInfo ocInfo)
    at Org.IdentityConnectors.Exchange.Service.Impl.PowerShellExchangeServiceImpl.ExecuteQuery(ObjectClass oclass, String query, ResultsHandler handler, OperationOptions options)
    at Org.IdentityConnectors.Exchange.ExchangeConnector.ExecuteQuery(ObjectClass oclass, String query, ResultsHandler handler, OperationOptions options)
    at Org.IdentityConnectors.Framework.Impl.Api.Local.Operations.RawSearcherImpl`1.RawSearch(SearchOp`1 search, ObjectClass oclass, Filter filter, ResultsHandler handler, OperationOptions options)
    at Org.IdentityConnectors.Framework.Impl.Api.Local.Operations.RawSearcherImpl`1.RawSearch(Object search, ObjectClass oclass, Filter filter, ResultsHandler handler, OperationOptions options)
    at Org.IdentityConnectors.Framework.Impl.Api.Local.Operations.SearchImpl.Search(ObjectClass oclass, Filter originalFilter, ResultsHandler handler, OperationOptions options)
    at Org.IdentityConnectors.Framework.Impl.Api.Local.Operations.ConnectorAPIOperationRunnerProxy.Invoke(Object proxy, MethodInfo method, Object[] args)
    at ___proxy1.Search(ObjectClass , Filter , ResultsHandler , OperationOptions )
    at Org.IdentityConnectors.Framework.Impl.Server.ConnectionProcessor.ProcessOperationRequest(OperationRequest request)
    DateTime=2013-05-30T14:49:37.1880494Z
    h4. #3 - Powershell using the service account
    Get a 2003 database
    [PS] C:\Windows\system32>Get-MailboxDatabase "ORME-DE-COUR\Premier groupe de stockage\Banque de boîtes aux lettres (ORME-DE-COUR)"
    Name Server Recovery ReplicationType
    Banque de boîtes aux lettre... ORME-DE-COUR False None
    Get a 2003 mailbox
    [PS] C:\Windows\system32>Get-Mailbox -Filter "DisplayName -eq 'Marchand Robert 0'"
    Name Alias ServerName ProhibitSendQuota
    marchanr marchanr orme-de-cour unlimited
    Edited by: SG on May 30, 2013 11:57 AM
    Edited by: SG on May 30, 2013 1:41 PM

    Any update on this? I have the exact same problem...
    Thanks,
    --jtellier                                                                                                                                                                                       

  • Mailbox recipient does not have a mailbox database

    For one of our customers we are currently working on a prove of concept to implement on premise exchange servers. The problem mentioned below takes place on test servers.
    Server names and mail domain names are changed to generic values.
    On our on premise exchange environment we encounter the following problems when emailing to a specific email domain .
    Email to the domain companyname.com is placed in to the Unreachable Domain queue with the following error:
    Last Error: The mailbox recipient does not have a mailbox database
    Queue ID: SERVEREX01\Unreachable
    Recipients:  [email protected];2;3;The mailbox recipient does not have a mailbox database;1;<No Home Database>
    Situation:
    Customer uses a local Active Directory which contains all the user accounts and uses Office 365 / Exchange Online to provide these users with a mailbox. SSO between the local AD and O365 is provided by a third party identity provider.
     Dirsync is used to sync all user information from the local AD to O365 AD. This also includes the SMTP addresses users have on the Office 365 mailbox. In the local AD this information is saved is the proxyaddress attribute field and synced
    to O365. Office 365 uses the following mail domains for customer: companyname.com and companyname.onmicrosoft.com.
    Customer wants to use local on premise exchange servers for specific locations and users and doesn’t want to implement a hybrid exchange environment. Therefore we installed an Exchange 2010 Edge server in the DMZ and an Exchange 2013 MBX
    / CAS server in the server network. The Exchange 2013 server is installed in the same Active Directory as the one mentioned above. This environment uses the mail domain @central.companyname.com. The email environment is configured to only accept email for
    this domain.
    The email environment works fine. It can send and receive email internally and externally. There is only one issue. It’s impossible to send email from the on premise environment to office 365. The other way around (O365 to on premise)
    works fine.
    When an email is send to a companyname.com email address the exchange 2013 mail server places the email in the Unreachable Domain queue and reports 
    the following error:
    Last Error: The mailbox recipient does not have a mailbox database
    Queue ID: SERVEREX01\Unreachable
    Recipients:  [email protected];2;3;The mailbox recipient does not have a mailbox database;1;<No Home Database>
    This is caused by the fact that the @companyname.com email addresses are stored in the active directory exchange uses. We tried to fix this problem to create a internal and external relay domain with the appropriate send connector but
    this didn’t help.
    When we remove the proxyaddress attribute in the local active directory we are able to send email from the on premise exchange server to Office365. Removing the proxyaddresses is not a solution because these settings will be synced to
    Office 365 and users can’t receive email anymore in there cloud mailbox.
    It looks like the SMTP Categorizer first looks in active directory if the target email addresses is available. If so it will send the email to this users (but doesn’t have a mailbox server and mailbox database).
    Can we configure a working mailflow for email from on premise to Office 365 for @companyname.com addresses?

    Hi,
    Please try to set the target Address from the on premise AD account in ADSIedit to match the Cloud mailbox address, and then check the result.
    In addition, I recommend you post this thread on office 365 forum:
    http://community.office365.com/en-us/forums/default.aspx
    Hope this helps!
    Thanks.
    Niko Cheng
    TechNet Community Support

  • Exchange 2010 - Mail Database Recovery after Database Portability Applied

    Background:
    We had a city-wide power failure  at Office A and as a result Exchange Server A (ES-A) was taken offline for an extended period of time.  The last good backup of ES-A-DB was from the previous business day.  The DR plan was enacted and the
    ES-A mailbox database (ES-A-DB) was recovered to Exchange Server B (ES-B) as ES-B-DB2.  Keeping in mind that a days worth of emails still reside on ES-A-DB.
    Process:
    I employed the database portability method when restoring the ES-A-DB to ES-B-DB2 at Office B.  I rehomed the exchange users in active directory to now use ES-A-DB2.  Users are working fine, activesync worked without issue.  All is well.
    I now face the situation where power has been restored to Office A and the server is available.  I have NOT turned this server on yet as I am not sure what the net affect will be on ES-A and ES-A-DB.
    The primary goal of the business is to recover the mail items from the missing day that was not backed up and recovered to ES-B-DB2.  What would be the best way to do achieve this objective?  
    This is what I am thinking, though its all theoretical since I've never been in this situation.
    - boot the Exchange Server with the network card disconnected
    - Dismount ES-A-DB from ES-A
    - Remove ES-A-DB from Exchange Org on ES-B
    - Process logs and put the ES-A-DB in a Clean state
    - mount as recovery database
    - copy differential mail items to ES-B-DB2 mailboxes
    Anyone have insight on this?
    Thanks for your help in advance.

    No need to dismount , remove from the org or boot the server w/o a NIC. The association between Exchange and the user is in AD and you already changed that when you set the new database with database portability.
    I would just follow the instructions for restoring back to their current production mailboxes (DB2).
    http://exchangeserverpro.com/restoring-mailbox-exchange-server-2013-recovery-database/
    Try it with a sample mailbox or two and see how it handles the conflict resolution for duplicates.
    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

  • Exchange 2010 - Moving mailbox database from exchange 2010 server to another exchange 2010 server

    Hi,
    I have a current existing exchange server running on 2008 R2. apparently the partition that holds the mailbox database is getting full and i need to move some user mailboxes to another environment ( exchange 2010 running on 2008 R2). i transferred some users
    successfully to the new location, but am not able to transfer the rest. I am getting the errors:
    Summary: 1 item(s). 0 succeeded, 1 failed.
    Elapsed time: 00:00:00
    Erastus XXXXX
    Failed
    Error:
    The queue in 'MBX2010_STAFF' database already contains a move request for 'Erastus XXXXX', while AD reports the mailbox as not being moved. It is possible that someone created this move request recently, while targeting a different domain controller, and AD
    replication did not yet occur. You can examine this move request by running 'Get-MoveRequestStatistics -MoveRequestQueue 'MBX2010_STAFF' -MailboxGuid f8023bc7-9d65-4194-9f6b-10e4780558b5 -IncludeReport | fl'. If you believe this to be an abandoned move request,
    you can remove it by running 'Remove-MoveRequest -MoveRequestQueue 'MBX2010_STAFF' -MailboxGuid f8023bc7-9d65-4194-9f6b-10e4780558b5'.
    Exchange Management Shell command attempted:
    'xxxxxxxx.co.ke/Training Department/XXXXXXX/XXXXXXX/Erastus XXXXX' | New-MoveRequest -TargetDatabase 'OFFICE_STAFF_MB_DB' -BadItemLimit '0'
    Elapsed Time: 00:00:00
    AND
    Summary: 1 item(s). 0 succeeded, 1 failed.
    Elapsed time: 00:00:01
    George XXXXX
    Failed
    Error:
    Service 'net.tcp://win-u5bjh2oamaa.xxxxxxxxx.co.ke/Microsoft.Exchange.MailboxReplicationService' encountered an exception. Error: MapiExceptionNoAccess: Unable to open message store. (hr=0x80070005, ec=-2147024891)
    Diagnostic context:
        Lid: 18969   EcDoRpcExt2 called [length=207]
        Lid: 27161   EcDoRpcExt2 returned [ec=0x80070005][length=202][latency=0]
        Lid: 32881   StoreEc: 0x80070005
        Lid: 50035 
        Lid: 64625   StoreEc: 0x80070005
        Lid: 1494    ---- Remote Context Beg ----
        Lid: 26426   ROP: ropLogon [254]
        Lid: 56503 
        Lid: 12716   StoreEc: 0x80070005
        Lid: 20794 
        Lid: 28474   StoreEc: 0x80070005
        Lid: 22330   dwParam: 0x0        Msg: 14.01.0270.001:CPLSERVER
        Lid: 1750    ---- Remote Context End ----
        Lid: 23354   StoreEc: 0x80070005
        Lid: 25913 
        Lid: 21817   ROP Failure: 0x80070005
        Lid: 26297 
        Lid: 16585   StoreEc: 0x80070005
        Lid: 32441 
        Lid: 1706    StoreEc: 0x80070005
        Lid: 24761 
        Lid: 20665   StoreEc: 0x80070005
        Lid: 25785 
        Lid: 29881   StoreEc: 0x80070005
    Exception details: MapiExceptionNoAccess (80070005): MapiExceptionNoAccess: Unable to open message store. (hr=0x80070005, ec=-2147024891)
    Diagnostic context:
        Lid: 18969   EcDoRpcExt2 called [length=207]
        Lid: 27161   EcDoRpcExt2 returned [ec=0x80070005][length=202][latency=0]
        Lid: 32881   StoreEc: 0x80070005
        Lid: 50035 
        Lid: 64625   StoreEc: 0x80070005
        Lid: 1494    ---- Remote Context Beg ----
        Lid: 26426   ROP: ropLogon [254]
        Lid: 56503 
        Lid: 12716   StoreEc: 0x80070005
        Lid: 20794 
        Lid: 28474   StoreEc: 0x80070005
        Lid: 22330   dwParam: 0x0        Msg: 14.01.0270.001:CPLSERVER
        Lid: 1750    ---- Remote Context End ----
        Lid: 23354   StoreEc: 0x80070005
        Lid: 25913 
        Lid: 21817   ROP Failure: 0x80070005
        Lid: 26297 
        Lid: 16585   StoreEc: 0x80070005
        Lid: 32441 
        Lid: 1706    StoreEc: 0x80070005
        Lid: 24761 
        Lid: 20665   StoreEc: 0x80070005
        Lid: 25785 
        Lid: 29881   StoreEc: 0x80070005
    Exchange Management Shell command attempted:
    'xxxxxxxxxx.co.ke/Training Department/xxxxxx/xxxxxxx/George xxxxxxx' | New-MoveRequest -TargetDatabase 'OFFICE_STAFF_MB_DB' -BadItemLimit '0'
    Elapsed Time: 00:00:01
    I have all the proper rights.
    YOUR ASSISTANCE WILL BE HIGHLY APPRECIATED. THANX :)

    0x80070005 is pretty standard access denied entries.  I would start digging into ACLs on a handful
    of mailboxes.
    Is there another Admin that can give it a shot to test their permissions vs yours?
    - If you find my post to be helpful, or the answer, please mark it appropriately. Thank you.
    Chris Ream

  • Mailbox Database Copy Status Failed

    We have 2 Exchange 2010 servers.  We run a DAG.  Recently I have noticed that database copy DB2 which is located on Exch-1 is showing "Failed".  Database copy DB1 which is located on Exch-2 is showing Healthy.  I searched online
    for information regarding the issue with the failed database copy.  I found information that led me to run these commands.
    Suspend-MailboxDatabaseCopy -Identity “Mailbox Database XXXXX\Server Name”
    Update-MailboxDatabaseCopy -Identity “Mailbox Database XXXXX\Server Name” -DeleteExistingFiles
    It went thru the seeding process and completed but the database copy still shows "Failed".  Copy Q Length is 19.  I have refreshed the console.  What else do I need to do to correct this?  I did recently shut down Exch-2 server
    for maintenance.  thanks

    Hi,
    It's glade to hear the good news. Thanks for your updating.
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • Exchange 2010 - Create a new Mailbox Database

    Hello all and thanks in advance for your time and expertise.
    Here's my scenario:
    In my ORG we have one exchange server.  The hard drive space on this server was quite low so we added two more drives which are independent and in their own Raid Configuration from the drives that were already installed.  In other words, the current
    mailbox database is housed on drives with a total storage capacity of 837GB. 
    We recently added two more drives, each 2TB, and configured them in a RAID1. 
    I'm going to create a new Mailbox Database on the 2TB drives and move over some mailboxes to balance out the storage. 
    Question one:  When we move some of the mailboxes over to the new database - will this free up space on the existing database or do we have to reclaim it such as with an offline degrag.
    Question two:  When I create the new mailbox database and I'm prompted to Enter the new file locations for the database (database path and log folder path) - do I just change the paths to the new drive letter path such as G:
    We're eventually going to Office365 (hopefully sooner rather than later) but I just want to make sure I handle this process correctly. Your input here is greatly appreciated.

    Hello,
    Your databse size is 650 GB.  As per my experience , it would not take more than 14 hours for total mailbox movement.
    You will be creating new database of 2 TB , you have already allocated 2 Tb drive to exchange server.
    If you are dividing drive into 2 or four part and creating that much databse, it will be helpful for maintence activity in future.
    It is recommended that you move mailbox during off bussiness hours, it will fasten the movment,as there will be no load on exchange server . You can do it on daily basis Or you can do it on weekend .
    You need to take care of logs generated during movment, are you going to  use seperate log drive for databse, or combine with database drive. If you are moving all mailbox to one database, It will genrate same size of logs file as of total mailboxes
    size (650 GB). You neeed to handle it properly. Enable circular logging on database, after movment ,you can disable it.
    Moreover, if you will create move request of all mailboxes, exchange will process nly 50 request, rest will be in queue state.
    Regarding public folders, I understand there is no seperate disk for public folders, if you planning to delete old dtabse and free up disk space, you will have to move this public folders database to new disk also.
    Would recommend that you take advice  from other expert in this forum, before implementation.

  • Event ID 218 Copy of database 'Mailbox Database'- experienced a performance problem

    Hi,
    We have 16 GB of RAM for EXchange 2010 and 4 Processor and using iSCSI Starwind LUN.
    Event ID : 218
    Event Source : ExchangeStoreDB
    Event Category :Database Recovery
    the copy of database 'Mailbox Database - NYM' on this server experienced a performance problem. Failover returned the following
    error: here is only one copy of this mailbox database (Mailbox Database - NYM). Automatic recovery is not available.
    It occurs specially when the exchange backup start ; we are using window backup for taking exchange backup
    I can see warnning of ESE below the event 218 - Information Store (3912) Mailbox Database - NYM: A request to write to the file "D:\Program Files\Microsoft\Exchange Server\V14\Mailbox\Mailbox Database 0959355037\Mailbox Database 0959355037.edb" at
    offset 150801350656 (0x000000231c760000) for 32768 (0x00008000) bytes has not completed for 68 second(s). This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.
    Also,
    1. How can I enable verbose logging to expert level for exchange MailboxDatabase.
    2. What type performace counter need to be set for exchange database in Performance Monitor
    Any Help ?
    Thanks
    Prakash

    We had the same issue on our mbx server with Exchange 2010 Ent SP3, Win Svr 2008 R2 SP1 running on VMware v5.1 with Exchange dbs mounted to the VM via iSCSI LUNs on our NetApp SAN.  
    We escalated the ticket, and the Microsoft Exchange escalation team stated that the EIDs of the database corruption and automatic recovery seem to point to a hardware issue.  And, they told us not to panic and that there was no need to rebuild the environment
    and migrate the databases immediately.  They instead asked us to focus all our efforts on solving the iSCSI environment issues, since each Exchange EID db corruption/ autorecovery would be preceded by some type of corresponding iSCI System EID.  
    We hence opened tickets with MS Storage Team and with NetApp support and worked on this ticket with input from all 3 groups.
    After about a month an a half of troubleshooting & trial error- with tickets open with NetApp, MS Storage Team, and MS Exchange team, we finally seem to have applied a configuration change that worked. 
    NetApp support referred us to the following article relating to VMware:
    http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2039495
    So, per NetApp support and MS Storage team, do the following:
    1.    Manually dismount Exchange Databases on the mailbox server.
    2.    Open Device Manager, Network Adapters, VMXNET3 Ethernet Adapter #3, Properties
    3.    Change Small RX Buffers from the default 512 to the maximum 8192 using the drop down selector.
    4.    Change the RX Ring #1 from the default 1024 to the maximum of 4096 using the drop down selector.
    5.    Click OK and save the change.
    6.    Re-mount the Exchange Databases
    And, to our surprise, this seems to have done the trick.  It seems like the issue is an iSCSI-related NIC setting all along.
    Thanks,
    Detrich

Maybe you are looking for

  • TMS has lost connection with VCS

    I've enforced group policies since adding TMS to a domain and now my TMS isn't getting a https response from the VCS.  Any ideas? Gives the error "Configuration conflict - A domain is in use by the OCS Relay application that has not been configured o

  • Procurement of Capital Goods-Accounting entries error

    Hi All I processing procurement of Capital Goods scenario. Qty - 1; Base Amount: 100; BED: 16%; AED: 8%; SED: 4% When I posted Goods Receipt, I beleive the accounting entries are expected to be as follows: Dr  BED  16 Dr  AED   8 Dr  SED   4 Cr  CENV

  • Creation of Vendor in EBP

    HI All, I created a Vendor in transaction BP, and attached this vendor to vendor group in PPOMV_bbp and maintained attributes. But in the shopping cart i am not getting this vendor in drop down list.If i manualy put this vendor . It is throwing error

  • Upgrading but not installing Flash with MSI

    I have an environment of some 600 PCs running XP. A few have Flash installed, most do not. Those that have Flash installed are a variety of versions. It's my intent to perform a Flash install using MSI and GPO, and that's (mostly) tested and working.

  • Setting the count of display in User Admin

    Hi.. does an one know that where and how can we set the no. of users to be displayed for the ""user admin"" containing the users list for the UCM user list.