Link to home
Start Free TrialLog in
Avatar of phermi
phermi

asked on

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:

<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() +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
Avatar of Sembee
Sembee
Flag of United Kingdom of Great Britain and Northern Ireland image
The last line shows your problem.

Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.42


Exchange is a .net framework 1.1 application.
2.0 does not contain the code for 1.1 - they should be treated as two separate tools. Check that the the correct version is set and then iisreset.

Simon.

Avatar of phermi
phermi

ASKER

Simon,

Thanks. So, should we changed the .NET version to 1.1.4322 for Vdirs: Exchange, Exadmin, exchange-oma, Microsoft-Server-ActiveSync, OMA?


On server # 2, everything is 1.1. On server # 2, OWA and RPCoHTTP works fine having 2.0. Just for my education, does that makes sense?

Thand again and regards
Avatar of Sembee
Sembee
Flag of United Kingdom of Great Britain and Northern Ireland image
RPC over HTTPS doesn't use asp.net. I am surprised that OWA worked with version 2.0. Perhaps it over rode it.
Exchange 2003 was written for 1.1, so all of the directories that are Exchange related need to be 1.1

Simon.
Avatar of phermi
phermi

ASKER

Simon,

Just to be sure. Chaging .NET version is done by chaging the version under the ASP.NET tab from the VDir properties.Nothing else requiered?

I read somewhere something about a command line that needed to be executed, but I can not find it now.

Please advice.

Thanks for all your help.

Regards,

Pedro
Avatar of Sembee
Sembee
Flag of United Kingdom of Great Britain and Northern Ireland image
If that doesn't fix it, then there is a command line that you run which resets the asp.net installation. It isn't always necessary to do that.

If you do need to do it, then the command is:

C:\Windows\Microsoft.NET\Framework\<version>\aspnet_regiis.exe" -i

adjust C:\Windows for your system, and the version for the exact version number you have installed (1.1.x).

Simon.
Avatar of phermi
phermi

ASKER

Simon,

Thanks. You have been totally helpfull.

I'll do the change this evening and post results.

Regards,

Pedro
Avatar of phermi
phermi

ASKER

Simon,

We changed almost everything to 1.1. Some of the Exchange folders couldn't be changed to 1.1 so we decide to follow Henrik Walther's steps --> Fixing a Damaged or Incorrectly Configured OWA 2003 Installation , http://www.msexchange.org/tutorials/Fixing-Damaged-Incorrectly-Configured-OWA-2003-Installation.html. Things got better but still ....

Now, while browsing OMA we get:

ON THE BROWSER -->   A System error has occurred while processing your request. Please try again. If the problem persists, contact your administrator.

LOGS --> Event Type:      Error
Event Source:      MSExchangeOMA
Event Category:      (1000)
Event ID:      1503
Date:            9/13/2006
Time:            9:26:05 PM
User:            N/A
Computer:      KPI
Description:
An unknown error occurred while processing the current request:
Message: The remote server returned an error: (501) Not Implemented.
Source: Microsoft.Exchange.OMA.ExchangeDataProvider
Stack trace:
   at Microsoft.Exchange.OMA.ExchangeDataProvider.OmaWebRequest.GetRequestStream()
   at Microsoft.Exchange.OMA.ExchangeDataProvider.ExchangeServices.GetSpecialFolders()
   at Microsoft.Exchange.OMA.ExchangeDataProvider.ExchangeServices..ctor(UserInfo user)

Message: Exception has been thrown by the target of an invocation.
Source: mscorlib
Stack trace:
   at System.Reflection.RuntimeConstructorInfo.InternalInvoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean isBinderDefault)
   at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
   at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
   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.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.
Avatar of phermi
phermi

ASKER

on the local host, accessing the ActiveSync Wed Admin tool produce the following: (see last line, becuase the VDir is set to 1.1 as all the others)

Server Error in '/MobileAdmin' Application.
--------------------------------------------------------------------------------

