UNSOLVED

CulturaIT

updated

3 months ago

C

CulturaIT

1 Rookie

•

3 Posts

•

10 Points

0

214

July 30th, 2026 07:49

Unable to activate Dell AIOps Plugin in Dell OpenManage

Hello

We are unable to activate Dell AIOps Plugin in Dell OpenManage

Generated Access Key and PIN successfully and now getting following errors:

"Could not complete request because of following error(s).
Unable to complete the operation because the value provided for {0} is invalid.
Recommended Action
Enter a valid value and retry the operation."

Dell OpenManage version 4.7.0 (Build 105)
Dell AIOps plugin version 2.7.0.12

Network connectivity works fine to esrs3-core.emc.com

Has anyone had a similar problem?

Thanks!

  • DELL-Josh Cr

    Community Manager

    •

    9792 Posts

    •

    45323 Points

    0

    0

    Posted August 3rd, 2026 13:37

    Hello,

     

    Thank you for reaching out and providing the details of your environment. The error you are encountering, where the message references "{0}" as a placeholder rather than specifying the actual field name, is a known formatting issue in certain versions of Dell OpenManage Enterprise and typically indicates that one of the input values being passed during the activation process is not being accepted by the plugin.

     

    There are several things worth checking and trying to resolve this.

     

    First, verify that the Access Key and PIN you generated have not expired. Depending on the portal used to generate them, these credentials can have a limited validity window. If too much time has passed between generating them and entering them into OpenManage, they may no longer be valid. Try generating a fresh Access Key and PIN and immediately entering them into the AIOps plugin activation screen.

     

    Second, ensure there are no leading or trailing spaces, hidden characters, or line breaks when you copy and paste the Access Key and PIN into the fields. This is a common cause of the "invalid value" error. It is worth manually retyping the values rather than pasting them to rule this out.

     

    Third, check for compatibility between your OpenManage Enterprise version and the AIOps plugin version. You are running OpenManage Enterprise version 4.7.0 Build 105 with AIOps plugin version 2.7.0.12. It would be worth reviewing the Dell OpenManage Enterprise Support Matrix to confirm that this specific combination of OME and plugin versions is fully supported. In some cases, a minor version mismatch can cause unexpected validation errors during activation. The support matrix and release notes can be found on the Dell Support site at https://www.dell.com/support by searching for "OpenManage Enterprise Support Matrix" or checking the documentation section for OpenManage Enterprise.

     

    Fourth, confirm that your OpenManage Enterprise appliance can reach all the required external endpoints, not just esrs3-core.emc.com. The AIOps plugin may need to communicate with additional Dell backend services for activation and validation. Review the AIOps plugin documentation or release notes for the complete list of required URLs and ports, and verify that your firewall or proxy is not blocking any of them.

     

    Fifth, check whether your browser or session could be contributing to the issue. Try clearing the browser cache, using a different browser, or using a private or incognito browsing session when entering the activation credentials.

     

    Sixth, review the OpenManage Enterprise application logs for more detailed error information. The logs may provide additional context about which specific field or value is being flagged as invalid, since the "{0}" in the error message suggests the UI failed to populate the actual field name. You can typically access logs through the OME console or by downloading them from the appliance.

  • CulturaIT

    1 Rookie

    •

    3 Posts

    •

    10 Points

    0

    0

    Posted August 4th, 2026 09:12

    @DELL-Josh Cr​

    Hi Josh

    Thank you for all recommendations.

    1.) I confirm Access Key and PIN have not expired. I have generated fresh pair and unfortunately the same issue.

    2.) I confirm there are no leading or trailing spaces, hidden characters, or line breaks when I copy and paste the Access Key and PIN into the fields. I have also typed manually but still the same error....

    3.) I confirm the compatibility looks okay.
    According to the https://www.dell.com/support/manuals/en-in/openmanage-enterprise-cloudiq/ome_p_aiops_2.7_ug/versions-of-dell-aiops-plugin-compatible-with-openmanage-enterprise?guid=guid-0b1b26a1-efac-4362-b77b-b748ebb24347&lang=en-us Plugin v2.7 supports OpenManage Enterprise 4.7.x so I am running on the supported configuration.


    4.) I confirm that our OpenManage Enterprise appliance can reach all the required external endpoints.

    5.) Unfortunately, the same problem when using different browsers, even with private or incognito browsing.

    6.) I have generated the logs (ConsoleLogs-xxx.zip) - could you please adsive what log files I should check?

    Thanks for your help.

  • CulturaIT

    1 Rookie

    •

    3 Posts

    •

    10 Points

    0

    0

    Posted August 4th, 2026 10:00

    @DELL-Josh Cr​

    Not sure if this is relevant but I found these errors:
    Can you please let me know what other log files should I check?
    supportassistservice.log
    [ERROR] 2026-08-04 10:40:24.368Z [vert.x-worker-thread-8] com.dell.sae.lockbox.service.LockboxServiceImpl- 575 - Lockbox close operation failed::Cannot close the Lockbox because it is not open
    [ERROR] 2026-08-04 10:40:24.368Z [vert.x-worker-thread-8] com.dell.sae.lockbox.service.LockboxServiceImpl- 286 - Error in getItem from lockbox:
    com.dell.sae.lockbox.service.common.exception.LockboxStoreException: {"errorCode":"SAE-150005","errorMessage":"Get item from lockbox is failed.","httpStatus":0,"errorReason":""}
    at com.dell.sae.lockbox.service.common.exception.LockboxStoreExceptionUtility.throwLockboxStoreException(LockboxStoreExceptionUtility.java:16)
    at com.dell.sae.lockbox.service.LockboxServiceImpl.getItemFromLockbox(LockboxServiceImpl.java:565)
    at com.dell.sae.lockbox.service.LockboxServiceImpl.lambda$getItem$6(LockboxServiceImpl.java:283)
    at io.vertx.core.impl.ContextImpl.lambda$executeBlocking$5(ContextImpl.java:205)
    at io.vertx.core.impl.ContextInternal.dispatch(ContextInternal.java:270)
    at io.vertx.core.impl.ContextImpl$1.execute(ContextImpl.java:221)
    at io.vertx.core.impl.WorkerTask.run(WorkerTask.java:56)
    at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
    at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
    at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
    at java.base/java.lang.Thread.run(Thread.java:1583)
    [ERROR] 2026-08-04 10:40:24.369Z [vert.x-eventloop-thread-1] com.dell.sae.launcher.omeplugin.handler.VerticleDeployOMEPluginHandler- 565 - Persisting of required items to lockbox failed(RECIPIENT_FAILURE,-1) {"errorCode":"SAE-150005","errorMessage":"Get item from lockbox is failed.","httpStatus":0,"errorReason":""}
    [ERROR] 2026-08-04 10:40:24.369Z [vert.x-eventloop-thread-1] com.dell.sae.launcher.omeplugin.handler.VerticleDeployOMEPluginHandler- 762 - Persisting of keys failing : {}
    (RECIPIENT_FAILURE,-1) {"errorCode":"SAE-150005","errorMessage":"Get item from lockbox is failed.","httpStatus":0,"errorReason":""}
    [ERROR] 2026-08-04 10:40:24.369Z [vert.x-eventloop-thread-1] com.dell.sae.launcher.omeplugin.handler.VerticleDeployOMEPluginHandler- 347 - Deploying Of Service Discovery Failed
    [ERROR] 2026-08-04 10:40:24.370Z [vert.x-eventloop-thread-1] com.dell.sae.launcher.omeplugin.handler.VerticleDeployOMEPluginHandler- 188 - Deploying of All or one of the Verticles is failed : {}
    (RECIPIENT_FAILURE,-1) {"errorCode":"SAE-150005","errorMessage":"Get item from lockbox is failed.","httpStatus":0,"errorReason":""}
    [ERROR] 2026-08-04 10:40:24.371Z [vert.x-eventloop-thread-1] com.dell.sae.launcher.omeplugin.verticles.LauncherOMEPluginVerticle- 67 - Verticles Deployement Failed
    [ERROR] 2026-08-04 10:40:24.376Z [vert.x-eventloop-thread-0] io.vertx.core.impl.launcher.commands.VertxIsolatedDeployer-  - {"errorCode":"SAE-150005","errorMessage":"Get item from lockbox is failed.","httpStatus":0,"errorReason":""}
  • DELL-Josh Cr

    Community Manager

    •

    9792 Posts

    •

    45323 Points

    0

    0

    Posted August 5th, 2026 11:58


    Thank you for your patience and for thoroughly working through each of the previous recommendations. Since all six steps have been verified and the issue persists, let's dig deeper.

    Log Files to Check
    Within the ConsoleLogs-xxx.zip, look for the following logs that are most relevant to plugin activation issues:

    Plugin-related logs:
    Look for any files referencing AIOps, plugin, or cloudiq in the filename — these would contain plugin-specific activation and communication events.
    Application/Tomcat logs:
    Files such as openmanage_enterprise.log or application.log — these capture general application-level errors and may show the full stack trace behind the {0} error.
    API/Web Service logs:
    Any logs related to API calls or web services may show the exact request/response that is failing during the activation handshake.
    Connector/Gateway logs:
    Logs related to ESRS or connectivity services — while you've confirmed network connectivity, these could reveal whether the activation token exchange is failing at a backend validation step.
    Tip: Search across all log files for keywords like:

    "invalid"
    "activation"
    "AIOps"
    "error"
    "exception"
    "failed"
    "{0}"
    This should help pinpoint the exact field or process that is failing.

    Additional Troubleshooting Steps
    Since all initial recommendations have been exhausted, here are further steps to consider:

    1. Plugin Reinstallation
    Try uninstalling the AIOps plugin (v2.7.0.12) from OpenManage Enterprise and reinstalling it fresh.
    Sometimes the plugin installation can have a corrupted state that causes validation errors during activation.
    2. Check for Available Plugin Updates
    Verify whether there is a newer build of the AIOps plugin 2.7.x available on the Dell support site. A patch or minor update may have addressed this specific activation bug.
    3. Verify the Source Portal for Access Key/PIN
    Confirm you are generating the Access Key and PIN from the correct portal (CloudIQ portal) and that your site/account is properly registered and entitled for AIOps services.
    Ensure your CloudIQ account has the correct permissions and that the site ID associated with your OpenManage Enterprise appliance matches what is expected.
    4. Check DNS Resolution
    Verify that DNS resolution from the OME appliance is working correctly for all required Dell endpoints, not just connectivity. A DNS mismatch could cause the backend validation to fail.
    5. Proxy/SSL Inspection
    If your environment uses a proxy server or SSL inspection/decryption, this can interfere with the activation handshake even though basic connectivity appears to work. Try bypassing SSL inspection for Dell endpoints if applicable.
    6. Check Time Synchronization (NTP)
    Ensure the OME appliance clock is accurately synchronized via NTP. Even a small time drift can cause token/key validation failures.