Test-OutlookWebServices
Please help me clean up my lab exchange 2007 servers.
not sure where to start i dont have the UM piece configured but having issues wtih free/busy
Id : 1003
Type : Information
Message : About to test AutoDiscover with the e-mail address
[email protected].
: 1007
Type : Information
Message : Testing server labmb01.lab.Local with the published name https://
mail.lab.com/ews/exchange.asmx &
https://exchange.lab.com/EWS/Exc
hange.asmx.
Id : 1019
Type : Information
Message : Found a valid AutoDiscover service connection point. The AutoDiscover
URL on this object is
https://labmb01/Autodiscover/Autodiscover.xml.
Id : 1006
Type : Information
Message : The Autodiscover service was contacted at
https://labmb01/Autodiscover/Autodiscover.xml.
Id : 1013
Type : Error
Message : When contacting https://mail.lab.com/ews/exchange.asmx received the error The remote name could not be resolved: 'mail.lab.com'
Id : 1016
Type : Error
Message : [EXCH]-Error when contacting the AS service at
https://mail.lab.com
/ews/exchange.asmx. The elapsed time was 250 milliseconds.
Id : 1015
Type : Success
Message : [EXCH]-Successfully contacted the OAB service at
https://mail.lab.c
om/ews/exchange.asmx. The elapsed time was 0 milliseconds.
Id : 1004
Type : Error
Message : The certificate for the URL
https://labmb01.lab.local/UnifiedMess
aging/Service.asmx is incorrect. For SSL to work it needs to have a s
ubject of mail.lab.com, instead the subject was labmb01. Consider
correcting service discovery, or installing a correct SSL certificat
e.
Id : 1014
Type : Success
Message : [EXCH]-Successfully contacted the UM service at
https://labmb01.lab
ex.local/UnifiedMessaging/Service.asmx. The elapsed time was 78 milli
seconds.
Id : 1013
Type : Error
Message : When contacting https://exchange.lab.com/EWS/Exchange.asmx received
the error The remote name could not be resolved: 'exchange.lab.com
Id : 1016
Type : Error
Message : [EXPR]-Error when contacting the AS service at
https://exchange.lab
.com/EWS/Exchange.asmx. The elapsed time was 0 milliseconds.
Id : 1015
Type : Information
Message : [EXPR]-The OAB is not configured for this user.
Id : 1014
Type : Information
Message : [EXPR]-The UM is not configured for this user.
Id : 1013
Type : Error
Message : When contacting https://lab.com/Rpc received the error Unable to co
nnect to the remote server
Id : 1013
Type : Error
Message : When contacting https://lab.com/Rpc received the error A connection
attempt failed because the connected party did not properly respond
after a period of time, or established connection failed because conn
ected host has failed to respond 89.150.226.158:443
Id : 1017
Type : Error
Message : [EXPR]-Error when contacting the RPC/HTTP service at
https://lab.co
m/Rpc. The elapsed time was 984 milliseconds.
Id : 1006
Type : Success
Message : The Autodiscover service was tested successfully.
Id : 1021
Type : Information
Message : The following web services generated errors.
As in EXCH
As, in EXPR
Contacting server in EXPR
Please use the prior output to diagnose and correct the errors.
[PS] D:\Program Files\Microsoft\Exchange Server\Scripts>.\new-TestCasConnectivityUser.ps1
Please enter a temporary secure password for creating test users. For security
, the password will be changed regularly and automatically by the system.
Enter password: **********
Update test user permissions on: lab01.lab.Local
Control-Break to quit or Enter to continue:
UserPrincipalName: [email protected]
WARNING: The command completed successfully but no settings of
'lab.Local/Asia/CAS_{4aeaa3cf99664f45}' have been modified.
WARNING: Appropriate ACE is already present on object
"CN=CAS_{4aeaa3cf99664f45},OU=Asia,DC=lab,DC=Local" for account
"lab\Exchange Servers".
Identity User Deny Inherited Rights
lab.Local/Asia/... lab\Exchange Se... False False User-Force-Change-...
WARNING: Appropriate ACE is already present on object
"CN=CAS_{4aeaa3cf99664f45},OU=Asia,DC=lab,DC=Local" for account
"lab\Exchange Recipient Administrators".
lab.Local/Asia/... lab\Exchange Re... False False User-Force-Change-...
ClientAccessServer : lab01.lab.Local
Scenario : Reset Credentials
ScenarioDescription : Reset automated credentials for the Client Access test
user on Mailbox server lab01.lab.Local.
PerformanceCounterName :
Result : Failure
MailboxServer : lab01.lab.Local
StartTime : 3/9/2014 6:08:34 PM
Latency : 00:00:00.0156251
SecureAccess : True
Error : [Microsoft.Exchange.Monitoring.CasHealthStorageErrorEx
ception]: An error occurred while trying to access ma
ilbox lab01.lab.Local on behalf of user lab.Lo
cal\CAS_4aeaa3cf99664f45
Additional information:
[Microsoft.Exchange.Data.Storage.ConnectionFailedTran
sientException]: Cannot open mailbox /o=lab/ou=Excha
nge Administrative Group (FYDIBOHF23SPDLT)/cn=Recipien
ts/cn=CAS_{4aeaa3cf99664f45}.
UserName : CAS_4aeaa3cf99664f45
VirtualDirectoryName :
Url :
UrlType : Unknown
EventType : Error
Port : 0
ConnectionType : Plaintext
You can um-enable the test user by running this command with the following optio
nal parameters : [-UMDialPlan <dialplanname> -UMExtension <numDigitsInDialplan>]
.Either None or Both must be present.
[PS] D:\Program Files\Microsoft\Exchange Server\Scripts>Test-OutlookWebServices
Id
Type Message
1003 Information About to test AutoDisc...
1007 Information Testing server labmb...
1019 Information Found a valid AutoDisc...
1006 Information The Autodiscover servi...
1013
Error When contacting https:...
1016
Error [EXCH]-Error when cont...
1015 Success [EXCH]-Successfully
co...
1004
Error The certificate for th...
1014 Success [EXCH]-Successfully
co...
1013
Error When contacting https:...
1016
Error [EXPR]-Error when cont...
1015 Success [EXPR]-Successfully
co...
1014 Information [EXPR]-The UM is not c...
1013
Error When contacting https:...
1013
Error When contacting https:...
1017
Error [EXPR]-Error when cont...
1006 Success The
Autodiscover servi...
1021 Information The following web serv...
[PS] D:\Program Files\Microsoft\Exchange Server\Scripts>Test-WebServicesConnecti
vity
CasServer MailboxServer Scenario Result Latency(MS) Error
lab01 labCCR1 Reset Credentia Failure [Microsoft.Exchang
ls
e.Monitoring.CasHe
althStorageErrorEx
ception]: An error
occurred while tr
ying to access ma
ilbox labCCR1.La
bex.Local on behal
f of user lab.Lo
cal\CAS_0ad0507446
ef41e4
Additional inform
ation:
[Microsoft.Exchan
ge.Data.Storage.Co
nnectionFailedTran
sientException]: C
annot open mailbox
/o=lab/ou=Excha
nge Administrative
Group (FYDIBOHF23
SPDLT)/cn=Recipien
ts/cn=CAS_{0ad0507
446ef41e4}.
lab01 lab01 Reset Credentia Failure [Microsoft.Exchang
ls
e.Monitoring.CasHe
althStorageErrorEx
ception]: An error
occurred while tr
ying to access ma
ilbox lab01.La
bex.Local on behal
f of user lab.Lo
cal\CAS_4aeaa3cf99
664f45
Additional inform
ation:
[Microsoft.Exchan
ge.Data.Storage.Co
nnectionFailedTran
sientException]: C
annot open mailbox
/o=lab/ou=Excha
nge Administrative
Group (FYDIBOHF23
SPDLT)/cn=Recipien
ts/cn=CAS_{4aeaa3c
f99664f45}.
WARNING: Test user 'CAS_479c57ec434e458f' cannot be accessed. Therefore, this cmdlet will be unable to test Mailbox server 'labS.lab.Local'.
Test-WebServicesConnectivity : Could not find or log on with user lab.Local\CAS_479c57ec434e458f. If this task is being run without credentials, log on as a
Domain Administrator, and then run the new-TestCasConnectivityUser.ps1 to verify that the user exists on Mailbox server labS.lab.Local
At line:1 char:28
+ Test-WebServicesConnectivity <<<<
WARNING: Test user 'CAS_06e52accae044649' cannot be accessed. Therefore, this cmdlet will be unable to test Mailbox server 'labscc1.lab.Local'.
Test-WebServicesConnectivity : Could not find or log on with user lab.Local\CAS_06e52accae044649. If this task is being run without credentials, log on as a
Domain Administrator, and then run the new-TestCasConnectivityUser.ps1 to verify that the user exists on Mailbox server labscc1.lab.Local
At line:1 char:28
+ Test-WebServicesConnectivity <<<<
WARNING: No Client Access servers were tested.
Similar Messages
-
[PS] C:\>Test-OutlookWebServices | fl
When I am running above command getting below error for External url and internally it showing sucess
Please suggest is this default behaviour
Id : 1015
Type : Success
Message : [EXCH]-Successfully contacted the OAB service at https://gux02.as
ian.ad.zen.com/EWS/Exchange.asmx. The elapsed time was 0 millisec
onds.
Id : 1013
Type : Error
Message : When contacting https://legacy.zen.com/EWS/Exchange.asmx received
the error The request failed with HTTP status 401: Unauthorized.
Id : 1016
Type : Error
Message : [EXPR]-Error when contacting the AS service at https://legacy.zen
.com/EWS/Exchange.asmx. The elapsed time was 15 milliseconds.
Id : 1016
Type : Error
Message : [EXPR]-Error when contacting the AS service at https://legacy.zen
.com/EWS/Exchange.asmx. The elapsed time was 15 milliseconds.
Id : 1013
Type : Error
Message : When contacting https://inowa.zen.com/Rpc received the error The
remote server returned an error: (404) Not Found.
Id : 1017
Type : Error
Message : [EXPR]-Error when contacting the RPC/HTTP service at https://inowa.zen.com/Rpc. The elapsed time was 31 milliseconds.The thing to note is that this is really a 'benign' error message because every Outlook client will default to https://mydomain.com/Autodiscover/Autodiscover.xml and then to https://autodiscover.mydomain.com/Autodiscover/Autodiscover.xml
-> which will succeed if you have a properly configured Exchange server running a UCC SSL certificate. The 'Error 1104' comes from an 'improper' test where it goes on to test https://server.internaldomain.local/Autodiscover/Autodiscover.xml. This
test should never even be made (in my opinion) and isn't made by Exchange servers when running Test-OutlookWebServices.
If you are keen on that you could check this and set as default setting on EWS/RPC virtual directories. Else you can ignore http://blogs.technet.com/b/exchange/archive/2010/09/23/3411146.aspx
But I didn't see this error on a newly installed exchange.
Thanks, MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. -
Test-outlookwebservices and test-webservicesconnectivity fail
Hi all,
I am running Exchange 2010 SP3 in a lab environment. I was working on the different virtual directories to change the different URLs, I then deployed a SAN certificate from my AD certification authority.
for the URLs, I used "autodiscover.mycompany.com.tn" for the AutodiscoverServiceInternalUri and mail.mycompany.com.tn for the other virtual directories (OWA, OAB, EWS, AS and ECP). both names are included in the certificate.
I encountered no certificate errors for outlook or OWA, but when running outlook web services test and web services connectivity tests, I get errors related to certificate issues
Here's the output of test-outlookwebservices. As you can see, autodiscover and EWS use both the name that I configured and the server FQDN which is not included in the certifcate and thus the errors. any reasons why it would still look for the server FQDN?
RunspaceId : 20250c8e-6c6a-483e-ae13-e65c2da4b13f
Id : 1019
Type : Information
Message : A valid Autodiscover service connection point was found. The Autodiscover URL on this object is https://au
todiscover.mycompany.com.tn/Autodiscover/Autodiscover.xml.
RunspaceId : 20250c8e-6c6a-483e-ae13-e65c2da4b13f
Id : 1006
Type : Information
Message : Contacted the Autodiscover service at https://autodiscover.mycompany.com.tn/Autodiscover/Autodiscover.xml.
RunspaceId : 20250c8e-6c6a-483e-ae13-e65c2da4b13f
Id : 1016
Type : Information
Message : [EXCH] The AS service is configured for this user in the Autodiscover response received from https://autod
iscover.mycompany.com.tn/Autodiscover/Autodiscover.xml.
RunspaceId : 20250c8e-6c6a-483e-ae13-e65c2da4b13f
Id : 1015
Type : Information
Message : [EXCH] The OAB service is configured for this user in the Autodiscover response received from https://auto
discover.mycompany.com.tn/Autodiscover/Autodiscover.xml.
RunspaceId : 20250c8e-6c6a-483e-ae13-e65c2da4b13f
Id : 1014
Type : Information
Message : [EXCH] The UM service is configured for this user in the Autodiscover response received from https://autod
iscover.mycompany.com.tn/Autodiscover/Autodiscover.xml.
RunspaceId : 20250c8e-6c6a-483e-ae13-e65c2da4b13f
Id : 1022
Type : Success
Message : Autodiscover was tested successfully.
RunspaceId : 20250c8e-6c6a-483e-ae13-e65c2da4b13f
Id : 1113
Type : Error
Message : When contacting https://EXCH2010.MyCompany.local:443/Autodiscover/Autodiscover.xml received the error The
underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.
RunspaceId : 20250c8e-6c6a-483e-ae13-e65c2da4b13f
Id : 1113
Type : Error
Message : When contacting https://EXCH2010.MyCompany.local:443/Autodiscover/Autodiscover.xml received the error The
remote certificate is invalid according to the validation procedure.
RunspaceId : 20250c8e-6c6a-483e-ae13-e65c2da4b13f
Id : 1123
Type : Error
Message : The Autodiscover service couldn't be contacted.
RunspaceId : 20250c8e-6c6a-483e-ae13-e65c2da4b13f
Id : 1024
Type : Success
Message : [EXCH] Successfully contacted the AS service at https://mail.mycompany.com.tn/EWS/Exchange.asmx. The elaps
ed time was 46 milliseconds.
RunspaceId : 20250c8e-6c6a-483e-ae13-e65c2da4b13f
Id : 1026
Type : Success
Message : [EXCH] Successfully contacted the UM service at https://mail.mycompany.com.tn/EWS/Exchange.asmx. The elaps
ed time was 15 milliseconds.
RunspaceId : 20250c8e-6c6a-483e-ae13-e65c2da4b13f
Id : 1113
Type : Error
Message : When contacting https://exch2010.mycompany.local/ews/exchange.asmx received the error The underlying conne
ction was closed: Could not establish trust relationship for the SSL/TLS secure channel.
RunspaceId : 20250c8e-6c6a-483e-ae13-e65c2da4b13f
Id : 1113
Type : Error
Message : When contacting https://exch2010.mycompany.local/ews/exchange.asmx received the error The remote certifica
te is invalid according to the validation procedure.
RunspaceId : 20250c8e-6c6a-483e-ae13-e65c2da4b13f
Id : 1125
Type : Error
Message : [Server] Error contacting the AS service at https://exch2010.mycompany.local/ews/exchange.asmx. Elapsed ti
me was 0 milliseconds.
RunspaceId : 20250c8e-6c6a-483e-ae13-e65c2da4b13f
Id : 1113
Type : Error
Message : When contacting https://exch2010.mycompany.local/ews/exchange.asmx received the error The underlying conne
ction was closed: Could not establish trust relationship for the SSL/TLS secure channel.
RunspaceId : 20250c8e-6c6a-483e-ae13-e65c2da4b13f
Id : 1113
Type : Error
Message : When contacting https://exch2010.mycompany.local/ews/exchange.asmx received the error The remote certifica
te is invalid according to the validation procedure.
RunspaceId : 20250c8e-6c6a-483e-ae13-e65c2da4b13f
Id : 1127
Type : Error
Message : [Server] Error contacting the UM service at https://exch2010.mycompany.local/ews/exchange.asmx. Elapsed ti
me was 0 milliseconds.
Thanks.From the original post everything in Outlook and OWA is working - correct?
You only get issues with the test-* cmdlets? That is most likely as your custom certificates do not have the server FQDN contained as SAN entry. The test-* cmdlets expect that.
So add the ignore SSL check parameters to your commands. For example
Test-OwaConnectivity -TrustAnySSLCertificate
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter: LinkedIn:
Facebook:
XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose. -
Bindings in IIS on Exchange 2010 causing Test-outlookwebservices to fail on Autodiscover
Exchange 2010 is coexisting with Sharepoint 2013 Foundation.
Exchange 2010 have 2 internal IP's (1 for Exchange and 1 for Sharepoint).
Under IIS we had set up binding on port 443 to 1st IP, and second IP was used to bind it to 80 port for SharePoint. That kind of configuration gave as an error for: outlookwebservices, for Autodiscover, which is logical because both IP's have an A record
which points to servername.domain.com.
This are our configuration for EWS internal/external URL's and AUTODISCOVER internal/external URL'S:
EWS URL's
InternalUrl :
https://mail.domain.com/ews/exchange.asmx
ExternalUrl :
https://mail.domain.com/ews/exchange.asmx
AUTODISCOVER URL's
InternalUrl :
https://mail.domain.com/autodiscover/autodiscover.xml
ExternalUrl :
https://mail.domain.com/autodiscover/autodiscover.xml
This are the error messages for: Test-outlookwebservices
RunspaceId : 5ee30248-5bec-436f-808a-c56180a8a6d9
Id : 1113
Type : Error
Message : When contacting
https://SRVNAME.domain.com:443/autodiscover/autodiscover.xml received the error Unable to
read data from the transport connection: An existing connection was forcibly closed by the remote host.
RunspaceId : 5ee30248-5bec-436f-808a-c56180a8a6d9
Id : 1113
Type : Error
Message : When contacting
https://SRVNAME.domain.com:443/autodiscover/autodiscover.xml received the error An existi
ng connection was forcibly closed by the remote host
The "workaround" solution, because Sharepoint only goes thru PORT 80 on this server was chosing bindings 443 to all the ips (then Test-Outlookwebservices goes thru), but doing that we are unable to use anything else on port 443 on that server in
the future.
I was wondering if changing InternalNLBBypassUrl in our scenario would be a possible workaround or there would be no effect on this scenario?
Set-WebServicesVirtualDirectory -Identity "Contoso\EWS*" -InternalNLBBypassUrl
https://mail.domain.com/ews/exchange.asmx
With best regards,
bostjancHi Bostjan,
This was working fine before, Is it the first time we are facing the problem.
Make sure that all the exchange services are started.
Did you select the proper certificate at the Organization level and check the permission settings.
For the Autodiscover, please access
https://localhost/Autodiscover/Autodiscover.xml on the CAS. The 600 error code will be displayed.
Try to find the Error by running the Below cmdlets.
Get-ExchangeCertificate | FL
Get-WebServicesVirtualDirectory –Server ServerName | FL
Get-AutodiscoverVirtualDirectory –Server ServerName | FL
Get-ClientAccessServer
| FL
Than press Ctrl+right click the Outlook icon in the System Tray, select Test E-mail AutoConfiguration, uncheck Use Guessmart and Secure Guessmart Authentication, click Test button.
If found the problem is related to web services and basic authentication than try with the below cmdlet and the
Link
Set-WebServicesVirtualDirectory -identity "BOXEDUC-EXC1\EWS (Default Web Site)" -externalurl https://mail.domain.com/ews/exchange.asmx -internalurl https://mail.domain.com/ews/exchange.asmx -BasicAuthentication:$True
Mark as Answer/Helpful Post if it helps
Regards.
Naren Neelam, Messaging Consultant, ITBigBang (P) Ltd Www.ITBigBang.Com | Hire Us for Messaging Consulting -
With Exchange 2013 shell when executing "Test-OutlookWebServices" I have to supply the -MailboxCredential parameter in order for the "Autodiscover: Outlook Provider" to return success. E.g.
Test-OutlookWebServices -clientaccessserver ex2013 -identity [email protected] -MailboxCredential (get-credential test\asenna)
If I change the MailboxCredential to an that of an Exchange Administrator then the "Autodiscover: Outlook Provider" will return Failure.
Running the command on an Exchange 2010 server for a 2010 mailbox does not require the MailboxCredential parameter and always succeeds.
Why the change for 2013?
AlanHi,
Based on my experience, it will be more efficient to test web services by directly accessing their urls via IE.
Thanks,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support -
Test-outlookwebservices source MBX Server Query
I have 3 MBX servers, one server has an issue with web services so to do some testing I mount a mailbox database on the affected server with a new test mailbox
[email protected] on affected server SERVER3
if I run the cmdlet test-outlookwebservices -identity:[email protected] -mailboxcredential (getcredential) is see the source as SERVER3 with autodiscover test FAILED as expected
now if I run the command again the source has changed to mailbox server SERVER2 (which works) and the Availibility Service FAILS autodiscover and EWS works
Why/How does it change is the user mailbox/ mailbox database that
[email protected] is in is mounted on SERVER3?
***Don't forget to mark helpful or answer***Hi,
According to your description, I understand that you get different source when run same command to test outlook web service.
If I misunderstand your concern, please do not hesitate to let me know.
I suspect that the server which are you used to run this command is different. Basis on my test, when I run this command in Exch5-cu1 (mailbox server), the source is Exch5-cu1.cu1.com and vice versa.
For your question, it indicate that Server3 cannot connect to autodiscover services. Server2 can connect to autodiscover services, however cannot return the free/busy information from CAS server. Running the cmdlet on a Client Access server will test the
local server using the test mailbox user created earlier, you can also perform the test for a specific mailbox by using the –Identity and –MailboxCredential parameters.
Note: Testing a specific mailbox is useful if you are troubleshooting problems with one or more of the Outlook Web Services in a particular site within your organization. You can compare results between test mailboxes in different sites to help you narrow down
the source of any problems you’re seeing.
Additional, please refer to below link to get more details about Troublshooting Autodiscover:
http://blogs.technet.com/b/exchdxb/archive/2012/05/10/troublshooting-autodiscover-exchange-2007-2010.aspx
Best Regards,
Allen Wang
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Allen Wang
TechNet Community Support -
Receiving Below error every now and than in our Exchange Server production environment,
Exchange Server: 2010 SP3
Server OS: Windows server 2008 R2
Role Holder: CAS/HT
Log Error:
Log Name: MSExchange Management
Source: MSExchange CmdletLogs
Date: 20-12-2013 18:59:10
Event ID: 6
Task Category: General
Level: Error
Keywords: Classic
User: N/A
Computer: EXCHHTCAS2.test.local
Description:
Cmdlet failed. Cmdlet Test-OutlookConnectivity, parameters {Protocol=TCP, TrustAnySslCert=True, MonitoringContext=True}.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MSExchange CmdletLogs" />
<EventID Qualifiers="49152">6</EventID>
<Level>2</Level>
<Task>1</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-12-20T13:29:10.000000000Z" />
<EventRecordID>267940</EventRecordID>
<Channel>MSExchange Management</Channel>
<Computer>EXCHHTCAS2.test.local</Computer>
<Security />
</System>
<EventData>
<Data>Test-OutlookConnectivity</Data>
<Data>{Protocol=TCP, TrustAnySslCert=True, MonitoringContext=True}</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>Exchange Management Console-Local</Data>
<Data>7132</Data>
<Data>
</Data>
<Data>240</Data>
<Data>00:00:00.0624984</Data>
<Data>View Entire Forest: 'False', Default Scope: 'test.local', Configuration Domain Controller: 'HINJEWADI.test.local', Preferred Global Catalog: 'HINJEWADI.test.local', Preferred Domain Controllers: '{ HINJEWADI.test.local }'</Data>
<Data>Microsoft.Exchange.Monitoring.MailboxNotFoundException: Failed to find the mailbox. Mailbox = '[email protected]'.
at Microsoft.Exchange.Monitoring.TestOutlookConnectivityTask.GetDefaultTestAccount(ClientAccessContext context, MailboxIdParameter& mailboxId)
at Microsoft.Exchange.Monitoring.TestOutlookConnectivityTask.GetTestMailbox()
at Microsoft.Exchange.Monitoring.TestOutlookConnectivityTask.get_Identity()
at Microsoft.Exchange.Monitoring.TestOutlookConnectivityTask.InternalValidate()</Data>
<Data>14</Data>
<Data>
</Data>
</EventData>
</Event>
We have also checked no task scheduler or such job is enabled, still within in few hours we get MSExchange CmdletLogs with error code 6.
While running Best Practices Analyzer:
We were earlier using Exchange 2003 environment, its been few months we have migrated to Exchange 2010 SP3, we have removed all the older version application successfully after proper migration of the database and other files, still our production server
shows us with the FrontEnd Server error which in reality does not exists in our environment.
We are seeking some guidance as Googlin isn't kicking us anywhere.
If any further logs required please inform, as i am not able to attach images right now.
Regards,
Gyan MainaliSonny, sorry i couldn't reply you back then..
Ok problem was very simple...
Issue: Test-OutlookConnectivity not working
Answer: extest_something is the user id that's present in AD, same was removed., so we used the Test-OutlookConnectivity we got and option to re-register new extest_ id.
Done., no errors now. -
AutoDiscover is a new feature in Exchange 2007, to provide access to Microsoft Exchange features (OAB, Availability service, UM) for Outlook 2007
clients or later.
We can determine whether problems related to AutoDiscover via OWA.
For example:
OOF is not working in Outlook Client but it is working in OWA.
When we realized this issue is not related to Outlook Client side and network side after performing some troubleshooting steps, it should be something
abnormal on AutoDiscover.
There is a common tool to check AutoDiscover in Outlook, Test E-mail AutoConfiguration.
Today, we will introduce AutoDisocver and “Test E-mail AutoConfiguration” in details. Hope it is helpful for AutoDiscover troubleshooting and self-learning.
1. Differences between “Test E-mail AutoConfiguration” and other tools
The “Test-OutlookWebServices” cmdlet allows us to test the functionality of the following services:
Autodisocver
Exchange Web Services
Availability Service
Offline Address Book
When we run “Test-OutlookWebServices”, it returns all the web services’ states.
However, some information are useless for some scenarios.
For example:
We just want our Exchange 2010 Server working internally. So it is unnecessary to enable Outlook Anywhere.
However, when we run “Test-OutlookWebServices”, it returns Outlook Anywhere errors because the Outlook Anywhere does not need to been enabled.
In contrast, using “Test E-mail Autodiscover” is more intuitive.
If there is any problems, it will return error code from the test result, like 0x8004010F etc. We can do some research from TechNet articles or MS
KBs.
Although it is difficult to say where the specific problem is just via the error codes, we can combine with IIS logs to perform troubleshooting and
find the root of problem.
2. How to use “Test E-mail AutoConfiguration” Tool
a. Open Outlook, we can find there is an Outlook Icon at the right bottom of System tray. Holding down “Ctrl” button and right click the Outlook Icon, we will see “Test E-mail
AutoConfiguration” option. Please see Figure 01.
Figure 01
b. Click “Test E-mail AutoCofiguration” and input user name, uncheck the “Use Guessmart” and “Secure Guessmart Authentication” checkboxes, then click “Test”. Please see
Figure 02.
Figure 02
c. “Test E-mail AutoConfiguration” result panel and log panel. Please see Figure 03 and Figure 04.
Figure 03
Figure 04
3. How to understand “Test E-mail AutoConfiguration” result
According to the Figure 03, we found there are many URLs in the “Test E-mail AutoConfiguration” result panel. Let us understand the details of these
URLs.
If we these URLs are not the correct ones, we can re-setting or re-creating them via commands.
- Internal OWA URL:
https://vamwan310.vamwan.com/owa/
OWA internal access.
- External OWA URL:
https://mail.vamwan.com/owa/
OWA external access.
- Availability service URL:
https://vamwan310.vamwan.com/EWS/Exchange.asmx
Free/Busy, OOF and meeting suggestions.
- OOF URL:
https://vamwan310.vamwan.com/EWS/Exchange.asmx
Out of Office access.
- OAB URL:
https://vamwan310.vamwan.com/OAB/023ef307-b18a-4911-a52c-de26700f6173/
OAB access.
- Exchange Control Panel URL:
https://vamwan310.vamwan.com/ecp/
ECP access.
4. AutoDiscover Tips
- AutoDiscover Service itself is a web application running on the AutoDiscover virtual directory (not a server service) designed to provide connection information to various
clients.
- The AutoDiscover service is automatically installed and configured when CAS role is added to any Exchange Server.
- AutoDisocver virtual directory is created in IIS within the Default Web Site.
- A Sercive-Connection-Point (SCP) object is created in AD.
- The SCP contains a URL to the AutoDiscover service. This is for intranet clients so they do not have to use DNS to locate the AutoDiscover service.
- In AD this object is located at the following location:
DC=<domain>, CN=Configuration, CN=Services, CN=Microsoft Exchange, CN=First Organization, CN=Administrative Groups, CN=Exchange Administrative
Group, CN=Servers, CN=<CAS Name>, CN=Protocols, CN=AutoDiscover, CN=<CAS Name>
- Setup creates the AutoDiscover URL based on the following structure:
<CASNetbiosName>.domain.com/AutoDiscover/AutoDiscover.xml
If a PKI certificate is not already present, a self-signed certificate is installed on the Default Web Site.
To help allow this certificate pass the Issues to test it is set up with a Subject Alternative Name containing urls.
If a PKI certificate is present, that certificate is utilized and configured for use in IIS.
The Outlook Provider is used to configure separate settings for the Exchange PRC protocol (internal to network), Outlook Anywhere (Exchange HTTP protocol), and WEB:
EXCH, EXPR, WEB
The
EXCH and EXPR setting are vital for the proper configuration of Outlook.
5. AutoDiscover Workflow
General Process flow:
There are various components surrounding the AutoDiscover Service and all are necessary to complete a request. Including IIS, AutoDiscover service
itself, the provider, and AD.
a.
Client constructs service URL and submits Autodiscover Request. First attempt to locate the SCP object in AD. So, DNS is not needed.
b.
IIS Authenticates User.
c.
Is the Autodiscover service in the appropriate forest?
+ If YES.
1)
Parse/Validate Request
2)
Is there a provider that can service the Request?
++ If YES
a)
Config provider processes request and returns config settings.
b)
Return config setting to client
++ If NO
Inform client we cannot process request
+ If NO.
Redirect client to Autodiscover service in the appropriate forest.
Methods to find Autodiscover services: SCP and DNS
Domain-joined
a. Find SCP first.
The SCP contains the URL to the AutoDiscover service.
URL: https://CAS01.contoso.com(CAS’ FQDN)/AutoDiscover/AutoDiscover.xml
If more than one SCP object is found in AD (it means there are multiple CAS servers in the Exchange organization), Outlook client will choose one of the SCP entries that
are in the same site to obtain the AutoDisocover URL.
b. If we cannot find SCP object, then Outlook client will use DNS to locate AutoDiscover.
Outlook parses out the domain (SMTP suffix) via your EmaiAddress, then attempts to connect to the predetermined order of URLs via the suffix.
For example: If my email address is
[email protected]
Outlook tries POST commands to the following order of URLs:
https://contoso.com/autodiscover/autodiscover.xml
https://autodiscover.contoso.com/autodiscover/autodiscover.xml
NOTE: The URLs above is by design, hardcode
and cannot be changed.
c.
If those fail, Outlook tries a simple redirect to another URLs in IIS:
http://contoso.com/autodiscover/autodiscover.xml
http://autodiscover.contoso.com/autodiscover/autodiscover.xml
If none of these URLs work then DNS is most likely not set up correctly.
We can test that by pinging one of the above URLs.
If that is successful, we must ensure the URLs contoso.com or autodiscover.contoso.com are actually pointing to the CAS server.
If the ping fails then there is a chance that DNS is not set up correctly so be sure to check that the URLs are even registered.
NOTE: If contoso.com is a non-CAS server,
we should add a Host record with just AutoDiscover. And point that entry to your CAS server that is running AutoDiscover.
d.
If still failed, we can use DNS SRV lookup for _autodiscover._tcp.contoso.com, then “CAS01.contoso.com” returned. Outlook will ask permission from the user to continue
with AutoDiscover to post to https://CAS01.contoso.com/autodiscover/autodiscover.xml
Non-Domain-joined
It first tries to locate the Autodiscover service by looking up the SCP object in AD. However the client is unable to contact AD, it tries to locate
the Autodiscover service by using DNS.
Then, same as step b, c, d in
Domain-joined scenario.
6. How to change the AutoDiscover
service location order forcibly?
By default, Outlook client locates AutoDiscover service in that order above.
We can also change the order forcibly.
a.
If we want to locate AutoDiscover service via one of the autodiscover URLs, please running following command in EMS:
Set-ClientAccessServer -identity <servername> -AutodiscoverServiceInternalUri https://autodiscover.contoso.com/autodiscover/autodiscover.xml(URL
that you want)
b. If we want to locate AutoDiscover service via
SRV record, please follows this KB to set up SRV:
http://support.microsoft.com/kb/940881
7. How to check AutoDiscover Healthy
a. We should make sure the AutoDiscover
is healthy before using AutoDiscover to perform troubleshooting.
b.
We can browse following URL in IE explorer:
https://autodiscover.vamwan.com/autodiscover/autodiscover.xml
If it returns “code 600”, that means AutoDiscover is healthy.
Screenshot as below:
c. AutoDiscover itself returns errors to the requesting client if the incoming request does not contain the appropriate information to complete a
request.
The following table explains the possible errors that could be returned.
Error Value
Description
600
Mailbox not found and a referral could not be generated.
601
Address supplied is not a mailbox. The provided email address is not something a client can connect to. It could
be a group or public folder.
602
Active Directory error.
603
Others.
The 600 “Invalid Request” error is returned because a user name was not passed to the service. That is OK for this test because this does confirm
the service is running and accepting requests.
d.
If AutoDiscover service is not working well, I suggest re-building the AutoDiscover Virtual Directory for testing.
Steps as below:
1) Running following command in EMS to remove the AutoDiscover VD (we cannot delete it via EMC):
Remove-AutodiscoverVirtualDirectory -Identity "CAS01\autodiscover(autodiscover.contoso.com)"
Please refer:
http://technet.microsoft.com/en-us/library/bb124113(v=exchg.141).aspx
2)
Running following command in EMS to verify whether we have removed the AutoDisocver VD successfully:
Get-AutodiscoverVirtualDirectory | FL
Please refer:
http://technet.microsoft.com/en-us/library/aa996819(v=exchg.141).aspx
3)
Running following command in EMS to re-creating a new AutoDiscover VD:
New-AutodiscoverVirtualDirectory -Websitename <websitename> -BasicAuthentication:$true -WindowsAuthentication:$true
Please refer:
http://technet.microsoft.com/en-us/library/aa996418(v=exchg.141).aspx
8. Common issues
a. Outlook Disconnection
Issue and Troubleshooting
Issue:
Sometimes the Outlook clients cannot connect to the Exchange server after migrating to a new Exchange server or changing to new CAS. The Outlook clients
always connect to the old CAS server.
Troubleshooting:
To solve this issue, we should change the SCP via following command:
Set-ClientAccessServer -Identity
<var>CAS_Server_Name</var> -AutodiscoverServiceInternalUri
https://mail.contoso.com(newCAS’FQDN)/autodiscover/autodiscover.xml
b. Autodiscover
Certificate issue
Tips on Certificate:
Exchange requires a certificate to run an SSL protocol such as HTTPS. We can use the certificate that supports subject alternate names (SAN) in Exchange.
This is to allow the certificate to support resources that have different names, such as Outlook Anywhere and the Autodisocver Web application.
Issue and Troubleshooting
Issue:
We receiver the Certificate Principal Mismatch error when we use a SAN certificate.
Troubleshooting:
1) Please determine the FQDN that the client
uses to access the resource. Steps as below:
OutlookàToolsàAccount
SettingsàE-mailàclick
the Exchange accountàChangeàMore
SettingsàConnectionàExchange
Proxy Settingsànote the FQND that list in the
Only connect to proxy servers that have this principal name in their certificate box.
2)
Please using EMS to determine the value for the CerPrincipalName attribute: Get-OutlookProvider
This command returns the result for the EXPR name.
3)
Please re-setting the CertPrincipalName attribute to match the FQDN via following command:
Set-OutlookProvider EXPR –CertPrincipalName: “msstd:<FQDN the certificate is issued to>”
9. Resource for reference:
Autodiscover and Exchange 2007
http://technet.microsoft.com/en-us/library/bb232838(v=exchg.80).aspx
White Paper: Understanding the Exchange 2010 Autodiscover Service
http://technet.microsoft.com/en-us/library/jj591328(v=exchg.141).aspx
Certificate Principal Mismatch
http://technet.microsoft.com/en-us/library/aa998424(v=exchg.80).aspx
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.HI,
I get following? when run the test? user is login to Domain A but accessing exchange in Domain B? -
Test E-mail AutoConfiguration error!
Environment
Exchange 2010 SP2 RU5 with Outlook 2010 clients.
Issue:
One user is having an issue accessing Free\Busy. After briefly looking into the issue it was discovered that the autodiscover was not working via the Test E-mail AutoConfiguration. The specific error is:
Autoconfiguration has started, this may take up to a minute
Autoconfiguration was unable to determine your settings
Once this error was found a thorough investigation of our autodiscover configuration along with our CAS server settings was underway. Everything checks out and everything is working fine for everyone across the org. Its just this one PC.
Have reviewed\tested\or changed the following:
registry keys (lots of info about office 365 and the registry settings that can in some cases disable the clients autodiscover via the 1). We do not use office 365, but I looked into it.
patches
re-created profile
repaired office
confirmed and DNS is correct
disabled IPV6
OWA does work and they CAN view Free\Busy without issue!
new profiles for other employees on their PC fail also. But she can get a new profile on any other PC and it works fine, so we know it is specific to her PC.
can access the autodiscover XML page found https://autodiscover.domain.com/autodiscover/autodiscover.xml
disabled cache mode
disabled firewall
enabled debug mode in Outlook
certificate
The other error reads as follows when setting up a new profile for them:
The action cannot be completed. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action.
Definitely autodiscover related, but locally. Any thoughts or ideas out there for this?
Thanks,
BlindHere are the results from the test-outlookwebservices |fl
Thanks again for any direction you can provide. This has made my top 5 issues of the year award lol.
RunspaceId : 03d92840-abbf-45ec-b714-753970e9dc34
Id : 1019
Type : Information
Message : A valid Autodiscover service connection point was found. The Autodiscover URL on this object is https://ourCASserver.domain.corp/Auto
discover/Autodiscover.xml.
RunspaceId : 03d92840-abbf-45ec-b714-753970e9dc34
Id : 1006
Type : Information
Message : Contacted the Autodiscover service at https://ourCASserver.domain.corp/Autodiscover/Autodiscover.xml.
RunspaceId : 03d92840-abbf-45ec-b714-753970e9dc34
Id : 1016
Type : Information
Message : [EXCH] The AS service is configured for this user in the Autodiscover response received from https://ourCASserver.domain.corp/Autodis
cover/Autodiscover.xml.
RunspaceId : 03d92840-abbf-45ec-b714-753970e9dc34
Id : 1015
Type : Information
Message : [EXCH] The OAB service is configured for this user in the Autodiscover response received from https://ourCASserver.domain.corp/Autodi
scover/Autodiscover.xml.
RunspaceId : 03d92840-abbf-45ec-b714-753970e9dc34
Id : 1014
Type : Information
Message : [EXCH] The UM service is configured for this user in the Autodiscover response received from https://ourCASserver.domain.corp/Autodis
cover/Autodiscover.xml.
RunspaceId : 03d92840-abbf-45ec-b714-753970e9dc34
Id : 1016
Type : Information
Message : [EXPR] The AS service is configured for this user in the Autodiscover response received from https://ourCASserver.domain.corp/Autodis
cover/Autodiscover.xml.
RunspaceId : 03d92840-abbf-45ec-b714-753970e9dc34
Id : 1015
Type : Information
Message : [EXPR] The OAB service is configured for this user in the Autodiscover response received from https://ourCASserver.domain.corp/Autodi
scover/Autodiscover.xml.
RunspaceId : 03d92840-abbf-45ec-b714-753970e9dc34
Id : 1014
Type : Information
Message : [EXPR] The UM service is configured for this user in the Autodiscover response received from https://ourCASserver.domain.corp/Autodis
cover/Autodiscover.xml.
RunspaceId : 03d92840-abbf-45ec-b714-753970e9dc34
Id : 1022
Type : Success
Message : Autodiscover was tested successfully.
RunspaceId : 03d92840-abbf-45ec-b714-753970e9dc34
Id : 1024
Type : Success
Message : [EXCH] Successfully contacted the AS service at https://ourCASserver.domain.corp/EWS/Exchange.asmx. The elapsed time was 336 millisec
onds.
RunspaceId : 03d92840-abbf-45ec-b714-753970e9dc34
Id : 1026
Type : Success
Message : [EXCH] Successfully contacted the UM service at https://ourCASserver.domain.corp/EWS/Exchange.asmx. The elapsed time was 15 milliseco
nds.
RunspaceId : 03d92840-abbf-45ec-b714-753970e9dc34
Id : 1024
Type : Success
Message : [EXPR] Successfully contacted the AS service at https://mail.domain.com/ews/exchange.asmx. The elapsed time was 46 millisecon
ds.
RunspaceId : 03d92840-abbf-45ec-b714-753970e9dc34
Id : 1026
Type : Success
Message : [EXPR] Successfully contacted the UM service at https://mail.domain.com/ews/exchange.asmx. The elapsed time was 62 millisecon
ds.
RunspaceId : 03d92840-abbf-45ec-b714-753970e9dc34
Id : 1124
Type : Success
Message : [Server] Successfully contacted the AS service at https://ourCASserver.domain.corp/ews/exchange.asmx. The elapsed time was 46 millise
conds.
RunspaceId : 03d92840-abbf-45ec-b714-753970e9dc34
Id : 1126
Type : Success
Message : [Server] Successfully contacted the UM service at https://ourCASserver.domain.corp/ews/exchange.asmx. The elapsed time was 0 millisec
onds.
Thanks,
Blind -
OAB URL not found in Test E-mail Autoconfiguration
Hello, we are having issues implementing the Offline Address Book. I had everything working fine prior to preparing to remove my Exchange 2003 server.
This started happening after i changed from one address book to another. I have a UC certificate with all the correct FQDN, NetBios, and DNS names. This issue is affecting both internal and external users (OLAW).
From the client side if you do a Test E-mail autoconfiguration there is no "OAB URL" under the "OOF URL", where there used to be one.
I am able to access https://outlook.mydomain.com/autodiscover/autodiscover.xml & https://outlook.mydomain.com/oab/<GUID>/oab.xml from the inside as well as the outside and I get the XML text.
Here are some results from the EMC
Get-ClientAccessServer | fl
Name : <CASServer>
OutlookAnywhereEnabled : True
AutoDiscoverServiceCN : <CASServer>
AutoDiscoverServiceClassName : ms-Exchange-AutoDiscover-Service
AutoDiscoverServiceInternalUri : https://outlook.mydomain.com/Autodiscover/Autodiscover.xml
AutoDiscoverServiceGuid : 77378f46-2c66-4aa9-a6a6-3e7a48b19596
AutoDiscoverSiteScope : {<Default First Site Name>}
IsValid : True
OriginatingServer : ds-app1.corp.mydomain.com
ExchangeVersion : 0.1 (8.0.535.0)
DistinguishedName : CN=CASServer,CN=Servers,CN=Exchange Administrative Group
OHF23SPDLT),CN=Administrative Groups,CN=<OrganizationName>,C
osoft Exchange,CN=Services,CN=Configuration,DC=corp,DC=mydomain,DC=com
Identity : CASServer
Guid : d29ec49e-7f8c-414c-81c1-80e7ad322638
ObjectCategory : corp.mydomain.com/Configuration/Schema/ms-Exch-Exchange-Se
ObjectClass : {top, server, msExchExchangeServer}
WhenChanged : 10/4/2007 5:24:51 PM
WhenCreated : 8/28/2007 4:04:22 PM
Get-WebServicesDirectory | fl
InternalNLBBypassUrl :
Name : EWS (Default Web Site)
InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated}
ExternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated}
BasicAuthentication : True
DigestAuthentication : False
WindowsAuthentication : True
MetabasePath : IIS://CASServer.corp.mydomain.com/W3SVC/1/ROOT/EWS
Path : C:\Program Files\Microsoft\Exchange Server\ClientAccess\exchw
Server : <CASServer>
InternalUrl : https://outlook.mydomain.com/EWS/Exchange.asmx
ExternalUrl : https://outlook.mydomain.com/EWS/Exchange.asmx
AdminDisplayName :
ExchangeVersion : 0.1 (8.0.535.0)
Identity : <CASServer>\EWS (Default Web Site)
Guid : 41c65fc5-3ec2-4b21-b9d6-eadb69ff4376
ObjectCategory : corp.mydomain.com/Configuration/Schema/ms-Exch-Web-Services
al-Directory
ObjectClass : {top, msExchVirtualDirectory, msExchWebServicesVirtualDirecto
WhenChanged : 9/11/2007 2:50:01 PM
WhenCreated : 8/28/2007 4:07:24 PM
OriginatingServer : ds-app1.corp.mydomain.com
IsValid : True
Get-OabVirtualdirectory | fl
Name : OAB (Default Web Site)
PollInterval : 5
OfflineAddressBooks : {Offline Address Book}
RequireSSL : True
MetabasePath : IIS://CASServer.corp.mydomain.com/W3SVC/1/ROOT/OAB
Path : C:\Program Files\Microsoft\Exchange Server\ClientAccess\OAB
Server : <CASServer>
InternalUrl : https://CASServer.corp.mydomain.com/oab
InternalAuthenticationMethods : {WindowsIntegrated}
ExternalUrl : https://outlook.mydomain.com/OAB
ExternalAuthenticationMethods : {WindowsIntegrated}
AdminDisplayName :
ExchangeVersion : 0.1 (8.0.535.0)
DistinguishedName : CN=OAB (Default Web Site),CN=HTTP,CN=Protocols,CN=CasSERVER
ervers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=A
strative Groups,CN=Dynasplint Systems,CN=Microsoft Exchange,CN
ices,CN=Configuration,DC=corp,DC=mydomain,DC=com
Identity : CASServer\OAB (Default Web Site)
Guid : 1477428c-6b87-4991-bf4e-ce29e94e6ea5
ObjectCategory : corp.mydomain.com/Configuration/Schema/ms-Exch-OAB-Virtual-D
ory
ObjectClass : {top, msExchVirtualDirectory, msExchOABVirtualDirectory}
WhenChanged : 11/16/2007 10:17:46 AM
WhenCreated : 11/15/2007 3:04:41 PM
OriginatingServer : ds-app1.corp.mydomain.com
IsValid : True
Test-OutlookWebServices -identity administrator | ft * -AutoSize -Wrap
Id Type Message
1003 Information About to test AutoDiscover with the e-mail address [email protected].
1013 Error When contacting https://mydomain.com/Autodiscover/Autodiscover.xml received the error The remote server returned an error: (401) Unauthorized.
1006 Error Failed to contact AutoDiscover
Anyone have suggestions?Hello, we are having issues implementing the Offline Address Book. I had everything working fine prior to preparing to remove my Exchange 2003 server.
This started happening after i changed from one address book to another. I have a UC certificate with all the correct FQDN, NetBios, and DNS names. This issue is affecting both internal and external users (OLAW).
From the client side if you do a Test E-mail autoconfiguration there is no "OAB URL" under the "OOF URL", where there used to be one.
I am able to access
https://outlook.mydomain.com/autodiscover/autodiscover.xml & <a href="https://outlook.mydomain.com/oab//oab.xml" title="https://outlook.mydomain.com/oab/%3CGUID%3E/oab.xml">https://outlook.mydomain.com/oab/<GUID>/oab.xml from the inside as well
as the outside and I get the XML text.
Just resolved this issue with Microsoft support. The 3 users not receiving < OAB URL > from autodiscover.xml had a specific (and the wrong) OAB configured in their AD Object setting "msExchUseOAB", instead of being "< not set >". With the entries
for "msExchUseOAB" cleared, OAB settings were obtained from Autodiscover. -
Autodiscovery not working at a complete loss
Hi
I have a setup with one CAS server and one Exchange backend server. Serves 4 Domains.
Activesynch is working (both on intranet and internet). owa is working both Networks too.
heres some test data (domain and such stuff have been sanitized contoso.com is the excernal name, contoso is the internal name, casserver is the CAS Server etc.
my autodiscover is on
https://mail.contoso.com/autodiscover/autodiscover.xml
any http on autodiscovery.* (my 4 domains) will do a 302 redirect to
https://mail.contoso.com/autodiscover/autodiscover.xml
browsing https://mail.contoso.com/autodiscover/autodiscover.XML from intranet or internet yields this response (after providing username and password
<Autodiscover>
<Response>
<Error Time="09:32:02.3112517" Id="2271660173">
<ErrorCode>600</ErrorCode>
<Message>Invalid Request</Message>
<DebugData/>
</Error>
</Response>
</Autodiscover>
Other Things I've done to help showing the configuration:
1. Test autodiscover configuration: Test-OutlookWebServices -ClientAccessServer "casserver"
[PS] C:\Program Files\Microsoft\Exchange Server\V14\Scripts>Test-OutlookWebServices -ClientAccessServer casserver
RunspaceId : 735fd88b-e9e1-4350-b7d7-c0aca66ebecd
Id : 1019
Type : Information
Message : A valid Autodiscover service connection point was found. The Autodiscover URL on this object is https://casserver.contoso.com/Autodiscover/Autodiscover.xml.
RunspaceId : 735fd88b-e9e1-4350-b7d7-c0aca66ebecd
Id : 1013
Type : Error
Message : When contacting https://casserver.contoso.com/Autodiscover/Autodiscover.xml received the error The remote server returned an error: (404) Not Found.
RunspaceId : 735fd88b-e9e1-4350-b7d7-c0aca66ebecd
Id : 1023
Type : Error
Message : The Autodiscover service couldn't be contacted.
RunspaceId : 735fd88b-e9e1-4350-b7d7-c0aca66ebecd
Id : 1013
Type : Error
Message : When contacting https://casserver.contoso.com/EWS/Exchange.asmx received the error The request failed with HTTP status 404: Not Found.
RunspaceId : 735fd88b-e9e1-4350-b7d7-c0aca66ebecd
Id : 1025
Type : Error
Message : [EXCH] Error contacting the AS service at https://casserver.contoso.com/EWS/Exchange.asmx. Elapsed time was 437 milliseconds.
RunspaceId : 735fd88b-e9e1-4350-b7d7-c0aca66ebecd
Id : 1013
Type : Error
Message : When contacting https://casserver.contoso.com/EWS/Exchange.asmx received the error The remote server returned an error: (404) Not Found.
RunspaceId : 735fd88b-e9e1-4350-b7d7-c0aca66ebecd
Id : 1027
Type : Error
Message : [EXCH] Error contacting the UM service at https://casserver.contoso.com/EWS/Exchange.asmx. Elapsed time was 0 milliseconds.
RunspaceId : 735fd88b-e9e1-4350-b7d7-c0aca66ebecd
Id : 1013
Type : Error
Message : When contacting https://mail.contoso.com/ews/exchange.asmx received the error Client found response content type of '', but expected 'text/xml'.
The request failed with an empty response.
RunspaceId : 735fd88b-e9e1-4350-b7d7-c0aca66ebecd
Id : 1025
Type : Error
Message : [EXPR] Error contacting the AS service at https://mail.contoso.com/ews/exchange.asmx. Elapsed time was 468 milliseconds.
RunspaceId : 735fd88b-e9e1-4350-b7d7-c0aca66ebecd
Id : 1026
Type : Success
Message : [EXPR] Successfully contacted the UM service at https://mail.contoso.com/ews/exchange.asmx. The elapsed time was 140 milliseconds.
RunspaceId : 735fd88b-e9e1-4350-b7d7-c0aca66ebecd
Id : 1113
Type : Error
Message : When contacting https://casserver.contoso.com/ews/exchange.asmx received the error The request failed with HTTP status 404: Not Found.
RunspaceId : 735fd88b-e9e1-4350-b7d7-c0aca66ebecd
Id : 1125
Type : Error
Message : [Server] Error contacting the AS service at https://casserver.contoso.com/ews/exchange.asmx. Elapsed time was 0 milliseconds.
RunspaceId : 735fd88b-e9e1-4350-b7d7-c0aca66ebecd
Id : 1113
Type : Error
Message : When contacting https://casserver.contoso.com/ews/exchange.asmx received the error The remote server returned an error: (404) Not Found.
RunspaceId : 735fd88b-e9e1-4350-b7d7-c0aca66ebecd
Id : 1127
Type : Error
Message : [Server] Error contacting the UM service at https://casserver.contoso.com/ews/exchange.asmx. Elapsed time was 0 milliseconds.
[PS] C:\Program Files\Microsoft\Exchange Server\V14\Scripts>
2. Ping and browse https://mydomain/autodiscover/autodiscover.xm
Browse https://casserver/autodiscover/autodiscover.XML = 404
ping casserver Works OK
note above about
https://mail.contoso.com/autodiscover/autodiscover.XML actually Works.
3. If you are testing from outside, test https://autodiscover.mydomain/autodiscover/autodiscover.xml
See 2
4. Test autodiscover virtual diretories: Get-AutodiscoverVirtualDirectory |FL
[PS] C:\Program Files\Microsoft\Exchange Server\V14\Scripts>Get-AutodiscoverVirtualDirectory |FL
RunspaceId : 735fd88b-e9e1-4350-b7d7-c0aca66ebecd
Name : Autodiscover (Default Web Site)
InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated}
ExternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated}
LiveIdSpNegoAuthentication : False
WSSecurityAuthentication : False
LiveIdBasicAuthentication : False
BasicAuthentication : True
DigestAuthentication : False
WindowsAuthentication : True
MetabasePath : IIS://casserver.contoso.com/W3SVC/1/ROOT/Autodiscover
Path : C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\Autodiscover
ExtendedProtectionTokenChecking : None
ExtendedProtectionFlags : {}
ExtendedProtectionSPNList : {}
Server : CASSERVER
InternalUrl :
ExternalUrl :
AdminDisplayName :
ExchangeVersion : 0.10 (14.0.100.0)
DistinguishedName : CN=Autodiscover (Default Web Site),CN=HTTP,CN=Protocols,CN=CASSERVER,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Contoso,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=contoso,DC=com
Identity : CASSERVER\Autodiscover (Default Web Site)
Guid : 9f99c3b7-f63f-474c-899d-72c6d4f5d480
ObjectCategory : contoso.com/Configuration/Schema/ms-Exch-Auto-Discover-Virtual-Directory
ObjectClass : {top, msExchVirtualDirectory, msExchAutoDiscoverVirtualDirectory}
WhenChanged : 29-08-2014 02:45:44
WhenCreated : 29-08-2014 02:46:03
WhenChangedUTC : 29-08-2014 00:45:44
WhenCreatedUTC : 29-08-2014 00:46:03
OrganizationId :
OriginatingServer : adserver.contoso.com
IsValid : True
[PS] C:\Program Files\Microsoft\Exchange Server\V14\Scripts>
5. Also Checked my Certificate:
The certificate is a signed UCC / SAN certificate from my own authority it contains the following (sanitized) information:
Certificate:
Identity / Subject:
casserver.contoso.com
SAN
dns=casserver.contoso.com
dns=mail.contoso.com
dns=autodiscover.contoso.com
dns=mail.domain2.com
dns=autodiscover.domain2.com
dns=mail.domain4.com
dns=autodiscover.domain4.com
dns=mail.domain3.com
dns=autodiscover.domain3.com
dns=contoso.com
dns=domain2.com
dns=domain4.com
dns=domain3.com
dns=casserver
6. Tried resetting the Autodiscovery Virtual Directory.
7. Testing on https://testconnectivity.microsoft.com/ (remote Connectivity Analyzer):
Exchange ActiveSync Autodiscover:
<?xml version="1.0" encoding="utf-8"?>
<testresult status="Error" errorid="734044ef-11c2-4e30-9ee6-450d49e9d92c" contentUrl="" testdescription="Attempting the Autodiscover and Exchange ActiveSync test (if requested)." resultdescription="Testing of Autodiscover for Exchange ActiveSync failed." additionaldetails="" elapsedMilliseconds="22354">
<children>
<testresult status="Error" errorid="734044ef-11c2-4e30-9ee6-450d49e9d92c" contentUrl="" testdescription="Attempting each method of contacting the Autodiscover service." resultdescription="The Autodiscover service couldn't be contacted successfully by any method." additionaldetails="" elapsedMilliseconds="22354">
<children>
<testresult status="Error" errorid="734044ef-11c2-4e30-9ee6-450d49e9d92c" contentUrl="" testdescription="Attempting to test potential Autodiscover URL https://contoso.com:443/Autodiscover/Autodiscover.xml" resultdescription="Testing of this potential Autodiscover URL failed." additionaldetails="" elapsedMilliseconds="17286">
<children>
<testresult status="Success" errorid="00000000-0000-0000-0000-000000000000" contentUrl="" testdescription="Attempting to resolve the host name contoso.com in DNS." resultdescription="The host name resolved successfully." additionaldetails="IP addresses returned: 255.255.255.255" elapsedMilliseconds="332">
<children />
</testresult>
<testresult status="Success" errorid="00000000-0000-0000-0000-000000000000" contentUrl="" testdescription="Testing TCP port 443 on host contoso.com to ensure it's listening and open." resultdescription="The port was opened successfully." additionaldetails="" elapsedMilliseconds="293">
<children />
</testresult>
<testresult status="Success" errorid="734044ef-11c2-4e30-9ee6-450d49e9d92c" contentUrl="" testdescription="Testing the SSL certificate to make sure it's valid." resultdescription="The certificate passed all validation requirements." additionaldetails="" elapsedMilliseconds="15540">
<children>
<testresult status="Success" errorid="00000000-0000-0000-0000-000000000000" contentUrl="" testdescription="The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server contoso.com on port 443." resultdescription="The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate." additionaldetails="Remote Certificate Subject: CN=casserver.contoso.com, OU=contoso, O=contoso, L=City, S=State, C=US, Issuer: CN=my-ca-autority, DC=contoso, DC=com." elapsedMilliseconds="15517">
<children />
</testresult>
<testresult status="Success" errorid="00000000-0000-0000-0000-000000000000" contentUrl="" testdescription="Validating the certificate name." resultdescription="The certificate name was validated successfully." additionaldetails="Host name contoso.com was found in the Certificate Subject Alternative Name entry." elapsedMilliseconds="0">
<children />
</testresult>
<testresult status="Success" errorid="00000000-0000-0000-0000-000000000000" contentUrl="" testdescription="Testing the certificate date to confirm the certificate is valid." resultdescription="Date validation passed. The certificate hasn't expired." additionaldetails="The certificate is valid. NotBefore = 8/28/2014 11:15:35 PM, NotAfter = 8/27/2016 11:15:35 PM" elapsedMilliseconds="0">
<children />
</testresult>
</children>
</testresult>
<testresult status="Success" errorid="00000000-0000-0000-0000-000000000000" contentUrl="" testdescription="Checking the IIS configuration for client certificate authentication." resultdescription="Client certificate authentication wasn't detected." additionaldetails="Accept/Require Client Certificates isn't configured." elapsedMilliseconds="679">
<children />
</testresult>
<testresult status="Error" errorid="734044ef-11c2-4e30-9ee6-450d49e9d92c" contentUrl="" testdescription="Attempting to send an Autodiscover POST request to potential Autodiscover URLs." resultdescription="Autodiscover settings weren't obtained when the Autodiscover POST request was sent." additionaldetails="" elapsedMilliseconds="440">
<children>
<testresult status="Error" errorid="12f4b21a-7e8d-4c95-b4a8-f4608e7d73b0" contentUrl="" testdescription="The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL https://contoso.com:443/Autodiscover/Autodiscover.xml for user [email protected]." resultdescription="The Microsoft Connectivity Analyzer failed to obtain an Autodiscover XML response." additionaldetails="A Web exception occurred because an HTTP 404 - NotFound response was received from Unknown.
HTTP Response Headers:
Connection: close
Content-Length: 315
Content-Type: text/html; charset=us-ascii
Date: Fri, 29 Aug 2014 07:46:13 GMT
Server: Microsoft-HTTPAPI/2.0
" elapsedMilliseconds="440">
<children />
</testresult>
</children>
</testresult>
</children>
</testresult>
<testresult status="Error" errorid="734044ef-11c2-4e30-9ee6-450d49e9d92c" contentUrl="" testdescription="Attempting to test potential Autodiscover URL https://autodiscover.contoso.com:443/Autodiscover/Autodiscover.xml" resultdescription="Testing of this potential Autodiscover URL failed." additionaldetails="" elapsedMilliseconds="2303">
<children>
<testresult status="Success" errorid="00000000-0000-0000-0000-000000000000" contentUrl="" testdescription="Attempting to resolve the host name autodiscover.contoso.com in DNS." resultdescription="The host name resolved successfully." additionaldetails="IP addresses returned: 255.255.255.255" elapsedMilliseconds="321">
<children />
</testresult>
<testresult status="Success" errorid="00000000-0000-0000-0000-000000000000" contentUrl="" testdescription="Testing TCP port 443 on host autodiscover.contoso.com to ensure it's listening and open." resultdescription="The port was opened successfully." additionaldetails="" elapsedMilliseconds="347">
<children />
</testresult>
<testresult status="Success" errorid="734044ef-11c2-4e30-9ee6-450d49e9d92c" contentUrl="" testdescription="Testing the SSL certificate to make sure it's valid." resultdescription="The certificate passed all validation requirements." additionaldetails="" elapsedMilliseconds="505">
<children>
<testresult status="Success" errorid="00000000-0000-0000-0000-000000000000" contentUrl="" testdescription="The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server autodiscover.contoso.com on port 443." resultdescription="The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate." additionaldetails="Remote Certificate Subject: CN=casserver.contoso.com, OU=contoso, O=contoso, L=City, S=State, C=US, Issuer: CN=my-ca-autority, DC=contoso, DC=com." elapsedMilliseconds="483">
<children />
</testresult>
<testresult status="Success" errorid="00000000-0000-0000-0000-000000000000" contentUrl="" testdescription="Validating the certificate name." resultdescription="The certificate name was validated successfully." additionaldetails="Host name autodiscover.contoso.com was found in the Certificate Subject Alternative Name entry." elapsedMilliseconds="0">
<children />
</testresult>
<testresult status="Success" errorid="00000000-0000-0000-0000-000000000000" contentUrl="" testdescription="Testing the certificate date to confirm the certificate is valid." resultdescription="Date validation passed. The certificate hasn't expired." additionaldetails="The certificate is valid. NotBefore = 8/28/2014 11:15:35 PM, NotAfter = 8/27/2016 11:15:35 PM" elapsedMilliseconds="0">
<children />
</testresult>
</children>
</testresult>
<testresult status="Success" errorid="00000000-0000-0000-0000-000000000000" contentUrl="" testdescription="Checking the IIS configuration for client certificate authentication." resultdescription="Client certificate authentication wasn't detected." additionaldetails="Accept/Require Client Certificates isn't configured." elapsedMilliseconds="676">
<children />
</testresult>
<testresult status="Error" errorid="734044ef-11c2-4e30-9ee6-450d49e9d92c" contentUrl="" testdescription="Attempting to send an Autodiscover POST request to potential Autodiscover URLs." resultdescription="Autodiscover settings weren't obtained when the Autodiscover POST request was sent." additionaldetails="" elapsedMilliseconds="451">
<children>
<testresult status="Error" errorid="12f4b21a-7e8d-4c95-b4a8-f4608e7d73b0" contentUrl="" testdescription="The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL https://autodiscover.contoso.com:443/Autodiscover/Autodiscover.xml for user [email protected]." resultdescription="The Microsoft Connectivity Analyzer failed to obtain an Autodiscover XML response." additionaldetails="A Web exception occurred because an HTTP 404 - NotFound response was received from Unknown.
HTTP Response Headers:
Connection: close
Content-Length: 315
Content-Type: text/html; charset=us-ascii
Date: Fri, 29 Aug 2014 07:46:15 GMT
Server: Microsoft-HTTPAPI/2.0
" elapsedMilliseconds="451">
<children />
</testresult>
</children>
</testresult>
</children>
</testresult>
<testresult status="Error" errorid="734044ef-11c2-4e30-9ee6-450d49e9d92c" contentUrl="" testdescription="Attempting to contact the Autodiscover service using the HTTP redirect method." resultdescription="The attempt to contact Autodiscover using the HTTP Redirect method failed." additionaldetails="" elapsedMilliseconds="2487">
<children>
<testresult status="Success" errorid="00000000-0000-0000-0000-000000000000" contentUrl="" testdescription="Attempting to resolve the host name autodiscover.contoso.com in DNS." resultdescription="The host name resolved successfully." additionaldetails="IP addresses returned: 255.255.255.255" elapsedMilliseconds="8">
<children />
</testresult>
<testresult status="Success" errorid="00000000-0000-0000-0000-000000000000" contentUrl="" testdescription="Testing TCP port 80 on host autodiscover.contoso.com to ensure it's listening and open." resultdescription="The port was opened successfully." additionaldetails="" elapsedMilliseconds="161">
<children />
</testresult>
<testresult status="Success" errorid="00000000-0000-0000-0000-000000000000" contentUrl="" testdescription="The Microsoft Connectivity Analyzer is checking the host autodiscover.contoso.com for an HTTP redirect to the Autodiscover service." resultdescription="The redirect (HTTP 301/302) response was received successfully." additionaldetails="Redirect URL: https://mail.contoso.com/Autodiscover/Autodiscover.xml
HTTP Response Headers:
Content-Length: 179
Content-Type: text/html; charset=UTF-8
Date: Fri, 29 Aug 2014 07:46:15 GMT
Location: https://mail.contoso.com/Autodiscover/Autodiscover.xml
Server: Microsoft-IIS/7.5
X-Powered-By: ASP.NET
" elapsedMilliseconds="310">
<children />
</testresult>
<testresult status="Error" errorid="734044ef-11c2-4e30-9ee6-450d49e9d92c" contentUrl="" testdescription="Attempting to test potential Autodiscover URL https://mail.contoso.com/Autodiscover/Autodiscover.xml" resultdescription="Testing of this potential Autodiscover URL failed." additionaldetails="" elapsedMilliseconds="2006">
<children>
<testresult status="Success" errorid="00000000-0000-0000-0000-000000000000" contentUrl="" testdescription="Attempting to resolve the host name mail.contoso.com in DNS." resultdescription="The host name resolved successfully." additionaldetails="IP addresses returned: 255.255.255.255" elapsedMilliseconds="368">
<children />
</testresult>
<testresult status="Success" errorid="00000000-0000-0000-0000-000000000000" contentUrl="" testdescription="Testing TCP port 443 on host mail.contoso.com to ensure it's listening and open." resultdescription="The port was opened successfully." additionaldetails="" elapsedMilliseconds="169">
<children />
</testresult>
<testresult status="Success" errorid="734044ef-11c2-4e30-9ee6-450d49e9d92c" contentUrl="" testdescription="Testing the SSL certificate to make sure it's valid." resultdescription="The certificate passed all validation requirements." additionaldetails="" elapsedMilliseconds="354">
<children>
<testresult status="Success" errorid="00000000-0000-0000-0000-000000000000" contentUrl="" testdescription="The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server mail.contoso.com on port 443." resultdescription="The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate." additionaldetails="Remote Certificate Subject: CN=casserver.contoso.com, OU=contoso, O=contoso, L=City, S=State, C=US, Issuer: CN=my-ca-autority, DC=contoso, DC=com." elapsedMilliseconds="329">
<children />
</testresult>
<testresult status="Success" errorid="00000000-0000-0000-0000-000000000000" contentUrl="" testdescription="Validating the certificate name." resultdescription="The certificate name was validated successfully." additionaldetails="Host name mail.contoso.com was found in the Certificate Subject Alternative Name entry." elapsedMilliseconds="0">
<children />
</testresult>
<testresult status="Success" errorid="00000000-0000-0000-0000-000000000000" contentUrl="" testdescription="Testing the certificate date to confirm the certificate is valid." resultdescription="Date validation passed. The certificate hasn't expired." additionaldetails="The certificate is valid. NotBefore = 8/28/2014 11:15:35 PM, NotAfter = 8/27/2016 11:15:35 PM" elapsedMilliseconds="0">
<children />
</testresult>
</children>
</testresult>
<testresult status="Success" errorid="00000000-0000-0000-0000-000000000000" contentUrl="" testdescription="Checking the IIS configuration for client certificate authentication." resultdescription="Client certificate authentication wasn't detected." additionaldetails="Accept/Require Client Certificates isn't configured." elapsedMilliseconds="669">
<children />
</testresult>
<testresult status="Error" errorid="734044ef-11c2-4e30-9ee6-450d49e9d92c" contentUrl="" testdescription="Attempting to send an Autodiscover POST request to potential Autodiscover URLs." resultdescription="Autodiscover settings weren't obtained when the Autodiscover POST request was sent." additionaldetails="" elapsedMilliseconds="445">
<children>
<testresult status="Error" errorid="a28be452-a4b2-419c-851a-37f441f3120e" contentUrl="" testdescription="The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL https://mail.contoso.com/Autodiscover/Autodiscover.xml for user [email protected]." resultdescription="The Microsoft Connectivity Analyzer failed to obtain an Autodiscover XML response." additionaldetails="An HTTP 500 response was returned from Unknown.
HTTP Response Headers:
Content-Length: 0
Cache-Control: private
Date: Fri, 29 Aug 2014 07:46:18 GMT
Server: Microsoft-IIS/7.5
X-AspNet-Version: 2.0.50727
X-Powered-By: ASP.NET
" elapsedMilliseconds="444">
<children />
</testresult>
</children>
</testresult>
</children>
</testresult>
</children>
</testresult>
<testresult status="Error" errorid="734044ef-11c2-4e30-9ee6-450d49e9d92c" contentUrl="" testdescription="Attempting to contact the Autodiscover service using the DNS SRV redirect method." resultdescription="The Microsoft Connectivity Analyzer failed to contact the Autodiscover service using the DNS SRV redirect method." additionaldetails="" elapsedMilliseconds="132">
<children>
<testresult status="Error" errorid="8249cc81-d0ce-43d2-b319-48ceadb1bfe7" contentUrl="http://go.microsoft.com/?linkid=9843849" testdescription="Attempting to locate SRV record _autodiscover._tcp.contoso.com in DNS." resultdescription="The Autodiscover SRV record wasn't found in DNS." additionaldetails="" elapsedMilliseconds="132">
<children />
</testresult>
</children>
</testresult>
<testresult status="Warning" errorid="c0f75b77-072c-48d5-ab17-eebc99a4b3d9" contentUrl="http://go.microsoft.com/?linkid=9843786" testdescription="Checking if there is an autodiscover CNAME record in DNS for your domain 'contoso.com' for Office 365." resultdescription="Failed to validate autodiscover CNAME record in DNS. If your mailbox isn't in Office 365, you can ignore this warning." additionaldetails="There is no Autodiscover CNAME record for your domain 'contoso.com'." elapsedMilliseconds="145">
<children />
</testresult>
</children>
</testresult>
</children>
</testresult>
8. Testing Autodiscover from Exchange Client (intranet):
[email protected]
Attempting URL https://casserver.contoso.com/Autodiscover/Autodiscover.xml Found Through SCP
Autodiscover to https://casserver.contoso.com/Autodiscover/Autodiscover.xml starting
GetLastError=0;httpStatus=404.
... more errors...
Redirect Check to http:/autodiscover.contoso.com/Autodiscover/Autodiscover.xml starting
(recieves redirect)
Autodiscover to https://mail.contoso.com/Autodiscover/Autodiscover.xml starting
GetLastError=0;httpStatus=500.
..SRV Attempt..
.Fails.
End of tests.
(sorry for lack of details in this test) - the tests done by Outlook has to be transcribed by hand :-(
I hope anyone out there can help me resolve my issue.
Regards,
HenrikFound these instructions in another post:
After doing the below changes , Exchange 2010 and 2013 Autodiscovery working without any error .
Set-ClientAccessServer -Identity e2013ht -AutodiscoverServiceInternalUri https://mail.mydomain.com/autodiscover/autodiscover.xml
Set-WebServicesVirtualDirectory -Identity “e2013ht\EWS (Default Web Site)” –InternalUrl https://mail.mydomain.com/EWS/Exchange.asmx
Set-OABVirtualDirectory -Identity “e2013ht\OAB (Default Web Site)” -InternalURL https://mail.mydomain.com/OAB
Set-ActiveSyncVirtualDirectory -Identity “e2013ht\Microsoft-Server-ActiveSync (Default Web Site)” -InternalURL https://mail.mydomain.com/Microsoft-Server-Activesync
For Outlook Anywhere,
Set-WebServicesVirtualDirectory –Identity ‘e2013ht\EWS (Default Web Site)’ –ExternalUrl https://mail.mydomain.com/ews/exchange.asmx
Regards
Bhupen
After changing and applying these commands to match my server etc:
Set-ClientAccessServer -Identity CASSERVER -AutodiscoverServiceInternalUri https://mail.contoso.com/autodiscover/autodiscover.xml
Set-WebServicesVirtualDirectory -Identity "CASSERVER\EWS (Default Web Site)" –InternalUrl https://mail.contoso.com/EWS/Exchange.asmx
Set-OABVirtualDirectory -Identity "CASSERVER\OAB (Default Web Site)" -InternalURL https://mail.contoso.com/OAB
Set-ActiveSyncVirtualDirectory -Identity "CASSERVER\Microsoft-Server-ActiveSync (Default Web Site)" -InternalURL https://mail.contoso.com/Microsoft-Server-Activesync
Set-WebServicesVirtualDirectory –Identity "CASSERVER\EWS (Default Web Site)" –ExternalUrl https://mail.contoso.com/ews/exchange.asmx
The result of Test 1. Test autodiscover configuration: Test-OutlookWebServices -ClientAccessServer CASSERVER changed, its still not working - but there are less errors now.
[PS] C:\Program Files\Microsoft\Exchange Server\V14\Scripts>Test-OutlookWebServices -ClientAccessServer CASSERVER
RunspaceId : 735fd88b-e9e1-4350-b7d7-c0aca66ebecd
Id : 1019
Type : Information
Message : A valid Autodiscover service connection point was found. The Autodiscover URL on this object is https://mail.contoso.com/autodiscover/autodiscover.xml.
RunspaceId : 735fd88b-e9e1-4350-b7d7-c0aca66ebecd
Id : 1013
Type : Error
Message : When contacting https://mail.contoso.com/autodiscover/autodiscover.xml received the error The remote server returned an error: (500) Internal Server Error.
RunspaceId : 735fd88b-e9e1-4350-b7d7-c0aca66ebecd
Id : 1023
Type : Error
Message : The Autodiscover service couldn't be contacted.
RunspaceId : 735fd88b-e9e1-4350-b7d7-c0aca66ebecd
Id : 1113
Type : Error
Message : When contacting https://CASSERVER.contoso.com:443/autodiscover/autodiscover.xml received the error The remote server returned an error: (404) Not Found.
RunspaceId : 735fd88b-e9e1-4350-b7d7-c0aca66ebecd
Id : 1123
Type : Error
Message : The Autodiscover service couldn't be contacted.
RunspaceId : 735fd88b-e9e1-4350-b7d7-c0aca66ebecd
Id : 1013
Type : Error
Message : When contacting https://mail.contoso.com/EWS/Exchange.asmx received the error Client found response content type of '', but expected 'text/xml'.
The request failed with an empty response.
RunspaceId : 735fd88b-e9e1-4350-b7d7-c0aca66ebecd
Id : 1025
Type : Error
Message : [EXCH] Error contacting the AS service at https://mail.contoso.com/EWS/Exchange.asmx. Elapsed time was 15 milliseconds.
RunspaceId : 735fd88b-e9e1-4350-b7d7-c0aca66ebecd
Id : 1026
Type : Success
Message : [EXCH] Successfully contacted the UM service at https://mail.contoso.com/EWS/Exchange.asmx. The elapsed time was 15 milliseconds.
RunspaceId : 735fd88b-e9e1-4350-b7d7-c0aca66ebecd
Id : 1013
Type : Error
Message : When contacting https://mail.contoso.com/ews/exchange.asmx received the error Client found response content type of '', but expected 'text/xml'.
The request failed with an empty response.
RunspaceId : 735fd88b-e9e1-4350-b7d7-c0aca66ebecd
Id : 1025
Type : Error
Message : [EXPR] Error contacting the AS service at https://mail.contoso.com/ews/exchange.asmx. Elapsed time was 0 milliseconds.
RunspaceId : 735fd88b-e9e1-4350-b7d7-c0aca66ebecd
Id : 1026
Type : Success
Message : [EXPR] Successfully contacted the UM service at https://mail.contoso.com/ews/exchange.asmx. The elapsed time was 234 milliseconds.
RunspaceId : 735fd88b-e9e1-4350-b7d7-c0aca66ebecd
Id : 1113
Type : Error
Message : When contacting https://casserver.contoso.com/ews/exchange.asmx received the error The request failed with HTTP status 404: Not Found.
RunspaceId : 735fd88b-e9e1-4350-b7d7-c0aca66ebecd
Id : 1125
Type : Error
Message : [Server] Error contacting the AS service at https://casserver.contoso.com/ews/exchange.asmx. Elapsed time was 0 milliseconds.
RunspaceId : 735fd88b-e9e1-4350-b7d7-c0aca66ebecd
Id : 1113
Type : Error
Message : When contacting https://casserver.contoso.com/ews/exchange.asmx received the error The remote server returned an error: (404) Not Found.
RunspaceId : 735fd88b-e9e1-4350-b7d7-c0aca66ebecd
Id : 1127
Type : Error
Message : [Server] Error contacting the UM service at https://casserver.contoso.com/ews/exchange.asmx. Elapsed time was 0 milliseconds.
[PS] C:\Program Files\Microsoft\Exchange Server\V14\Scripts>
regards,
Henrik -
Out of office/free busy not working for Outlook 2013
Hi! I have a user on our network that cannot use Out of office or see free/busy information in meeting requests. We have hundreds of working 2010 clients but this one is 2013 and NOT a member of our domain. They are connected to exchange
and can do anything except the above. When I do a test of email autoconfiguration it just fails. DNS resolution is working fine but it can't connect to the server for these two functions only. Any articles I can find assume the user is remote
and outside the network but he is connected internally. Any ideas?
Thanks!Hi,
Please switch to Outlook 2010 client and login OWA to check this issue.
The Microsoft Exchange Server 2010 Availability service makes free/busy information available to Outlook client. Then Outlook uses the Exchange Server 2010 Autodiscover service to obtain the URL of the Availability service. As you
mentioned, it failed to do a test of email autoconfiguration. So I suggest the following methods for troubleshooting
Please switch to Outlook 2010 client and login OWA to check this issue.
Have you configured
Autodiscover Service for Internet Access?
Use Test-OutlookWebServices cmdlet to
verify that the Autodiscover service settings for Outlook clients are configured correctly.
Blog for
reference to troubleshooting Autodiscover.
Best Regards.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Lynn-Li
TechNet Community Support -
Exchange 2013 Autodiscover and Webservices virtual directories with wrong address
Hey people,
I have 3 2013 Servers
Server 1 CAS
Server 2 & 3 MBX
having a bit of trouble here - everything was working fine after migration (about 6months ago), and now mac users can't access e-mail.
If I try to access EWS page (https://webmail.domain.co.ao/EWS/exchange.asmx) , i get
Service
You have created a service.
To test this service, you will need to create a client and use it to call the service. You can do this using the svcutil.exe tool from the command line with the following syntax:
svcutil.exe https://SERVER2.domain.int:444/EWS/Services.wsdl
If I try to access the autodiscover webpage, i get
<?xml version="1.0" encoding="UTF-8"?>
-<Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">-<Response>-<Error Id="1286627925" Time="17:58:59.7730521"><ErrorCode>600</ErrorCode><Message>Invalid Request</Message><DebugData/></Error></Response></Autodiscover>
When testing outlook web services, i get the following error
[PS] C:\Windows\system32>Test-OutlookWebServices
Source ServiceEndpoint Scenario Result Latency
(MS)
SERVER2.domain.int webmail.domain.co.ao Autodiscover: Outlook Provider Failure 64
SERVER2.domain.int Exchange Web Services Skipped 0
SERVER2.domain.int Availability Service Skipped 0
SERVER2.domain.int Offline Address Book Skipped 0
if i run
[PS] C:\Windows\system32>Get-AutodiscoverVirtualDirectory | fl
Creating a new session for implicit remoting of "Get-AutodiscoverVirtualDirectory" command...
RunspaceId : 9f23dad1-7806-42a6-8545-89b66847a359
Name : Autodiscover (Default Web Site)
InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated, WSSecurity, OAuth}
ExternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated, WSSecurity, OAuth}
LiveIdNegotiateAuthentication : False
WSSecurityAuthentication : True
LiveIdBasicAuthentication : False
BasicAuthentication : True
DigestAuthentication : False
WindowsAuthentication : True
OAuthAuthentication : True
AdfsAuthentication : False
MetabasePath : IIS://SERVER1.domain.int/W3SVC/1/ROOT/Autodiscover
Path : C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\Autodiscover
ExtendedProtectionTokenChecking : None
ExtendedProtectionFlags : {}
ExtendedProtectionSPNList : {}
AdminDisplayVersion : Version 15.0 (Build 775.38)
Server : SERVER1
InternalUrl : https://webmail.domain.co.ao/autodiscover/autodiscover.xml
ExternalUrl : https://webmail.domain.co.ao/autodiscover/autodiscover.xml
AdminDisplayName :
ExchangeVersion : 0.10 (14.0.100.0)
DistinguishedName : CN=Autodiscover (Default Web
Site),CN=HTTP,CN=Protocols,CN=SERVER1A,CN=Servers,CN=Exchange Administrative
Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=DOMAIN,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=domain,DC=int
Identity : SERVERONE\Autodiscover (Default Web Site)
Guid : fbed978f-7442-46ac-bb3c-53d9d7995507
ObjectCategory : domain.int/Configuration/Schema/ms-Exch-Auto-Discover-Virtual-Directory
ObjectClass : {top, msExchVirtualDirectory, msExchAutoDiscoverVirtualDirectory}
WhenChanged : 12/19/2013 10:30:26 AM
WhenCreated : 12/19/2013 10:30:26 AM
WhenChangedUTC : 12/19/2013 9:30:26 AM
WhenCreatedUTC : 12/19/2013 9:30:26 AM
OrganizationId :
OriginatingServer : DC2.domain.int
IsValid : True
ObjectState : Changed
and run
[PS] C:\Windows\system32>Get-WebServicesVirtualDirectory | fl
RunspaceId : 9f23dad1-7806-42a6-8545-89b66847a359
CertificateAuthentication :
InternalNLBBypassUrl :
GzipLevel : High
MRSProxyEnabled : False
Name : EWS (Default Web Site)
InternalAuthenticationMethods : {Basic, Digest}
ExternalAuthenticationMethods : {Basic, Digest}
LiveIdNegotiateAuthentication :
WSSecurityAuthentication : False
LiveIdBasicAuthentication : False
BasicAuthentication : True
DigestAuthentication : True
WindowsAuthentication : False
OAuthAuthentication : False
AdfsAuthentication : False
MetabasePath : IIS://SERVER1.domain.int/W3SVC/1/ROOT/EWS
Path : C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\EWS
ExtendedProtectionTokenChecking : None
ExtendedProtectionFlags : {}
ExtendedProtectionSPNList : {}
AdminDisplayVersion : Version 15.0 (Build 775.38)
Server : SERVER1
InternalUrl : https://webmail.domain.co.ao/EWS/exchange.asmx
ExternalUrl : https://webmail.domain.co.ao/EWS/exchange.asmx
AdminDisplayName :
ExchangeVersion : 0.10 (14.0.100.0)
DistinguishedName : CN=EWS (Default Web Site),CN=HTTP,CN=Protocols,CN=SERVRE1,CN=Servers,CN=Exchange
Administrative Group (FYDIBOHF23SPDLT),CN=Administrative
Groups,CN=DOMAINL,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domainl,DC=int
Identity : SERVER1\EWS (Default Web Site)
Guid : cbdd447b-54f8-4bba-9834-6c28b807711e
ObjectCategory : domain.int/Configuration/Schema/ms-Exch-Web-Services-Virtual-Directory
ObjectClass : {top, msExchVirtualDirectory, msExchWebServicesVirtualDirectory}
WhenChanged : 12/19/2013 9:31:11 AM
WhenCreated : 12/19/2013 9:31:11 AM
WhenChangedUTC : 12/19/2013 8:31:11 AM
WhenCreatedUTC : 12/19/2013 8:31:11 AM
OrganizationId :
OriginatingServer : DC2.domain.int
IsValid : True
ObjectState : Changed
Summarizing:
webmail.domain.co.ao maps to server1
Autodiscover and exchange web services point out to server1 (CAS), but when openning the respective webpages, the result is an error.
I have already deleted and recreated the autodiscover and EWS virtual directories but with no success.
Help anyone?
Many thanks,
AndreyHi Andrey,
Exchange Web Service in Exchange server configuration is working for all users in your Exchange environment, not just for one specific user. If you want to double make sure the EWS service in client side, we can directly access the EWS URL in IE of your
Windows machine, and see whether a proper XML file is returned. If so, then we can safely ignore the web service test result.
As for automatic signature application, do you mean
Add a signature automatically to every message? Please try to remove the signature and reset it again to check whether the issue persists.
Thanks,
Winnie Liang
TechNet Community Support -
I have looked for hours and hours on Google and this web site for this type of issue and nothing seems to help.
Problem:
On my new Windows 2008 R2 /Exchange 2010 server with IIS7 installed, I can use Outlook 2010 client to login and send and receive e-mail but when I try to busy search internal Exchange users I get no information (cross-hatch), but the sender of the Meeting Request
can see their own free/busy information fine. And OWA users can see free/busy information fine, as can Outlook 2003 client users against this Exchange 2010 server when logged in.
I don't know if I have a certificate problem with regard to IIS7 or Exchange 2010, I did not create my own certificate , it is just what was installed by default when I installed and configured Win2K8 server, IIS7 and Exchange.
On the Windows 7 workstations with Outlook 2010 client, I am not logging into the Exchange 2010 server DNS domain, if that makes any difference. On these workstations I can ping "autodiscover.my.exchange.server.com" and my.exchange.server.com
with no problem. I even used this Microsoft KB to install a new _autodiscover dns entry, but it did not help :
When I turn on logging on my Outlook 2010 client, I see this in my C:\Users\Administrator\AppData\Local\Temp\1\outlook logging\20131208-135658864-fb.log :
2013/12/08 13:56:58.864: Getting ASURL
2013/12/08 13:56:58.864: URL returned from cached autodiscover: blah blah
2013/12/08 13:56:58.864: Request to URL:
2013/12/08 13:56:58.864: Request action:
2013/12/08 13:56:58.864: Request XML: <?xml version="1.0"?>
2013/12/08 13:56:59.051: Request sent
2013/12/08 13:56:59.051: Response error code: 00000000
2013/12/08 13:56:59.051: HTTP status code: 0
2013/12/08 13:56:59.051: -------------------------------
2013/12/08 13:56:59.051: There is an error in request/response.
2013/12/08 13:56:59.051: XML response:
2013/12/08 13:56:59.051: -------------------------------
2013/12/08 13:56:59.051: Getting ASURL
2013/12/08 13:56:59.644: Failed to get ASURL. Error 8004010F
At an Exchange shell console I enter this command and get these results :
Exchnage Management Shell :
VERBOSE: Connecting to BPExchange2010.my.exchange.server.com
VERBOSE: Connected to BPExchange2010.my.exchange.server.com.
[PS] C:\Windows\system32>Test-OutlookWebServices -id:[email protected] -TargetAddress:[email protected]
ll.com
RunspaceId : c929eacd-d53c-49d7-8532-c4b74e61b8be
Id : 1019
Type : Information
Message : A valid Autodiscover service connection point was found. The Autodiscover URL on this object is
Type : Success
Message : [Server] Successfully contacted the UM service at https://bpexchange2010.my.exchange.server.com/ews/exchan
ge.asmx. The elapsed time was 234 milliseconds.
[PS] C:\Windows\system32>
** Also frequently when I log into Outlook 2010 client and start to send a meeting request , I get the Security Alert dialog :
autodiscover.my.exchange.server.com
Information you exchange with this site cannot be viewed or changed by others. However, there is a problem with the site's security certificate.
Green Check Mark : The security cerficate is from a trusted certifying authority
Green Check Mark: The security certificate date is valid
Red X : The name on the security certificate is invalid or does not match the name of the site.
Do you want to proceed ? . I either import the certificate or click YES, but does not help this issue.
NOTE: Each user that shows as NO INFORMATION cross-hatch, these users have appointments and have logged into outlook before.
When I do this autodiscover url from a Windows 7 pc with outlook 2010 I get :
This XML file does not appear to have any style information associated with it. The document tree is shown below.
<Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
<Response>
<Error Time="14:47:01.5656198" Id="401440650">
<ErrorCode>600</ErrorCode>
<Message>Invalid Request</Message>
<DebugData/>
</Error>
</Response>
</Autodiscover>
Can anyone assist ? What am I missing ?
Thank You
NOTE: When will this go away. I had to strip out a lot of helpful information to post this. "Body text cannot contain images or links until we are able to verify your account."Hi,
How many users encounter this issue, all users with Outlook 2010 or some specific users?
According to your post, the Error code 600 indicates that your Autodiscover service is working well. as for the certificate mismatch issue, we can also following the KB below to resolve it:
http://support.microsoft.com/kb/940726/en-us
The Free/Busy information in Exchange 2010 is using the Availability service to
retrieve it. Please directly access
https://mail.mydomain.ae/EWS/Exchange.asmx in IE and see whether a proper XML file is returned.
Or we can go to
https://testexchangeconnectivity.com and check MS Exchange Web Services Connectivity Tests.
Thanks,
Winnie Liang
TechNet Community Support -
I am using Exchange server 2007 i am facing issue activesync,
my users are not able to emails from their smartphones
https://autodiscover.mydomain.com/autodiscover/autodiscover.xml
<?xml version="1.0" encoding="utf-8" ?>
- <Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
- <Response>
- <Error Time="12:31:17.3655146" Id="2053059689">
<ErrorCode>600</ErrorCode>
<Message>Invalid Request</Message>
<DebugData />
</Error>
</Response>
</Autodiscover>
https://mail.mydomain.com/autodiscover/autodiscover.xml
<?xml version="1.0" encoding="utf-8" ?>
- <Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
- <Response>
- <Error Time="12:31:19.5627343" Id="2053059689">
<ErrorCode>600</ErrorCode>
<Message>Invalid Request</Message>
<DebugData />
</Error>
</Response>
</Autodiscover>
[PS] C:\Users\Administrator.Mydomain\Desktop>Test-OutlookWebServices | fl
Id : 1003
Type : Information
Message : About to test AutoDiscover with the e-mail address Administrator@mydomain.
Id : 1007
Type : Information
Message : Testing server MAIL.mydomain with the published name https://mail.mydomain/EWS/Exchange.asmx & .
Id : 1019
Type : Information
Message : Found a valid AutoDiscover service connection point. The AutoDiscover URL on this object is https://mail.mydomain/autodiscover/autodiscover.xml.
Id : 1006
Type : Information
Message : The Autodiscover service was contacted at https://mail.mydomain/autodiscover/autodiscover.xml.
Id : 1016
Type : Success
Message : [EXCH]-Successfully contacted the AS service at https://mail.mydomain/EWS/Exchange.asmx. The elapsed time was 609 milliseconds.
Id : 1015
Type : Information
Message : [EXCH]-The OAB is not configured for this user.
Id : 1014
Type : Success
Message : [EXCH]-Successfully contacted the UM service at https://mail.mydomain/UnifiedMessaging/Service.asmx. The elapsed time was 181 milliseconds.
Id : 1016
Type : Information
Message : [EXPR]-The AS is not configured for this user.
Id : 1015
Type : Information
Message : [EXPR]-The OAB is not configured for this user.
Id : 1014
Type : Information
Message : [EXPR]-The UM is not configured for this user.
Id : 1017
Type : Success
Message : [EXPR]-Successfully contacted the RPC/HTTP service at https://mail.mydomain/Rpc. The elapsed time was 16 milliseconds.
Id : 1006
Type : Success
Message : The Autodiscover service was tested successfully.Hi
Error code 600 is an expected result. that means the Autodiscover directory is working fine.
What error is exchange logging in the application event log regarding users trying to sync phones? Are they domain admins at all? Inheritable permissions ticket?
Maybe you are looking for
-
Can I install Panther & OS 9.2.1 on a Firewire partition?
From reading other posts, it seems that Panther/Classic can be installed on a partitioned Firewire drive. Not quite sure how do do that as other posts were about different issues. Info There's a G3 beige tower that there is no space for, but I'd like
-
How to create a "sunbeam" effect in Illustrator CS3?
A very popular background created in Illustrator seems to be what is sometimes referred to as the sunbeam graphic. A bunch of lines bursting out of the middle, and getting thicker as they move away from the center, to which a gradient is often added.
-
I am importing RAW photos from my Lumix DMC-LX3. Some of the photos I shot in black and white. These photos show as such in the import viewer, but after import they appear in Aperture as color photos with a yellowish-green cast. Why is this happening
-
Can JDE BSSV on 11g be deployed without SSL
I am integrating JDE E1 with FMW SOA 11g. I want to know if BSSVs can be deployed on WLS without SSL. I understand that WLS 10.3.2 had a product limitation. Any help or pointers will be appreciated. Thanks, Ashwani
-
R400: Which LCDs/displays are compatible?
After years of good service, my think pad has a cracked LCD panel. Since the laptop is fine otherwise and I am quite content with it, I would like to replace the panel. The computer is a R400 7439 CT0, the display in question is a 14.1'' WXGA+ LED b