Hello,

i have a problem, because my N900, maemo 5, ver: 2.2009.51-1, is missing a lot of certs. It is like described in

https://bugs.maemo.org/show_bug.cgi?id=7357,

but i can't imagine that i'm not able to reinstall a package with this cert's that should be originally on the phone. Or did i only missed the right documentation how an d where to reget a basic-packet?

Please help.

With regards,
Christian

I doubt this is related - that bug was fixed in PR1.1 (MfE no longer uses a separate certificate store). The certificates would seem to be part of the maemosec-certman-common-ca package, so you could try running (in X Terminal):

hi Rob,

i've done this, there was one error:
1. "Notice, ... in oder to use this package, you must download and inst a very large image file . ... . "

If i click OK, (there is no extra disk with >1GB), then there will nothing mounted and the install proceed with an error, that the package was not correctly installed.

If i install again, same error (about Notice: ...), but installation went through without any error at the end of installation-process.
The count is now less then before:
ls -la /etc/certs/common-ca/ | grep -c lrw
118

But now, the directory /home/user/.maemosec-certs is missing at all :-(

Any ideas how to solve this problem?

regards,

Christian

Not sure why you got that notice - that looks like the alert for the debian-chroot package.

The number of certs you've got matches mine, so that looks okay. The /home/user/.maemosec-certs directory shouldn't be affected by this though. Mine is empty apart from the couple of CA certificates I've imported, so I don't know whether that matters anyway.

What errors are you actually getting with certificates now?

You are right, but i don't know why. Perhaps , because i've cancelled this installation-process when this messge appeared.


OK, why i reported at this:
i wanted to set up MfE and get message this at many points reported: "Error. Either Exchange server requires secure
connection or account is disabled.".
When I went through the posts and messages for this error, i landed at the above mentioned url because in syslog i found the
activesync[2118]: CurlConnectionManager: cannot get CfgConnExchanegServer
activesync[2118]:"CurlConnectionManager: curl Errorcode = 6"

Here is the syslog of the last MfE-try:
Feb 7 11:27:13 Nokia-N900-51-1 activesync[2163]: AS-COMMON-UTILS Version: libas-common-utils (0.0.2-27+0m5) unstable; urgency=low
Feb 7 11:27:18 Nokia-N900-51-1 activesync[2163]: AsConfigReader: unable to read string value of parameter 4 in account ActiveSyncAccount1. Error 5
Feb 7 11:27:18 Nokia-N900-51-1 activesync[2163]: AsConfigReader: unable to read string value of parameter 0 in account ActiveSyncAccount1. Error 5
Feb 7 11:27:18 Nokia-N900-51-1 activesync[2163]: CurlConnectionManager: cannot get CfgConnExchangeServer
Feb 7 11:27:18 Nokia-N900-51-1 activesync[2163]: AsConfigReader: unable to read string value of parameter 5 in account ActiveSyncAccount1. Error 5
Feb 7 11:27:18 Nokia-N900-51-1 activesync[2163]: CurlConnectionManager: cannot get CfgCredUsername
Feb 7 11:27:18 Nokia-N900-51-1 activesync[2163]: AsConfigReader: unable to read string value of parameter 6 in account ActiveSyncAccount1. Error 5
Feb 7 11:27:18 Nokia-N900-51-1 activesync[2163]: CurlConnectionManager: cannot get CfgCredEncryptedPassword
Feb 7 11:27:18 Nokia-N900-51-1 activesync[2163]: AsConfigReader: unable to read string value of parameter 5 in account ActiveSyncAccount1. Error 5
Feb 7 11:27:18 Nokia-N900-51-1 activesync[2163]: SyncScheduler: cannot get CfgCredUsername
Feb 7 11:27:18 Nokia-N900-51-1 activesync[2163]: AsConfigReader: unable to read string value of parameter 0 in account ActiveSyncAccount1. Error 5
Feb 7 11:27:18 Nokia-N900-51-1 activesync[2163]: CurlConnectionManager: cannot get CfgConnExchangeServer
Feb 7 11:27:18 Nokia-N900-51-1 activesync[2163]: SyncScheduler: Cancel all actions
Feb 7 11:27:18 Nokia-N900-51-1 activesync[2163]: ASDAEMON Version: 'as-daemon (0.0.2-28+0m5) unstable; urgency=low' starting
Feb 7 11:27:18 Nokia-N900-51-1 activesync[2163]: GLIB DEBUG ConIc - con_ic_connection_send_event(0x18ac10, 5ad15134-0d28-4bbb-8b23-5b9483d75704, WLAN_INFRA, 0)
Feb 7 11:27:18 Nokia-N900-51-1 activesync[2163]: ICListener: IAP '5ad15134-0d28-4bbb-8b23-5b9483d75704' with bearer 'WLAN_INFRA': connected; count 1
Feb 7 11:28:30 Nokia-N900-51-1 activesync[2163]: HTTP STATUS: 0
Feb 7 11:28:30 Nokia-N900-51-1 activesync[2163]: CurlConnectionManager: cURL errorcode = 6
Feb 7 11:30:24 Nokia-N900-51-1 activesync[2163]: HTTP STATUS: 0
Feb 7 11:30:24 Nokia-N900-51-1 activesync[2163]: CurlConnectionManager: cURL errorcode = 6
Feb 7 11:31:45 Nokia-N900-51-1 activesync[2163]: HTTP STATUS: 0
Feb 7 11:31:45 Nokia-N900-51-1 activesync[2163]: CurlConnectionManager: cURL errorcode = 6
Feb 7 11:32:25 Nokia-N900-51-1 activesync[2163]: HTTP STATUS: 0
Feb 7 11:32:25 Nokia-N900-51-1 activesync[2163]: CurlConnectionManager: cURL errorcode = 6
Feb 7 11:32:33 Nokia-N900-51-1 activesync[2163]: AS-LIB: Version: libas-protocol (0.0.2-27+0m5) unstable; urgency=low
Feb 7 11:32:33 Nokia-N900-51-1 activesync[2163]: CurlConnectionManager: cURL errorcode = 6
Feb 7 11:32:33 Nokia-N900-51-1 activesync[2163]: AS-LIB: Received HTTP response 904. Factory not created
Feb 7 11:32:51 Nokia-N900-51-1 activesync[2163]: AS-LIB: Version: libas-protocol (0.0.2-27+0m5) unstable; urgency=low
Feb 7 11:32:51 Nokia-N900-51-1 activesync[2163]: CurlConnectionManager: cURL errorcode = 60
Feb 7 11:32:51 Nokia-N900-51-1 activesync[2163]: AS-LIB: Received HTTP response 888. Factory not created
Feb 7 11:32:59 Nokia-N900-51-1 activesync[2163]: AS-LIB: Version: libas-protocol (0.0.2-27+0m5) unstable; urgency=low
Feb 7 11:32:59 Nokia-N900-51-1 activesync[2163]: CurlConnectionManager: cURL errorcode = 60
Feb 7 11:32:59 Nokia-N900-51-1 activesync[2163]: AS-LIB: Received HTTP response 888. Factory not created


....


Feb 7 14:01:47 Nokia-N900-51-1 activesync[2163]: GLIB DEBUG ConIc - con_ic_connection_send_event(0x18ac10, 5ad15134-0d28-4bbb-8b23-5b9483d75704, WLAN_INFRA, 2)
Feb 7 14:01:47 Nokia-N900-51-1 activesync[2163]: ICListener: IAP '5ad15134-0d28-4bbb-8b23-5b9483d75704' with bearer 'WLAN_INFRA': disconnecting; count 0

....
Feb 7 17:22:47 Nokia-N900-51-1 activesync[2118]: AS-COMMON-UTILS Version: libas-common-utils (0.0.2-27+0m5) unstable; urgency=low
Feb 7 17:22:52 Nokia-N900-51-1 activesync[2118]: AsConfigReader: unable to read string value of parameter 4 in account ActiveSyncAccount1. Error 5
Feb 7 17:22:52 Nokia-N900-51-1 dbus[700]: WARNING: match destination=':1.198' added by :1.198 (pid=2118, uid=29999) who owns services:
Feb 7 17:22:52 Nokia-N900-51-1 dbus[700]: :1.198
Feb 7 17:22:52 Nokia-N900-51-1 activesync[2118]: AsConfigReader: unable to read string value of parameter 0 in account ActiveSyncAccount1. Error 5
Feb 7 17:22:52 Nokia-N900-51-1 activesync[2118]: CurlConnectionManager: cannot get CfgConnExchangeServer
Feb 7 17:22:52 Nokia-N900-51-1 activesync[2118]: AsConfigReader: unable to read string value of parameter 5 in account ActiveSyncAccount1. Error 5
Feb 7 17:22:52 Nokia-N900-51-1 activesync[2118]: CurlConnectionManager: cannot get CfgCredUsername
Feb 7 17:22:52 Nokia-N900-51-1 activesync[2118]: AsConfigReader: unable to read string value of parameter 6 in account ActiveSyncAccount1. Error 5
Feb 7 17:22:52 Nokia-N900-51-1 activesync[2118]: CurlConnectionManager: cannot get CfgCredEncryptedPassword
Feb 7 17:22:52 Nokia-N900-51-1 activesync[2118]: AsConfigReader: unable to read string value of parameter 5 in account ActiveSyncAccount1. Error 5
Feb 7 17:22:52 Nokia-N900-51-1 activesync[2118]: SyncScheduler: cannot get CfgCredUsername
Feb 7 17:22:52 Nokia-N900-51-1 activesync[2118]: AsConfigReader: unable to read string value of parameter 0 in account ActiveSyncAccount1. Error 5
Feb 7 17:22:52 Nokia-N900-51-1 activesync[2118]: CurlConnectionManager: cannot get CfgConnExchangeServer
Feb 7 17:22:52 Nokia-N900-51-1 activesync[2118]: SyncScheduler: Cancel all actions
Feb 7 17:22:52 Nokia-N900-51-1 activesync[2118]: ASDAEMON Version: 'as-daemon (0.0.2-28+0m5) unstable; urgency=low' starting
Feb 7 17:22:52 Nokia-N900-51-1 dbus[890]: WARNING: match destination=':1.119' added by :1.119 (pid=2118, uid=29999) who owns services:
Feb 7 17:22:52 Nokia-N900-51-1 dbus[890]: :1.119
Feb 7 17:22:52 Nokia-N900-51-1 activesync[2118]: GLIB DEBUG ConIc - con_ic_connection_send_event(0x18a410, 5ad15134-0d28-4bbb-8b23-5b9483d75704, WLAN_INFRA, 0)
Feb 7 17:22:52 Nokia-N900-51-1 activesync[2118]: ICListener: IAP '5ad15134-0d28-4bbb-8b23-5b9483d75704' with bearer 'WLAN_INFRA': connected; count 1
Feb 7 17:23:15 Nokia-N900-51-1 [2091]: GLIB DEBUG hildon-1 - ca_context_play_full Success
Feb 7 17:24:07 Nokia-N900-51-1 activesync[2118]: HTTP STATUS: 0
Feb 7 17:24:07 Nokia-N900-51-1 activesync[2118]: CurlConnectionManager: cURL errorcode = 6
Feb 7 17:25:07 Nokia-N900-51-1 activesync[2118]: AS-LIB: Version: libas-protocol (0.0.2-27+0m5) unstable; urgency=low
Feb 7 17:25:07 Nokia-N900-51-1 activesync[2118]: CurlConnectionManager: cURL errorcode = 60
Feb 7 17:25:07 Nokia-N900-51-1 activesync[2118]: AS-LIB: Received HTTP response 888. Factory not created

...

OK, could you see any help in this. It seems to that there is an error in the activesync dialog. But now the above mentioned error is gone away.

with regards,
Christian

[Update]

The problem with the certificates is solved:

i'v reinstalled them, like rob1n said and installed again the ones from our ext. CA and the exchange-Server, then i am able to go one step more in the MfE-setup-process:
I can choose now, what i want to synchronize and proceed by clicking next, but the synchronisationprocess stops imediately, because i get an Exchange deny-Error. In the N900-syslog i can see the this:

Feb 8 23:59:26 Nokia-N900-51-1 ke_recv[7783]: prop_modified:1889: udi /org/freedesktop/Hal/devices/platform_slide modified button.state.value
Feb 8 23:59:49 Nokia-N900-51-1 ke_recv[7783]: session_sig_handler:860: NotificationClosed for 1
Feb 8 23:59:49 Nokia-N900-51-1 ke_recv[7783]: notification_closed:814: unknown dialog id: 1
Feb 8 23:59:55 Nokia-N900-51-1 activesync[7930]: AS-COMMON-UTILS Version: libas-common-utils (0.0.2-27+0m5) unstable; urgency=low
Feb 8 23:59:55 Nokia-N900-51-1 activesync[7930]: SyncScheduler: Cancel all actions
Feb 8 23:59:56 Nokia-N900-51-1 activesync[7930]: AS-LIB: Version: libas-protocol (0.0.2-27+0m5) unstable; urgency=low
Feb 8 23:59:56 Nokia-N900-51-1 activesync[7930]: AS-LIB: Created factory for version 2.5
Feb 8 23:59:57 Nokia-N900-51-1 activesync[7930]: HTTP STATUS: 403
Feb 8 23:59:57 Nokia-N900-51-1 activesync[7930]: AS-LIB: FolderSync failed with status 403. Abort retrieving estimations
Feb 8 23:59:57 Nokia-N900-51-1 activesync[7930]: ActionFullSync: ItemEstimate failed with status 403. Abort.
Feb 8 23:59:57 Nokia-N900-51-1 [7902]: GLIB DEBUG hildon-1 - ca_context_play_full Success
Feb 9 00:00:00 Nokia-N900-51-1 ke_recv[7783]: session_sig_handler:860: NotificationClosed for 6
Feb 9 00:00:00 Nokia-N900-51-1 ke_recv[7783]: notification_closed:814: unknown dialog id: 6
Feb 9 00:01:45 Nokia-N900-51-1 [7902]: GLIB DEBUG hildon-1 - ca_context_play_full Success


and on the apache-reverse-proxy side in front of the exchange-server i get this:

N900 (IP, Name and IMEI replaced with [...]):
access.log.1:[IP] - - [08/Feb/2010:16:40:10 +0100] "OPTIONS /Microsoft-Server-ActiveSync HTTP/1.1" 200 - "-" "N900/
1.1"
access.log.1:[IP] - - [08/Feb/2010:16:40:11 +0100] "POST /Microsoft-Server-ActiveSync?Cmd=FolderSync&DeviceId=[My IMEI]&DeviceType=SmartPhone HTTP/1.1" 403 44 "-" "N900/1.1"


Why do i see a http error, i thought MfE handles with https?

Au contrair, same MfE with an I-Phone works like a charme (IP, Name and IMEI replaced with [...]):

access.log.1:[IP] - - [08/Feb/2010:13:32:50 +0100] "POST /Microsoft-Server-ActiveSync?User=[my login]&DeviceId=Appl889420HR3NR&DeviceType=iPhone&Cmd=Fo lderSync HTTP/1.1" 449 74 "-" "Apple-iPhone/704.11"
access.log.1:[IP] - - [08/Feb/2010:13:32:51 +0100] "POST /Microsoft-Server-ActiveSync?User=[my login]&DeviceId=Appl889420HR3NR&DeviceType=iPhone&Cmd=Pr ovision HTTP/1.1" 200 945 "-" "Apple-iPhone/704.11"
access.log.1:[IP] - - [08/Feb/2010:13:32:51 +0100] "POST /Microsoft-Server-ActiveSync?User=[my login]&DeviceId=Appl889420HR3NR&DeviceType=iPhone&Cmd=Pr ovision HTTP/1.1" 200 54 "-" "Apple-iPhone/704.11"
access.log.1:[IP] - - [08/Feb/2010:13:32:51 +0100] "POST /Microsoft-Server-ActiveSync?User=[my login]&DeviceId=Appl889420HR3NR&DeviceType=iPhone&Cmd=Fo lderSync HTTP/1.1" 200 1116 "-" "Apple-iPhone/704.11"
access.log.1:[IP] - - [08/Feb/2010:13:32:53 +0100] "POST /Microsoft-Server-ActiveSync?User=[my login]&DeviceId=Appl889420HR3NR&DeviceType=iPhone&Cmd=Sy nc HTTP/1.1" 200 111 "-" "Apple-iPhone/704.11"
access.log.1:[IP] - - [08/Feb/2010:13:32:53 +0100] "POST /Microsoft-Server-ActiveSync?User=[my login]&DeviceId=Appl889420HR3NR&DeviceType=iPhone&Cmd=Sy nc HTTP/1.1" 200 2209 "-" "Apple-iPhone/704.11"
access.log.1:[IP] - - [08/Feb/2010:13:32:54 +0100] "POST /Microsoft-Server-ActiveSync?User=[my login]&DeviceId=Appl889420HR3NR&DeviceType=iPhone&Cmd=Sy nc HTTP/1.1" 200 1668 "-" "Apple-iPhone/704.11"


Funny thing, isn it?

Does anyone know, why my login and foldersync reach an error?
The commands that are shown in the apache-log doesn't seems equal in the syntax used.

with regards,
Christian

Does your Exchange server allow non-provisionable devices?

Hello,

Provisioning is off and there is alredy the same error i've reported earlier.
I cannot already use MfE with our Exchange 2003 and my N900. I've attached the
last log from my N900 with checked the whole MfE-advices from
maemo with MfE including
the ssl-check, which are ok.

We are running exchange 2003 behind a squid reverse-proxy with ssl-certs.

The error is in the attachment documentated, first enhanced n900-log, then two squid-log-parts.
The iPhones are working with any disturbance.

Is there any advice?


With regards,
Christian Kneisel

So the server's set to allow legacy devices?

The problem there is a 403 (permission denied) error from the server, so you'll need to have a look at the server logs (probably IIS, but possibly Exchange) to see why it's returning that. From a quick look through the MfE thread, Vitaliy has said that it usually indicates a provisioning issue though.