Hi!
I just came across a very interesting situation and hope someone here can help me fix it. I installed an Exchange Server 2016 to migrate vom SBS 2011. Everything fine there. All the mailboxes have been moved to the new server, but the old one hasn't been uninstalled yet. A co-worker is configuring an achriving software that accesses the Exchange Server using EWS. He can connect and sees the mailboxes, but can not archive them. This ist the Error he gets in his logs:
2020/12/01 10:24:11 138 [014] [i] [TryAutodiscover] ErrorCode: NoError
2020/12/01 10:24:11 138 [014] [i] [TryAutodiscover] resolved
2020/12/01 10:24:11 138 [014] [i] [GetUserSettings] autodiscover completed
2020/12/01 10:24:11 142 [014] [i] [USRSETTING.Dump] EwsSupportedSchemas : Exchange2007, Exchange2007_SP1, Exchange2010, Exchange2010_SP1, Exchange2010_SP2, Exchange2013, Exchange2013_SP1, Exchange2015
2020/12/01 10:24:11 144 [014] [i] [GetBestExchangeVersion] request highest version in Exchange2007, Exchange2007_SP1, Exchange2010, Exchange2010_SP1, Exchange2010_SP2, Exchange2013, Exchange2013_SP1, Exchange2015
2020/12/01 10:24:11 144 [014] [i] [GetBestExchangeVersion] highest EWS version for XcService@<Customer Domain>: Exchange2015
....
2020/12/01 10:24:11 994 [014] [F] [EWSLOG] msg : Exchange Server doesn't support the requested version.
2020/12/01 10:24:11 994 [014] [F] [EWSLOG] src : ELOxc
2020/12/01 10:24:11 994 [014] [F] [EWSLOG] type: Microsoft.Exchange.WebServices.Data.ServiceVersionException
2020/12/01 10:24:11 994 [014] [e] [LogonService] administrative exchange login failed
Can someone pleeeeezzzz explain to me how an Exchange Server 2016 can reply as an Exchange Server 2015? (Btw. it is the newest CU!)
I've been working with Exchange as an MCT/MCSE for over twenty years and never seen anything like this. Does anyone here have a solution?
Thanks in advance for your support.
Best Regards,
Gerrit