cancel
Showing results for 
Search instead for 
Did you mean: 
Create Post
Level 12

Unable to add Azure Cloud Account for Monitoring VMs - Getting Credentials issue however they'r not

Hi,

Has anyone faced this kind of issues earlier, where you are able to add Azure Cloud Account successfully in one SolarWinds instance whereas when you try to add the same cloud account in production instance it does not work. Giving below error.

When checked logs then it gives credentials error. I found below article but that do not seems to be applicable as we are able to successfully add same cloud account in dev instance. Do we know what ports, network permissions do we need or how do we resolve this issues. Not getting enough help from support.

 

Attached below snapshot. Below are the logs.

 

https://support.solarwinds.com/SuccessCenter/s/article/Test-Connection-Fails-When-You-Are-Adding-a-C...

 

 

2020-10-16 00:58:54,502 [STP SmartThreadPool Thread #0] ERROR SolarWinds.CloudMonitoring.Jobs.AzureTestConnectionJob - Azure credential test failed with error: An error occurred while sending the request.
2020-10-16 00:58:54,502 [STP SmartThreadPool Thread #0] DEBUG SolarWinds.CloudMonitoring.Jobs.OneTimeJobExecutor`2 - Result serialized. Stream length 384
2020-10-16 00:58:54,502 [STP SmartThreadPool Thread #0] DEBUG SolarWinds.JobEngine.WorkerProcess.JobMonitor - Stop tracking job ff6f2488-6556-4b1c-ac15-6726008fe44b
2020-10-16 00:58:54,502 [STP SmartThreadPool Thread #0] DEBUG SolarWinds.JobEngine.WorkerProcess.AgentDispatcher - } ExecuteJob exited
2020-10-16 00:58:55,192 [7] DEBUG SolarWinds.JobEngine.WorkerProcess.WorkerExecutionEngine - { GetJobResult entered
2020-10-16 00:58:55,192 [7] DEBUG SolarWinds.JobEngine.WorkerProcess.WorkerExecutionEngine - } GetJobResult exited
2020-10-16 00:58:55,192 [7] DEBUG SolarWinds.JobEngine.WorkerProcess.WorkerExecutionEngine - { CleanupJobResults entered
2020-10-16 00:58:55,192 [7] DEBUG SolarWinds.JobEngine.WorkerProcess.WorkerExecutionEngine - } CleanupJobResults exited
2020-10-16 00:59:00,881 [5] DEBUG SolarWinds.JobEngine.WorkerProcess.WorkerExecutionEngine - { SubmitJob entered
2020-10-16 00:59:00,881 [5] DEBUG SolarWinds.JobEngine.WorkerProcess.WorkerExecutionEngine - Submitting job 5d68d25c-db3b-4538-a6f8-3bb275aec6d4
2020-10-16 00:59:00,881 [5] DEBUG SolarWinds.JobEngine.WorkerProcess.WorkerExecutionEngine - } SubmitJob exited
2020-10-16 00:59:00,881 [QueueMonitoringManager] DEBUG SolarWinds.JobEngine.WorkerProcess.WorkerExecutionEngine - { OnJobAvailable entered
2020-10-16 00:59:00,881 [QueueMonitoringManager] DEBUG SolarWinds.JobEngine.WorkerProcess.LocalJobFactory - { CreateJob entered
2020-10-16 00:59:00,881 [QueueMonitoringManager] DEBUG SolarWinds.JobEngine.WorkerProcess.RemoteJobFactory - { CreateJob entered
2020-10-16 00:59:00,881 [QueueMonitoringManager] DEBUG SolarWinds.JobEngine.WorkerProcess.RemoteJobFactory - } CreateJob exited
2020-10-16 00:59:00,881 [QueueMonitoringManager] DEBUG SolarWinds.JobEngine.WorkerProcess.LocalJobFactory - } CreateJob exited
2020-10-16 00:59:00,881 [QueueMonitoringManager] DEBUG SolarWinds.JobEngine.WorkerProcess.WorkerExecutionEngine - } OnJobAvailable exited
2020-10-16 00:59:00,881 [STP SmartThreadPool Thread #0] DEBUG SolarWinds.JobEngine.WorkerProcess.JobMonitor - Start tracking job 5d68d25c-db3b-4538-a6f8-3bb275aec6d4
2020-10-16 00:59:00,881 [STP SmartThreadPool Thread #0] DEBUG SolarWinds.JobEngine.WorkerProcess.AgentDispatcher - { ExecuteJob entered
2020-10-16 00:59:00,944 [STP SmartThreadPool Thread #0] ERROR SolarWinds.CloudMonitoring.Jobs.AzureTestConnectionJob - Azure credential test failed with error: An error occurred while sending the request.

 

@aLTeReGo @KMSigma @jason.carrier 

0 Kudos
4 Replies
Product Manager
Product Manager

@nks7892  Can you share the ticket number you have open with support? I'd like to review what they have tried so far and potentially escalate for you if needed.

Thanks!

@jvb

Thanks for prompt response. Below is the case number for your reference.

Case # - 00634980

I am happy to tell that issue has been resolved. It was related to few Azure endpoints URL that were required to be enabled from Orion Platform server. Since this information is nowhere mentioned in Solarwinds documents I had to struggle a lot to find where all solarwinds is hitting from working instance. Finally I got below details from little research and with the help of azure architect.

If anyone else faces this issue and above provided URL does not help then make sure below URLs re whitelisted and allowed from Polling Engines (port https 443) - 

 

1. *azure.com

2. login.microsoftonline.com

3. manage.azure.com

4. office.com

 

Note - 1 and 2 point from above list should potentially resolve all connectivity issues. I could be missing other endpoints which I am not aware, may be Solarwinds official knowledge article might help for everyone.

If you can update more information on Solarwinds article with regards to what is required from network connectivity point of view then it would be much helpful for others who might face issue similar to me.

 

https://support.solarwinds.com/SuccessCenter/s/article/Test-Connection-Fails-When-You-Are-Adding-a-C...

 

Hi,

 

I just noticed that allowing above provided endpoints will let you only add azure cloud accounts but its not letting you collect other metrics. I think this is a mandatory information to be passed on.

Please let us know what all endpoints needs to be whitelisted to properly monitor azure cloud account.

 

@jvb  @aLTeReGo  @jason.carrier 

@nks7892 

I'll look into it and get NPM's documentation updated. Thanks for the heads up.