Event 1310 asp.net

more info: Exchange 2013 and 2007 coexist.  I installed 2013 CU9 after upgrading 2007 to CU13.  I am looking at the event viewer because active-sync and auto-discover are not working properly.  2007 users can only connect via smart phone by using legacy.domain.com. Mail.domain.com fails.

using MSRCA I get the error below. In IIS I looked at the Advanced setting for Autodiscover and the Physical path for autodiscover.xml says it is in ...V15\frontend\httpproxy\autodiscover  but it is not there.   I found it in ...v15\clientAccess\Autodiscover.    Is this normal?

The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL https://autodiscover.domain.com:443/Autodiscover/Autodiscover.xml for user me@domain.com.
   The Microsoft Connectivity Analyzer failed to obtain an Autodiscover XML response.

  Additional Details

An HTTP 500 response was returned from Unknown.
  HTTP Response Headers:
  request-id: f3644d3b-613e-43a1-b835-7191377d4891
  X-CalculatedBETarget: exch2013.domain.com
  X-DiagInfo: EXCH2013
  X-BEServer: EXCH2013
  Cache-Control: private
  Content-Type: text/html; charset=utf-8
  Set-Cookie: ClientId=FJVIVFPIURWYLXXJSUW; expires=Tue, 09-Aug-2016 13:39:49 GMT; path=/; HttpOnly,X-BackEndCookie=S-1-5-21-3970167411-3836497950-71674325-1164=u56Lnp2ejJqBx5zLyZ2encjSz8+aytLLxsqZ0p2byMzSyZueyM/Jy8nNzcmagYHNz87K0s/G0s/Gq87MxczGxcvG; expires=Wed, 09-Sep-2015 13:39:49 GMT; path=/Autodiscover; secure; HttpOnly
  Server: Microsoft-IIS/8.5
  X-AspNet-Version: 4.0.30319
  Persistent-Auth: true
  X-Powered-By: ASP.NET
  X-FEServer: EXCH2013
  Date: Mon, 10 Aug 2015 13:39:49 GMT
  Content-Length: 7062


Attempting to contact the Autodiscover service using the HTTP redirect method.
   The attempt to contact Autodiscover using the HTTP Redirect method failed.

  • Edited by bassoml Monday, August 10, 2015 7:23 PM more info
August 10th, 2015 12:38pm

more info: Exchange 2013 and 2007 coexist.  I installed 2013 CU9 after upgrading 2007 to CU13.  I am looking at the event viewer because active-sync and auto-discover are not working properly.  2007 users can only connect via smart phone by using legacy.domain.com. Mail.domain.com fails.

using MSRCA I get the error below. In IIS I looked at the Advanced setting for Autodiscover and the Physical path for autodiscover.xml says it is in ...V15\frontend\httpproxy\autodiscover  but it is not there.   I found it in ...v15\clientAccess\Autodiscover.    Is this normal?

The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL https://autodiscover.domain.com:443/Autodiscover/Autodiscover.xml for user me@domain.com.
   The Microsoft Connectivity Analyzer failed to obtain an Autodiscover XML response.

  Additional Details

An HTTP 500 response was returned from Unknown.
  HTTP Response Headers:
  request-id: f3644d3b-613e-43a1-b835-7191377d4891
  X-CalculatedBETarget: exch2013.domain.com
  X-DiagInfo: EXCH2013
  X-BEServer: EXCH2013
  Cache-Control: private
  Content-Type: text/html; charset=utf-8
  Set-Cookie: ClientId=FJVIVFPIURWYLXXJSUW; expires=Tue, 09-Aug-2016 13:39:49 GMT; path=/; HttpOnly,X-BackEndCookie=S-1-5-21-3970167411-3836497950-71674325-1164=u56Lnp2ejJqBx5zLyZ2encjSz8+aytLLxsqZ0p2byMzSyZueyM/Jy8nNzcmagYHNz87K0s/G0s/Gq87MxczGxcvG; expires=Wed, 09-Sep-2015 13:39:49 GMT; path=/Autodiscover; secure; HttpOnly
  Server: Microsoft-IIS/8.5
  X-AspNet-Version: 4.0.30319
  Persistent-Auth: true
  X-Powered-By: ASP.NET
  X-FEServer: EXCH2013
  Date: Mon, 10 Aug 2015 13:39:49 GMT
  Content-Length: 7062


Attempting to contact the Autodiscover service using the HTTP redirect method.
   The attempt to contact Autodiscover using the HTTP Redirect method failed.

  • Edited by bassoml Monday, August 10, 2015 7:23 PM more info
Free Windows Admin Tool Kit Click here and download it now
August 10th, 2015 12:38pm