The remote server returned an error: (501) Not Implemented.
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.Net.WebException: The remote server returned an error: (501) Not Implemented.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.  

Stack Trace:


[WebException: The remote server returned an error: (501) Not Implemented.]
   System.Net.HttpWebRequest.GetResponse() +1502011
   Microsoft.Exchange.AirSync.Admin.Mailbox.propFindRequest(String deviceUri) +466
   Microsoft.Exchange.AirSync.Admin.Mailbox.getDevices() +188
   Microsoft.Exchange.AirSync.Admin.Devices.refreshDevicesTable() +116
   Microsoft.Exchange.AirSync.Admin.Devices.Page_Load(Object sender, EventArgs e) +160
   System.Web.UI.Control.OnLoad(EventArgs e) +99
   System.Web.UI.Control.LoadRecursive() +47
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1061

 


--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.42
Avatar of phermi
phermi

ASKER

I ran aspnet_regiis for .NET 1.1.4322 ...same results
Avatar of phermi
phermi

ASKER

Yes, but my Event is 1503, category 1000 and I do not beleive we are usign form auth.

Can I just remove .NET 2.0? it has to be a mess some where because after running aspnet_regiis I still have    the Microsoft SharePoint Administration in 2.0, not changeable, while SharePoint Central Administration is 1.1.

Everything else is 1.1.

Can we just REMOVE .NET 2.0? Is there anything that may use it? Our WebApp is 1.1 and we use Sharepoint for a tem collboration site that is also 1.1

This is the Event info -->
Event Type:      Error
Event Source:      MSExchangeOMA
Event Category:      (1000)
Event ID:      1503
Date:            9/14/2006
Time:            8:22:25 AM
User:            N/A
Computer:      KPI
Description:
An unknown error occurred while processing the current request:
Message: The remote server returned an error: (501) Not Implemented.
Source: Microsoft.Exchange.OMA.ExchangeDataProvider
Stack trace:
   at Microsoft.Exchange.OMA.ExchangeDataProvider.OmaWebRequest.GetRequestStream()
   at Microsoft.Exchange.OMA.ExchangeDataProvider.ExchangeServices.GetSpecialFolders()
   at Microsoft.Exchange.OMA.ExchangeDataProvider.ExchangeServices..ctor(UserInfo user)

Message: Exception has been thrown by the target of an invocation.
Source: mscorlib
Stack trace:
   at System.Reflection.RuntimeConstructorInfo.InternalInvoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean isBinderDefault)
   at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
   at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
   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.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.
Avatar of phermi
phermi

ASKER

additionally, Simon, we are able to access the mobileadmin site, login and select the wipe option. But when an inbox is typed we got this, which for me is the mess with .NET 2

Event Type:      Warning
Event Source:      ASP.NET 2.0.50727.0
Event Category:      Web Event
Event ID:      1309
Date:            9/14/2006
Time:            8:12:49 AM
User:            N/A
Computer:      KPI
Description:
Event code: 3005 Event message: An unhandled exception has occurred. Event time: 9/14/2006 8:12:49 AM Event time (UTC): 9/14/2006 12:12:49 PM Event ID: cf246908b6f944ebb769fc7b352fb05a Event sequence: 19 Event occurrence: 2 Event detail code: 0  Application information:     Application domain: /LM/W3SVC/5/Root/MobileAdmin-1-128027092974843750     Trust level: Full     Application Virtual Path: /MobileAdmin     Application Path: C:\Program Files\Microsoft Exchange ActiveSync Administration\     Machine name: KPI  Process information:     Process ID: 1416     Process name: w3wp.exe     Account name: NT AUTHORITY\SYSTEM  Exception information:     Exception type: WebException     Exception message: The remote server returned an error: (501) Not Implemented.  Request information:     Request URL: http://localhost/mobileadmin/devices.aspx     Request path: /mobileadmin/devices.aspx     User host address: 127.0.0.1     User: NETWORK4LEADERS\phermi     Is authenticated: True     Authentication Type: Negotiate     Thread account name: NT AUTHORITY\SYSTEM  Thread information:     Thread ID: 7     Thread account name: NT AUTHORITY\SYSTEM     Is impersonating: False     Stack trace:    at System.Net.HttpWebRequest.GetResponse()
   at Microsoft.Exchange.AirSync.Admin.Mailbox.propFindRequest(String deviceUri)
   at Microsoft.Exchange.AirSync.Admin.Mailbox.getDevices()
   at Microsoft.Exchange.AirSync.Admin.Devices.refreshDevicesTable()
   at Microsoft.Exchange.AirSync.Admin.Devices.Page_Load(Object sender, EventArgs e)
   at System.Web.UI.Control.OnLoad(EventArgs e)
   at System.Web.UI.Control.LoadRecursive()
   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
  Custom event details:

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
ASKER CERTIFIED SOLUTION
Avatar of Sembee
Sembee
Flag of United Kingdom of Great Britain and Northern Ireland image
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of phermi
phermi

