yostoi evgui

MGL Buka 0 Reputation points
2025-11-21T10:51:22.3933333+00:00

NoSuchKeyThe specified key does not exist.No such object: public-sensor-pages/msft/px/captcha_close

can u please assist?

Azure AI Anomaly Detector
Azure AI Anomaly Detector

An Azure service that identifies anomalies and defects early with time-series detection.

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anshika Varshney 15,625 Reputation points Microsoft External Staff Moderator
    2025-12-09T10:26:54.7166667+00:00

    Hey MGL Buka,

    Thank you for reaching out on the Microsoft Q&A.**
    **It looks like you're encountering a NoSuchKey error related to the public-sensor-pages/msft/px/captcha_close object. This usually indicates that the specific key or object you're trying to access doesn't exist in the specified path.

    To help you resolve this issue, I recommend checking the following:

    1. Verify the Key/Object Path: Double-check that the object path public-sensor-pages/msft/px/captcha_close is correct. There might be a typo or the object may have been moved or deleted.
    2. Permissions: Ensure that the Azure service or account you are using has the necessary permissions to access the object. If you're dealing with Azure Blob Storage, make sure your SAS token or access key is valid and has permissions to read from the storage.
    3. Check for Deletions: Sometimes, objects might get deleted. If this is the case, you may need to restore it if you have a backup or check if it was moved.
    4. Consult Documentation or Support: If you're using Azure Anomaly Detector or related services, you may want to follow detailed steps for running the Anomaly Detection container, as outlined in the Anomaly Detector Containers documentation.

    Relevant Documentation:

    I Hope this helps. Do let me know if you have any further queries.

    If this answers your query, please do click Accept Answer and Yes for was this answer helpful.

    Thank you!

    Was this answer helpful?

    0 comments

  2. AI answer

    2025-11-21T10:52:39.94+00:00

    The error message NoSuchKey indicates that the specified key does not exist in the storage. This typically occurs when trying to access an object that has either been deleted or never existed in the specified location. To resolve this issue, you can take the following steps:

    1. Check the Key: Ensure that the key you are using is correct and matches the expected format.
    2. Verify Object Existence: Confirm whether the object you are trying to access is indeed present in the storage. You may need to list the objects in the bucket to see if it exists.
    3. Permissions: Ensure that you have the necessary permissions to access the object in the storage.
    4. Check for Typos: Look for any typographical errors in the key name or path.

    If the object is critical and you believe it should exist, consider checking the logs or contacting support for further assistance.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.