|
Hi, This is a bit off topic but one
of my colleagues is trying to establish if anyone has any experience of the
following issue when using OMA. This is his posting from other
newsgroups. As yet he has had no response. I know this list
is quite good even off topic so I offered to post here too. Cheers in advance. I have a single Exchange 2003 SP2 Server
that is also a GC running Windows Server 2003 SP1. The Server is setup for forms based
authentication and requires SSL for OWA. Access to OMA is not working with the
following event being logged on the exchange server every time the OMA app
fails. Event Type: Error Event Source: MSExchangeOMA Event Category: (1000) Event ID: 1503 Date: 02/06/2006 Time: 14:24:51 User: N/A Computer: FLINTJACK Description: An unknown error occurred while processing
the current request: Message: Input string was not in a correct
format. Source: mscorlib Stack trace: at
System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info) at
System.Web.Mobile.MobileCapabilities.get_ScreenCharactersWidth() at
Microsoft.Exchange.OMA.UserInterface.MainMenu.OnInit(EventArgs e) at
System.Web.UI.Control.InitRecursive(Control namingContainer) at
System.Web.UI.Control.AddedControl(Control control, Int32 index) at
System.Web.UI.MobileControls.MobilePage.AddedControl(Control control, Int32 index) at
System.Web.UI.ControlCollection.Add(Control child) at
Microsoft.Exchange.OMA.UserInterface.Page.Page_Load(Object sender, EventArgs e) at
System.Web.UI.Control.OnLoad(EventArgs e) at
System.Web.UI.MobileControls.MobilePage.OnLoad(EventArgs e) at
System.Web.UI.Control.LoadRecursive() at
System.Web.UI.Page.ProcessRequestMain() Message: Exception of type
System.Web.HttpUnhandledException was thrown. Source: System.Web Stack trace: at
System.Web.UI.Page.HandleError(Exception e) at
System.Web.UI.Page.ProcessRequestMain() at
System.Web.UI.Page.ProcessRequest() at System.Web.UI.Page.ProcessRequest(HttpContext
context) at System.Web.CallHandlerExecutionStep.System.Web.HttpApplication+IExecutionStep.Execute() at
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) Also get the following in IE 6.0 SP2 A System error has occurred while
processing your request. Please try again. If the problem persists, contact your
administrator. Home For more information, see Help and Support
Center at http://go.microsoft.com/fwlink/events.asp. I have been through KBs 817379, 842119,
898131 all with no resolution. The server is patched up with no critical
downloads available from Microsoft and has the following hotfixes: 907747, 911829, 916640, 916803 The server is also running Trend Micro
Scanmail version 7.0 with the latest pattern files and updates applied. I cannot
find anything in Trend Micro KB's on this issue and there are no
warnings of any virus detections in either this or the file virus scanner which
is Symantect Anti Virus version 10.1.0.394 and it is excluding the exchange
directories. Interestingly if I test this locally using
localhost/oma it works perfectly well until I try this remotely from another
server, then after the failure from the other server I get the issue
locally as well and OMA stops working. So it appears that something remotely is
causing the OMA application in the ExchangeMobileBrowseApplicationPool to die.
Recycling the app pool allows me to restart the application and this works again
locally. The identity for this application pool is correctly set to
Network Service. I have have no host headers and although
ASP 2.0 is installed the Web Sites are all set to use ASP 1.1. OWA works perfectly, I cannot test
ActiveSync as I have no device and I have not setup an emulator. It seems to me OMA is not as robust as
hoped as there are still lots of issues arounf event ID 1503. Any help appreciated. |
