Exchange 2010 Restore Fails Due To Application Impersonation Error
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet Microsoft Exchange 2010 GRT restore of individual emails fails with error 0xe0000389 - Unable to create a role assignment for ApplicationImpersonation Article:000013390 Publish: Article URL:http://www.veritas.com/docs/000013390 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem Restore from Microsoft Exchange 2010 GRT AVVI backup set or RAWS based backup set for individual email fails with error “unable to create a role assignment for ApplicationImpersonation” Error Message Final error: 0xe0000389 - The resource credentials for the restore job were unable to create a role assignment for ApplicationImpersonation. Review the credentials to ensure that it has the rights that are required for ApplicationImpersonation.Final error category: Resource Errors For additional information regarding this error refer to link V-79-57344-905 SGMON log from media server shows the following errors: BEREMOTE: [0000] [10036] [fsys\mb2] - Checking Permissions for EWSBEREMOTE: [0000] [10036] [fsys\shared] - EnsureEwsPermissions returned 80131501BEREMOTE: [0000] [10036] [fsys\mb2] - FATAL: failed to aquire EWS ApplicationImpersonation rightsBEREMOTE: [0000] [10036] [ndmp\loops] - Error: CreateObj returns extended error e0000389 Cause This issue could occur due to following multiple reasons: Cause A. If the Backup Exec Service Account/Logon Account is having insufficient rights or does not have an active mailbox associated with it or it is hidden from Global Address list. Cause B. The role assignment for ApplicationImpersonation is not set on the Backup Exe
JoshiNovember 29, 20111 0 0 0 A customer recently reported a problem to Microsoft where they were dicovering that their exchange web services were unable to connect to some mailboxes. Often support engineers need to ask probing questions about what recently happened in the companys organisation, what recent tools and software updates that were applied and some back ground information about their network topology is neeed to be able to isolate the problem at hand. In this customers case, they had recently performed a migration from 1900 exchange 2003 mailbox accounts to https://www.veritas.com/support/en_US/article.TECH168297 exchange 2010 mailboxes. Some of these accounts were unable to be accessed using impersonation from exchange web servicesI wanted to document some tools and questions that might be worth asking to try and help isolate the root cause and be able to find an appropriate troubleshooting path. The core issue was related to impersonation code not working in customers EWS code to access certain https://blogs.msdn.microsoft.com/pareshj/2011/11/29/exchange-web-services-fail-using-impersonation-to-access-mailboxes/ mailboxes. these articles are a good reference to determine how you can get configure impersonation to work with EWS and ensure the accounts you are using have the appropriate privileges/roles.scope to perform the taskhttp://msdn.microsoft.com/en-us/library/bb204095.aspx Using Exchange Impersonationhttp://msdn.microsoft.com/en-us/library/bb204088.aspx Working with impersonation by using the EWS Managed APIhttp://msdn.microsoft.com/en-us/library/dd633680(EXCHG.80).aspx The soap test tool is a good tool to determine (outside of yoru code) if your EWS code is working correctly, you can find this here -http://soaptestapp.codeplex.com/ There is a brief introduction here: http://soaptestapp.codeplex.com/wikipage?title=Introduction With the call succeeding we can rule out if it was related to the customers code so we wanted to know what ServiceError reports back from EWS http://msdn.microsoft.com/en-us/library/microsoft.exchange.webservices.data.serviceerror(v=exchg.80).aspxIn the SOAP requests in your code can you add.. svc.TraceEnabled = true;svc.TraceFlags |= TraceFlags.All; more information here - Tracing EWS requestshttp://msdn.microsoft.com/en-us/library/dd633676(v=EXCHG.80).aspxThis will add additional logging information to the SOAP data chck that the customer was using the latest EWS API libraries(14.02.0051.000)http://www.microsoft.com/download/en/details.aspx?id=13480 It's always good to understand what the underlying SOAP requests are so using tools such as netmon and fiddler is always good to use to determine what web service errors you may be seeing . These mailboxes were
Enterprise Software Restoring Exchange 2010 using Backup Exec 2010 + Post New Thread Results 1 to 5 of 5 Enterprise Software Thread, Restoring Exchange 2010 using Backup Exec 2010 in Technical; We're backing up our Exchange databases with Backup Exec. The backup completes fine, http://www.edugeek.net/forums/enterprise-software/93952-restoring-exchange-2010-using-backup-exec-2010-a.html but we are unable to restore anything. ... LinkBack LinkBack URL About LinkBacks Bookmark & Share Digg this Thread!Add Thread to del.icio.usBookmark in TechnoratiTweet this threadShare on Facebook!Reddit! Thread Tools Search Thread Advanced Search 24th April 2012,02:09 PM #1 https://forum.commvault.com/forums/41267/ShowThread.aspx AnnDroyd Join Date Sep 2007 Posts 150 Thank Post 4 Thanked 2 Times in 2 Posts Rep Power 19 Restoring Exchange 2010 using Backup Exec 2010 We're backing up our Exchange databases with Backup Exec. The backup completes fine, but exchange 2010 we are unable to restore anything. Fortunately, I don't need to at the moment, but we could in future. Errors include: V-79-57344-898 - Backup Exec attempted to restore an Exchange database according to the job settings. The Exchange server was not found V-79-57344-905 - The resource credentials for the restore job were unable to create a role assignment for ApplicationImpersonation. V-79-57344-766 - Cannot log on to MAPI with the specified credentials. Review the resource credentials for the job, and then exchange 2010 restore run the job again. Has anyone experienced this kind of problem and found a solution? We're potentially going to have to replace our backup software to get around this. Send PM 25th April 2012,06:58 PM #2 sukh Join Date Dec 2008 Location Essex Posts 2,157 Thank Post 1 Thanked 326 Times in 316 Posts Rep Power 81 Seems like an issue with the credentials, have you seen the backupexec documentation? Send PM 26th April 2012,10:06 AM #3 AnnDroyd Join Date Sep 2007 Posts 150 Thank Post 4 Thanked 2 Times in 2 Posts Rep Power 19 The backup and restore jobs are running with the domain administrator account, so that should be ok, shouldn't it? Send PM 26th April 2012,10:18 AM #4 Domino Join Date Oct 2006 Location Bromley Posts 4,468 Thank Post 230 Thanked 1,605 Times in 922 Posts Blog Entries4 Rep Power 578 You might just wanna check in the RBAC that the admin account has the required access. it also needs a mailbox associated with it - the requirements in full are here; Enterprise Support - Symantec Corp. - Exchange 2010 restore fails due to Application Impersonation error. Send PM 26th April 2012,12:37 PM #5 sukh Join Date Dec 2008 Location Essex Posts 2,157 Thank Post 1 Thanked 326 Times in 316 Posts Rep Power 81 Check the above link posted by Domino Send PM SHARE: + Post New Thread Similar Thread
Posts: Oldest to newest Newest to oldest Previous Next Exchange MailBox Discovery failed Posted:01-30-2015, 8:31 AM omer Joined on 08-28-2014 Newcomer Points 28 Hello, When i discover mailbox i have receive this error. I was check ADSIEDIT config is correctly. CommServe Simpana 10 sp9, Windows 2008 AD Simpana 10 sp9 Windows 2003 Exchange Server Simpana 10 sp9 Exchange 2010 92692 17638 01/30 15:02:40 ### ****************ExchDiscover.exe has started with args [ExchDiscover.exe -j 0 -a 2:109 -c ExchangeServerName -m ExchangeServerName -t 2 -r 0 -i 0 -cn ExchangeServerName cvshost:CommServe*CommServe cvsport:60451:0 cvsmyplatform:4 cvsremoteplatform:1 -vm Instance001]****************92692 17638 01/30 15:02:40 ### Failed to create working dir (C:\Program Files\CommVault\Simpana\iDataAgent\JobResults), error code 1792692 17638 01/30 15:02:40 ### Working dir (C:\Program Files\CommVault\Simpana\iDataAgent\JobResults)92692 17638 01/30 15:02:40 ### Agent dir is C:\Program Files\CommVault\Simpana\iDataAgent\JobResults92692 17638 01/30 15:02:40 ### Exchange server list : ExchangeServerName, Multiple Servers: false 92692 17638 01/30 15:02:40 ### getServerName [ExchangeServerName]92692 17638 01/30 15:02:40 ### Create temporary per process profile for this job: true92692 17638 01/30 15:02:40 ### Use of mailbox info DB is turned ON.92692 17638 01/30 15:02:40 ### Mailbox DB refresh interval: 30 minute(s).92692 17638 01/30 15:02:40 ### User Name - acs-bim92692 17638 01/30 15:02:40 ### Domain Name - DomainName92692 17638 01/30 15:02:47 ### CVImpersonateLoggedOnUserByRef() - Failing user impersonation as the user is not able to write to Galaxy log files92692 17638 01/30 15:02:47 ### Unable to impersonate user.92692 17638 01/30 15:02:47 ### Sending last APPMAN_GENERAL_MSG_ID92692 17638 01/30 15:02:47 ### Discover terminated due to session disconnection92692 17638 01/30 15:02:47 ### User impersonation error92692 17638 01/30 15:02:47 ### Sending last APPMAN_GENERAL_MSG_ID: 92692 17638 01/30 15:02:47 ### Discover terminated due to session disconnection92692 17638 01/30 15:02:47 ### ** CVSession::sendBytes(...) iSocketMember=428 send failed, err=0x8007276D:{QiSocket.cpp[CQiSocket::Send(397)]/W32.10093.(Either the application has not called WSAStartup, or WSAStartup failed.)}.92692 17638 01/30 15:02:47 ### ** CVSession::sendMessageInt(...): - RemoteHost=CommServe Name - RemoteProcess=AppMgr