more info: Exchange 2013 and 2007 coexist.  I installed 2013 CU9 after upgrading 2007 to CU13.  I am looking at the event viewer because active-sync and auto-discover are not working properly.  2007 users can only connect via smart phone by using legacy.domain.com. Mail.domain.com fails.

using MSRCA I get the error below. In IIS I looked at the Advanced setting for Autodiscover and the Physical path for autodiscover.xml says it is in ...V15\frontend\httpproxy\autodiscover  but it is not there.   I found it in ...v15\clientAccess\Autodiscover.    Is this normal?

The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL https://autodiscover.domain.com:443/Autodiscover/Autodiscover.xml for user me@domain.com.
   The Microsoft Connectivity Analyzer failed to obtain an Autodiscover XML response.

  Additional Details

An HTTP 500 response was returned from Unknown.
  HTTP Response Headers:
  request-id: f3644d3b-613e-43a1-b835-7191377d4891
  X-CalculatedBETarget: exch2013.domain.com
  X-DiagInfo: EXCH2013
  X-BEServer: EXCH2013
  Cache-Control: private
  Content-Type: text/html; charset=utf-8
  Set-Cookie: ClientId=FJVIVFPIURWYLXXJSUW; expires=Tue, 09-Aug-2016 13:39:49 GMT; path=/; HttpOnly,X-BackEndCookie=S-1-5-21-3970167411-3836497950-71674325-1164=u56Lnp2ejJqBx5zLyZ2encjSz8+aytLLxsqZ0p2byMzSyZueyM/Jy8nNzcmagYHNz87K0s/G0s/Gq87MxczGxcvG; expires=Wed, 09-Sep-2015 13:39:49 GMT; path=/Autodiscover; secure; HttpOnly
  Server: Microsoft-IIS/8.5
  X-AspNet-Version: 4.0.30319
  Persistent-Auth: true
  X-Powered-By: ASP.NET
  X-FEServer: EXCH2013
  Date: Mon, 10 Aug 2015 13:39:49 GMT
  Content-Length: 7062


Attempting to contact the Autodiscover service using the HTTP redirect method.
   The attempt to contact Autodiscover using the HTTP Redirect method failed.

  • Edited by bassoml 12 hours 3 minutes ago more info
August 11th, 2015 8:37am

Thanks Ed,

The Exchange Back End has a certificate assigned to port 444 called "Microsoft Exchange" (not my mail.domain.com SAN certificate).

When I browse to the url I get the following:

Server Error in '/Autodiscover' Application.

Configuration Error
  Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

 Parser Error Message: Could not load file or assembly 'Microsoft.Exchange.Security, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.

Source Error:

Line 39:         <!--add assembly="Microsoft.Exchange.Common, Version=8.0.00207.0, Culture=neutral, publicKeyToken=31bf3856ad364e35"/-->
Line 40:         <!--add assembly="Microsoft.Exchange.Data.Common, Version=8.0.00207.0, Culture=neutral, publicKeyToken=31bf3856ad364e35"/-->
Line 41:         <add assembly="Microsoft.Exchange.Security, Version=15.0.0.0, Culture=neutral, publicKeyToken=31bf3856ad364e35" />
Line 42:       </assemblies>
Line 43:     </compilation>

 Source File:  C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\Autodiscover\web.config    Line:  41

Assembly Load Trace: The following information can be helpful to determine why the assembly 'Microsoft.Exchange.Security, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' could not be loaded.

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

 


Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.34248

Free Windows Admin Tool Kit Click here and download it now
August 11th, 2015 9:13am

I think your problem is beyond what we can do for you here.  I recommend you open a ticket with Microsoft Support.
August 11th, 2015 1:37pm

First, try connecting to the Autodiscover URL using a browser.

Also make sure that the Exchange Back End website in IIS has the self-signed certificate bound

Free Windows Admin Tool Kit Click here and download it now
August 12th, 2015 12:54am

I upgraded to Exchange 2013 this weekend. Active sync, autodiscover and OWA (somewhat) not working.  I am getting the following warnings in the event viewer every few seconds.  One for just about every virtual directory (active sync, autodiscover, OWA, etc...)  Any help much appreciated.

Event code: 3008

Event message: A configuration error has occurred.

Event time: 8/10/2015 12:45:46 AM

Event time (UTC): 8/10/2015 4:45:46 AM

Event ID: 2db32c4626c6467e96fbd51e877d5698

Event sequence: 1

Event occurrence: 1

Event detail code: 0

Application information:

    Application domain: /LM/W3SVC/2/ROOT/Microsoft-Server-ActiveSync-163-130836555466260814

    Trust level: Full

    Application Virtual Path: /Microsoft-Server-ActiveSync

    Application Path: C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\sync\

    Machine name: EXCH2013

