469,332 Members | 6,650 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,332 developers. It's quick & easy.

Exchange, OMA, an ASP Problem?

I have had an OMA problem for a month now, and cannot figure it out. A
while back, can't rememeber a specific time, I was able to browse to my OMA
at the local host using http://127.0.0.1/oma - it was maybe a year ago that
I last saw it work. I remember thinking "cool feature, but don't need it"
and moving on. Now, a service pack later I cannot get it to work. (now I
need it) I am running exchange 2003 sp2 on server 2000 sp4. Basically, I
browse to oma on the exchange server, and I get the following info on
screen -

Server Application Unavailable

The web application you are attempting to access on this web server is
currently unavailable. Please hit the "Refresh" button in your web browser
to retry your request.

Administrator Note: An error message detailing the cause of this specific
request failure can be found in the application event log of the web server.
Please review this log entry to discover what caused this error to occur.

I then go to the event viewer and in the application log and get the
following three errors/warning -

Event Id: 1309
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 3/2/2006 8:41:51 AM
Event time (UTC): 3/2/2006 2:41:51 PM
Event ID: 369914e570da44a8939351c7cf41e6e1
Event sequence: 4
Event occurrence: 1
Event detail code: 0

Application information:
Application domain: /LM/W3SVC/1/root/OMA-1-127857840988593750
Trust level: Full
Application Virtual Path: /OMA
Application Path: C:\Program Files\Exchsrvr\OMA\Browse\
Machine name: SERVER

Process information:
Process ID: 1648
Process name: aspnet_wp.exe
Account name: DOMAIN\IWAM_SERVER-TEMPLATE

Exception information:
Exception type: InvalidOperationException
Exception message: Collection was modified; enumeration operation may
not execute.

Request information:
Request URL: http://127.0.0.1/oma/oma.aspx
Request path: /oma/oma.aspx
User host address: 127.0.0.1
User:
Is authenticated: False
Authentication Type:
Thread account name: DOMAIN\IWAM_SERVER-TEMPLATE

Thread information:
Thread ID: 1
Thread account name: DOMAIN\IWAM_SERVER-TEMPLATE
Is impersonating: False
Stack trace: at
System.Collections.ArrayList.ArrayListEnumeratorSi mple.MoveNext()
at Microsoft.Exchange.OMA.Tracing.OmaTrace.set_DebugO utputTracing(Boolean
value)
at Microsoft.Exchange.OMA.UserInterface.Global..ctor( )
at ASP.global_asax..ctor()
Custom event details:
Event Id: 5000

EventType clr20r3, P1 aspnet_wp.exe, P2 2.0.50727.42, P3 4333aece, P4
microsoft.exchange.oma.userinterface, P5 6.5.0.0, P6 430e745e, P7 463, P8 0,
P9 system.nullreferenceexception, P10 NIL.
Event Id:1008

aspnet_wp.exe (PID: 1648) was recycled because it failed to respond to ping
message.
One thing to note, is I am working on 2 servers, my production exchange
server and a test server. I have the same problem on both servers.



Mar 2 '06 #1
0 4137

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

8 posts views Thread by Rob Edwards | last post: by
reply views Thread by Tim Sapp | last post: by
1 post views Thread by Robbert van Geldrop | last post: by
reply views Thread by arjen1984 | last post: by
reply views Thread by zhoujie | last post: by
reply views Thread by Marylou17 | last post: by
1 post views Thread by Marylou17 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.