ASKER

That is what we are working on ... let me tell you what I just did. I just saved the configuration of the Default Web Site that gets created when you install de Active Sync Web Admin Tool. I delete the site and re-created from the file and it comes back as .Net 2.0

So I edited the file, by comparing with another server, and changed references to .Net 2.0 to .Net 1.1. I created the site from the modified file and it came again as .Net 2.0, like something is telling which version to use.

Then, I took a llok to the Web Sites folder that contains all Sites. On my other server, where everything is perfect, the .Net version is fixed to 1.1. In the server where all the problems are, it is fixed to 2.0.

I'm thinking, is that the reason why the creation from file is comming to 2.0? Can that be changed?  As you see, I AM GETTING DESPERATE. I have 15 users with WM5.0 devices waiting in line after the company purchase them.
Avatar of Sembee
Sembee
Flag of United Kingdom of Great Britain and Northern Ireland image
Is 1.1 installed correctly on this machine? I am struggling to come up with a reason why the application is defaulting to 2.0

Simon.
Avatar of phermi
phermi

ASKER

well, how do I know if it is "correctly"?

the web app is up and running and its web site is contained in site with .net 1.1

Should I expect problems with sharepoint if v2 is uninstalled?
Avatar of Sembee
Sembee
Flag of United Kingdom of Great Britain and Northern Ireland image
My experience with sharepoint isn't that great, so I cannot comment on whether you will experience issues with sharepoint or not.
Did you make the exclusions in sharepoint for the Exchange virtual directories?

Simon.
Avatar of phermi
phermi

ASKER

I am not sure I understand your question. But, no Vdir under the Default was turned (extended)  into a SharePoint site
Avatar of Sembee
Sembee
Flag of United Kingdom of Great Britain and Northern Ireland image
Sharepoint takes over a web server.
If you have Exchange on there you have to put some exclusions in place within Sharepoint

http://support.microsoft.com/default.aspx?kbid=823265

Simon.
Avatar of phermi
phermi

ASKER

thanks for continuing with me. Please remember,, this is a SBS 2003 Premium box, so nothing was installed separedtly. OS, Exchange and Sharepoint are thightly integraded.

On the other hand, OWA  works fine. It is OMA the one giving the errors.

Unless you come up with something else, I will be unistalling Net 2 at 6:00 pm EST.

Thanks
Avatar of Jeffrey Kane - TechSoEasy
Jeffrey Kane - TechSoEasy
Flag of United States of America image
Can you tell me why you have .NET 2.0 installed at all???

It's not required by SBS and really shouldn't be there unless you are running .NET 2.0 applications.  And it doesn't sound like you are doing that... so uninstall it!

Jeff
TechSoEasy
Avatar of phermi
phermi

ASKER

