is OMA still using v1.1 ?

With OMA I have always a blank page.
I dont know what to do more!
Eprs_AdminSystem ArchitectAsked:
Who is Participating?
 
Eprs_AdminConnect With a Mentor System ArchitectAuthor Commented:
0
 
LeeDerbyshireCommented:
Hard to say what's wrong if you only get a blank page.  Can you see the /OMA requests in your IIS log file?
0
 
Eprs_AdminSystem ArchitectAuthor Commented:
Yes, I see the requests in the logfiles.
Can we chekc together, why I just recieve a blank page for OMA ?

For OMA I get always this error:
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.
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
LeeDerbyshireConnect With a Mentor Commented:
In IIS Manager, have a look at the OMA Virtual Directory.  On the ASP.Net tab, see which version it is configured to use.  I think it should be v1 (as you may suspect, from the title of your original message).
0
 
Eprs_AdminSystem ArchitectAuthor Commented:
I have version 2.0.50727 installed.
I tried to switch it back to v1.
But later on it is swtiched back automatically to v2 . Why?

All other settings in the ISS are v1.

But my error in eventlog is now:

An unknown error occurred while processing the current request:
Message: Unrecognized attribute 'SessionStateHistorySize'. Note that attribute names are case-sensitive. (D:\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.


Maybe ASP.NET is the problem ?
0
 
LeeDerbyshireCommented:
Try temporarily renaming the OMA\Browse\web.config file to web.config.old .  There seems to be something in there that isn't compatible with its own operation.  Maybe something else, like SharePoint, got installed on the server?
0
 
Eprs_AdminSystem ArchitectAuthor Commented:
ok, I have renamed.
Sharepoint is not installed on exchange.
Whats now to test ?
0
 
Eprs_AdminSystem ArchitectAuthor Commented:
now I got this error:
  A System error has occurred while processing your request. Please try again. If the problem persists, contact your administrator.

AppEventlog:
An unknown error occurred while processing the current request:
Message: Value cannot be null.
Parameter name: assemblyString
Source: mscorlib
Stack trace:
   at System.Reflection.Assembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
   at System.Reflection.Assembly.Load(String assemblyString)
   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)


SystemEventlog:
A process serving application pool 'ExchangeMobileBrowseApplicationPool' terminated unexpectedly. The process id was '7488'. The process exit code was '0xe0434f4d'.


0
 
LeeDerbyshireCommented:
Are you able to reset OMA to v1 after renaming the file?
0
 
Eprs_AdminSystem ArchitectAuthor Commented:
When I rename the file and switch back to v1.
After the test, it is switched back to v2 automatically.

I am using the testtool : https://www.testexchangeconnectivity.com/
And the check tells me :
      Exchange Activesync returned an HTTP 500 response.

What about the configfile, put it back ?
0
 
MesthaConnect With a Mentor Commented:
I have seen this where asp.net version is set on the web site itself, rather than on the virtual directories.

-M
0
 
LeeDerbyshireCommented:
The config file you have is correct, so it should go back if changing it didn't help.  You will somehow need to get it to accept the v1 setting.
0
 
Eprs_AdminSystem ArchitectAuthor Commented:
The default website has v1 but always the OMA has v2
How to change it permanently?
All other virtual directories have v1.
Strange or ?
0
 
LeeDerbyshireCommented:
How about if you create a new VDir (called OMA2, or something like that)?  I don't think there's anything special about it (like there is with the Exchange VDir, which can't be created manually).  With luck, it will retain the v1 setting.

Or, you could delete the original, and recreate it with this:
http://support.microsoft.com/kb/883380
but I'd prefer to just try creating a copy manually, first.
0
 
Eprs_AdminSystem ArchitectAuthor Commented:
But is it sure, that OMA just accepts ASP v1 ??
0
 
Eprs_AdminSystem ArchitectAuthor Commented:
I have installed a new virtual directory called OMA2.
But this directory is empty. What to do with it ?
I have seen, this OMA2 folder is now ASP version 1

When I log in to https://domain.com/oma2 I get the content of the folder directory.

Please help me here.

George
0
 
LeeDerbyshireCommented:
How did you create the OMA2 VDir?  If you did it in IIS Manager, I think that some of the settings (like the source folder path) have not been correctly set to the same value as the original.  But I think that if you do it in Exchange System Manager (under Protocols/HTTP/Exchange Virtual Server), then the settings will be made automatically.
0
 
Eprs_AdminSystem ArchitectAuthor Commented:
please write it down how to do it !
0
 
Eprs_AdminSystem ArchitectAuthor Commented:
I created the OMA3 Vdir.
But automatically the v2 from ASP.NET is assigned.
And after the login I get this error:

Server Error in '/OMA3' 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() +2833870
   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) +268
   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) +200
   System.Web.HttpApplicationFactory.GetApplicationInstance(HttpContext context) +114
   System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) +350

 


--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:2.0.50727.1433; ASP.NET Version:2.0.50727.1433
0
 
LeeDerbyshireCommented:
Sorry for the delay - I was away for a few hours.  Anyway, it would be good to see if your new OMA3 directory will accept the ASP.Net v1 setting, or if it keeps getting reset to v2 like your original one does.
0
 
Eprs_AdminSystem ArchitectAuthor Commented:
ok I did it.
now the ASP.NET version is v1.
But its a long description from MS to create it correctly for OMA.

0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.