Process information:

    Process ID: 23436

    Process name: w3wp.exe

    Account name: NT AUTHORITY\SYSTEM

Exception information:

    Exception type: ConfigurationErrorsException

    Exception message: Could not load file or assembly 'Microsoft.Exchange.Security, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified. (C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\sync\web.config line 248)

   at System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective)

   at System.Web.Configuration.AssemblyInfo.get_AssemblyInternal()

   at System.Web.Compilation.BuildManager.GetReferencedAssemblies(CompilationSection compConfig)

   at System.Web.Compilation.BuildManager.CallPreStartInitMethods(String preStartInitListPath, Boolean& isRefAssemblyLoaded)

   at System.Web.Compilation.BuildManager.ExecutePreAppStart()

   at System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters, PolicyLevel policyLevel, Exception appDomainCreationException)

Could not load file or assembly 'Microsoft.Exchange.Security, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.

   at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)

   at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)

   at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean forIntrospection)

   at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)

   at System.Reflection.Assembly.Load(String assemblyString)

   at System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective)

Request information:

    Request URL: https://exch2013.bcsdny.org:444/Microsoft-Server-ActiveSync/Proxy/default.eas?Cmd=Ping&User=apatrick1258@bcsdny.org&DeviceId=android1074080&DeviceType=Android

    Request path: /Microsoft-Server-ActiveSync/Proxy/default.eas

    User host address: fe80::9561:f196:4010:3ed9C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\sync\

    User: 

    Is authenticated: False

    Authentication Type: 

    Thread account name: NT AUTHORITY\SYSTEM

Thread information:

    Thread ID: 64

    Thread account name: NT AUTHORITY\SYSTEM

    Is impersonating: False

    Stack trace:    at System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective)

   at System.Web.Configuration.AssemblyInfo.get_AssemblyInternal()

   at System.Web.Compilation.BuildManager.GetReferencedAssemblies(CompilationSection compConfig)

   at System.Web.Compilation.BuildManager.CallPreStartInitMethods(String preStartInitListPath, Boolean& isRefAssemblyLoaded)

   at System.Web.Compilation.BuildManager.ExecutePreAppStart()

   at System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters, PolicyLevel policyLevel, Exception appDomainCreationException)

Custom event details:

August 12th, 2015 12:59am

You didn't share what CU you installed, and what version you "upgraded" from and how you did it.  Based on very limited information (nothing more than part of an event log message), I would advise that you remove and reinstall.  Maybe with a lot more information I or someone else could offer something better.
Free Windows Admin Tool Kit Click here and download it now
August 12th, 2015 1:03am

I opened a ticket with Microsoft:

Problem: OWA fails when new 2013 user accounts attempt to log on

Fix 1: %systemroot%\Program Files\Microsoft\Exchange Server\V15\ClientAccess\SharedWebConfig.config was missing.  The tech created an empty file and copied the contents from the same file from his lab environment

Fix 2: In IIS on the 2013 server, he removed the HTTP Redirect from the Exchange Back End site

Problem: both 2007 users and 2013 users cannot get email on their mobile devices due to autodiscover and active-sync issues

Fix:

  • With Fix 1 and 2 being already applied, ExRCA now only produced a 403 error on Active-Sync.In
  • IIS on Exchange 2013 server, the 2 binding for 127.0.0.1 were missing.  One for port 80 and the other for port 443. Be sure to apply the 3rd party certificate for mail.mydomain.com to 443
  • On 2007 Exchange CAS server, in Exchange Management Console, removed the external URL from Microsoft-Server-ActiveSync found in Server Configuration - Client Access - Exchange ActiveSync
  • On 2007 Exchange CAS Server Enabled Windows Authentication on Active Sync via:

Get-ActiveSyncVirtualDirectory -Server exchcas01 | Set-ActiveSyncVirtualDirectory -WindowsAuthEnabled $true

  • Marked as answer by bassoml 19 hours 10 minutes ago
August 12th, 2015 8:19am

Hi,

Please confirm whether the SharedWebConfig.config is missing in the following path:

c:\program files\microsoft\Exchange server\v15\clientaccess\

If that is the case, please copy the sharedewebconfig file from a worked server and paste it to appropriate destination on problem server.  Then restart IIS service by running IISReset from a command prompt window to have a try.

Regards,

Free Windows Admin Tool Kit Click here and download it now
August 12th, 2015 8:38am

Thanks Winnie,

If your response came a few hours earlier, I may have saved $500.00.  But yes, that missing file was a big missing piece of the puzzle.  Most everything else I mentioned in my earlier post I had changed in my frantic attempt to "try something different" to get it to work.

August 12th, 2015 10:11am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics