locked
Event ID 1310 error RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    We're seeing this warning in our Exchange 2010 event logs. I've done some looking on the KB but there doesn't seem to be a good explanation of what might be going on here. This server is Exchange 2010 SP1 with all rollups (save the latest one rollup 5 which isn't out on Windows Update yet)

    Anyone have any tips on what this is? Our IIS configuration should be fairly vanilla as this server host Exchange only,

     

    Log Name:      Application
    Source:        ASP.NET 4.0.30319.0
    Date:          9/19/2011 8:51:05 AM
    Event ID:      1310
    Task Category: Web Event
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:      MAIL.rf.ohio-state.edu
    Description:
    Event code: 3008
    Event message: A configuration error has occurred.
    Event time: 9/19/2011 8:51:05 AM
    Event time (UTC): 9/19/2011 12:51:05 PM
    Event ID: 12dea4fa59ff49f98c0247de0916edf0
    Event sequence: 2027
    Event occurrence: 297
    Event detail code: 0
     
    Application information:
        Application domain: /LM/W3SVC/1/ROOT-1-129598328637575000
        Trust level: Full
        Application Virtual Path: /
        Application Path: C:\inetpub\wwwroot\
        Machine name: MAIL
     
    Process information:
        Process ID: 3996
        Process name: w3wp.exe
        Account name: IIS APPPOOL\DefaultAppPool
     
    Exception information:
        Exception type: ConfigurationErrorsException
        Exception message: It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level.  This error can be caused by a virtual directory not being configured as an application in IIS. (C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\owa\web.config line 37)
       at System.Configuration.ConfigurationSchemaErrors.ThrowIfErrors(Boolean ignoreLocal)
       at System.Configuration.BaseConfigurationRecord.GetSectionRecursive(String configKey, Boolean getLkg, Boolean checkPermission, Boolean getRuntimeObject, Boolean requestIsHere, Object& result, Object& resultRuntimeObject)
       at System.Configuration.BaseConfigurationRecord.GetSection(String configKey)
       at System.Web.Configuration.RuntimeConfig.GetSectionObject(String sectionName)
       at System.Web.Configuration.RuntimeConfig.GetSection(String sectionName, Type type, ResultsIndex index)
       at System.Web.Configuration.RuntimeConfig.get_Identity()
       at System.Web.HttpContext.SetImpersonationEnabled()
       at System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context)

     
     
    Request information:
        Request URL: https://131.187.90.221:443/exchange/?P='
        Request path: /exchange/
        User host address: 131.187.90.157
        User: 
        Is authenticated: False
        Authentication Type: 
        Thread account name: IIS APPPOOL\DefaultAppPool
     
    Thread information:
        Thread ID: 5617
        Thread account name: IIS APPPOOL\DefaultAppPool
        Is impersonating: False
        Stack trace:    at System.Configuration.ConfigurationSchemaErrors.ThrowIfErrors(Boolean ignoreLocal)
       at System.Configuration.BaseConfigurationRecord.GetSectionRecursive(String configKey, Boolean getLkg, Boolean checkPermission, Boolean getRuntimeObject, Boolean requestIsHere, Object& result, Object& resultRuntimeObject)
       at System.Configuration.BaseConfigurationRecord.GetSection(String configKey)
       at System.Web.Configuration.RuntimeConfig.GetSectionObject(String sectionName)
       at System.Web.Configuration.RuntimeConfig.GetSection(String sectionName, Type type, ResultsIndex index)
       at System.Web.Configuration.RuntimeConfig.get_Identity()
       at System.Web.HttpContext.SetImpersonationEnabled()
       at System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context)
     
     
    Custom event details:

    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="ASP.NET 4.0.30319.0" />
        <EventID Qualifiers="32768">1310</EventID>
        <Level>3</Level>
        <Task>3</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2011-09-19T12:51:05.000000000Z" />
        <EventRecordID>237774</EventRecordID>
        <Channel>Application</Channel>
        <Computer>MAIL.rf.ohio-state.edu</Computer>
        <Security />
      </System>
      <EventData>
        <Data>3008</Data>
        <Data>A configuration error has occurred.</Data>
        <Data>9/19/2011 8:51:05 AM</Data>
        <Data>9/19/2011 12:51:05 PM</Data>
        <Data>12dea4fa59ff49f98c0247de0916edf0</Data>
        <Data>2027</Data>
        <Data>297</Data>
        <Data>0</Data>
        <Data>/LM/W3SVC/1/ROOT-1-129598328637575000</Data>
        <Data>Full</Data>
        <Data>/</Data>
        <Data>C:\inetpub\wwwroot\</Data>
        <Data>MAIL</Data>
        <Data>
        </Data>
        <Data>3996</Data>
        <Data>w3wp.exe</Data>
        <Data>IIS APPPOOL\DefaultAppPool</Data>
        <Data>ConfigurationErrorsException</Data>
        <Data>It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level.  This error can be caused by a virtual directory not being configured as an application in IIS. (C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\owa\web.config line 37)
       at System.Configuration.ConfigurationSchemaErrors.ThrowIfErrors(Boolean ignoreLocal)
       at System.Configuration.BaseConfigurationRecord.GetSectionRecursive(String configKey, Boolean getLkg, Boolean checkPermission, Boolean getRuntimeObject, Boolean requestIsHere, Object&amp; result, Object&amp; resultRuntimeObject)
       at System.Configuration.BaseConfigurationRecord.GetSection(String configKey)
       at System.Web.Configuration.RuntimeConfig.GetSectionObject(String sectionName)
       at System.Web.Configuration.RuntimeConfig.GetSection(String sectionName, Type type, ResultsIndex index)
       at System.Web.Configuration.RuntimeConfig.get_Identity()
       at System.Web.HttpContext.SetImpersonationEnabled()
       at System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context)

    </Data>
        <Data>https://131.187.90.221:443/exchange/?P='</Data>
        <Data>/exchange/</Data>
        <Data>131.187.90.157</Data>
        <Data>
        </Data>
        <Data>False</Data>
        <Data>
        </Data>
        <Data>IIS APPPOOL\DefaultAppPool</Data>
        <Data>5617</Data>
        <Data>IIS APPPOOL\DefaultAppPool</Data>
        <Data>False</Data>
        <Data>   at System.Configuration.ConfigurationSchemaErrors.ThrowIfErrors(Boolean ignoreLocal)
       at System.Configuration.BaseConfigurationRecord.GetSectionRecursive(String configKey, Boolean getLkg, Boolean checkPermission, Boolean getRuntimeObject, Boolean requestIsHere, Object&amp; result, Object&amp; resultRuntimeObject)
       at System.Configuration.BaseConfigurationRecord.GetSection(String configKey)
       at System.Web.Configuration.RuntimeConfig.GetSectionObject(String sectionName)
       at System.Web.Configuration.RuntimeConfig.GetSection(String sectionName, Type type, ResultsIndex index)
       at System.Web.Configuration.RuntimeConfig.get_Identity()
       at System.Web.HttpContext.SetImpersonationEnabled()
       at System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context)
    </Data>
      </EventData>
    </Event>

    Monday, September 19, 2011 1:23 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks for the info. I ended up restoring an IIS configuration backup I made before the conversion to address this issue.
    • Proposed as answer by Martina_Miskovic Monday, September 26, 2011 5:03 AM
    • Marked as answer by Fiona_Liao Tuesday, September 27, 2011 6:02 AM
    Sunday, September 25, 2011 10:06 PM

