locked
Reader Module no longer working RRS feed

  • Question

  • Hello.  I have a set of experiments with reader modules loading Blob content (.csv files).  These were working fine until tonight.  I am now getting an error stating:  Error 0052: The Azure storage account key is incorrect.

    This is still the case when I copy and paste the proper primary key directly from my storage account.

    [ModuleOutput] DllModuleHost Error: 1 : Program::Main encountered fatal exception: Microsoft.Analytics.Exceptions.ErrorMapping+ModuleException: Error 0052: The Azure storage account key is incorrect.

    Here is an example experiment which creates this problem:

    https://studio.azureml.net/Home/ViewWorkspace/ffac4490b5e448fa8778ceadc74a0b97#Workspaces/Experiments/Experiment/ffac4490b5e448fa8778ceadc74a0b97.f-id.bc74f748eb7d4e94b3d4f4333cc03253/ViewExperiment

    Thanks for your help

    Sunday, February 1, 2015 12:21 AM

Answers

  • can you please try it now? This is should be fixed now
    • Proposed as answer by neerajkh_MSFT Wednesday, February 4, 2015 6:41 AM
    • Marked as answer by Ga_G2 Wednesday, February 4, 2015 11:01 AM
    Wednesday, February 4, 2015 6:08 AM

All replies

  • Thanks, looks like this problem isn't isolated to just what you're seeing, we are investigating and will follow up as we resolve the situation.

    Sorry for the inconvenience!

    AK

    Sunday, February 1, 2015 1:38 AM
  • I also have some experiments failing for no apparent reason (no module is highlighted as failed).  For instance:

    https://studio.azureml.net/Home/ViewWorkspace/ffac4490b5e448fa8778ceadc74a0b97?&hashSeg=#Workspaces/Experiments/Experiment/ffac4490b5e448fa8778ceadc74a0b97.f-id.2b2b522e99734173b1cfa815464ab48e/ViewExperiment

    Thanks

    Sunday, February 1, 2015 11:08 AM
  • Thanks, looks like this problem isn't isolated to just what you're seeing, we are investigating and will follow up as we resolve the situation.

    Sorry for the inconvenience!

    AK

    Hi AK:

    Any news on this?  My experiments are still failing.

    Thanks

    Monday, February 2, 2015 12:27 PM
  • Could you try the following workaround?

    - Create a new empty experiment
    - Copy/Paste the Reader and Writer modules from the failing experiments to the new empty experiment. Save.
    - Copy/Paste all the other modules to the new experiment. This can be done one module at a time, or in bulk. The modules can be just recreated from the pallet as well.
    - Run the new experiment. The Reader and Writers in this case, should be getting properly formatted credentials.

    Thanks,

    Tong

    Monday, February 2, 2015 6:26 PM
  • Hi.  That doesn't work.  In fact I got rid of all the writer modules and replaced the reader modules with Saved Datasets.  So as mentioned in my prior message there is something else going on that is failing the experiments.  Here is an example.  Note that there is no detail when the experiment fails.  No particular module is highlighted.

    https://studio.azureml.net/Home/ViewWorkspace/ffac4490b5e448fa8778ceadc74a0b97?&hashSeg=#Workspaces/Experiments/Experiment/ffac4490b5e448fa8778ceadc74a0b97.f-id.05dc2d6b2be24114b0afed2403181bbc/ViewExperiment

    Monday, February 2, 2015 9:33 PM
  • Also in this experiment I can't copy and paste because otherwise it will force me to rerun the individual models (of which there are 24) due to the change you made in October 2014.  In fact I can't change anything at all to the experiment.  Any idea as to what can be done from the back-end?

    https://studio.azureml.net/Home/ViewWorkspace/ffac4490b5e448fa8778ceadc74a0b97?&hashSeg=#Workspaces/Experiments/Experiment/ffac4490b5e448fa8778ceadc74a0b97.f-id.8fe641353097430499b0142adcf1c430/ViewExperiment

    Thanks


    • Edited by Ga_G2 Monday, February 2, 2015 9:48 PM
    Monday, February 2, 2015 9:47 PM
  • The root cause has just been identified. The hotfix is expected to be in tomorrow. Thank you very much for reporting the issue!

    Best,

    Tong

    Tuesday, February 3, 2015 2:19 AM
  • Ok thanks for your help
    Tuesday, February 3, 2015 8:18 AM
  • Is there an updated ETA on this fix?  It's been almost a day since this post.  We're unable to process any predictions until resolved.  Thanks.  -Jason
    Wednesday, February 4, 2015 12:44 AM
  • can you please try it now? This is should be fixed now
    • Proposed as answer by neerajkh_MSFT Wednesday, February 4, 2015 6:41 AM
    • Marked as answer by Ga_G2 Wednesday, February 4, 2015 11:01 AM
    Wednesday, February 4, 2015 6:08 AM
  • It works now.  Thanks
    Wednesday, February 4, 2015 11:01 AM
  • Hi i have similar problem.

    My account key does not work for OLD experimenet, but ok for new experiement in the SAME work space.

    any clues?

    Sunday, May 6, 2018 6:52 AM