DCOM was unable to communicate

FormerMember

Our web console is up and reporting data, however the site will randomly generate an error on top right corner of the screen: 

{
"data": "",
"status": 500,
"config": {
"method": "GET",
"transformRequest": [
null
],
"transformResponse": [
null
],
"jsonpCallbackParam": "callback",
"params": {
"lang": "en-us",
"viewId": 2,
"swAlertOnError": true,
"swLogOutOnAuthError": false,
"swLogOnError": [
401,
403,
500,
501,
502,
503,
504,
505,
506,
507,
508,
509,
510
],
"swToastOnError": [
401,
403,
500,
501,
502,
503,
504,
505,
506,
507,
508,
509,
510
]
},
"headers": {
"Accept": "application/json, text/plain, */*",
"X-XSRF-TOKEN": "[redacted]"
},
"cache": false,
"url": "[redacted]
},
"statusText": "",
"xhrStatus": "complete"
}

All services are running; however, when I open up our local server in Server Manager we get a continuous alert stating something like:

Is this related? Any tips for how to resolve? We only have the one poller and use 2020.2. I've tried repairing NPM and rebuilding the site in IIS using the Configuration Manager but the database fails each time that's run. Because we can't get support from SW for these product versions, I'm hoping some of you can help. 

taylor.crowley

I see you have blanked out a part of the DCOM message and I assume this is an IP address. DCOM errors are generally produced as a result of failed WMI polls to the device specified in the message i.e the IP Address.

If you go to this device within SolarWinds and edit the node, are the WMI credentials testing successfully? If so, also check the Application monitors assigned to the node as sometimes they can be configured to use their own credentials rather than inheriting from the node that they are assigned to.

Please let me know