Uncategorized

oma and activesync do not work on sbs server

Posted on by Computer

Out of the box activesynce doesn’t work. Not very helpful. You may be getting the following errors trying to activesync to the server:

Outlook Mobile Access

  • You receive the following error message:
    Unable to connect to your mailbox on server Servername. Please try again later. If the problem persists contact your administrator.

    Additionally, the following error message is logged in the Application log in Event Viewer on the Exchange computer:
    Date: Date
    Source: MSExchangeOMA
    Time: Time
    Category: (1000)
    Type: Error
    Event ID: 1805
    User: N/A
    Computer: ServerName

    Description: Request from user UserA@domain.com resulted in the Microsoft(R) Exchange back-end server <ServerName> returning an HTTP error with status code 403:Forbidden

    Response:
    Content-Length: 1409
    Content-Type: text/html
    Server: Microsoft-IIS/6.0
    MicrosoftOfficeWebServer: 5.0_Pub
    X-Powered-By: ASP.NET
    Date: Fri, 21 Feb 2003 02:25:34 GMT

    <!DOCTYPE HTML PUBLIC “-//W3C//DTD HTML 4.01//EN” “http://www.w3.org/TR/html4/strict.dtd”> <HTML><HEAD><TITLE>The page must be viewed over a secure channel</TITLE> <META HTTP-EQUIV=”Content-Type” Content=”text/html; charset=Windows-1252″>

  • You receive the following error message:
    A System error has occurred while processing your request. Please try again. If the problem persists, contact your administrator.

    Additionally, the following error message is logged in the Application log in Event Viewer on the Exchange computer:
    Date: Date
    Source: MSExchangeOMA
    Time: Time
    Category: (1000)
    Type: Error
    Event ID: 1507
    User: N/A
    Computer: ServerName

    Description:
    An unknown error occurred while processing the current request: Exception of type Microsoft.Exchange.OMA.DataProviderInterface.ProviderException was thrown.

    Stack trace:
    at Microsoft.Exchange.OMA.UserInterface.Global.Session_Start(Object sender, 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)

    Inner Error: Exception has been thrown by the target of an invocation.

    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)

    Inner Error: The remote server returned an error: (440) Login Timeout.

    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)

–

Leave a Reply