OK, so following up on this issue, which appeared out of the blue this week,
CEICW did not help, nor did a reboot.
I can get TestExchangeConnectivity to spit back either the 401 error in my
first message, or a slightly different one:
Attempting FolderSync command on ActiveSync session
FolderSync command test failed
Exchange ActiveSync returned an HTTP 500 response
I believe HTTP 500 is my true error, however, since I recalled that I had
Integrated authentication checked under Microsoft-Server-ActiveSync, instead
of just Basic. I had it set this way originally because when I first setup
ActiveSync, TestExchangeConnectivity wouldn't pass the important part of the
test without it. It gave me a warning about having Integrated selected, but
passed the important part of the test. That changed this week, so I've no
So, 401 or 500, same difference, it doesn't work now.
"Milhouse Van Houten" <email@example.com> wrote in message
> I'm getting the vexing "A Web Exception occurred because an HTTP 401 -
> Unauthorized response was received from Unknown" from
> TestExchangeConnectivity, despite what I think is all settings being
> I was following an earlier thread here on ActiveSync, when I came across
> this quote from Ace Fekay:
>> Curious, have you been changing the authentication methods in IIS and not
>> the ESM? You should only be using the ESM to change anything like that.
>> it is not available in the ESM, then you use IIS. This is because there
>> is a
>> utility that runs in the background called the DS2Meta function that
>> the the data in AD (the Config Container in AD is where the Exchange
>> it's data), and populates the IIS Metabase.
> Where ARE the equivalent settings in the Exchange from SBS 2003 R2? The
> closest I've found is here:
> And then you see the Exchange Virtual Server items on the right, but most
> anything of relevance in those is grayed out (most particularly,
> ActiveSync's Authentication button is). I don't see how you can avoid
> using IIS to make these changes, but Ace is suggesting that with at least
> some of them, you can.
> Is the "Connect to the Internet" wizard supposed to magically fix this
> error on SBS? I've run it, but not lately. The only other alternative
> from what I've gathered is this, which I very much want to avoid: