asked on

Event id 1310 event code 3008 ASP.net 4.0.30319.0 configuration error

I have an Exchange2010 running on SBS2011 with multiple users with email on their smartphones. Some of the users have iphones and some have blackberries. It appears that every time one of the blackberry users is fetching his/her email, they get their emails but I get the following error on the event log:

Event code: 3008
Event message: A configuration error has occurred.
Event time: 7/4/2012 12:36:43 PM
Event time (UTC): 7/4/2012 4:36:43 PM
Event ID: 09e9b56b0bde480fb42a3957d804d931
Event sequence: 290
Event occurrence: 289
Event detail code: 0

Application information:
Application domain: /LM/W3SVC/1/ROOT-1-129858787968147086
Trust level: Full
Application Virtual Path: /
Application Path: C:\inetpub\wwwroot\
Machine name: domain-name-THO

Process information:
Process ID: 14852
Process name: w3wp.exe
Account name: NT AUTHORITY\NETWORK SERVICE

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://mail.<domain-name>.com:443/exchange/<userloginname>
Request path: /exchange/<userloginname>
User host address: 74.82.82.111
User:
Is authenticated: False
Authentication Type:
Thread account name: NT AUTHORITY\NETWORK SERVICE

Thread information:
Thread ID: 36
Thread account name: NT AUTHORITY\NETWORK SERVICE
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:

How can I get rid of this error?

Cris Hanna

Is blackberry the only type of smart phone you ? Based on the IP address information in error message, I'm wonding if the problem isn't in the with the Blackberry service. Are you using a BES server as well?

ivolach

ASKER

I am not using BES servers.
We also have users with iphone but I don't get an error for them.
Blackberries are getting the email but I see the error message in the server event log.

Cris Hanna

Unless something has changed since I last checked (and none of my customers use crackberry's :-) ) they can't do direct Exchange Active Sync like the Iphone can

And since you don't see the issue with the Iphones, it would appear the issue is caused by whatever is providing the interface between SBS/Exchange and the devices.

Jeffrey Kane - TechSoEasy

@CrisHannah -- Some Blackberry devices will fetch email from Exchange using OWA.

@ivolach -- Please see this troubleshooting article to help you resolve your BIS devices:
http://www.blackberry.com/btsc/KB02858

And this is the basic setup article: http://www.blackberry.com/btsc/KB03133

Jeff
TechSoEasy

ivolach

ASKER

Let me clarify:
1. Blackberry users are getting their emails on their Blackberry, so it is working but generating the error message in the event log.

2. BIS service is provided by the ISP (Rogers, Bell). The users define and manage the account on the ISP site. Again, everything is working except for the error message.

3. everything seems to be setup as per the articles Jeff has pointed to.

Jeffrey Kane - TechSoEasy

Have you contacted your ISP to inquire about the error messages? It may be something they have configured wrong.

Jeff
TechSoEasy

ivolach

ASKER

I have not contacted the ISP - waste of time.
Since everybody gets their emails, I'll live with the error for now.

Thanks.

Jeffrey Kane - TechSoEasy

Really? Then why even post a question if you don't want to resolve it?

Jeff
TechSoEasy

ivolach

ASKER

I do want to resolve it but since I have posted it, many other issues came up making this issue a minor nuisance for which a I have no time right now - it is all about priorities. I may come back to it at a later time when the other more pressing problems are resolved.

Thanks,

ASKER CERTIFIED SOLUTION

Jeffrey Kane - TechSoEasy

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

ivolach

ASKER

Thank you for this work around, it'll help reduce the 'noise'

sWninja

ivolach: I too fought with this- the answer is mind-numbingly simple once you realize it--

sbs 2011 breaks the "/exchange" access point-- go to your blackberry enterprise server, or wherever you setup your bb email at- and change the <yourdomain>.tld/exhcnage to <yourdomain>.tld/owa and the problem is fixed..

this is not very well documented anywhere- as a "break" when moving through previous versions of SBS

this is no "workaround" this is the answer.

ivolach

ASKER

Thank you for the suggestions. I will have hard time trying to fix it since it is done on the ISP for the individual users and I don't have access to it.

Thanks,