|
|
|
Question : Errors acessing OMA virtual directory
|
|
ANY HELP WILL BE HIGHLY APPRECIATTED!
BACKGROUND:
System: SBS2003 Premium, SP1, Exchange SP2. Default Web Site with self-signed SSL cert.
1.- Initially 3rd party developers installed the production web site under Default Web site and changed the home directory to the web app folder. They required ASP.NET V 1.X so the Default Web Site was changed from 2.0 to 1.X. No problems with the app
2.- When Exchanged was setup, we discovered issues accessing OWA. The issue was fixed by setting the Exchange virtual directory to ASP.NET 2.0. No problems with the app nor OWA.
3.- Then, we needed to start using Exchange ActiveSync. We took the app out of the Default Web Site and changed Default Web Site and all its virtual directories to ASP.NET 2.0 (except RPC and tsweb). No problem with the app nor OWA.
OMA virtual directory security is set not to accept anonymous and only basic auth.
Every time we access the OMA folder, HTTP or HTTPS, we get and error on the browser (below) and on the server the following entries are added in the logs:
Event Type: Warning
Event Source: ASP.NET 2.0.50727.0
Event Category: Web Event
Event ID: 1309
Date: 9/10/2006
Time: 9:19:16 PM
User: N/A
Computer: KPI
Description:
Event code: 3005 Event message: An unhandled exception has occurred. Event time: 9/10/2006 9:19:16 PM Event time (UTC): 9/11/2006 1:19:16 AM Event ID: 7ff336d39a124a93b0c2a3d56dab5c27 Event sequence: 2 Event occurrence: 1 Event detail code: 0 Application information: Application domain: /LM/W3SVC/1/root/OMA-1-128024111561470814 Trust level: Full Application Virtual Path: /OMA Application Path: C:\Program Files\Exchsrvr\OMA\Browse\ Machine name: KPI Process information: Process ID: 5048 Process name: w3wp.exe Account name: NT AUTHORITY\NETWORK SERVICE Exception information: Exception type: InvalidOperationException Exception message: Collection was modified; enumeration operation may not execute. Request information: Request URL: http://team.network4leaders.com/oma/oma.aspx Request path: /oma/oma.aspx User host address: 65.99.192.151 User: Is authenticated: False Authentication Type: Thread account name: NT AUTHORITY\NETWORK SERVICE Thread information: Thread ID: 1 Thread account name: NT AUTHORITY\NETWORK SERVICE Is impersonating: False Stack trace: at System.Collections.ArrayList.ArrayListEnumeratorSimple.MoveNext()
at Microsoft.Exchange.OMA.Tracing.OmaTrace.set_DebugOutputTracing(Boolean value)
at Microsoft.Exchange.OMA.UserInterface.Global..ctor()
at ASP.global_asax..ctor()
Custom event details:
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Error
Event Source: .NET Runtime 2.0 Error Reporting
Event Category: None
Event ID: 5000
Date: 9/10/2006
Time: 9:19:09 PM
User: N/A
Computer: KPI
Description:
EventType clr20r3, P1 w3wp.exe, P2 6.0.3790.1830, P3 42435be1, P4 microsoft.exchange.oma.userinterface, P5 6.5.0.0, P6 430e745e, P7 463, P8 0, P9 system.nullreferenceexception, P10 NIL.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Error
Event Source: MSExchangeOMA
Event Category: (1000)
Event ID: 1503
Date: 9/10/2006
Time: 9:19:09 PM
User: N/A
Computer: KPI
Description:
An unknown error occurred while processing the current request:
Message: Unrecognized attribute 'SessionStateHistorySize'. Note that attribute names are case-sensitive. (C:\Program Files\Exchsrvr\OMA\Browse\web.config line 99)
Source: System.Configuration
Stack trace:
at System.Configuration.BaseConfigurationRecord.EvaluateOne(String[] keys, SectionInput input, Boolean isTrusted, FactoryRecord factoryRecord, SectionRecord sectionRecord, Object parentResult)
at System.Configuration.BaseConfigurationRecord.Evaluate(FactoryRecord factoryRecord, SectionRecord sectionRecord, Object parentResult, Boolean getLkg, Boolean getRuntimeObject, Object& result, Object& resultRuntimeObject)
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, Boolean getLkg, Boolean checkPermission)
at System.Configuration.BaseConfigurationRecord.GetSection(String configKey)
at System.Web.HttpContext.GetSection(String sectionName)
at System.Web.UI.MobileControls.ControlsConfig.GetFromContext(HttpContext context)
at System.Web.UI.MobileControls.MobilePage.get_RequestingDeviceConfig()
at System.Web.UI.MobileControls.MobilePage.get_Adapter()
at System.Web.UI.MobileControls.MobilePage.OnUnload(EventArgs e)
at System.Web.UI.Control.UnloadRecursive(Boolean dispose)
at System.Web.UI.Page.UnloadRecursive(Boolean dispose)
at System.Web.UI.Page.ProcessRequestCleanup()
at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest()
at System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context)
at System.Web.UI.Page.ProcessRequest(HttpContext context)
at ASP.oma_aspx.ProcessRequest(HttpContext context)
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Error
Event Source: MSExchangeOMA
Event Category: (1000)
Event ID: 1503
Date: 9/10/2006
Time: 9:19:03 PM
User: N/A
Computer: KPI
Description:
An unknown error occurred while processing the current request:
Message: Method not found: 'System.String System.DirectoryServices.DirectoryEntry.get_Password()'.
Source: Microsoft.Exchange.OMA.Preferencing
Stack trace:
at Microsoft.Exchange.OMA.Preferencing.AdUserObject.get_globalWirelessEnable()
at Microsoft.Exchange.OMA.Preferencing.AdUserObject.get_UserIsWirelesslyEnabled()
at Microsoft.Exchange.OMA.Preferencing.OmaUserInfo.get_UserIsWirelesslyEnabled()
at Microsoft.Exchange.OMA.UserInterface.Global.Session_Start(Object sender, EventArgs e)
Message: Exception of type 'Microsoft.Exchange.OMA.DataProviderInterface.ProviderException' was thrown.
EventMessage:
UserMessage: A System error has occurred while processing your request. Please try again. If the problem persists, contact your administrator.
Source: Microsoft.Exchange.OMA.UserInterface
Stack trace:
at Microsoft.Exchange.OMA.UserInterface.Global.Session_Start(Object sender, EventArgs e)
at System.Web.SessionState.SessionStateModule.RaiseOnStart(EventArgs e)
at System.Web.SessionState.SessionStateModule.CompleteAcquireState()
at System.Web.SessionState.SessionStateModule.BeginAcquireState(Object source, EventArgs e, AsyncCallback cb, Object extraData)
at System.Web.HttpApplication.AsyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
BROWSER ERROR:
Server Error in '/OMA' Application.
--------------------------------------------------------------------------------
Collection was modified; enumeration operation may not execute.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.InvalidOperationException: Collection was modified; enumeration operation may not execute.
Source Error:
The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:
1. Add a "Debug=true" directive at the top of the file that generated the error. Example:
<%@ Page Language="C#" Debug="true" %>
or:
2) Add the following section to the configuration file of your application:
Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.
Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.
Stack Trace:
[InvalidOperationException: Collection was modified; enumeration operation may not execute.]
System.Collections.ArrayListEnumeratorSimple.MoveNext() +2754446
Microsoft.Exchange.OMA.Tracing.OmaTrace.set_DebugOutputTracing(Boolean value) +167
Microsoft.Exchange.OMA.UserInterface.Global..ctor() +262
ASP.global_asax..ctor() +5
[TargetInvocationException: Exception has been thrown by the target of an invocation.]
System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandle& ctor, Boolean& bNeedSecurityCheck) +0
System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean fillCache) +103
System.RuntimeType.CreateInstanceImpl(Boolean publicOnly, Boolean skipVisibilityChecks, Boolean fillCache) +261
System.Activator.CreateInstance(Type type, Boolean nonPublic) +66
System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes) +1036
System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes) +114
System.Web.HttpApplicationFactory.GetNormalApplicationInstance(HttpContext context) +184
System.Web.HttpApplicationFactory.GetApplicationInstance(HttpContext context) +106
System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) +214
--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.42
|
Answer : Errors acessing OMA virtual directory
|
|
There is nothing in Exchange 2003 that uses asp.net 2.0 so you could remove it.
You are constantly getting the same error: (501) Not Implemented
Therefore I suspect that there is a single underlying cause - the problem is finding it.
Simon.
|
|
|
|
|
|
|
