Search Engine: Elastic

Article ID: 127523, created on Nov 23, 2015, last review on Nov 7, 2016

  • Applies to:
  • Operations Automation 6.0
  • Operations Automation 5.5


Office365 tasks fail with the following errors:

 error id "validation-error", setting id "Configuration":Method edit_customer calling failed. Reason:Keyset does not exist Method: ValidateOrder


error id "validation-error", setting id "Configuration":Method edit_customer calling failed.
Reason:Found multiple X.509 certificates using the following search criteria: StoreName


Insufficient permissions on certificate.


Log into Office365 Endpoint server and check the certificate private keys permissions:

  1. Check what certificate is used for the 'Mosi' site in IIS via Bindings > Edit
  2. Open the Microsoft Management Console (MMC) and add the Certificates snap-in:

    • In the top menu, go to File > Add/Remove Snap-in.
    • Select the Certificates snap-in and click Add.
    • Select the Computer account option and click Next.
    • Select the Local computer option and click Finish.
    • Click OK.
  3. Go to the Personal > Certificates folder, right-click the required SSL certificate and choose the All Tasks > Manage Private Keys.
  4. Check if IIS AppPool\IIS_mosi_pool_name identity is added. If not, then add it in the following way: add > change locations to local computer > add IIS AppPool\IIS_mosi_pool_name > read only

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0 5b048d9bddf8048a00aba7e0bdadef37 2554725ed606193dd9bbce21365bed4e

Email subscription for changes to this article
Save as PDF