This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Access is denied with Windows Remote Command Execution

Hello,

I have windows servers in version 2019. Everything was working fine but following the application of KB5014692

I have the error below when I want to connect remotely with the RemoteExecution action (/Base [1.12.4] /Library/Operations/Operating Systems/Windows/Windows Command).

I tried with the latest version (/Base [1.21.7]/Library/Operations/Operating Systems/Windows/Windows Command) and it's the same.

I have no problem connecting to these machines outside of OO whatever the method...

The error is: {exception=System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)) at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo) at System.Management.ManagementScope.InitializeGuts(Object o) at System.Management.ManagementScope.Initialize() at dotNET_Commons.WMI.WMISearch(String strHost, String strNameSpace, String strQuery, String strUser, String strPass, ImpersonationLevel il, AuthenticationLevel al, String locale) at dotNET_Commons.WMI.WMISearch(String strHost, String strNameSpace, String strQuery, String strUser, String strPass) at dotNET_Commons.Identities.addLocalComputerAsDomainIfNeeded(String host) at dotNETWebActions_RemoteExecution.RemoteExecution.DoExecute(ActionRequest req, ISession s, IActionRegistry reg);StdErr=;returnCode=1;ReturnCode=;returnResult=Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED));StdOut=;sessionId=new session;isSessionOn=False;Result=;}

An idea ? Any way to put a trace in oo?

Thanks

Thierry

  • 0  

    Can you please roll back MS patch KB5014692 and run the flow again as a test? I could like to confirm if the issue is caused by the MS patch.

  • Verified Answer

    +1 in reply to   
    Hello, if I uninstall the KB5014692, it's fine. 
    But the problem was solved by installing the KB5014702 on the central which is in windows 2016.
    Thank you for your reply. I forgot I opened this thread :-)