Windows / Code / 0x00000455
0x00000455
Decimal: 1109 · Signed: 1109
As HRESULT:- S: 0 (Success)
- C: 0 (Microsoft-defined)
- N: 0 (Not an NTSTATUS value)
- Facility: 0x000 (FACILITY_NULL: Default)
- Code: 0x0455 (1109)
As NTSTATUS:- Sev: 0 (STATUS_SEVERITY_SUCCESS)
- C: 0 (Microsoft-defined)
- Facility: 0x000 (Default)
- Code: 0x0455 (1109)
Associated Modules
| Module | Found in | Description |
|---|
| Autofmt.exe | 78.110 | %1 KB in %2 files. |
| KernelBase.dll | 78.1 | Unable to unload the media. |
| autochk.exe | 78.11011 | %1 KB in %2 files. |
| autoconv.exe | 78.110 | %1 KB in %2 files. |
| dhcpsapi.dll | 78.11011 | Server found that belongs to DS domain |
| gpsvc.dll | 8.11011 | The user account is in a different forest than the computer account. The processing of Group Policy from another forest is not allowed. Group Policy will be processed using Loopback Replace mode. The scope of the user policy settings will be determined by the location of the computer object in Active Directory. The settings will be acquired from the User Configuration of these policies. |
| gpsvc.dll | 7 | The user account is in a different forest than the computer account. The processing of Group Policy from another forest is not allowed. Group Policy will be processed using Loopback Replace mode. The scope of the user policy settings will be determined by the location of the computer object in Active Directory. The settings will be aquired from the User Configuration of these policies. |
| imapi2fs.dll | 78.11011 | %1 KB in %2 files. |
| kernel32.dll | 78.11011 | Unable to unload the media. |
| microsoft-windows-system-events.dll | 1011 | Sizing Workflow: Mirroring Phase 1 ended. |
| reagent.dll | 78.11011 | The boot manager was corrupt. |
| ulib.dll | 78.11011 | %1 KB in %2 files. |
| webservices.dll | 8.11011 | The server returned a secure conversation fault: 'The specified context token could not be renewed'. |
| webservices.dll | 7 | The server returned an addressing fault: 'A message information header is not valid and the message cannot be processed. The validity failure can be either structural or semantic, e.g. a destination that is not a URI or a relationship to a message id that was never issued.'. |
| 14 entries |
Associated Headers
Documented in Win32