Crossroads305
asked on
CRM Email Router 2013 giving errors when deploying a rule for a new queue
Environment: migrated to Exchange 2013 on server 2012r2 and migrated our mailboxes over to the server. Our Exchange 2010 on server 2008r2 Environment is still up with out any user mailboxes on it.
It's still routing emails but testing hangs for a very very long time on incoming server but the outgoing passes right away when we test, I never see it finish but the window disappears. I'm assuming if this failed it would stay open? This is a new development, on the Exchange 2010 only environment this would go right away. I have made a send connector in exchange 2013 to accept connections from the CRM server.
Now when attempting to deploy the rules all the previous rules pass but the new rule will fail with the following error and not route emails to the queue.
<?xml version="1.0"?>
-<ArrayOfRequestResult xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
-<RequestResult>
<RequestAction>DeployRule< /RequestAc tion>
<RequestStatus>Failure</Re questStatu s>
<ExceptionInfo>Microsoft.C rm.Tools.E xchangeCon nectorDepl oyment.Rul eDeploymen tException : Failed to access the default store for the user. ---> System.Runtime.InteropServ ices.COMEx ception: Failed to access the default store for the user. --- End of inner exception stack trace --- at Microsoft.Crm.Tools.Exchan geConnecto rDeploymen t.RuleDepl oymentSess ion.SendCo mmand(Stri ng command, String exchangeServerName, String exchangeStoreDn, String exchangeSystemDn, String exchangeMailboxDn, String crmEmailAddress, Boolean disabledMode, String exchangeServerLegacyName, String exchangeAdminMailboxDn, Boolean isExchange14, RULE_STATUS& ruleStatus) at Microsoft.Crm.Tools.Exchan geConnecto rDeploymen t.RuleDepl oymentRequ est.Proces sNext()</E xceptionIn fo>
<DataInfo xsi:type="xsd:string">Path :GC://CN=r chh003supp ort,OU=CRM Queues,DC=Company,DC=com;h omeMDB:CN= Support_Qu eues_2015, CN=Databas es,CN=Exch ange Administrative Group (FYDIBOHF23SPDLT),CN=Admin istrative Groups,CN=Company,CN=Micro soft Exchange,CN=Services,CN=Co nfiguratio n,DC=Compa ny,DC=com; sAMAccount Name:rchh0 03support; CN:rchh003 support;le gacyExchan geDN:/o=Co mpany/ou=E xchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recip ients/cn=r chh003supp orte3d;msE xchHomeSer verName:/o =Company/o u=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Confi guration/c n=Servers/ cn=exchang e2013;</Da taInfo>
</RequestResult>
</ArrayOfRequestResult>
I'm not sure what the error means, or how to trouble shoot it. I found a tech net that said add it to the administrator full rights to the mailbox which I followed and completed but still get the same error. Has anyone ever come across this error in their deployment with exchange 2013 and figured a way to solve it? We also tried moving the mailbox back to 2010 and seeing if that work, which did not and giving the CRM account application impersonation abilities.
::EDIT:: I was told from the previous tech who worked on this that the test access is good and doing what its supposed to do because we are using a forwarding mailbox.
It's still routing emails but testing hangs for a very very long time on incoming server but the outgoing passes right away when we test, I never see it finish but the window disappears. I'm assuming if this failed it would stay open? This is a new development, on the Exchange 2010 only environment this would go right away. I have made a send connector in exchange 2013 to accept connections from the CRM server.
Now when attempting to deploy the rules all the previous rules pass but the new rule will fail with the following error and not route emails to the queue.
<?xml version="1.0"?>
-<ArrayOfRequestResult xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
-<RequestResult>
<RequestAction>DeployRule<
<RequestStatus>Failure</Re
<ExceptionInfo>Microsoft.C
<DataInfo xsi:type="xsd:string">Path
</RequestResult>
</ArrayOfRequestResult>
I'm not sure what the error means, or how to trouble shoot it. I found a tech net that said add it to the administrator full rights to the mailbox which I followed and completed but still get the same error. Has anyone ever come across this error in their deployment with exchange 2013 and figured a way to solve it? We also tried moving the mailbox back to 2010 and seeing if that work, which did not and giving the CRM account application impersonation abilities.
::EDIT:: I was told from the previous tech who worked on this that the test access is good and doing what its supposed to do because we are using a forwarding mailbox.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.