Active Topics
-
Maemo repository (4)
to Community by teroyk - 14 hrs, 55 mins ago -
Error after installing Leste on sdcard (13)
to Maemo 7 / Leste by Maemish - 1 day, 21 hrs ago -
TLS 1.2 for N9 is ready (29)
to MeeGo / Harmattan by smatkovi - 2 days, 6 hrs ago -
Camera phone competition March 2023 "Endless" (35)
to General by Maemish - 5 days, 15 hrs ago - more...
javierinclan |
2010-02-17
, 21:20
|
|
Posts: 14 |
Thanked: 0 times |
Joined on Feb 2010
@ USA
|
#1
|
I have installed correctly the certificate and have the latest 3.xx firmware. It still will not alllow the MFE initial sync. Says communication with exchange server fails.
|
|
2010-02-17
, 21:27
|
|
Posts: 14 |
Thanked: 0 times |
Joined on Feb 2010
@ USA
|
#2
|
I have the N900. Other mail accounts work fine.
|
|
2010-02-17
, 21:27
|
|
Posts: 3,617 |
Thanked: 2,412 times |
Joined on Nov 2009
@ Cambridge, UK
|
#3
|
Originally Posted by javierinclan
Does your Exchange server require provisioning support?
I have installed correctly the certificate and have the latest 3.xx firmware. It still will not alllow the MFE initial sync. Says communication with exchange server fails.
|
|
2010-02-17
, 21:28
|
|
Posts: 14 |
Thanked: 0 times |
Joined on Feb 2010
@ USA
|
#4
|
It is set up to accept non provisional devices.
|
|
2010-02-17
, 21:42
|
|
Posts: 14 |
Thanked: 0 times |
Joined on Feb 2010
@ USA
|
#7
|
I got a message that if I wanted to break my phone to continue...
|
|
2010-02-17
, 21:45
|
|
Posts: 3,617 |
Thanked: 2,412 times |
Joined on Nov 2009
@ Cambridge, UK
|
#8
|
Originally Posted by javierinclan
At what point did you get that message?
I got a message that if I wanted to break my phone to continue...
|
|
2010-02-17
, 21:47
|
|
Posts: 14 |
Thanked: 0 times |
Joined on Feb 2010
@ USA
|
#9
|
right after I executed the # start sysklogd
|
|
2010-02-17
, 21:49
|
|
Posts: 3,617 |
Thanked: 2,412 times |
Joined on Nov 2009
@ Cambridge, UK
|
#10
|
Originally Posted by javierinclan
Oh, right - I've never actually run this myself. Anyway, if you want the logs & to get this fixed then you're going to have to continue. I don't think there's really much of a danger - just make sure that you disable the logging again when you're finished.
right after I executed the # start sysklogd