[BETA 7314] Autodiscover "User does not exist"
Problem reported by Alex Clarke - 1/13/2020 at 10:48 AM
Submitted
Autodiscover is failing for me.

The log is filling up with errors as below (IP redacted).

[2020.01.13] 17:42:31.968 [xxx.xxx.xxx.xxx]Error: User does not exist.

When hitting the autodiscover page in a web brower (after entering in my valid credentials) I'm presented with the following error. I presume if the log was set to detailed then this would be capture too.

Invalid XML Request - Error: User does not exist. Server stack trace:   at MailService.Remoting.Mail.GetUserStatic(String email)   at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs)   at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg) Exception rethrown at [0]:   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)   at SmarterMail.RemoteInterface.IMail.GetUser(String sessionStr, String emailAddress)   at SmarterMail.Logic.Remoting.RemoteMail.GetUser(String sessionStr, String email)   at SmarterMail.Web.SyncProtocols.AutoDiscover.AutoDiscoverProcessor.DoWork(Object workItemState),

We've not previously used autodiscover, so there is a chance it's been set up incorrectly. However, I did following the instuctions below.

4 Replies

Reply to Thread
0
Larry Duran Replied
Employee Post
Hey Alex, you could try running something like Fiddler to capture the traffic.  This would show us information like what user they're trying to authenticate against as well as what user they're trying to get autodiscover settings for.

Also, in the domain's settings make sure you have the proper autodiscover protocols enabled for the user you're testing with and that they are enabled for that protocol.  
Larry Duran
Software Developer
SmarterTools Inc.
(877) 357-6278
www.smartertools.com
0
Alex Clarke Replied
Thanks Larry.

I’m testing this with my own accounts, so know the credentials are correct.

All the autodiscover protocols are enabled too. 
0
Larry Duran Replied
Employee Post
Ok, thanks for the update.  If you do get a fiddler trace and want a second pair of eyes to look it over you can private message it to me.
Larry Duran
Software Developer
SmarterTools Inc.
(877) 357-6278
www.smartertools.com
1
Alex Clarke Replied
I've managed to get this working.

The DNS records were not updating correctly (buggy GUI managed by a third-party). After changing nameservers for our domain and setting up the DNS on our system autodiscover works.

We do experience an SSL warning when Outlook performs an autodiscover lookup. This is owing to the mailbox domain being different to the SM server domain. Is there a way around this (without having to set up a SSL cert. for each domain)?

Reply to Thread