Erreur de JavaScript in method ZaController.prototype._setView
Page 1 of 3 123 LastLast
Results 1 to 10 of 24

Thread: Erreur de JavaScript in method ZaController.prototype._setView

  1. #1
    Active Member
    Join Date
    Aug 2015
    Posts
    14

    Erreur de JavaScript in method ZaController.prototype._setView

    Hi,

    I meet a problem since few days. I generate a new certificatin CLI and since ... only my Ipad in zXmobile works. Phone under Android generate a handshake error on logs.
    I try to install le CAcert on phone and only DAVcald works now but, no Sync Account in Exchange mode.

    So I try to generate cert by admin panel on Zimbra directly and now, it's zExtra who generate this error : "Erreur de JavaScript in method ZaController.prototype._setView"
    I try to add the ?dev=1 and the end of the URL not nothing more.

    I need your help to understand :
    - why when I try to generated a new certificate in CLI, zExtras Mobile don't sync on Android (SSLv3 failure on handshake),
    - why when I try to generated a new certificate in Admin Panel, zExtras is dead ( error method ZaController.prototype._setView),
    - how install a self deploy certificate and make everything working again (my old configuration works very well with the defaut Zimbra certificate).

    For Information, I work on Zimbra Version 8.6.0_GA_1153.FOSS 15 Déc 14.

    Thanks a lot.

  2. #2
    ZeXtras Community Manager ZeXtras Employee Cine's Avatar
    Join Date
    Apr 2011
    Posts
    2,360
    Hello shreg,
    welcome to the forums!

    The "disappering zimlet" and SSLv3 handshake error issues are very unlikely to be related.
    To fix the former, clearing both your browser's cache and the zimlet's one should do the trick: you can do so by running the following command as the 'zimbra' user
    Code:
    zmprov fc zimlet com_zextras_zextras
    About the SSLv3 handshake error, could you please add an Account Logger to the affected mailbox, reproduce the issue and send the full error's stacktrace to community@zextras.com? A complete guide about self-signed certificates is available on the Zimbra Wiki, did you follow the exact same steps?

    Have a nice day,
    Cine
    the ZeXtras Team

  3. #3
    Active Member
    Join Date
    Aug 2015
    Posts
    14
    Hi Cine and the community :-)

    Thanks a lot for your answer.

    The disappering zimlet is fix. done.

    For handshake problem with Android's mobile :
    - Yes, I follow exactly the same step than wrote on the guide about self-signed certificates.
    - I recreate a new one. My Ipad simply ask me is I agree to connect to an seld-signed certificate. I click Yes, and everythink's working, like before.
    - I create a accound logger but the file stay empty.

    tail -f xxxx\@yyyy.com.log
    2015-08-31 15:03:59,457 [ZxLink Handler Thread] info Logging xxxx@yyyy.com

    But there is a masqued export from sync.log. There is :

    1/ I recreate an account on my Android phone :

    2015-08-31 15:15:12,080 INFO [qtp2054798982-201:https://127.0.0.1:8443/Microsoft-Server-ActiveSync] [tid=201;account=xxxx@yyyy.com;oip=127.0.0.1;eas=14 .1;rid=7;] sync - Device asked server configurations, available EAS versions: 2.5,12.0,12.1,14.0,14.1

    2/ On zimbraadmin, the device status is stop on "waiting for authorization" so I click on "resume" :
    2015-08-31 15:15:54,433 INFO [qtp2054798982-204:https://xxx.xxx.xxx.xxx:7071/service.../soap/zextras] [name=xxxx@yyyy.com;mid=8;ip=xxx.xxx.xxx.xxx;ua=Zim braWebClient - FF40 (Linux);tid=204;] sync - Resuming synchronization for device: androidc17x4yyyy19

    Nothing more...

    An other idea ?

    Thanks ...


    Quote Originally Posted by Cine View Post
    Hello shreg,
    welcome to the forums!

    The "disappering zimlet" and SSLv3 handshake error issues are very unlikely to be related.
    To fix the former, clearing both your browser's cache and the zimlet's one should do the trick: you can do so by running the following command as the 'zimbra' user
    Code:
    zmprov fc zimlet com_zextras_zextras
    About the SSLv3 handshake error, could you please add an Account Logger to the affected mailbox, reproduce the issue and send the full error's stacktrace to community@zextras.com? A complete guide about self-signed certificates is available on the Zimbra Wiki, did you follow the exact same steps?

    Have a nice day,
    Cine
    the ZeXtras Team

  4. #4
    ZeXtras Community Manager ZeXtras Employee Cine's Avatar
    Join Date
    Apr 2011
    Posts
    2,360
    Hello Shreg!

    Could you please remove the current Account Logger, add a new one with "debug" verbosity and reproduce the issue again?

    Have a nice day,
    Cine
    the ZeXtras Team

  5. #5
    Active Member
    Join Date
    Aug 2015
    Posts
    14
    Hi,

    I create a new one :

    #xxx : zxsuite mobile doAddAccountLogger xxxx@yyyy.com debug /opt/zimbra/log/xxxxx.log

    id 7
    level Debug (debug)
    log file /opt/zimbra/log/xxxxx.log
    remove command zxsuite mobile doRemoveLogger 7


    It's verbose :-)

    1/ There is logs when I configure an account on my android phone :



    2015-09-01 14:36:51,919 [qtp2054798982-9126:https://127.0.0.1:8443/Microsoft-Server-ActiveSync] info Device asked server configurations, available EAS versions: 2.5,12.0,12.1,14.0,14.1
    2015-09-01 14:36:52,315 [ZxMobile] debug Raw mobile request:
    AwFqAAAHVlIDMAABAQ==

    2015-09-01 14:36:52,316 [ZxMobile] debug Mobile request:
    <n1:FolderSync xmlns:n1="FolderHierarchy">
    <n1:SyncKey>0</n1:SyncKey>
    </n1:FolderSync>
    2015-09-01 14:36:52,319 [ZxMobile] debug Encoder: LoggerEncoder {
    FolderSyncEncoder
    }
    2015-09-01 14:36:52,320 [ZxMobile] debug Actions:
    StartEndWrapperAction { ActionContainer {
    CollectionsSyncedEvent
    } }
    2015-09-01 14:36:52,320 [ZxMobile] debug Event: StartEvent
    2015-09-01 14:36:52,320 [ZxMobile] debug Event: CollectionsSyncedEvent
    2015-09-01 14:36:52,320 [ZxMobile] debug Event: EndEvent
    2015-09-01 14:36:52,320 [ZxMobile] debug Raw mobile response:
    AwFqAAAHVkwDMTQ0AAEB

    2015-09-01 14:36:52,320 [ZxMobile] debug Tags are valid
    2015-09-01 14:36:52,321 [ZxMobile] debug Mobile response:
    <n1:FolderSync xmlns:n1="FolderHierarchy">
    <n1:Status>144</n1:Status>
    </n1:FolderSync>
    2015-09-01 14:36:57,964 [ZxMobile] debug XML Validation valid
    2015-09-01 14:36:58,410 [ZxMobile] debug Raw mobile request:
    AwFqAAAORQASVkhXA0Rlc2lyZSBIRAABWgNBbmRyb2lkIDQuMw ABYANBbmRyb2lkLzQuMy1FQVMtMS4z
    AAEBAQAORkdIA01TLUVBUy1Qcm92aXNpb25pbmctV0JYTUwAAQ EBAQ==

    2015-09-01 14:36:58,410 [ZxMobile] debug Mobile request:
    <n1:Provision xmlns:n1="Provision">
    <n2: DeviceInformation xmlns:n2="Settings">
    <n2:Set>
    <n2:Model>Desire HD</n2:Model>
    <n2:OS>Android 4.3</n2:OS>
    <n2:UserAgent>Android/4.3-EAS-1.3</n2:UserAgent>
    </n2:Set>
    </n2: DeviceInformation>
    <n1:Policies>
    <n1:Policy>
    <n1:PolicyType>MS-EAS-Provisioning-WBXML</n1:PolicyType>
    </n1:Policy>
    </n1:Policies>
    </n1:Provision>
    2015-09-01 14:36:58,414 [ZxMobile] debug Encoder: LoggerEncoder {
    ProvisionEncoder
    }
    2015-09-01 14:36:58,415 [ZxMobile] debug Actions:
    StartEndWrapperAction { PoliciesSyncAction }
    2015-09-01 14:36:58,415 [ZxMobile] debug Event: StartEvent
    2015-09-01 14:36:58,416 [ZxMobile] debug Event: SendPoliciesEvent
    2015-09-01 14:36:58,416 [ZxMobile] debug Event: EndEvent
    2015-09-01 14:36:58,416 [ZxMobile] debug Raw mobile response:
    AwFqAAAORUsDMQABRkdIA01TLUVBUy1Qcm92aXNpb25pbmctV0 JYTUwAAUsDMQABSQMxNDQxMTExMDE4
    AAFKTU4DMQABTwMwAAFQAzAAAVQDNAABVQM5MDAAAVYDNAABWA MwAAFZAzAAAVoDOAABWwMxAAFcAzEA
    AV0DMAABXgMxAAFfAzEAAWEDMQABYgMxAAFjAzEAAWQDMgABZQ MxAAFmAzAAAWcDMQABaAM0AAFpAzEA
    AWoDNQABawMtMQABbAMtMQABbQMwAAFuAzAAAW8DMAABcAMwAA FxAzEAAXIDMQABcwMxAAF0AzEAAXUD
    MQABdgMxAAEBAQEBAQ==

    2015-09-01 14:36:58,417 [ZxMobile] debug Tags are valid
    2015-09-01 14:36:58,417 [ZxMobile] debug Mobile response:
    <n1:Provision xmlns:n1="Provision">
    <n1:Status>1</n1:Status>
    <n1:Policies>
    <n1:Policy>
    <n1:PolicyType>MS-EAS-Provisioning-WBXML</n1:PolicyType>
    <n1:Status>1</n1:Status>
    <n1:PolicyKey>1441111018</n1:PolicyKey>
    <n1: Data>
    <n1:EASProvisionDoc>
    <n1: DevicePasswordEnabled>1</n1: DevicePasswordEnabled>
    <n1:AlphanumericDevicePasswordRequired>0</n1:AlphanumericDevicePasswordRequired>
    <n1:RequireStorageCardEncryption>0</n1:RequireStorageCardEncryption>
    <n1:MinDevicePasswordLength>4</n1:MinDevicePasswordLength>
    <n1:MaxInactivityTimeDeviceLock>900</n1:MaxInactivityTimeDeviceLock>
    <n1:MaxDevicePasswordFailedAttempts>4</n1:MaxDevicePasswordFailedAttempts>
    <n1:AllowSimpleDevicePassword>0</n1:AllowSimpleDevicePassword>
    <n1: DevicePasswordExpiration>0</n1: DevicePasswordExpiration>
    <n1: DevicePasswordHistory>8</n1: DevicePasswordHistory>
    <n1:AllowStorageCard>1</n1:AllowStorageCard>
    <n1:AllowCamera>1</n1:AllowCamera>
    <n1:RequireDeviceEncryption>0</n1:RequireDeviceEncryption>
    <n1:AllowUnsignedApplications>1</n1:AllowUnsignedApplications>
    <n1:AllowUnsignedInstallationPackages>1</n1:AllowUnsignedInstallationPackages>
    <n1:AllowWiFi>1</n1:AllowWiFi>
    <n1:AllowTextMessaging>1</n1:AllowTextMessaging>
    <n1:AllowPOPIMAPEmail>1</n1:AllowPOPIMAPEmail>
    <n1:AllowBluetooth>2</n1:AllowBluetooth>
    <n1:AllowIrDA>1</n1:AllowIrDA>
    <n1:RequireManualSyncWhenRoaming>0</n1:RequireManualSyncWhenRoaming>
    <n1:AllowDesktopSync>1</n1:AllowDesktopSync>
    <n1:MaxCalendarAgeFilter>4</n1:MaxCalendarAgeFilter>
    <n1:AllowHTMLEmail>1</n1:AllowHTMLEmail>
    <n1:MaxEmailAgeFilter>5</n1:MaxEmailAgeFilter>
    <n1:MaxEmailBodyTruncationSize>-1</n1:MaxEmailBodyTruncationSize>
    <n1:MaxEmailHTMLBodyTruncationSize>-1</n1:MaxEmailHTMLBodyTruncationSize>
    <n1:RequireSignedSMIMEMessages>0</n1:RequireSignedSMIMEMessages>
    <n1:RequireEncryptedSMIMEMessages>0</n1:RequireEncryptedSMIMEMessages>
    <n1:RequireSignedSMIMEAlgorithm>0</n1:RequireSignedSMIMEAlgorithm>
    <n1:RequireEncryptionSMIMEAlgorithm>0</n1:RequireEncryptionSMIMEAlgorithm>
    <n1:AllowSMIMEEncryptionAlgorithmNegotiation>1</n1:AllowSMIMEEncryptionAlgorithmNegotiation>
    <n1:AllowSMIMESoftCerts>1</n1:AllowSMIMESoftCerts>
    <n1:AllowBrowser>1</n1:AllowBrowser>
    <n1:AllowConsumerEmail>1</n1:AllowConsumerEmail>
    <n1:AllowRemoteDesktop>1</n1:AllowRemoteDesktop>
    <n1:AllowInternetSharing>1</n1:AllowInternetSharing>
    </n1:EASProvisionDoc>
    </n1: Data>
    </n1:Policy>
    </n1:Policies>
    </n1:Provision>
    2015-09-01 14:36:59,369 [ZxMobile] debug XML Validation valid

    >> NOTHING MORE (no sync, jus the status "waiting for authorizing" on zimbraAdmin)



    2/ Logs when I Click on "resume sync" on zimbraAdmin :

    empty.

    3/ Delete old certificate manually imported into CA root library
    4/ reboot phone
    5/ Recreate the account
    6/ Email application always write "waiting for sync" and no logs ... and no sync.

    An other clue, DAVdroid is working for contact and schedule ... So curious!

  6. #6
    Active Member
    Join Date
    Aug 2015
    Posts
    14
    I correct myself, DAVdroid doesn't work since I deteled the CA root autosigned certificate.
    If can use CAdroid cause there is no CA flag = TRUE so I have to import it manually.
    But when it's done, DAVdroid is syncing very well.

    It don't know if thoses explanation may help but I just share ...

  7. #7
    ZeXtras Community Manager ZeXtras Employee Cine's Avatar
    Join Date
    Apr 2011
    Posts
    2,360
    Hello Shreg!

    My first guess would be an issue in the device's MDM policy management: is Mobile Device Management enabled on your server and for the specific account? If so, could you please disable it and create the EAS account on your device from scratch?

    Also, could you please run the official EAS Connectivity Test found at https://testconnectivity.microsoft.com/ and send the results to community@zextras.com?

    Have a nice day,
    Cine
    the ZeXtras Team

  8. #8
    Active Member
    Join Date
    Aug 2015
    Posts
    14
    Hi,

    My result ...

    1/ Create a TEST account on Zimbra with no MDM, and recreate a EAS account on the mobile fot this account :
    > exactly the same.

    2/ Result of the Microsoft Test with the "Ignorer l’approbation pour SSL (=uncheck SSL)" :

    L’analyseur de connectivité de Microsoft teste Exchange ActiveSync... Merci de patienter.
    Échec du test Exchange ActiveSync (=FAILED)

    Détails supplémentaires

    Temps écoulé : 1921 ms.

    Étapes de test

    Tentative de résolution du nom d'hôte xxxxx.com dans DNS.
    Le nom d'hôte a été résolu correctement.

    Détails supplémentaires
    Test du port TCP 443 sur l'hôte xxxxx.com pour s'assurer qu'il écoute/est ouvert.
    Le port a été ouvert correctement.

    Détails supplémentaires
    Test du certificat SSL pour confirmer sa validité.
    Le certificat a transmis toutes les exigences de validation.

    Détails supplémentaires

    Étapes de test
    Vérification de la configuration IIS pour l'authentification du certificat client.
    L'authentification du certificat client n'a pas été détectée.

    Détails supplémentaires
    Test des méthodes d'authentification HTTP pour l'URL https://xxxxx.com/Microsoft-Server-ActiveSync/.
    Le test d'authentification HTTP a échoué (=authentification test failed).

    Détails supplémentaires

    Une réponse HTTP 500 a été renvoyée de Unknown.
    En-têtes de réponse HTTP :
    Transfer-Encoding: chunked
    Connection: keep-alive
    Date: Tue, 01 Sep 2015 14:18:25 GMT
    Server: nginx
    Temps écoulé : 538 ms.

    >> GREAT CLUE ! My problem is link to and error 500 on NGINX ? Waou ... What do you think about that ?

    Thanks ... I try to found more doc on my side ...

  9. #9
    ZeXtras Community Manager ZeXtras Employee Cine's Avatar
    Join Date
    Apr 2011
    Posts
    2,360
    Hello Shreg!

    Could you please send the Account Logger logfile for the non-MDM account to community@zextras.com?

    Also, a couple of additional pointers:
    * You can find a good SSL checker at https://www.ssllabs.com/ssltest/analyze.html
    * SSLv3 has been proven insecure after the "Poodle" vulnerability (CVE-2014-3566), we strongly suggest to disable it so that clients will fall back to more secure protocols
    * Self-signed certificates are gradually becoming more and more troublesome for many clients, please consider a commercial one (those are quite cheap right now and there are even companies providing a free cert for personal use)

    Have a nice day,
    Cine
    the ZeXtras Team

  10. #10
    Active Member
    Join Date
    Aug 2015
    Posts
    14
    Hi Cine,

    1/ Thanks for the 3 links about SSLv3. My Zimbra is 8.6 and SSLv3 is disable. I unfortunatly know that the futur of self-signed certificate isn't sure but It was working on all device before generate a new certificat (for remember, my idea was to found how put the FLAG = TRUE on the certificat to be fetch by CAdroid and make DAVdroid's working). So It should work again.

    There is the answer for the SSL Labs :

    This server's certificate is not trusted, see below for details
    This server supports weak Diffie-Hellman (DH) key exchange parameters. Grade capped to B
    Certificate uses a weak signature. When renewing, ensure you upgrade to SHA2.
    This server accepts the RC4 cipher, which is weak. Grade capped to B.
    This server's certificate chain is incomplete. Grade capped to B >

    2/ About the Account Logger :

    $ zxsuite mobile doAddAccountLogger test1312@xxxx.com debug /opt/zimbra/log/test1312.log

    id 8
    level Debug (debug)
    log file /opt/zimbra/log/test1312.log
    remove command zxsuite mobile doRemoveLogger 8


    $ tail -f /opt/zimbra/log/test1312.log
    2015-09-01 17:14:47,74 [ZxLink Handler Thread] info Logging test1312@xxxx.com

    >> I lauch a Microsoft Test (testconnectivity.microsoft.com) on the test account :
    * logs still empty...
    * same error 500 on nginx on the microsoft side.

    I'm feeling so lost ...
    What can I do to make the mobile sync working again ?

Page 1 of 3 123 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •