04-19-2011 11:06 AM - edited 03-16-2019 04:35 AM
04-19-2011 11:43 AM
I've been fighting with this issue and finally found a resolution.
I used the Microsoft tool EWS Editor (http://archive.msdn.microsoft.com/ewseditor) to test the configuration on the Exchange server. Use the URL "https://<servername>/EWS/Exchange.ASMX". Use the server name that is referenced by the server certificate you loaded on the Unity box. You can input the Unity Server Account and test the impersonation function to access a users mailbox. This tool will verify the permission setting of the Unity service account.
The big issue that I ran into was the test functionality within Unity. I had the incorrect password for the Unity service account. When I used the configuration of Forms Based Authentication within Exchange, Digest Authentication on Unity and the incorrect password, Unity reported that it was able to access the user mailboxes. This is a FALSE POSITIVE!! We disabled Forms Based Authentication on Exchange, change to NTLM authentication on Unity and corrected the password used. This corrected the issue.
Please keep in mind that Single Inbox on 8.5 to Exchange 2010 is new and TAC has a very small toolbox to troubleshoot issues.
Chris
04-19-2011 12:18 PM
thanks Chris,
I just passed this along to their exchange team. They are looking at the program now to see how it works.
In your response below you mention loading a certificate on unity connection. Am i missing a step? i don't recall doing that during the setup
04-19-2011 12:35 PM
If you will be using SSL, you will need to upload the correct Exchange cert to the Unity server. Please reference the link below.
04-19-2011 12:40 PM
ahh thats why i didn't see it. not using ssl here.
thanks! waiting to hear back from their exchange group to see if they fixed the issue
04-19-2011 12:58 PM
Please reach out to me if I can help in the future.
07-28-2011 08:34 PM
Hey Chris. Running into the same issue here with the 401 error message when I test the account. We followed the steps all the way. Any idea what fixed it on your end?
12-18-2011 01:31 PM
Though am late to answer , whoever run in to the same issue may use the below resolution .
Very simple . reset the password of the Unity Service account and use a password which does not have any special charecters !!!.. It'll work . It just worked for me
Best Regards
Rajesh
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