Thanks to TechSoEasy as well for giving me confort to elimnate it.

Ok, I uninstalled .Net 2.0 from Add/Remove Programs and there is not even a TAB now for ASP.NET. I do not know if not being 2.0 this is expected behavior.

Any way, still the same problem accessing OMA, via HTTP or HTTPS. On the browser, after credentials:
->   A System error has occurred while processing your request. Please try again. If the problem persists, contact your administrator.

On the Event Viewer/Application -->
Event Type:      Error
Event Source:      MSExchangeOMA
Event Category:      (1000)
Event ID:      1503
Date:            9/14/2006
Time:            9:07:21 PM
User:            N/A
Computer:      KPI
Description:
An unknown error occurred while processing the current request:
Message: The remote server returned an error: (501) Not Implemented.
Source: Microsoft.Exchange.OMA.ExchangeDataProvider
Stack trace:
   at Microsoft.Exchange.OMA.ExchangeDataProvider.OmaWebRequest.GetRequestStream()
   at Microsoft.Exchange.OMA.ExchangeDataProvider.ExchangeServices.GetSpecialFolders()
   at Microsoft.Exchange.OMA.ExchangeDataProvider.ExchangeServices..ctor(UserInfo user)

Message: Exception has been thrown by the target of an invocation.
Source: mscorlib
Stack trace:
   at System.Reflection.RuntimeConstructorInfo.InternalInvoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean isBinderDefault)
   at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
   at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
   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.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.


And the 15 WM devices are waiting for my (and you, ja ja) to fix this nightmare so they can connect to Exchange.

.................... never give up, never surrender

Avatar of Jeffrey Kane - TechSoEasy
Jeffrey Kane - TechSoEasy
Flag of United States of America image
At this point, since you have made a number of changes, I would suggest that you follow this KB article to remove and reinstall IIS and Exchange:
http://support.microsoft.com/kb/320202/

I wouldn't think that this would affect your main web app... but be sure to back up the IIS configuration and IIS metabase prior to doing any of this.

Jeff
TechSoEasy
Avatar of phermi
phermi

ASKER

Jeff,

I've been advice to avoid doing partial un-installs and re-installs in SBS. So, unless experts like you trully recommend   doing so, I won't do it. The server sits in Dallas in collocation ... and if something goes terribly worng during that process, I am risking the web app not the up tomorrow morning or MOnday morning.

Please do not take me wrong. I am in unpleasant, unkown waters here.

Regards,

pedro
Avatar of phermi
phermi

ASKER

How Do I know if OMA, or anything else, is using Forms Authentication?

Being a SBS2003, I have to assume that ISA is somewhere there doing something?

...... still fighting
SOLUTION
Avatar of Jeffrey Kane - TechSoEasy
Jeffrey Kane - TechSoEasy
Flag of United States of America image
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of phermi
phermi

ASKER

Dear Simon & Jeff,

After researching, reading and testing I was finally able to get it to works. Definetly, the problem was caused by the version change for .Net. I remember reading something about a command line utility to adjust the content of the web.config files when yochange .Net version but I was unable to find that article.

By trial and error, I was able to edit the web.config files until no errors where shown. As of now, OWA, OMA, Sharepoint, and the web application are running and consultants are synchronizing their WM 5.0 devices over the air.

Some of the articles I used the most , in addition to your advice, were:
http://www.msexchange.org/tutorials/Fixing-Damaged-Incorrectly-Configured-OWA-2003-Installation.html
http://blogs.technet.com/mjmurphy/archive/2006/02/07/418902.aspxppp

Now, there is one event happening on that server every 15 minutes for which I have not being able to find the solution:
--------------------------------------------------------------------------------------------------------------------------------------
Event Type:      Warning
Event Source:      MSExchangeMU
Event Category:      General
Event ID:      1040
Date:            9/19/2006
Time:            8:08:40 AM
User:            N/A
Computer:      KPI
Description:
Metabase Update failed replication 5 times with error 80070003 (The system cannot find the path specified.). Please change the diagnostic logging level of MSExchangeMU to 'minimum' or greater to find the source of the problem.

For more information, click http://www.microsoft.com/contentredirect.asp.
---------------------------------------------------------------------------------------------------------------------------------------

The link above provides 4 possible causes and a registry key set (that is already as recommended). I do not think the first 2 apply to me but I do not know how to proceed with the other two.

I wonder if you can take a look into it.

Thanks again

Pedro
Avatar of Jeffrey Kane - TechSoEasy
Jeffrey Kane - TechSoEasy
Flag of United States of America image
I wonder how much time you have spent troubleshooting this when you could have resolved most all of it by following KB 320202.  

To be honest, you've continued to manually configure many things on your SBS that should have been done with the wizards.  This is why you are now having issues that require further manual fixing.  The reason I recommended that you reinstall IIS & Exchange was to get you back to the baseline necessary to more easily maintain and manage your server.  

I'm sorry, but I can't review the possible causes from the link because that link only works while viewing your event logs.  It's otherwise a generic link to MS KB Search.  

Jeff
TechSoEasy
Avatar of phermi
phermi

ASKER

Dear Jeff,

Thanks. We consider your suggestion and noted all the consecuences to our Exchange set up, Sharepoint Sites and more importantly to the web application. Due to the fact that the server is in collocation and in production, this approach will take it out of production for some time and imply a tremendous effort to reconfigure it. We may still need to do that, but we allocated some hours to attempt fixing it and we did it on that window.

Now, here is the text from Help:

 
Details
Product: Exchange
Event ID: 1040
Source: MSExchangeMU
Version: 6.5.0000.0
Message: Metabase Update failed replication %1 times with error %2.
Please change the diagnostic logging level of MSExchangeMU to 'minimum' or greater to find the source of the problem.
   
Explanation
Metabase Update Agent failed repeatedly.



This is probably not a sporadic failure. Obtain detailed event logs to find the problem.


Set the following key in the registry to obtain more detailed event logs.

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeMU\Diagnostics]
"1 General"=dword:00000000

Here are some known causes of this event:


Cause 1 - Internet Information Server (IIS) has been uninstalled and reinstalled, but Exchange server was not reinstalled.
Cause 2 - The IIS Lockdown was not configured correctly to work with Exchange.
Cause 3 - The metabase is not being updated with changes made to the Default SMTP Virtual Server due to unknown reasons -- when checking the metabase with medaedit.exe, the changes are not being replicated.
Cause 4 - Active Directory replication is not working properly or DSaccess problems are preventing directory replication. Changes to Active Directory are not being propagated to the metabase.
 
   
User Action
This is probably not a sporadic failure. Obtain detailed event logs to find the problem.
Set the following key in the registry to obtain more detailed event logs.

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeMU\Diagnostics]
"1 General"=dword:00000000

Resolutions for known causes as listed above:

Resolution 1 - After reinstalling IIS and hotfixes, reinstall Exchange server (do not perform an uninstall of Exchange -- only use the /reinstall). Then reinstall the same Exchange server service pack and hotfixes.
Resolution 2 - Configure the IIS Lockdown Tool to work correctly with Exchange server.
Resoluion 3 - This depends on the error. Search the Knowledge Base, and contact PSS if there is no resolution for the error indicated.
Resolution 4 - Fix the root cause of active directory replication problems or add another DC as a replication partner or fix the root cause of the DSAccess problems.

 
   
   
Version: 6.5.6940.0
Component: Microsoft Exchange Metabase Update
Message: Metabase Update failed replication <number> times with error <error code>.Please change the diagnostic logging level of MSExchangeMU to 'minimum' or greater to find the source of the problem.
   
Explanation
Metabase Update Agent failed repeatedly.

This is probably not a sporadic failure. Obtain detailed event logs to find the problem.

Here are some known causes of this event:

Cause 1 - Internet Information Server (IIS) has been uninstalled and reinstalled, but Exchange server was not reinstalled.
Cause 2 - The IIS Lockdown was not configured correctly to work with Exchange.
Cause 3 - The metabase is not being updated with changes made to the Default SMTP Virtual Server due to unknown reasons -- when checking the metabase with Medaedit.exe, the changes are not being replicated.
Cause 4 - Active Directory replication is not working properly or DSAccess problems are preventing directory replication. Changes to Active Directory are not being propagated to the metabase.
 
   
User Action
This is probably not a sporadic failure. Obtain detailed event logs to find the problem.

Set the following key in the registry to obtain more detailed event logs:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeMU\Diagnostics]
"1 General"=dword:00000000

The following are resolutions for the known causes listed above:

Resolution 1 - After reinstalling IIS and hotfixes, reinstall Exchange server (do not perform an UNINSTALL of Exchange - only use the REINSTALL from the SETUP menu). Then apply the same Exchange server service pack and hotfixes that were present before.
Resolution 2 - Configure the IIS Lockdown Tool to work correctly with Exchange server.
Resolution 3 - This depends on the error. Search the Microsoft Knowledge Base, and contact Microsoft Product Support Services if there is no resolution for the error indicated.
Resolution 4 - Fix the root cause of active directory replication problems or add another DC as a replication partner or fix the root cause of the DSAccess problems.
 
 

--------------------------------------------------------------------------------
 
 
Currently there are no Microsoft Knowledge Base articles available for this specific error or event message. For information about other support options you can use to find answers online, see http://support.microsoft.com/default.aspx.
   
 Related Sites
 
 • Exchange Server TechCenter
 Connect to Exchange Server-related technical articles and other resources developed by Microsoft and the broader Exchange Server community.  
 • Downloads for Exchange Server 2003
 Use this site to download the latest product updates and tools.
 • Exchange Server 2003 Support Center
 Visit the Exchange Server 2003 Support Center for links to common questions and answers, instructions, most popular downloads, and more. From the Support Center, you can also search the Microsoft Product Support Knowledge Base and contact Microsoft Product Support Services.  
 
 
 
 
Avatar of Jeffrey Kane - TechSoEasy
Jeffrey Kane - TechSoEasy
Flag of United States of America image
I"ve run the reinstall IIS and Exchange process at least 15 or 20 times on various servers and it's never taken more than about 45 minutes to an hour to complete.  So I don't agree that it would be easier to continue to troubleshoot.

Jeff
TechSoEasy
Avatar of phermi
phermi

ASKER

Jeff,

I respect your position. You do not have to agree with me; or viceversa. Feel free not to reply any more to this topic.

Thanks,

Pedro
Avatar of krajewskik
krajewskik
I had a similar problem with OMA after installing Service Pack 2 for Exchange 2003. OMA had previously worked and then broke with similar error messages. I had never gotten it to work until I had read through this topic. To get mine working again the only thing I had to do was to set the OMA virtual directory to use .NET 1.1. Apparently SP2 may have changed it to .NET 2.0. I have a GFI Mailarchiver application on that box that uses 2.0 but everything was working fine until SP2 so I have to assume SP2 changed it for some reason. Simply changing it back to 1.1 solved it for me.
Avatar of Sembee
Sembee
Flag of United Kingdom of Great Britain and Northern Ireland image
Exchange 2003 SP2 would not have changed the asp.net configuration. It doesn't change that - why would it when Exchange 2003 is not asp.net 2.0 compatible. Something else would have changed it, not the Exchange installation.

Simon.
Avatar of A-T-1
A-T-1
I figured out the answer! Just go to IIS and then to the properties of OMA. Go to the ASP.Net tab and change the version from 2.0 to 1.1. Do an IIS reset. Of course you'll still need to do the exchange-oma fix but it sounds like everyone else already did that.