locked
Azure Batch Apps - ImageMagick Sample - (403) Forbidden Error RRS feed

  • Question

  • Hi there,

    I am trying to run the sample from code.msdn.microsoft.com/Azure-Batch-Apps-Samples-dd781172

    As mentioned in the instructions, I have configured the App.Config file in the ImageMagick.Console.Client project with the required details.

    I have also uploaded the Cloud Assembly and the Application Image.

    When I run the program, it tries to get computation resources 4 times and then fails. 

    Here is the log output: 

    12:59:17 pm 07 January 2015 | (Job)

    Failed to submit job, abandoning. Reported error was: Job 4b805f35-02e0-4b95-bb3b-799b86be49d4 exceeded retry attempts, failing.

    12:59:08 pm 07 January 2015 | (Job)

    Failed to submit job, will retry. Reported error was: The remote server returned an error: (403) Forbidden.

    12:58:58 pm 07 January 2015 | (Job)

    Failed to submit job, will retry. Reported error was: The remote server returned an error: (403) Forbidden.

    12:58:48 pm 07 January 2015 | (Job)

    Failed to submit job, will retry. Reported error was: The remote server returned an error: (403) Forbidden.

    12:58:37 pm 07 January 2015 | (Job)

    Failed to submit job, will retry. Reported error was: The remote server returned an error: (403) Forbidden.

    12:58:35 pm 07 January 2015 | (Job)

    Job queued for processing

    12:58:33 pm 07 January 2015 | (Job)

    Job request received

    I am not sure how to go about fixing this. Any help would be greatly appreciated :)




    Wednesday, January 7, 2015 12:20 AM

Answers

  • Hi Pranshu,

    Azure Batch Apps depends on Azure Batch for job scheduling.  Is it possible that you regenerated the Batch keys or even deleted the Batch account via the Azure Portal?  If so, Batch Apps will have stale references to your Batch account, hence the '403/Forbidden'. 

    We will be adding functionality to the Batch Apps Portal in the near future to re-synchronise account keys, but in the meantime you will need to re-create the Batch Apps service via the Batch Apps Portal. 

    Login, navigate to the existing service and delete it.  Recreate the service, upload you application image and you should be good to go.

    If you're still having issue's let us know.

    Thanks,

    Christian

    Friday, January 9, 2015 1:36 AM