cw1972
Posts: 54
Joined: 10.Jan.2007
From: Sheffield
Status: offline
|
Hello - I know this board is for OWA issues, but I thought it was appropriate to post an OMA issue here too.
Recently I changed my installed ASP.NET version from v1.1.4322 to v2.0.50727 using the apsnet_regiis.exe command, I just found out yesterday that this broke my OMA access, resulting in a variety of differing errors
Acessing http://exchangeserver/oma - give as http 500 Internal Server error
I tried many combinations of reverting back to v1.1.4322, removing all installed versions and putting on v1.1.4322 back on alone, setting v2.0.50727 to "Prohibit" in IIS Mnanger, nothing worked.
So I took the step of letting Exchange recreate the virtual OMA directory back to the defaults by follwing the steps here: http://support.microsoft.com/kb/883380/en-us
No change.
So I created a new OMA virtual directory under the root of the Virtual HTTP server, choosing the OMA setting for the Exchange path
Now accessing http://exchangeserver/oma2 gives me a:
"Server Error in '/oma2' Application.
--------------------------------------------------------------------------------
Runtime Error "
Yet accessing that page directly from the server itself gives me a blank page and an entry in the Application Event Log:
Source: MSExchangeOMA - EventID: 1503
An unknown error occurred while processing the current request:
Message: There can be only one 'page' directive.
Source: System.Web
Stack trace:
at System.Web.UI.TemplateParser.ProcessError(String message)
at System.Web.UI.TemplateParser.ProcessDirective(String directiveName, IDictionary directive)
at System.Web.UI.BaseTemplateParser.ProcessDirective(String directiveName, IDictionary directive)
at System.Web.UI.TemplateControlParser.ProcessDirective(String directiveName, IDictionary directive)
at System.Web.UI.PageParser.ProcessDirective(String directiveName, IDictionary directive)
at System.Web.UI.TemplateParser.ParseStringInternal(String text, Encoding fileEncoding)
Message: There can be only one 'page' directive.
Source: System.Web
Stack trace:
at System.Web.UI.TemplateParser.ProcessException(Exception ex)
at System.Web.UI.TemplateParser.ParseStringInternal(String text, Encoding fileEncoding)
at System.Web.UI.TemplateParser.ParseString(String text, VirtualPath virtualPath, Encoding fileEncoding)
Message: There can be only one 'page' directive.
Source: System.Web
Stack trace:
at System.Web.UI.TemplateParser.ParseString(String text, VirtualPath virtualPath, Encoding fileEncoding)
at System.Web.UI.TemplateParser.ParseFile(String physicalPath, VirtualPath virtualPath)
at System.Web.UI.TemplateParser.ParseInternal()
at System.Web.UI.TemplateParser.Parse()
at System.Web.Compilation.BaseTemplateBuildProvider.get_CodeCompilerType()
at System.Web.Compilation.BuildProvider.GetCompilerTypeFromBuildProvider(BuildProvider buildProvider)
at System.Web.Compilation.BuildProvidersCompiler.ProcessBuildProviders()
at System.Web.Compilation.BuildProvidersCompiler.PerformBuild()
at System.Web.Compilation.BuildManager.CompileWebFile(VirtualPath virtualPath)
at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile)
at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile)
at System.Web.Compilation.BuildManager.GetVirtualPathObjectFactory(VirtualPath virtualPath, HttpContext context, Boolean allowCrossApp, Boolean noAssert)
at System.Web.Compilation.BuildManager.CreateInstanceFromVirtualPath(VirtualPath virtualPath, Type requiredBaseType, HttpContext context, Boolean allowCrossApp, Boolean noAssert)
at System.Web.UI.PageHandlerFactory.GetHandlerHelper(HttpContext context, String requestType, VirtualPath virtualPath, String physicalPath)
at System.Web.UI.PageHandlerFactory.System.Web.IHttpHandlerFactory2.GetHandler(HttpContext context, String requestType, VirtualPath virtualPath, String physicalPath)
at System.Web.HttpApplication.MapHttpHandler(HttpContext context, String requestType, VirtualPath path, String pathTranslated, Boolean useAppConfig)
at System.Web.HttpApplication.MapHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
I have also been getting entries in the System Event Log:
Source: W3SVC - EventID 1009
A process serving application pool 'ExchangeMobileBrowseApplicationPool' terminated unexpectedly. The process id was '1120'. The process exit code was '0xe0434f4d'.
Searching for The process exit code was '0xe0434f4d'. let me to http://support.microsoft.com/kb/911816 - which describe my issues, but the stated fixes make no dofference.
One page talked about the NETWORK/NETWORK SERVICE not have write access to the TEMP directory being an issue, but adding this made no difference either, even though it would seem that some process is trying to write an XML file there (mmc2C6C32A5.xml) at 0bytes.
For further information, I've also been getting these errors logged in Application Event Log around to times of attempted access.
Source: .NET Runtime 2.0 Error Reporting - EventID 5000
EventType clr20r3, P1 w3wp.exe, P2 6.0.3790.3959, P3 45d6968e, P4 microsoft.exchange.oma.userinterface, P5 6.5.0.0, P6 430e745e, P7 463, P8 0, P9 system.nullreferenceexception, P10 NIL.
Source: ASP.NET 2.0.50727.0 - EventID 1309
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 01/05/2007 08:29:09
Event time (UTC): 01/05/2007 07:29:09
Event ID: e1847106658b46348327b7cbe181f296
Event sequence: 2
Event occurrence: 1
Event detail code: 0
Application information:
Application domain: /LM/W3SVC/1/root/oma2-1-128224781495391251
Trust level: Full
Application Virtual Path: /oma2
Application Path: C:\Program Files\Exchsrvr\OMA\Browse\
Machine name: SHEFF-W2K3-EX01
Process information:
Process ID: 1820
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://exchangeserver/oma2/oma.aspx
Request path: /oma2/oma.aspx
User host address:
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()
These last two errors haven't happened in a while though.
Now I'm a bit stumped as to what to do.
< Message edited by cw1972 -- 1.May2007 4:43:14 AM >
|
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
Printable Version
Limited time MSExchange.org offer! -- 1.Sep.2008 1:00:00 PM
changing the installed ASP.NETversion broke my OMA - 
New Messages
No New Messages
Hot Topic w/ New Messages
Hot Topic w/o New Messages
Locked w/ New Messages
Locked w/o New Messages
Post New Thread