All replies

  • Question
    Sign in to vote
    1
    Sign in to vote

    Hi,

    Have you verified the configuration of your OWA Virtual Directory?

    What about the authentication for that Virtual Directory, how has it been configured?

    Grts,

    Michael

    __________________________________
    Michael Van Horenbeeck Check out my blog @ Pro-Exchange (Belgian Usergroup)
    Monday, September 19, 2011 8:06 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    This error indicates that the Exchange virtual directory in IIS is not an Application.  To correct this issue you should open the IIS Manager and expand the sites and the Default Web Site so that you can see the Exchange virtual directory.  Right click on it and select Convert to Application. Then run the IISRESET /noforce in cmd in run.

    Besides, verify the authentication in /OWA, make sure it is "Basic". 

    Let me know if you have further question.

    Fiona
    • Proposed as answer by Fiona_Liao Wednesday, September 21, 2011 3:13 AM
    Wednesday, September 21, 2011 3:12 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Some of the Virtual Directories in IIS is and should not be an Application in IIS and those are:
    /Exchange
    /Exchweb
    /OAB
    /Public

    ...and that is by design, so I wouldn´t change that.


    I would investigate why 131.187.90.157 is connecting to https://131.187.90.221:443/exchange/?P='

    Martina Miskovic - http://www.nic2012.com/
    Wednesday, September 21, 2011 4:23 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I'm now seeing this error, any advice on how I can fix this issue?

    Log Name:      Application
    Source:        MSExchange OWA
    Date:          9/21/2011 4:21:35 PM
    Event ID:      64
    Task Category: ADNotifications
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      mail
    Description:
    The Outlook Web App configuration settings couldn't be read and updated. Virtual directory: "Exchange". Web site: "Default Web Site".
    Error message:
    "The Active Directory configuration settings couldn't be accessed for virtual directory "Exchange" under Web site "Default Web Site"."
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MSExchange OWA" />
        <EventID Qualifiers="49152">64</EventID>
        <Level>2</Level>
        <Task>8</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2011-09-21T20:21:35.000000000Z" />
        <EventRecordID>239190</EventRecordID>
        <Channel>Application</Channel>
        <Computer>MAIL</Computer>
        <Security />
      </System>
      <EventData>
        <Data>Exchange</Data>
        <Data>Default Web Site</Data>
        <Data>The Active Directory configuration settings couldn't be accessed for virtual directory "Exchange" under Web site "Default Web Site".</Data>
      </EventData>
    </Event>

    Thursday, September 22, 2011 1:27 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

     

    How about the event id 1310? Is it disappearing? If yes, don't forget to mark the answer.

     

    Regarding the event id 64, this event may occur if the Web site that hosts the Outlook Web Access virtual directories was removed but the directories still have references to the Web site. Just for your reference, you  may try the KB below for troubleshooting:

     

    KB930864

    http://support.microsoft.com/kb/930864

    Event ID 64

    http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Exchange&ProdVer=8.0&EvtID=64&EvtSrc=MSExchange%20OWA&LCID=1033

     

    if the event id 64 continues, I’d suggest you submit a new thread because it might not related to the original event id 1310 issue in this thread. Troubleshooting multiple issues in the same thread may cause confusion. Your understanding would be appreciated.

     

    Just a reminder, when you poste a new thread, please describe your Exchange organization topology and the scenario or how can you reproduce the event ID 64. The information can help us research.

     

    Thanks.

    Fiona
    • Edited by Fiona_Liao Thursday, September 22, 2011 8:31 AM
    Thursday, September 22, 2011 8:30 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    The default web site (where OWA lives) has not been deleted. The only thing that I modified was to convert the exchange virtual directory to a application as suggested above. That is when the event 64s started. I did begin a new thred where someone suggested restoring the old IIS configuration. Which application pool should the Exchange directory be part of? MSExchOWA is where I put it.

    Thursday, September 22, 2011 10:08 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi P.Bossley,
    I think you should delete the converted /Exchange legacy virtual directory. As I wrote before, it should not be configured as an application in IIS.

    How to recreate the legacy Exchange Virtual Directories in Exchange 2010?
    http://blogs.technet.com/b/exchange/archive/2010/02/10/3409322.aspx
    Martina Miskovic - http://www.nic2012.com/
    Sunday, September 25, 2011 8:40 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks for the info. I ended up restoring an IIS configuration backup I made before the conversion to address this issue.
    • Proposed as answer by Martina_Miskovic Monday, September 26, 2011 5:03 AM
    • Marked as answer by Fiona_Liao Tuesday, September 27, 2011 6:02 AM
    Sunday, September 25, 2011 10:06 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks. it is great to know the issue is resolved.
    Fiona
    Tuesday, September 27, 2011 6:02 AM