I seem to be having issues making a WMI call via a windows service in Server 2019. I have an application that makes Remote WMI calls and is installed as a service that runs under a service account. Firewall is disabled on both host and destination machine. If I run the application under the same service account via command line I am able to make the remote query without issue, however in my logs that I write for the service I am constantly getting the following error: The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)
FYI.. This app was originally developed years ago and worked fine under Server 2012R2. I am just now revisiting the application and will make a test on Server 2016 as well.
Has anything changed via Server 2016/2019 that would break this type of implementation? The application is built on .net 4, but again the oddity is it works fine with the same user that I have specified for the service running via console, just not via the windows service. In fact the window service spawns the application when it is needed by simply calling it with a hidden command window.
Any ideas would be greatly appreciated!
User contributions licensed under CC BY-SA 3.0