Server Error in '/OMA' Application.

Server Error in '/OMA' Application.

Post by SWFu » Wed, 30 Aug 2006 03:40:02


I am receiving the following error after logging into OMA via IE.


Server Error in '/OMA' Application.


--------------------------------------------------------------------------------

Runtime Error

Description: An application error occurred on the server. The current custom
error settings for this application prevent the details of the application
error from being viewed remotely (for security reasons). It could, however,
be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable
on remote machines, please create a <customErrors> tag within a "web.config"
configuration file located in the root directory of the current web
application. This <customErrors> tag should then have its "mode" attribute
set to "Off".



<!-- Web.Config Configuration File -->



<configuration>

<system.web>

<customErrors mode="Off"/>

</system.web>

</configuration>



Notes: The current error page you are seeing can be replaced by a custom
error page by modifying the "defaultRedirect" attribute of the application's
<customErrors> configuration tag to point to a custom error page URL.



<!-- Web.Config Configuration File -->



<configuration>

<system.web>

<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>

</system.web>

</configuration>
 
 
 

Server Error in '/OMA' Application.

Post by SWFu » Wed, 30 Aug 2006 05:24:01

tried a couple of different things but it still doesn't work.

1. Reinstalled .NET
2. Change the account for the application pool that OMA runs under from
"Network Service" to LOCAL SYSTEM". Restart IIS. Recycle worker processes
for OMA app pool. OMA now works under the LOCAL SYSTEM account. Change the
account for the app pool back to run under "Network Service". Restart IIS.
Recycle worker processes again.


Now I am getting this 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:

<configuration>
<system.web>
<compilation debug="true"/>
</system.web>
</configuration>

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() +2755646
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




-------------------------
 
 
 

Server Error in '/OMA' Application.

Post by VGltIEpvcm » Wed, 30 Aug 2006 05:56:01

re you using SSL by chance? This error looks familiar and the only time
I've had errors with OMA is when configuring it for SSL.

Tim

"Ian" wrote:

 
 
 

Server Error in '/OMA' Application.

Post by SWFu » Wed, 30 Aug 2006 06:33:02

i Tim -

I already thought of that and removed Require SSL.

Thanks....



"Tim Jordan" wrote:

 
 
 

Server Error in '/OMA' Application.

Post by SWFu » Thu, 31 Aug 2006 04:21:02

SOLUTION

I figured it out. It was .NET 2.0.xxxx

Change the Default Web Site and OMA Directory to ASP .NET to version 1.1.4322.

RESET IIS

Do this to "companyweb" site if you are having a .NET error.