OMA-ActiveSync Problems 2003

The following are events that I recieve attempting to use the OMA in a newer Exchange 2003 config. This is a relatively new install, we recently migrated from Groupwise. The setup is a single server(no front/back) no FBA. I am attempting to connect some new smartrtphones we have purchased. The OMA setup looks pretty straight forward. I get this error after I attempt to launch the OMA with a web browser.

1/23/2008      2:00:58 PM      MSExchangeOMA      Information      (1000)      1001      N/A      

AWEXCP01      Outlook(R) Mobile Access Browse Application started successfully.


1/23/2008      2:00:59 PM      MSExchangeOMA      Error      (1000)      1503      N/A      AREXCP01      

"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)
"


1/23/2008      2:00:59 PM      MSExchangeOMA      Error      (1000)      1503      N/A      AREXCP01      

"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)
"


1/23/2008      2:00:59 PM      .NET Runtime 2.0 Error Reporting      Error      None      5000      

N/A      AREXCP01      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.

1/23/2008      2:02:08 PM      ASP.NET 2.0.50727.0      Warning      Web Event       1309      N/A      

AWEXCP01      "Event code: 3005
Event message: An unhandled exception has occurred.
E

vent time: 1/23/2008 2:02:08 PM
Event time (UTC): 1/23/2008 8:02:08 PM
Event ID:

f318ea0b7f064d1e8b24b6fc338346c2
Event sequence: 2
Event occurrence: 1
Event detail code:

0
 
Application information:
    Application domain:

/LM/W3SVC/1/root/OMA-1-128455921287499168
    Trust level: Full
    Application Virtual

Path: /OMA
    Application Path: C:\Program Files\Exchsrvr\OMA\Browse\
    Machine name:

AREXCP01
 
Process information:
    Process ID: 3444
    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://mail.companies.com/oma/oma.aspx 
    Request path: /oma/oma.aspx
    User host

address: 192.x.x.x
    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:
"
aharvalaAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

LeeDerbyshireCommented:
A shot in the dark...  If the server has both .Net 1 and .Net 2 installed, have a look at the properties of the OMA VDir in IIS Manager, and make sure that it is configured to use .Net 1.
0
aharvalaAuthor Commented:
The only option for the ASP .NET setting for the OMA and Active-Sync virtual directories is 2.0.5.727. Looking in the add/remove programs I only see Microsoft .Net 1.1 - Device update 4.0. In the add/remove Windows components .Net 1.1 in not an option. Is there a Server 2003 R2/ .Net 1.1 issue?

Where do I find .Net 1.1 for Server 2003 R2?

0
LeeDerbyshireCommented:
When you look at Add/Remove, and select 'Show Updates', is the .Net Framework 1 listed underneath .Net Framework 2?
0
The Ultimate Tool Kit for Technolgy Solution Provi

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy for valuable how-to assets including sample agreements, checklists, flowcharts, and more!

aharvalaAuthor Commented:
No, the only update under the .Net 2.0 is a Security update for .Net Framework 2.0 KB928365. Is the fix as easy as throwing is the Server 2003 R2 setup discs and load 1.1?
0
LeeDerbyshireCommented:
Well, I think that you got .Net 1 if you selected ASP.Net as a component when you installed the server.  I've a feeling that you no longer get this option after you install .Net 2.
0
aharvalaAuthor Commented:
So if I need the OMA and Active-Sync VDirectories to run under .net 1.1 and I cannot select 1.1 in the ASP.NET tab, could this be the issue?

0
LeeDerbyshireCommented:
I seem to remember that OMA only works with 1.1, and a search:
http://www.google.co.uk/search?hl=en&q=oma+.net+1.1+problem
suggests that there is some truth in that.  If you want to see if 1.1 will make a difference, you will now probably need to get the separate download:
http://www.microsoft.com/downloads/details.aspx?FamilyId=262D25E3-F589-4842-8157-034D1E7CF3A3&displaylang=en
and then use automatic updates to see if it needs updating.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
aharvalaAuthor Commented:
Using these instructions from the link above was able to get the 1.1 .net to appeat as an ASP.NET option in the vDirectories. I first needed to uninstall and reinstall v1.1 using.

aspnet_regiis.exe -u
aspnet_regiis.exe -i
 in the C:\Windows\Microsoft.NET\Framework\v1.1.4322 directory. This may have been the fix all along) I then used the aspnet_regiis command line utility. It can be used to manage the
registration of ASP.NET in IIS. This is found in each .NET version's
folder.

C:\Windows\Microsoft.NET\Framework\v1.1.4322        (for .NET version
1.1), and
C:\Windows\Microsoft.NET\Framework\v2.0.50727        (for .NET version
2.0)

If you run "aspnet_regiis -lk" it wil list the versions of ASP.NET
being used by each IIS directory. By using the -sn switch you can force
a specified version on a particular directory. I reverted the OMA
directory to ASP.NET v1.1 by using the aspnet_regiis command for
version 1.1:

aspnet_regiis -sn W3SVC/1/ROOT/OMA/

Then OMA started to work as expected.

Thanks for the solution.

0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.