locked
Azure - Message: An error occurred while sending the request. RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I've installed the Azure MP and it seemed to be successful but when the discoveries run they fail with "Message: An error occurred while sending the request."

    I can't see any other error or anything to help diagnose what the issue is.

    I do use a proxy so that did complicate things during the setup but I managed to get the wizard to complete and I could select the resources and metrics etc. so I know it was able to make the connection at that point.

    Does anyone have a suggestion?

    Thursday, May 16, 2019 11:42 AM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    I did but only by changing which proxy I used. We have Forcepoint in production and I ended up swapping to our dev proxy, which is Forefront TMG. I can only assume that we have something in Forcepoint that is blocking it or responding differently.
    • Marked as answer by Nick_STW Tuesday, May 26, 2020 9:04 AM
    Friday, July 19, 2019 3:08 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    It's the same suggestion from last year and, funnily enough, is still not applicable. I had to change the proxy that I was using to resolve.
    Tuesday, May 26, 2020 9:08 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    have you waited enough?

    It is also very important to have the newest version of the managemnt pack, because there were some issues with discoveries in the past versions. Which version are you running? 

    As always I would strat by examining the "Operations Manager" even log on your management server. Look for related events and check their details. Anything interesting?

    Here a known issue, mentioned in the MP guide (a must read):

    Issue: “Full scan” in Azure Wizard has been selected and no objects are discovered, warning with id 33333 and error with id 10801 appear in Event Log.

    Resolution: Some hidden services such as networkinterfaces/ipConfigurations, networkSecurityGroups/defaultSecurityRules, networkSecurityGroups/securityRules, virtualNetworks/subnets that obtained with Full Scan might cause discovery failures. Uncheck additional services and their parents in Service types tab, uncheck  “Full scan” checkbox in Subscription tab and press [Refresh Data].

    Hope I could help. Regards,

    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer" where applicable. This helps the community, keeps the forums tidy, and recognizes useful contributions. Thanks!) Blog: https://blog.pohn.ch/ Twitter: @StoyanChalakov

    Thursday, May 16, 2019 12:26 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    hi,

    I've left these discoveries run for a few days now so I've definitely waited long enough :)

    The alert comes from a rule that looks for a 11422 event in the Operations Manager event log and that is the only sign of a failure that I can find.

    I haven't enabled full scan so I don't think my issue is related to that known issue.

    Thanks

    Thursday, May 16, 2019 1:49 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    thanks for the prompt replies. Can you please find the event in the event logs and paste its complete description here. Please make sure that your environment related data is hidden :)

    Thanks and Regards,

    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer" where applicable. This helps the community, keeps the forums tidy, and recognizes useful contributions. Thanks!) Blog: https://blog.pohn.ch/ Twitter: @StoyanChalakov

    Thursday, May 16, 2019 2:07 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    - System

      - Provider

       [ Name]  MS Azure MP Module
     
      - EventID 11422

       [ Qualifiers]  0
     
       Level 3
     
       Task 0
     
       Keywords 0x80000000000000
     
      - TimeCreated

       [ SystemTime]  2019-05-17T09:08:18.000000000Z
     
       EventRecordID 10124317
     
       Channel Operations Manager
     
       Computer
     
       Security
     

    - EventData

       Message: An error occurred while sending the request.
      
       Microsoft.SystemCenter.Azure.Modules.Discovery.ResourceDiscoveryDS
       7.0.5070.0
    Friday, May 17, 2019 12:15 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    just found this in the MP Guide:

    Issue: “An error occurred while sending the request” warning with event id 11422 from MS Azure MP Module

    Resolution:  Issue periodically might occur when monitor large number of instances because of too many requests have been made to Azure API.   Resolution – increase interval of workflows for monitored objects or exclude some services from monitoring in Azure Wizard.

    Have you seen this? Please try the suggestion and post a short feedback, I am really curious if this will help.

    Regards,

    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer" where applicable. This helps the community, keeps the forums tidy, and recognizes useful contributions. Thanks!) Blog: https://blog.pohn.ch/ Twitter: @StoyanChalakov

    Friday, May 17, 2019 12:32 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I did see that. Our Azure subscription only has a very small number of instances (12) and this isn't a periodic issue.
    Friday, May 17, 2019 1:35 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Possible cause could be if servers defined in the Resource Pool you chose to communicate with Azure doesn't have access to use the proxy.

    I got same errors during setup, but got discovered objects after some time anyway.

    Are you missing discovered objects?

    Do you see your subscription under Monitoring - Microsoft Azure - ... - Subscription state?

    Pål

    Friday, May 24, 2019 11:31 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I can manually connect to the internet using the proxy and user settings on the management server that I've got in the resource pool so it's very odd.

    I can see the subscription but it's "Not monitored" and I have no discovered objects.

    I've opened a case with Microsoft now and will be looking to use Fiddler to get to the bottom of it.

    Tuesday, May 28, 2019 9:13 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hey Nick, did you manage to resolve this issue? i'm experiencing exactly the same thing and struggling to find answers anywhere.
    Thursday, July 18, 2019 8:51 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I did but only by changing which proxy I used. We have Forcepoint in production and I ended up swapping to our dev proxy, which is Forefront TMG. I can only assume that we have something in Forcepoint that is blocking it or responding differently.
    • Marked as answer by Nick_STW Tuesday, May 26, 2020 9:04 AM
    Friday, July 19, 2019 3:08 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    This issue is documented in the Azure management pack guide.

    Issue:
    “An error occurred while sending the request” warning with event id 11422 from Azure MP Module

    Resolution:Issue periodically might occur when monitor large number of instances because of too many requests have been made to Azure API. To solve this, you may increase interval of workflows for monitored objects (override the frequency) or exclude some service types from the template in authoring wizard.

    Best regards,
    Leon

    Blog: https://thesystemcenterblog.com LinkedIn:

    Monday, May 18, 2020 10:12 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Nick,

    were you able to check on Leon's suggestion?

    Thanks in advance for a short feedback!

    Regards,

    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer" where applicable. This helps the community, keeps the forums tidy, and recognizes useful contributions. Thanks!) Blog: https://blog.pohn.ch/ Twitter: @StoyanChalakov

    Tuesday, May 26, 2020 6:32 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    It's the same suggestion from last year and, funnily enough, is still not applicable. I had to change the proxy that I was using to resolve.
    Tuesday, May 26, 2020 9:08 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    It's the same suggestion from last year and, funnily enough, is still not applicable. I had to change the proxy that I was using to resolve.

    Hey,

    thanks for sharing the answer :)

    Regards,

    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer" where applicable. This helps the community, keeps the forums tidy, and recognizes useful contributions. Thanks!) Blog: https://blog.pohn.ch/ Twitter: @StoyanChalakov

    Tuesday, May 26, 2020 9:10 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    The known issue is not the same suggestion as mentioned previously, but a different resolution, but it is also mentioned in the management pack guide.

    Blog: https://thesystemcenterblog.com LinkedIn:

    Tuesday, May 26, 2020 9:12 AM