07-13-2012 08:19 AM - edited 03-19-2019 05:14 AM
We have thousands of users configured with the same BPOS UM connector, no issues. We have one account that can not access their exchange mailbox, and have been told the mailbox properties/permissions are set properly by Microsoft.
Does anyone have any suggestions as to what this error message really means? Would traces give me more information or just tell me the same level of detail?
HTTP status=[200] Diagnostic=[Failed extract folder ID '' from response] Verb=[POST] url=[https://mail.bsnconnect.com/EWS/Exchange.ASMX] request=[<?xml version="1.0" encoding="utf-8"?> <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:t="http://schemas.microsoft.com/exchange/services/2006/types"> <soap:Header> <t:RequestServerVersion Version="Exchange2007_SP1"/> <t:ExchangeImpersonation> <t:ConnectingSID> <t:PrimarySmtpAddress>TerHelpDesk@dow.com</t:PrimarySmtpAddress> </t:ConnectingSID> </t:ExchangeImpersonation> </soap:Header> <soap:Body> <GetFolder xmlns="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:t="http://schemas.microsoft.com/exchange/services/2006/types"> <FolderShape> <t:BaseShape>Default</t:BaseShape> </FolderShape> <FolderIds> <t:DistinguishedFolderId Id="deleteditems"> <t:Mailbox> <t:EmailAddress>TerHelpDesk@dow.com</t:EmailAddress> </t:Mailbox> </t:DistinguishedFolderId> </FolderIds> </GetFolder> </soap:Body> </soap:Envelope> ] response=[<?xml version="1.0" encoding="utf-8"?><s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"><s:Header><h:ServerVersionInfo MajorVersion="14" MinorVersion="2" MajorBuildNumber="309" MinorBuildNumber="3" Version="Exchange2010_SP2" xmlns:h="http://schemas.microsoft.com/exchange/services/2006/types" xmlns="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"/></s:Header><s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><m:GetFolderResponse xmlns:m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:t="http://schemas.microsoft.com/exchange/services/2006/types"><m:ResponseMessages><m:GetFolderResponseMessage ResponseClass="Error"><m:MessageText>Access is denied. Check credentials and try again.</m:MessageText><m:ResponseCode>ErrorAccessDenied</m:ResponseCode><m:DescriptiveLinkKey>0</m:DescriptiveLinkKey><m:Folders/></m:GetFolderResponseMessage></m:ResponseMessages></m:GetFolderResponse></s:Body></s:Envelope>]
Thanks
07-22-2012 11:10 AM
You mention a "connector" so I am assuming this isn't Single Inbox/UM for CUC and Exchange or maybe just a mis-use of the term "connector." If you are using some odd connector solution with proxy smtp to make this work, I would imagine this isn't in our range of supported solutions. If you are using SIB, then we need to know additional information.
What version of exchange?
Are you using HTTP or HTTPS on the UM account?
Are you using Basic, forms based, or NTLM on the UM account?
From what I see on the error you posted here, it seems to be an issue with access just with that one account...
ResponseClass="Error">
It even says to check credentials.
Also keep in mind that we only support hosted Exchnage of Office365 or on site Exchange with SIB CUC solutions. If it is true MS BPOS, then it would have to be approved by bu before being implimented. Please provide the additional info as to what solution this is (ms connector of some kind or SIB) and answers to the other questions posed and we might be able to help you further.
Tray
07-11-2014 07:06 PM
Was there any resolution to this issue? I have this same with (UCON 8.6.2 - single inbox using BPOS, NTLM, HTTPS, Exchange 2007 (latest SP) with only a few users everyone else is working without issues. I have re-applied all of the exchange impersonation permissions as outlined in the Cisco guide for the service account being used. I have applied these permissions at the organizational level to no avail. I'm about to call Microsoft on this issue. How were you able to resolve this if you did? Thanks Phillip
07-14-2014 05:00 AM
I believe we had to contact Microsoft as well, and no information was shared with us as to what the issue was, but it was resolved. Good luck.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide