Toggle navigation
hresult
Home
/
Facilities
/
FACILITY_WINRM
/
0x803381D6
Error 0x803381D6
Value: -2144108074 | 0x803381D6 | 2150859222
What does it mean ?
ERROR_WINRS_SHELLCOMMAND_CLIENTID_RESOURCE_CONFLICT
The WinRM service cannot process the request. A command already exists with the command ID specified by the client.
Value: 33238 | 0x81D6 | 0b1000000111010110
Where does it come from ?
FACILITY_WINRM
Windows Resource Manager
Value: 51 | 0x033 | 0b00110011
StackOverflow
{{ item.title | htmlDecode}}
Other Errors for FACILITY_WINRM
0x80338150
- ERROR_WSMAN_SENDSHELLINPUT_INVALID_STREAMID_INDEX
0x803380A1
- ERROR_WSMAN_EVENTING_MISSING_NOTIFYTO_ADDRESSS
0x80338132
- ERROR_WINRS_CLIENT_CLOSERECEIVEHANDLE_NULL_PARAM
0x803380B1
- ERROR_WSMAN_CLIENT_CERT_UNNEEDED_USERNAME
0x8033812A
- ERROR_WINRS_CLIENT_CLOSESHELL_NULL_PARAM
0x803381D4
- ERROR_WINRS_SHELLCOMMAND_CLIENTID_NOT_VALID
0x8033809D
- ERROR_WSMAN_SECURITY_UNMAPPED
0x8033807C
- ERROR_WSMAN_NO_UNICAST_ADDRESSES
0x8033818C
- ERROR_WSMAN_CLIENT_RECEIVE_NULL_PARAM
0x803380E2
- ERROR_WSMAN_CLIENT_KERBEROS_AUTHENTICATION_DISABLED
0x8033819F
- ERROR_WSMAN_CLIENT_GETSESSIONOPTION_DWORD_INVALID_PARAM
0x803381DB
- ERROR_WSMAN_CLIENT_INVALID_SHELL_COMMAND_PAIR
0x803380CC
- ERROR_WSMAN_CLIENT_PUSH_HOST_TOO_LONG
0x803381A4
- ERROR_WSMAN_CLIENT_ALLOWFRESHCREDENTIALS_NTLMONLY
0x803380A2
- ERROR_WSMAN_EVENTING_INVALID_NOTIFYTO_ADDRESSS
0x8033802F
- ERROR_WSMAN_INVALID_BATCH_PARAMETER
0x80338122
- ERROR_WSMAN_CANNOT_PROCESS_FILTER
0x80338197
- ERROR_WSMAN_CLIENT_INVALID_LANGUAGE_CODE
0x80338139
- ERROR_WSMAN_URI_NON_DMTF_CLASS
0x8033801F
- ERROR_WSMAN_EVENTING_INVALID_EXPIRATION_TIME