locked
Live Mesh won't start - certificate error? RRS feed

  • Question

  • Live Mesh (v0.9.4014.4) will no longer start on a laptop that it worked on for at least 6 months. The log indicates that it is a certificate mismatch. The only thing I can think of that has been installed lately is the most recent 2nd Tuesday patch in June. Here is a snippet of the log with the error:

    ---

    2009-06-17 12:07:16.852,INFO,AccountsManager,0,1,4,AccountsManager has been created. Its settings: AccountServiceUrl=https://accounts.mesh.com/, BaseUrl=http://localhost:2048/, UseFakeAuthentication=False, AccountServicePollInterval=1800000, AccountsManagerOperationTimeout=300000
    2009-06-17 12:07:16.882,INFO,AccountsManager,0,1,4,Starting current device provisioning...
    2009-06-17 12:07:16.892,INFO,AuthenticationProvider,0,1,4,+SetDeviceConsent:
    2009-06-17 12:07:16.902,INFO,AuthenticationProvider,0,1,4,-SetDeviceConsent: S_OK, t = 11 ms.
    2009-06-17 12:07:16.912,INFO,AuthenticationProvider,0,1,4,+GetDeviceInformation:
    2009-06-17 12:07:16.922,INFO,AuthenticationProvider,0,1,4,+CacheDeviceInformation:
    2009-06-17 12:07:17.273,INFO,AuthenticationProvider,0,1,4, CacheDeviceInformation: Device certificate is valid for 178 more days.
    2009-06-17 12:07:17.283,INFO,AuthenticationProvider,0,1,4,-CacheDeviceInformation: S_OK, t = 364 ms.
    2009-06-17 12:07:17.283,INFO,AuthenticationProvider,0,1,4,-GetDeviceInformation: S_OK, t = 370 ms.
    2009-06-17 12:07:17.283,INFO,AccountsManager,0,1,4,Get device certificate - PUID: 6825766039681400
    2009-06-17 12:07:17.323,WARN,AccountsManager,0,1,4,The current device certificate in MOE accounts cache doesn't match the device certificate obtained from the AuthenticationProvider.
    2009-06-17 12:07:17.323,ERRR,AccountsManager,0,1,4,The cached device name CN=00180000800FB41E is different from the current AuthenticationProvider device name CN=00183FFF801D7978.  This is an unrecoverable error.  Contact customer support for recover options.
    2009-06-17 12:07:17.323,ERRR,AccountsManager,0,1,4,Cannot provision this device on attempt #1
    2009-06-17 12:07:17.323,INFO,AccountsManager,0,1,4,Starting current device provisioning...
    2009-06-17 12:07:17.323,INFO,AuthenticationProvider,0,1,4,+SetDeviceConsent:
    2009-06-17 12:07:17.333,INFO,AuthenticationProvider,0,1,4,-SetDeviceConsent: S_OK, t = 15 ms.
    2009-06-17 12:07:17.343,INFO,AuthenticationProvider,0,1,4,+GetDeviceInformation:
    2009-06-17 12:07:17.343,INFO,AuthenticationProvider,0,1,4,-GetDeviceInformation: S_OK, t = 0 ms.
    2009-06-17 12:07:17.343,INFO,AccountsManager,0,1,4,Get device certificate - PUID: 6825766039681400
    2009-06-17 12:07:17.393,WARN,AccountsManager,0,1,4,The current device certificate in MOE accounts cache doesn't match the device certificate obtained from the AuthenticationProvider.
    2009-06-17 12:07:17.393,ERRR,AccountsManager,0,1,4,The cached device name CN=00180000800FB41E is different from the current AuthenticationProvider device name CN=00183FFF801D7978.  This is an unrecoverable error.  Contact customer support for recover options.
    2009-06-17 12:07:17.393,ERRR,AccountsManager,0,1,4,Cannot provision this device on attempt #2
    2009-06-17 12:07:17.393,INFO,AccountsManager,0,1,4,Starting current device provisioning...
    2009-06-17 12:07:17.393,INFO,AuthenticationProvider,0,1,4,+SetDeviceConsent:
    2009-06-17 12:07:17.403,INFO,AuthenticationProvider,0,1,4,-SetDeviceConsent: S_OK, t = 10 ms.
    2009-06-17 12:07:17.433,INFO,AuthenticationProvider,0,1,4,+GetDeviceInformation:
    2009-06-17 12:07:17.433,INFO,AuthenticationProvider,0,1,4,-GetDeviceInformation: S_OK, t = 0 ms.
    2009-06-17 12:07:17.433,INFO,AccountsManager,0,1,4,Get device certificate - PUID: 6825766039681400
    2009-06-17 12:07:17.443,WARN,AccountsManager,0,1,4,The current device certificate in MOE accounts cache doesn't match the device certificate obtained from the AuthenticationProvider.
    2009-06-17 12:07:17.443,ERRR,AccountsManager,0,1,4,The cached device name CN=00180000800FB41E is different from the current AuthenticationProvider device name CN=00183FFF801D7978.  This is an unrecoverable error.  Contact customer support for recover options.
    2009-06-17 12:07:17.443,ERRR,AccountsManager,0,1,4,Cannot provision this device on attempt #3
    2009-06-17 12:07:17.593,CRIT,Moe,0,1,4,Fatal Exception Throw:
    Microsoft.Live.Moe.Runtime.FailedToStartException: StartupFailedDeviceProvision
       at Microsoft.Live.Moe.Runtime.Services.AccountsManager.Start()
       at Microsoft.Live.Moe.Runtime.MoeRuntime.Start()
       at Microsoft.Live.Moe.Runtime.ApplicationDomainManager.<>c__DisplayClass5.<Start>b__3()
       at Microsoft.Live.Moe.ExceptionFilterLibrary.ExceptionFilter.TryFilterCatch(TryDelegate tryDelegate, FilterDelegate filterDelegate, CatchDelegate catchDelegate, FinallyDelegate finallyDelegate)
    Wednesday, June 17, 2009 12:36 PM

