E6 - Mail for Exchange (Mandatory Server Policy Fa...

I bought my E6 for couple of weeks, and have been having this problem when I tried to setup Mail for Exchange on my company's email account, and got this "Mandatory Server Policy Failed".
Just have Nokia Care reinstall all latest firmware, same problem exists. My software version is 022.014, version date is 2011-07-05.
I used to have the same setting on C7, E7 and my Android phones for my company's email, all works fine.
Any solutions for this?

I have been trying to configure Mail for Exchange on Nokia E6-00, but it doesn't work at all. It doesn't ask for auto phone lock option mandatory. Which is asked while configuring Mail for Exchange on Nokia E63, E72 and 5530, 5800 and so on.
Also I have searched Mail for Exchange software on OVi store but it is not available for E6-00. So that I can updated the existing software in my phone.
Can anyone please guide to resolve this issue?
Mail for exchange is perfectly working on my E6-00 for Hotmail, Gmail, Yahoo but its not working while I tried to configure my Official email.

Similar Messages

Mail for Exchange : HTTP Server Error 500

Just installed MFE on my Nokia E90 and having issues synching it up with my exchange account. I checked the log and this is what it says :
19/12/2008 9:23:03 Setting OFFLINE Status to False
19/12/2008 9:23:03 Setting ROAMING status to False
19/12/2008 9:23:03 Setting DISK FULL status to False
19/12/2008 9:23:08 Setting OFFLINE Status to False
19/12/2008 9:23:08 Setting ROAMING status to False
19/12/2008 9:23:08 Setting DISK FULL status to False
19/12/2008 9:24:34 Profile Updated
19/12/2008 9:24:34 unable to open snapshot database (-1)
19/12/2008 9:24:34 OffPeakTime active
19/12/2008 9:24:42 Cancel Job:0, Type:"Sync Job On Profile":
19/12/2008 9:25:06 HTTP error code=500
19/12/2008 9:25:06 HTTP Server Error 500: Internal Server Error
19/12/2008 9:49:10 OffPeakTime active
19/12/2008 9:55:09 HTTP error code=500
19/12/2008 9:55:09 HTTP Server Error 500: Internal Server Error
19/12/2008 10:02:01 HTTP error code=500
19/12/2008 10:02:01 HTTP Server Error 500: Internal Server Error
19/12/2008 10:04:21 Profile Updated
19/12/2008 10:04:22 OffPeakTime active
19/12/2008 10:04:30 HTTP error code=500
19/12/2008 10:04:30 HTTP Server Error 500: Internal Server Error
19/12/2008 10:05:17 HTTP error code=500
19/12/2008 10:05:17 HTTP Server Error 500: Internal Server Error
19/12/2008 10:09:39 HTTP error code=500
19/12/2008 10:09:39 HTTP Server Error 500: Internal Server Error
19/12/2008 10:11:06 OffPeakTime active
19/12/2008 10:11:06 Setting OFFLINE Status to False
19/12/2008 10:11:07 Setting ROAMING status to False
19/12/2008 10:11:07 Setting DISK FULL status to False
19/12/2008 10:11:23 HTTP error code=500
19/12/2008 10:11:24 HTTP Server Error 500: Internal Server Error
19/12/2008 10:35:27 Profile Updated
19/12/2008 10:35:28 OffPeakTime active
19/12/2008 10:35:29 Profile Updated
19/12/2008 10:35:29 OffPeakTime active
19/12/2008 10:35:30 Cancel Job:1, Type:"Sync Job On Profile":
19/12/2008 10:35:43 HTTP error code=500
19/12/2008 10:35:43 HTTP Server Error 500: Internal Server Error
19/12/2008 10:40:12 OffPeakTime active
19/12/2008 10:42:23 Profile Updated
19/12/2008 10:42:23 OffPeakTime active
19/12/2008 10:42:36 HTTP error code=500
19/12/2008 10:42:36 HTTP Server Error 500: Internal Server Error
19/12/2008 10:43:44 Profile Updated
19/12/2008 10:43:45 OffPeakTime active
19/12/2008 10:43:45 Profile Updated
19/12/2008 10:43:46 OffPeakTime active
19/12/2008 10:43:59 HTTP error code=401
19/12/2008 10:43:59 HTTP Server Error 401: UnAuthorized
19/12/2008 10:46:17 Profile Updated
19/12/2008 10:46:17 OffPeakTime active
19/12/2008 10:46:18 Profile Updated
19/12/2008 10:46:19 OffPeakTime active
19/12/2008 10:46:20 Cancel Job:5, Type:"Sync Job On Profile":
19/12/2008 10:46:33 HTTP error code=401
19/12/2008 10:46:33 HTTP Server Error 401: UnAuthorized
19/12/2008 10:47:50 HTTP error code=401
19/12/2008 10:47:50 HTTP Server Error 401: UnAuthorized
19/12/2008 10:49:54 HTTP error code=401
19/12/2008 10:49:54 HTTP Server Error 401: UnAuthorized
19/12/2008 10:51:02 Profile Updated
19/12/2008 10:51:02 OffPeakTime active
19/12/2008 10:51:03 Profile Updated
19/12/2008 10:51:04 OffPeakTime active
19/12/2008 10:51:15 HTTP error code=500
19/12/2008 10:51:15 HTTP Server Error 500: Internal Server Error
19/12/2008 10:53:02 Profile Updated
19/12/2008 10:53:03 OffPeakTime active
19/12/2008 10:53:04 Profile Updated
19/12/2008 10:53:04 OffPeakTime active
19/12/2008 10:53:05 Cancel Job:10, Type:"GlobalAddressLookup":
19/12/2008 10:53:31 Profile Updated
19/12/2008 10:53:31 Cancel Job:11, Type:"UnKnown Job":
19/12/2008 10:53:31 OffPeakTime active
19/12/2008 10:53:32 HTTP error code=403
19/12/2008 10:53:32 HTTP Server Error 403 : Forbidden
19/12/2008 10:53:43 HTTP error code=403
19/12/2008 10:53:43 HTTP Server Error 403 : Forbidden
19/12/2008 10:53:51 HTTP error code=403
19/12/2008 10:53:51 HTTP Server Error 403 : Forbidden
19/12/2008 10:54:41 Profile Updated
19/12/2008 10:54:41 OffPeakTime active
19/12/2008 10:54:50 HTTP error code=500
19/12/2008 10:54:50 HTTP Server Error 500: Internal Server Error
19/12/2008 11:24:50 HTTP error code=500
19/12/2008 11:24:50 HTTP Server Error 500: Internal Server Error
19/12/2008 11:54:51 HTTP error code=500
19/12/2008 11:54:51 HTTP Server Error 500: Internal Server Error
20/12/2008 12:17:46 HTTP error code=500
20/12/2008 12:17:46 HTTP Server Error 500: Internal Server Error
20/12/2007 12:24:37 OffPeakTime active
20/12/2007 12:24:49 HTTP error code=500
20/12/2007 12:24:49 HTTP Server Error 500: Internal Server Error
20/12/2008 12:25:23 AUDT Timer expired
20/12/2008 12:25:23 OffPeakTime active
20/12/2008 12:25:23 OffPeakTime active
20/12/2008 12:25:25 OffPeakTime active
20/12/2008 12:26:38 HTTP error code=500
20/12/2008 12:26:38 HTTP Server Error 500: Internal Server Error
20/12/2007 12:29:46 OffPeakTime active
20/12/2008 12:32:11 AUDT Timer expired
20/12/2008 12:32:11 OffPeakTime active
20/12/2008 12:32:11 OffPeakTime active
20/12/2008 12:32:21 HTTP error code=500
20/12/2008 12:32:21 HTTP Server Error 500: Internal Server Error
20/12/2008 12:40:09 OffPeakTime active
Any idea ?

I have the same problem, the microsoft link not solve my problem:
23/10/2009 11:42:36 Profile Updated
23/10/2009 11:42:36 PeakTime active
23/10/2009 11:42:42 HTTP error code=501
23/10/2009 11:42:42 HTTP Server Error 501: Not Implemented
23/10/2009 12:16:55 Profile Updated
23/10/2009 12:16:55 PeakTime active
23/10/2009 12:16:56 PING Command Requested
23/10/2009 12:16:59 HTTP error code=403
23/10/2009 12:16:59 Exception during Ping.
23/10/2009 12:16:59 HTTP Server Error 403 : Forbidden
23/10/2009 12:17:00 Error occurred during Ping.
23/10/2009 12:17:00 Error occurred during Ping. Setting Status to Waiting For Reconnect
23/10/2009 12:17:15 HTTP error code=403
23/10/2009 12:17:15 HTTP Server Error 403 : Forbidden
23/10/2009 12:17:35 HTTP error code=403
23/10/2009 12:17:35 HTTP Server Error 403 : Forbidden
23/10/2009 12:17:55 HTTP error code=403
23/10/2009 12:17:55 HTTP Server Error 403 : Forbidden
23/10/2009 12:21:55 PING Command Requested
23/10/2009 12:21:58 HTTP error code=403
23/10/2009 12:21:58 Exception during Ping.
23/10/2009 12:21:58 HTTP Server Error 403 : Forbidden
23/10/2009 12:21:58 Error occurred during Ping.
23/10/2009 12:21:58 Error occurred during Ping. Setting Status to Waiting For Reconnect
Many thanks

Mail for Exchange / Small Business Server

It appears that Nokia has overlooked a part of the market with its Mail for Exchange application. Apparently, M4E has difficulty communicating with Exchange if it is part of Small Business Server and a self signed certificate is used.
It would be a good idea if someone at Nokia reads this and cares to put it on a list of 'things we could do - to keep customers happy". Small Business Sever is Microsoft's Server product for up to 75 clients. That is a nice world wide market of small businesses that are known to adept quickly, unlike larger organizations.
This lack of "sweating the details" has caused me personally probably 20-30 hours, and judging from the the number of entries other people have also wasted lots of time.
In addition to the time wasted, we are now forced to purchased a commercial server certificate.
More details on the M4E/SBS issue can be found here: http://blogs.technet.com/sbs/archive/2006/12/07/using-a-nokia-device-to-sync-with-small-business-ser...

Has this been corrected in 1.5.0? the realser notes state
"Support for Microsoft Small Business Server"
John32

E50 Mail for Exchange - "Exchange Server Error" co...

Mail for Exchange cannot synchronize with the Exchange Server. The most usefull information can be found in the IIS log for the ActiveSync Server. (Se below)
Does any one know what the error code 1236 refers to?
2007-02-23 14:39:36 158.39.96.10 OPTIONS /Microsoft-Server-ActiveSync User=akvaplan%5Cjos&DeviceId=IMEI251892015795724&DeviceType=IMEI351892015799724&Log=VNATNASNC:0A0C0D0FS:0A0C0D0SP:0C0I0S0R0S0L0H 80 - 212.17.141.53 NokiaE50/1.0 200 0 0
2007-02-23 14:39:50 158.39.96.10 POST /Microsoft-Server-ActiveSync User=akvaplan%5Cjos&DeviceId=IMEI251892015795724&DeviceType=IMEI351892015799724&Cmd=FolderSync&Log=VNATNASNC:0A0C0D0FS:0A0C0D0SP:0C0I0S0R0S0L0H 80 - 212.17.141.53 NokiaE50/1.0 500 0 1236

Finally found the solution, and thought to post it in case someone else has the same problem.
First make sure ActiveSync at the Exchange server is set up correctlt. Follew the instructions at http://support.microsoft.com/?kbid=817379 , method 2
BUT the article is wrong at points 13 and 14:
13. Under IP address and domain name restrictions, click Edit.
14. Click Denied access, click Add, click Single computer, type the IP address of the server that you are configuring, and then click OK.
If you skip these points (do not deny access to all), it works!

Mail for Exchange - doesn't work with Ex. server 2...

I wanted to connect my N900 to Exchange server 2003 (ES2003). There is a problem in answer from ES2003. It doesn't answer.
Is there any setting I cannot to find or any apps which can solve this problem?

Bleky wrote:
I wanted to connect my N900 to Exchange server 2003 (ES2003). There is a problem in answer from ES2003. It doesn't answer.
Is there any setting I cannot to find or any apps which can solve this problem?
Check the Maemo Wiki: Mail for Exchange
http://wiki.maemo.org/Mail_For_Exchange_%28MfE%29_Heartbeat_and_FAQ
and discussion at:
http://talk.maemo.org/showthread.php?t=35136

N8: Mail for exchange and changing server name?

Hello,
I did setup company mail for my new N8 using mail for exchange. I entered email address and username and phone automatically discovered company mail server name. I would like to change that server information but I can't. If I go mail for exchange properties I can't edit server name?! How can I manually set up server name?

Hi,
I had the same Problem with my N8. The only solution was to delete "Mail for Exchange" profile on the device. After that all contacts, calendar entries and mails wehre deleted.
Now you start from scratch... and create a new Mail for Exchange Profile with the correct settings.
Maybe It's a Problem with your company Mailserver (Active Sync/ Autodiscover) Setup. In my case the autodiscover Funktion ist not correct configured on the mailserver. During Mail for Exchange configuration I will be asked for the correct mailservername. I'm not shure what happend if the autodiscovery function is properly set up. Maybe you will never see a dialog to put in your Servername.

N9 Mail for Exchange Sync failure

I just got the N9 and when setup my mfe account I got a error with " mandatory Mail for Exchange server policy failed. Access refused."
On my previous E7 works fine and never got a problem.
Any tip to solve this problem?

I have the same problem, I have tried out all thinkable combination’s of port 80, 443, Non-provisionable devide, but nothing works. I can log on to the web exchange server I can see that the N9 has been in connection, but it seems that it fails before completing.
My company exchange server forces me to create a phone lock code and that remains active even after deleting the exchange account. I am not able to change this, only by resetting the phone deleting everything I can get rid of the code.
I have no doubt, that this is something to do with the settings on the company exchange server that are very strict. And the N9 can for some reason not deal with this.
I can use the exchange account with no problems on my e52, 5800 and N8 so the problem is the N9 and not the server.
Attachments:
Exchange server after setup.JPG ‏65 KB
Server settings.JPG ‏69 KB

E6-00 Error mandatory server policy failed access ...

Hello
We just got a new E6-00 and wanted to connect it to our Exchange 2007 Servers using Mail for Exchange and Activesync.
We get the error "mandatory server policy failed access refused". E72 Nokia work with the same Activesync policy and E7-00 also. We have in the policy the setting that the device must be encrypted and I think this causes the error.
Does somebody know what can be done to get the E6-00 to connect, without changing the Activesync Policy?
Thank you for your answers.
regards
d
r

Hi, Even same isue being observed in E7-00(RM-626) with updated mail for exchange 3.0; but this time now admin_log.txt shows some more help regarding failure.
"04/12/2011 19:46:00 Policy Update: Partial failure
04/12/2011 19:46:00 Policy status 2
04/12/2011 19:46:00 Refused exchange access.
04/12/2011 19:46:00 Policy Update: This device is unable to implement all requested 04/12/2011 19:46:00 password policies. Your Exchange Server's 'Device Security'
04/12/2011 19:46:00 settings are currently configured to disallow access
04/12/2011 19:46:00 from any device that can't support all password policies.
04/12/2011 19:46:00 Contact your Exchange Administrator.
04/12/2011 19:46:00 ProcessStatusResponse LEAVE error=-15017
04/12/2011 19:46:00 CEasCmdHandler:oRunL - Main state machine. PreviousMainState = 8.CurrentMainState = 3. CurrentPolicyState =2.Error =-15017"
so we can approch exchnage server administrator for help and provide little lenecy for configuring mail on E7 handset. i have tried similar connection on iphone and android its working, i am attaching snapshot of android handset procedure which shows server policy downloaded from the GW server. this may help coder for resolution and make nokia suceed in CBA for mail for exchnage.
complete log attached for reference.
04/12/2011 19:40:37 Profile Updated
04/12/2011 19:45:38 Connected to connection method named Vodafone Mobile Connect with type Packet Data
04/12/2011 19:45:44 HTTP error code=449
04/12/2011 19:45:44 Policy Update: The Exchange Server has new Policy information. 04/12/2011 19:45:44 Policy Update: Requesting Policy.
04/12/2011 19:45:44 Server Protocol Version for provisioning is 4
04/12/2011 19:45:44 Ready to process policy response
04/12/2011 19:45:45 Continue Processing elements
04/12/2011 19:45:45 The following policies are not relevant to our phone
04/12/2011 19:45:45 Policy PasswordRecoveryEnabled = 0
04/12/2011 19:45:45 Policy AllowIrDA = 1
04/12/2011 19:45:45 Policy AllowRemoteDesktop = 1
04/12/2011 19:45:45 Policy MaxEmailHTMLBodyTruncationSize = -1
04/12/2011 19:45:46 Policy AllowSMIMESoftCerts = 1
04/12/2011 19:45:46 Policy AllowSMIMEEncryptionAlgorithmNegotiation = 2
04/12/2011 19:45:46 Policy AllowDesktopSync = 1
04/12/2011 19:45:46 Policy Approved Application List
04/12/2011 19:45:46 Policy Unapproved Application List
04/12/2011 19:45:46 End of not relevant policies section
04/12/2011 19:45:46 Version 12.0 policies
04/12/2011 19:45:46 Policy DevicePasswordEnabled = 1
04/12/2011 19:45:46 Policy RequireStorageCardEncryption = 1
04/12/2011 19:45:46 Policy RequireDeviceEncryption = 1
04/12/2011 19:45:46 Policy AlphanumericDevicePasswordRequired = 0
04/12/2011 19:45:46 Policy AttachmentsEnabled = 1
04/12/2011 19:45:46 Policy AllowSimpleDevicePassword = 1
04/12/2011 19:45:46 Policy MinPasswordLength =4
04/12/2011 19:45:46 Policy MaxInactivityTimeDeviceLock = 1800
04/12/2011 19:45:46 Policy MaxDevicePasswordFailedAttempts = 5
04/12/2011 19:45:46 Policy MaxAttachmentSize = -1
04/12/2011 19:45:46 Policy DevicePasswordExpiration = -1
04/12/2011 19:45:46 Policy DevicePasswordHistory = 0
04/12/2011 19:45:46 End Version 12.0 policies
04/12/2011 19:45:46 Version 12.1 policies
04/12/2011 19:45:46 Policy EmailBodyTruncateSize = -1
04/12/2011 19:45:46 Policy MaxCalendarAgeFilter = 0
04/12/2011 19:45:46 Policy MaxEmailAgeFilter = 0
04/12/2011 19:45:46 Policy MinDevicePasswordComplexCharacters = 3
04/12/2011 19:45:46 Policy AllowStorageCard = 1
04/12/2011 19:45:46 Policy AllowCamera = 1
04/12/2011 19:45:46 Policy AllowWiFi = 1
04/12/2011 19:45:46 Policy AllowBluetooth = 2
04/12/2011 19:45:46 End Version 12.1 policies
04/12/2011 19:45:46 The following received policies may cause us to fail server policy support
04/12/2011 19:45:47 Policy AllowTextMessaging = 1
04/12/2011 19:45:47 Policy SyncWhileRoaming = 1
04/12/2011 19:45:47 Policy AllowHtmlEmail = 1
04/12/2011 19:45:47 Policy RequireSignedSMIMEMessages = 0
04/12/2011 19:45:47 Policy RequireEncryptedSMIMEMessages = 0
04/12/2011 19:45:47 Policy RequireSignedSMIMEAlgorithm = 0
04/12/2011 19:45:47 Policy RequireEncryptionSMIMEAlgorithm = 0
04/12/2011 19:45:47 Policy AllowUnsignedApplications = 1
04/12/2011 19:45:47 Policy AllowUnsignedInstallationPackages = 1
04/12/2011 19:45:47 Policy AllowInternetSharing = 1
04/12/2011 19:45:47 Policy AllowPOPIMAPEmail = 1
04/12/2011 19:45:47 Policy AllowConsumerEmail = 1
04/12/2011 19:45:47 Policy AllowBrowser = 1
04/12/2011 19:45:47 *** Warning: Some unsupported server policies were found -- syncing may fail
04/12/2011 19:45:59 Policy Download: Updating to KAttachmentsEnabled = 1
04/12/2011 19:45:59 Policy Download: Updating to KMaxAttachmentSize = 0
04/12/2011 19:45:59 Policy Download: Updating to KEmailBodyTruncationSize = -1 04/12/2011 19:45:59 Policy Download: Updating to KMessageFormat = 1
04/12/2011 19:45:59 Policy Download: Updating to RequireManualSyncWhenRoaming = 1 04/12/2011 19:45:59 Policy Download: Updating to KMaxCalendarAgeFilter = 0
04/12/2011 19:45:59 Policy Download: Updating to KMaxEmailAgeFilter = 0
04/12/2011 19:46:00 Policy Update: Partial failure
04/12/2011 19:46:00 Policy status 2
04/12/2011 19:46:00 Refused exchange access.
04/12/2011 19:46:00 Policy Update: This device is unable to implement all requested 04/12/2011 19:46:00 password policies. Your Exchange Server's 'Device Security'
04/12/2011 19:46:00 settings are currently configured to disallow access
04/12/2011 19:46:00 from any device that can't support all password policies.
04/12/2011 19:46:00 Contact your Exchange Administrator.
04/12/2011 19:46:00 ProcessStatusResponse LEAVE error=-15017
04/12/2011 19:46:00 CEasCmdHandler:oRunL - Main state machine. PreviousMainState = 8.CurrentMainState = 3. CurrentPolicyState =2.Error =-15017
Attachments:
Android_mail.pdf ‏1299 KB

MfE on N8 Anna - Mandatory server policy failed. A...

Was previously using MfE on N8 with PR1.2 to our corporate exchange server with no problem. The server has security poicly that enforces setting of keylock code and keylock timeout.
Following update to Anna yesterday I'm no longer able to access my exchange mail. The error "Mandatory server policy failed. Access was refused. Contact your Exchange administrator." is displayed. This is a major disaster!
I do not have any control over the Exchange server - and am not able to get any settings changed.
I don't want to delete acount and recreate as if it fails I'll loose all syncronised contacts on phone.
I've seen other threads of MfE access problems, but my problem is specific to the security policy issue.
Regards
Cliff

This item is listed in another topic as solved but unfortunately it is not solved.
It is shame for Nokia. This problem is known since Mid of Jun 2011 so since 4 months, but nothing done.
Altough I just updated my device in mid of October, I was not informed by anyone about this bug.
Blackbarry has published a lot of free applications to their customers because of just two days down time in their mail server. We will see also the power of Nokia after resolvng the problem, (surely if ever anyone resolves this problem)
Thank you Nokia, that you are connecting us just with you by this kind of forums instead of with people...

E90 mail for exchange issue - spurious calendar en...

My Chief Exec uses an E90 to connect to an Exchange 2007 server, using Mail for Exchange.
Everything syncs ok but some of his calendar entries refuse to sync onto the phone so we can't guarantee that he has all his meetings available.
It does the same for 2.0.7 and 2.0.9
I moved his sim into a Palm Treo and the calendar picked up everything.
Any ideas?

Don't know if it helps but we were told that turning off Cached Exchange mode, in Outlook, resolves the issue. Only problem is that our exchange server is run by a third party company and Cached Echange mode is mandatory to using Outlook. You just get blocked if you haven't enabled it. Catch 22. Looks like it will be Smartphones for the whole of the my company. Thats a massive market that Nokia have just lost, considering that we are the third biggest employer in the world.

Mail for Exchange credential error or corrupted

Hello everybody. I have a latest firmware update (V 06.41.3.0) Nokia E50 and Mail for Exchange latest update also (1.06) installed on it.
In my windows installation there are a policy to change password every 30 days and all works fine in my phone after first day I change password in my Windows account for policy reasons. My problem is as follows:
I have a M4E configuration working correctly. My first syncronisation works fine and I have all my Exchange contacts, Calendar and Mail. This works fine for several times for several hours but suddenly the sync process locks my user account in Windows and I have a message in device noting this situations. After this situation, I call to my Help Desk to unlock user account and all begins to work fine without changing nothing included password credential in M4E.
Why M4E locks my Windows user account?
Looks like M4E sometimes doesn't read password correctly...I'm sure that action that lock my Windows account is M4E syncronisation because log in Front-End server has 3 times a HTTP 401 message comming from my device.
What happen? my account has any problem? what do you think?....any clue will be appreciate...
Regards
Daniel

Hey All, I had these problems:
07/04/2008 10:53:46 HTTP error code=401
07/04/2008 10:53:46 HTTP Server Error 401: UnAuthorized
...and the exchange administrator sorted it out for me straight away as below;
It’s the IIS settings that changed. I can only assume that it was some update that was applied but I don’t know who did it.
The IIS security settings need to be...
For the Exchange web site and the Microsoft-Server-Activesync site and the OMA site.
They should be setup for Anonymous access for the ExchWeb site.
The default domain should be your AD domain name.
This configuration works.
A screen capture that describes this is available here:
http://farm3.static.flickr.com/2235/2398972715_e1ba4ca6ec.jpg?v=0
Hope this helps.
Luke.

Mail For Exchange - Compatability/Downloads menu i...

Using N79
SW 31.002.205.4.
Up until this morning running MfE 2.9.158. Just been offerred 2.9.160 via App.Update. Post install check indicates this has been available for months - why the delay in pushing it through to App.Update?
MfE 2.9.160 still not fixed old issue of being unable to open MfE settings following phone restart - why not? - threads dating back to 1st quarter 2009! but this one explains the issue precisely:
/t5/Messaging-Email-and-Browsing/Mail-for-Exchange-corrupted/m-p/603626/highlight/true#M21922
It's the only app on my phone that cannot be routinely opened - not good.
Notwithstanding this idiosyncrasy email syncing is more hit than miss but falls way short of my iPod touch which is 100% rock solid regarding Exchange compatability. Does Nokia want Exchange Server based customers- my guess is not enough. Generally speaking if I notice emails hitting my iPod but not my N79 it's time for a phone restart. But that kills the ability to open MfE settings So it's back to a re-install.
If the above isn't bad enough Nokia has just made it worse. This "current" link from the N79 support page is dead;
http://businesssoftware.nokia.com/mail_for_exchange_downloads.php
and after much dead-ending find that the Ovi Store now contains MfE - no problem with that it makes sense to consolidate. But no mention of N79 being supported by the latest greatest MfE and Ovi only lists 3.0 as supporting FP1 phones - so wht about FP2?
Is my N series phone supported anymore - I've got no idea.
Wake up Nokia it's 2010 not 1990 - we shouldn't have to put up with this **bleep** in basic functionality.
Judging by lack of action over the past 12 months have no hope Nokia will put this right but that my dear Nokia is how you lose customers to your rivals Apple and RIM. Pull your finger out.

I'm hoping this fix works for me long term and post as is.
Multiple phone calls to Nokia Tier 1 and 2 phone support heavily supplemented by some determined Google searching led me to the following solution.
First off the bad news. To fix the MfE issue requires a hard reset of the device. There's no way around this so resign yourself to it early.
The good news however is you can dramatically reduce the time needed to return your device back to its pre-reset condition by backing up your device using Ovi Suite. Forget to do this and you'll be re-installing your apps one at a time.
My issue was made more difficult because the usual hard re-set code (*#7370 #) would not reset the device i.e. full recovery of phone memory, complete wiping of contacts etc. Ignoring Nokia's advice to return the phone for repair! I turned up an alternative method which achieved the hard re-set I was seeking.
As follows:
Hold these three keys down - *, 3 and green accept call - whie the phone is off, then power on keeping them depressed until the Nokia logo plays.
On the N79 this involves an usual amount of manual dexterity but nevertheless worked where the re-set code failed. Hopefully this won't be necessary for most users.
Once re-set you will be presented with the Set up menu as per a new phone.
With a fully recovered phone memory you can now restore your earlier backup via Ovi Suite, which for me did 90% of the work needed to get my phone back to its earlier personalised condition. I took the opportunity of checking for any programme updates of essential apps and updated as necessary. Re-installation of Speed Dial settings and permitted Bluetooth devices amongst other items was required but all in all all my data and file structure was faithfully restored first time around.
I am now running MfE 3.0 (actually 2.09.208 - see initial thread posting ) which Nokia support advise is not supported for the N79 - given the varying level of advice received I'm prepared to run with my own view that it works fine. If you wish to play safe you should be running 2.9.160.
I have re-booted the phone multiples times over the last two days and on only one occasion (which I'm going to pretend never happened) MfE has been rock solid. In addition Ovi Maps which had stopped opening - and was fundamentally what set me off down the road of a hard re-set - is now working perfectly.
I'm hoping this cures the irritating MfE problem long term pending Nokia sorting out whether they even support the N79 any longer as far as MfE is concerned.
As a sign off I will just say for my purposes the N79 is the best smartphone I've ever owned and supplemented with an iPod Touch is a fantastic work/play combination. If you are allowed tethering on your contract I contend Walking Hot Spot is THE killer app and so confident am I of my choice of phone I've just bought a second N79, at a much reduced price, which I'm going to use as a backup/extension to my existing N79 when it dies and goes to heaven.
Hope this post saves someone else some timeand effort.

Problem with Mail For Exchange over Nokia E7-00 (a...

Hi, I have a problem with my nokia E7-00 (Symbian Anna).
Until recently it worked fine with my terminal synchronization with GMAIL via Mail For Exchange.
I synchronized the mail (including folders / labels I have on my account), address book and calendar.
Suddenly, this synchronization does not work anymore, the mail is no longer recovered, the calendar does not show appointments and contacts are no longer synchronized.
Trying to send an email that works perfectly, but the mail is not saved in Sent folder on my nokia e7-00, also if I search on the remote server is a contact I found it perfectly.
In practice it seems that something in the synchronization mechanism does not work.
Do you have ideas on how to fix this problem?
Thanks in advance.
MP

You may try rebooting the device to check if it works. If this did not help, you will have to re-setup outlook account on your device to get it worked.
Hope, this can resolve your issue.

Calendar sync problem with Mail for Exchange

I have troubles syncing my calendar with Mail for Exchange.
I've configured MfE the same way I did on my N8-00 and it worked perfectly there. On my new N9 it just syncs Mail and the ToDo list of from the Exchange Server. Any suggestions what I am doing wrong?
Also, when I remove my MfE settings, the Calendars still are in the Calendar App. How can I delete them?

Hi,
There could be some problem with the contact sync, because you had synched with MFE . Remove the existing sync for Mail for exchange and then try creating a new sync and then check, That should maybe solve the issue.
I had mfe configured and then removed and now then i sync with the Address book and Ical. Seems to be working fine for me, just that i use a N95.
Hopefully it fixes, let me know the outcome.
Cheers
Sandy
Helpful information, then dont forget to hit the kudos star :-) Or say it accepted solution and thanks

N9 after PR 1.2 update - Mail for Exchange is sync...

I have a problem with my N9 Meego after 1.2 update. I have mail for exchange account talking with exchange 2010 server and sync works just just fine with calendar and e-mail. Contacts on otherhand doens`t work. It says its bringing contact like 78 from mail for exchange but when its done you can`t see any.
i have done my account again many times but still contacts aren`t working. Should I do some hardreset but does that uninstall PR 1.2 update?
Help is needed or any ideas what could be done?
-mika

Hey mate, As far as I am aware there is no going back from PR 1.2, so you could try hardreset without concern of loosing this update. Keep in mind you are likely to lose data, so make sure you back it up first.
I am sure of this, as I have tried to go back to PR 1.1 to get my mail exchange to work and even with trying to flash the device "downgrade disallowed" comes up and prevents me getting rid of the PR 1.2
You are luckier than me, I can't get mail, calender or contacts. I am so annoyed that I accepted the update. I am hoping that Nokia take note of this and fix the mail exchange in a new update

E6 - Mail for Exchange (Mandatory Server Policy Fa...

Similar Messages

Maybe you are looking for