ERROR_DDM_NOT_RUNNING
Code: 0x387 (903)
As HRESULT:- S: 0 (Success)
- C: 0 (Microsoft-defined)
- N: 0 (Not an NTSTATUS value)
- Facility: 0x000 (FACILITY_NULL: Default)
- Code: 0x0387 (903)
- Sev: 0 (STATUS_SEVERITY_SUCCESS)
- C: 0 (Microsoft-defined)
- Facility: 0x000 (Default)
- Code: 0x0387 (903)
Documented in Win32
Routing and Remote Access Error Codes: 903
The Demand-dial Interface Manager (DDM) is not running.
Associated Modules
| Module | Code | Found in | Description |
|---|---|---|---|
| ESENT.dll | 0x387 | 8.11011 | %1 (%2) %3The database engine detected two different cursors of the same session illegally trying to update the same record at the same time. SessionId: %4 ThreadId: %5 Database: %6 Table: %7 Current cursor: %8 Cursor owning original update: %9 Bookmark size (prefix/suffix): %10 Session-trace: %11 |
| EventCreate.exe | 0x387 | 78.11011 | %1 |
| azsqlext.dll | 0x387 | 78.11011 | Modification Made Database Name: %1 SQL Role: %2 Object ID: %3 Object Type: %4 Logon ID: %5 Member Name: %6 Modification Type -- add role(1), delete role(2), add member(3), remove Member(4): %7 |
| microsoft-windows-system-events.dll | 0x387 | 1011 | The backing-file for the real-time session "%1" has reached its maximum size. As a result, new events will not be logged to this session until space becomes available. This error is often caused by starting a trace session in real-time mode without having any real-time consumers. |
| mprmsg.dll | 0x387 | 78.11011 | The Demand-dial Interface Manager is not running. |
| webservices.dll | 0x387 | 8.11011 | The MTOM writer has generated the MIME parts so no more of the XML document may be written. |
| webservices.dll | 0x387 | 7 | The MTOM writer must close all open elements before requesting this property. |
| 7 entries | |||