Answers

  • Thanks for your post. Uninstalling/reinstalling will resolve the certificate mismatch issue:

    1.  Remove the machine from your device ring at www.mesh.com
    2.  Uninstall Live Mesh
    3.  Reboot
    4.  Reinstall Live Mesh from www.mesh.com
    Wednesday, June 17, 2009 6:20 PM

All replies

  • While we await advice on how to proceed, can you please file a bug report on Connect and attach your logs per the instructions here:
     

    How to Submit Bugs and Live Mesh Logs

    And post the link to the bug report of the ID here in the thread. Thanks.

    If you wish to try the brute force approach, it may be worth reinstalling the client on this PC.

    -steve


    Microsoft MVP Windows Live / Windows Live OneCare & Live Mesh Forum Moderator
    Wednesday, June 17, 2009 1:31 PM
    Moderator
  • Thanks for your post. Uninstalling/reinstalling will resolve the certificate mismatch issue:

    1.  Remove the machine from your device ring at www.mesh.com
    2.  Uninstall Live Mesh
    3.  Reboot
    4.  Reinstall Live Mesh from www.mesh.com
    Wednesday, June 17, 2009 6:20 PM
  • Mesh is not even installed for the first time in my Windows XP home SP3 and still produces the same error. What I can do?
    Saturday, July 4, 2009 2:51 PM
  • My windows XP is the spanish version

    Saturday, July 4, 2009 5:32 PM
  • If the information that Evan provided above does not apply and you are still getting the certificate error on a new installation, please go ahead and file a bug report.
     

    How to Submit Bugs and Live Mesh Logs

    -steve


    Microsoft MVP Windows Live / Windows Live OneCare, Live Mesh, & MS Security Essentials Forums Moderator
    Sunday, July 5, 2009 5:50 PM
    Moderator