Question

Setting Up Exchange Web Service

Updated October 19, 2020

asked on June 22, 2017

We are trying to setup the Exchange Web Service to connect to our 2016 Exchange server.

The URL we are using is https://mail.domain.com/ews/exchange.asmx

When I test it with my credentials I get the following:

However, if I test my EWS at https://testconnectivity.microsoft.com/ the only error I get about autodiscover is the following:

Attempting to test potential Autodiscover URL https://mviusa.com:443/Autodiscover/Autodiscover.xml

Testing of this potential Autodiscover URL failed.

Additional Details

Elapsed Time: 6066 ms.

That URL should fail since that is pointing to our webhost / website and not our internally hosted Exchange server. Autodiscover seems to work with our Outlook clients, so not sure what I may need to have our Exchange admin look at.

We have also tried using the local DNS name for that server as well as the FQDN for that server. We have tried the following paths with both the Public URL, Internal Friendly Name as well as the FQDN.

/ews/Exchange.asmx
/ews/UM2007Legacy.asmx
/Autodiscover/Autodiscover.xml

Both of the EWS links give the error about finding auto discover whereas the Autodiscover link just times out.

Using the ews urls above we tried to change the Type in the Edit Web Service dialog box from Exchange to Custom. If we leave the User Name as username @domain.com we get 401 unauthorized. However, if we change the login name to Domain\Username the connection tests successfully. The issue there is when the workflow runs we get the following error.

I am sure we are missing something simple. Any help would be appreciated.

0 0

Answer

SELECTED ANSWER

replied on July 11, 2017

You don't have a For Each token on the Subject field, though I don't know if that would be the issue. It would be worth testing by manually entering each field entry in your Create Exchange activity i.e. type in the dates, subject, etc. to check that it's not a token issue or similar.

1 0

Replies

replied on July 9, 2017

Hi Jason,

I'm having the same sort of problem, were you able to resolve this?

Thanks,

Mike

0 0

View 1 previous reply

replied on July 10, 2017

Mike,

Sadly no, this is the response I received from Laserfiche Presales.

Can you confirm that the Autodiscover service is configured correctly on your Exchange server? Please refer to this article (or this article) for more information on how to configure exchange services. Since you are receiving an error when using the test utility (https://testconnectivity.microsoft.com/), it seems like you may be experiencing a security issue within Exchange. Once you are able to successfully connect to Microsoft’s test utility, we can further investigate this issue.

I have attached our test results from our exchange administrator.

Autodiscover 1.PNG (35.21 KB)

| Download

Autodiscover 2.PNG (70.84 KB)

| Download

0 0

replied on July 10, 2017

Hi Jason,

I've been testing based on the same response from LF Support and seem to have found a workaround, although we're on Exchange 2013 so I'm not sure if it will work with 2016. The issue was with the UPN format and I couldn't get consistently successful tests using my email address as username - it would work sometimes, but more often would fail. However, domain\username format worked every time. So I used my account as the "Log On As" account for the Laserfiche Workflow Service, and set the Web Service to "Use default authentication" and it tested/connected successfully. I'm talking with our server admins and will look at using a service account with an Exchange mailbox as the Log On account for the Workflow service as that seems to be the fix.

Hopefully this is helpful in your case.

Cheers,

Mike

0 0

replied on July 10, 2017

Just to confirm, I assume you are using the EWS url correct? https://mail.domain.com/ews/exchange.asmx

0 0

replied on July 10, 2017

Yes, correct.

0 0

replied on July 10, 2017

Here's the result:

0 0

replied on July 10, 2017

So here is my setup. Only difference is Exchange 2016. I am doing everything with my user, and my users calendar so I should have full rights. But now using this setup I am getting 403 forbidden.

nd.

0 0

View 3 previous replies

replied on July 10, 2017

Try with HTTPS, does that make a difference?

0 0

replied on July 11, 2017

It allowed the connection to test successfully. Then when the workflow ran, I got a warning for the Create Exchange Item step.

0 0

SELECTED ANSWER

replied on July 11, 2017

1 0

replied on July 12, 2017

So when I went with Static values it worked. Doing that, I think I found the last issue. My dates didn't have times with them. So once I put all my tokens back in, and this time put a time with the dates. It worked! Thanks for the assistance!

1 0

replied on July 12, 2017

No problem, glad to hear you've got it sorted.

1 0

replied on October 19, 2020

Wow guys. I don't know how you got from an autodiscover service that couldn't be located to simply missing a specified date and time but sure enough this seems to be my problem too. A customer set up this integration and received this error on one of their instances causing confusion. I checked the date and time field and sure enough it was empty, so looks like they have the same issue.

What I don't get is if the autodiscover service requires a date and time, which is perfectly reasonable, why would it say it couldn't be located as if it ran away in terror and is now MIA.

0 0

replied on August 25, 2020

I having the same issues here. I've tried the various URLs, but typically just have the error about not finding the autodiscover service. The service tests properly from the exchange management shell as well as the internal autodiscover test from the outlook client. Microsoft's connectivity test is also fine except the attempt to find autodiscover information at our public website. Is there a better way to connect to exchange. We could really use the ability to create appointments for approved events on a number of forms. I tried a custom type as well but the connection is closed immediately. Is there something specific that Workflow is looking for? Is there a more manual way to configure the connection settings? I'm running Exchange 2019, I've had the same errors on a prior server running Exchange 2016 and now two different workflow servers.

0 0

replied on October 19, 2020 • Show version history

This seems to be an issue with Microsoft's error reporting more than anything. If they always say the autodiscover has gone missing, regardless of the problem, it could be like finding a needle in a haystack. Maybe the Exchange server logs would give you the accurate error.

0 0

You are not allowed to follow up in this post.

Question

Question

Setting Up Exchange Web Service

Answer

Replies

Sign in to reply to this post.