Solved

Active Sync between exchange server 2003 and PDA using GPRS

Posted on 2006-06-30
12
1,324 Views
Last Modified: 2012-06-21
Active Sync between exchange server 2003 standard with SP2 and a t-mobile (UK) MDA Vario (latest and greatest rom)

Tough one this, attempting to sync with exchange server from MDA vario (T-mobile, UK) with exchange 2003 over GPRS. Should be straight forward but this is not the case. Gone through all the instructions for IIS and Active Directory and users

All answers I’ve found so fare tend to be for pre SP2

Mobile has latest and greatest software
Likewise server has latest and greatest

In theory with the below settings all should work
The server SSL disabled on;
Microsoft-server-Activesync
Exchange-oma
OMA

Browser based (OWA) e-mail is still SSL, whilst the mobile services have no SSL (unchecked in directory security), this is reflected on the phone, SSL unchecked in server configuration settings

We have one exchange server, front end is not enabled, Forms-based authentication is enabled.

When attempting to sync MDA keeps asking for password, I’ve confirmed that the phone has established contact with the server.

One thing that has come to my attention, you should be able to browse to
http://xxx.xx.xx.xx/oma   (xxx is the IP address)
the simple exchange page should display, get the following error message
“A System error has occurred while processing your request. Please try again. If the problem persists, contact your administrator”

Although https://xxx.xx.xx.xx/exchange
Works fine.

Is this a matter of reinstalling web services?
Or enabling front-end server, what would impact would this have on the server?
0
Comment
Question by:weatherj
  • 5
  • 5
12 Comments
 
LVL 104

Expert Comment

by:Sembee
Comment Utility
If you enable the server as a frontend - then the server can't be a backend. No mailboxes.

The fact that OMA doesn't work is a good indication of a problem.

I have put the most common problems on a page on my web site here: http://www.amset.info/exchange/mobile-eastrouble.asp

The one that is missing from that list at the moment is the SMTP address issue.
If you have multiple SMTP addresses on the server, make sure that all mobile users have an address on the default domain as well as the primary domain that they use.

Simon.
0
 

Author Comment

by:weatherj
Comment Utility
The repeat for password on MDA has now gone, but is replaced with the an 0x85030022 error code


Made a little progress, now get a fill error...
when trying to browse to the OMA page get the following:

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() +2755806
   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
0
 
LVL 104

Accepted Solution

by:
Sembee earned 500 total points
Comment Utility
Here is your problem:

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

OMA/OWA/EAS is NOT a .net Framework 2.0 application.
It is 1.1.

While they are the same name, the two versions are in effect two different applications. You cannot run a version 1.1 application in version 2.0 of the tool.

Check the virtual directories and ensure that they are set to use 1.1 and not 2.0.

Simon.
0
 

Author Comment

by:weatherj
Comment Utility
Hi  Sembee, thanks for the feedback
This is now addressed all levels (including virtual directories) of the site now set to 1.1

on visiting
http://xxx.xx.xx.xx/oma   (xxx is the IP address)
from mail server browse from within IIS
the simple exchange page should display, get the following error message has rwturned
“A System error has occurred while processing your request. Please try again. If the problem persists, contact your administrator”
not a very helpful error message, this is with friendly erros switched off.

from another workstaion on the same domain using LAN IP address
404 page.

Whilst the PDA returns the follwoing error an 0x85030022

I suspect that the OMA & Microsoft-server-Activesync has a few issues, is there a way to install/reset this part on the mail server?
0
 
LVL 104

Expert Comment

by:Sembee
Comment Utility
You can reset the virtual directories by following this KB article:
http://support.microsoft.com/default.aspx?kbid=883380

Simon.
0
Are your corporate email signatures appalling?

Is it scary how unprofessional your email signatures look? Do users create their own terrible designs and give themselves stupid job titles? You can make this a lot easier for yourself by choosing an email signature management solution from Exclaimer today.

 

Author Comment

by:weatherj
Comment Utility
ran the followoing:
http://www.msexchange.org/tutorials/Fixing-Damaged-Incorrectly-Configured-OWA-2003-Installation.html
which did clear up a couple of other issues
on visiting
http://xxx.xx.xx.xx/oma   (xxx is the IP address)
from mail server browse from within IIS
get a more useful message:
Server Error in '/OMA' Application.
--------------------------------------------------------------------------------

Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".


<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>
 

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.


<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
    </system.web>
</configuration>
 
0
 
LVL 104

Expert Comment

by:Sembee
Comment Utility
That should have put something in the event viewer on the Exchange server. What does it say?

Simon.
0
 

Author Comment

by:weatherj
Comment Utility
Event viewer, application:

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.
0
 
LVL 104

Expert Comment

by:Sembee
Comment Utility
I have no idea what that means.

If a client put that in front of me, then I would be recommending a rebuild of the Exchange server. If you have reset the virtual folders and ensured that the .net framework is the correct version then it would appear that is more extensive damage to the system.

Simon.
0
 

Author Comment

by:weatherj
Comment Utility
Hi, Simon

Thanks for your feedback, this could be the case, currently the server is behaving correctly, I do some more digging.
0

Featured Post

How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

Join & Write a Comment

Check out this infographic on what you need to make a good email signature that will work perfectly for your organization.
Disabling the Directory Sync Service Account in Office 365 will stop directory synchronization from working.
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
This video discusses moving either the default database or any database to a new volume.

762 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

11 Experts available now in Live!

Get 1:1 Help Now