Good afternoon.
I have been unable to get the latest Microsoft Platform protocol (6.0.0.2) polling a Windows 2022 VM hosted in Azure work stable. I have the following error message after the element was stopped and started
"Contacting server failed: Connection to [//xxxx/root/cimv2] failed. The RPC server is unavailable. (hr = 0x800706BA)"
At some point it just started working again, then I restarted the element and now it has not been able to poll data again.
I have followed the possible root causes without success some of the tests that I have already attempted.
1.) Stopping the firewall to be sure it is not being dropped by the firewall.
2.) Making sure the required services are running on the Windows vm.
3.) Making sure the local user has the correct permissions based on the documentation in the online catalog (I have tried all the possible solutions in the online document as well as what I could find on the internment).
4.) On the target VM logged in with the local user and used WBEMTEST to connect to //xxxx/root/cimv2 without errors.
5.)The target host is reachable from our DMS, the Microsoft SNMP protocol works without issues.
6.)Deleted and re-created the element, as well as checking the "Security Settings" tab to ensure User Name and Password is correctly set.
7.)Ensured the user used in step 6 has access to log in remotely.
8.)Stopping and starting the element as well as a test.
9.) Restarting the target VM.
Thank you.
Any ideas would be greatly appreciated!
Good morning! For anyone that might stumble on this question. The problem turned out to be asymmetric routing where the request would route one way and the reply would go another. This explains the weird "unstable" behaviour I encountered.
Hope this is able to help someone at some point!
Hi Johannes,
The Latest version for the 6.0.0.X branch is actually the 6.0.0.5. If you are cloud connected, you can try Deploying it. Alternatively check with your Skyline contact to get it
https://catalog.dataminer.services/details/4abcf220-c001-4ffd-bab8-559dee47088f
I would also like to point out that the 6.0.0.X branch is used for Physical Hardware Environment while the 1.1.3.X is for a Virtual Machine Environment. Since I noticed that you are running it on a VM.
Regarding the Error message specifically, can you try checking your firewall to make sure that there were no changes?
I hope this helps
Thank you for getting back to me. I will deploy 1.1.3.21 as a test to see if it perhaps has any effect. This is a DaaS solution so the DMA is a windows VM that is currently being polled by version 6.0.0.2, this is allot simpler though as there are no firewalls in-between since it’s on the local machine. I will investigate the firewall more, thank you.