| 500 | Diagnosticeringspolitik-tjeneste |
Diagnostic Policy Service |
| 501 | Tjenesten Diagnosticeringspolitik gør det muligt at registrere problemer i, foretage fejlfinding af og implementere løsninger for Windows-komponenter. Hvis denne tjeneste stoppes, fungerer diagnosticeringen ikke længere. |
The Diagnostic Policy Service enables problem detection, troubleshooting and resolution for Windows components. If this service is stopped, diagnostics will no longer function. |
| 600 | Microsoft Corporation |
Microsoft Corporation |
| 602 | Værten for Windows Diagnosticeringsinfrastruktur-løsningen muliggør interaktive løsninger på systemproblemer, der er registreret af Diagnosticeringspolitik. Den udløses af Diagnosticeringspolitik, når det er nødvendigt i den pågældende brugersession. Hvis Diagnosticeringspolitik ikke kører, køres opgaven ikke |
The Windows Diagnostic Infrastructure Resolution host enables interactive resolutions for system problems detected by the Diagnostic Policy Service. It is triggered when necessary by the Diagnostic Policy Service in the appropriate user session. If the Diagnostic Policy Service is not running, the task will not run |
| 0x1000000A | Hukommelsessporingshændelser |
Memory tracing events |
| 0x10000021 | Tidshændelser |
Timing Events |
| 0x10000022 | Scenarieudløserhændelser |
Scenario trigger events |
| 0x10000023 | Fejlfindingshændelser |
Debug events |
| 0x10000024 | Scenarielivscyklushændelser |
Scenario lifecycle events |
| 0x10000025 | Beskedhændelser for diagnosticeringsmodul |
Diagnostic Module notification events |
| 0x3000000A | Tjenesten Diagnosticeringspolitik startede |
The Diagnostic Policy Service started |
| 0x3000000B | Et diagnosticeringsscenarie blev konfigureret forkert |
A diagnostic scenario was misconfigured |
| 0x3000000C | Et diagnosticeringsmodul registrerede et problem |
A diagnostic module detected a problem |
| 0x3000000D | En scenarieforekomst blev sendt til fejlfinding |
A scenario instance was dispatched for troubleshooting |
| 0x3000000E | Et diagnosticeringsmodul fuldførte fejlfinding uden at angive en løsning |
A diagnostic module completed troubleshooting without setting a resolution |
| 0x3000000F | Et diagnosticeringsmodul fuldførte fejlfinding og angav en øjeblikkelig løsning |
A diagnostic module completed troubleshooting and set an immediate resolution |
| 0x30000010 | Et diagnosticeringsmodul fuldførte fejlfinding og angav en løsning, der er i kø |
A diagnostic module finished troubleshooting and set an queued resolution |
| 0x30000011 | En scenarieforekomst blev sendt til løsning |
A scenario instance was dispatched for resolution |
| 0x30000012 | Et diagnosticeringsmodul satte sig selv i kø til senere aktivering |
A diagnostic module queued itself for later invocation |
| 0x30000013 | Et diagnosticeringsmodul fuldførte en løsning |
A diagnostic module completed resolution |
| 0x30000014 | Tjenesten Diagnosticeringspolitik kunne ikke oprette en forekomst af en vært for diagnosticeringsmodulet |
The Diagnostic Policy Service was not able to instantiate a diagnostic module host |
| 0x30000015 | Denne hændelse forekommer, når et scenarie mislykkes |
This event is raised when a scenario fails |
| 0x30000016 | Et diagnosticeringsmodul blev flyttet til en afbrudt tilstand |
A diagnostic module was moved to a broken state |
| 0x30000017 | Fejlfindingshændelse |
Debug event |
| 0x30000018 | Denne hændelse forekommer ved ServiceMain for tjenesten |
This event is raised at the ServiceMain for the service |
| 0x30000019 | Denne hændelse forekommer, når tjenesten Diagnosticeringspolitik signalerer sin status som KØRENDE til SCM |
This event is raised when the DPS signals its status as RUNNING to the SCM |
| 0x3000001A | Denne hændelse forekommer, når tjenesten modtager en besked om lukning/stop fra SCM |
This event is raised when the service receives a shutdown/stop notification from the SCM |
| 0x3000001B | Denne hændelse forekommer, når tjenesten er stoppet |
This event is raised when the service is successfully stopped |
| 0x3000001C | Denne hændelse forekommer, når tjenesten Diagnosticeringspolitik opdaterer gruppepolitik |
This event is raised when DPS refreshes group policy |
| 0x50000002 | Fejl |
Error |
| 0x50000003 | Advarsel |
Warning |
| 0x50000004 | Oplysninger |
Information |
| 0x50000005 | Detaljeret |
Verbose |
| 0x70000001 | Livscyklus for scenarium |
Scenario Lifecycle |
| 0x70000002 | Fejlfindingsopgave |
Debug task |
| 0x70000003 | Initialisering af Diagnosticeringspolitik |
DPS Initialization |
| 0x70000004 | Beskedopgave |
Notification task |
| 0x90000001 | Microsoft-Windows-Diagnosis-DPS |
Microsoft-Windows-Diagnosis-DPS |
| 0x90000002 | Microsoft-Windows-Diagnosis-DPS/Debug |
Microsoft-Windows-Diagnosis-DPS/Debug |
| 0x90000003 | Microsoft-Windows-Diagnosis-DPS/Operational |
Microsoft-Windows-Diagnosis-DPS/Operational |
| 0x90000004 | Microsoft-Windows-Diagnosis-DPS/Analytic |
Microsoft-Windows-Diagnosis-DPS/Analytic |
| 0x91000001 | Microsoft-Windows-Diagnosis-WDI |
Microsoft-Windows-Diagnosis-WDI |
| 0x91000002 | Microsoft-Windows-Diagnosis-WDI/Debug |
Microsoft-Windows-Diagnosis-WDI/Debug |
| 0xB0000001 | Diagnosticeringspolitik startede. Denne hændelse signalerer diagnosticeringsmoduler til forsinket behandling, efter at tjenesten er initialiseret. |
The Diagnostic Policy Service started. This event signals diagnostic modules for delayed processing after the service is initialized. |
| 0xB0000002 | Tjenesten Diagnosticeringspolitik blev startet. Med denne hændelse signaleres til diagnosticeringsmodulerne, så der kan ske øjeblikkelig behandling, når tjenesten er initialiseret. |
The Diagnostic Policy Service started. This event signals diagnostic modules for immediate processing after the service is initialized. |
| 0xB0000005 | Scenariet %1 har en konfigurationsfejl, eller den er eksplicit deaktiveret, i WDI-registreringsdatabasenavneområdet. Diagnosticeringspolitikken ignorerer scenariet. |
The scenario %1 has a configuration error or has been explicitly disabled in the WDI registry namespace. The Diagnostic Policy Service will ignore the scenario. |
| 0xB0000064 | Diagnosticeringsmodul %5 (%4) registrerede et problem for scenariet %1, forekomst %2, oprindeligt aktivitets-id %3. |
Diagnostic module %5 (%4) detected a problem for scenario %1, instance %2, original activity ID %3. |
| 0xB0000069 | Diagnosticeringsmodul %5 (%4) startede fejlfindingsscenariet %1, forekomst %2, oprindeligt aktivitets-id %3. |
Diagnostic module %5 (%4) started troubleshooting scenario %1, instance %2, original activity ID %3. |
| 0xB000006E | Diagnosticeringsmodul %5 (%4) afsluttede fejlfindingsscenariet %1, forekomst %2, oprindeligt aktivitets-id %3. Diagnosticeringsmodulet angav ingen løsning. |
Diagnostic module %5 (%4) finished troubleshooting scenario %1, instance %2, original activity ID %3. No resolution was set by the diagnostic module. |
| 0xB0000073 | Diagnosticeringsmodulet %9 (%4) har afsluttet fejlfindingsscenario %1, forekomst %2, original aktivitets-id %3. Det angav løsning %5 til brugeren %6 i sessionen %7 med udløbsdatoen %8. Løsningen startes med det samme. |
Diagnostic module %9 (%4) finished troubleshooting scenario %1, instance %2, original activity ID %3. It set resolution %5 for user %6 in session %7 with expiration date %8. The resolution will be started immediately. |
| 0xB0000078 | Diagnosticeringsmodulet %9 (%4) har afsluttet fejlfindingsscenario %1, forekomst %2, original aktivitets-id %3. Det angav løsning %5 til brugeren %6 i sessionen %7 med udløbsdatoen %8. Løsningen er sat i kø til senere start. |
Diagnostic module %9 (%4) finished troubleshooting scenario %1, instance %2, original activity ID %3. It set resolution %5 for user %6 in session %7 with expiration date %8. The resolution was queued to start later. |
| 0xB000007D | Diagnosticeringsmodul %5 (%4) startede løsning af scenariet %1, forekomst %2, oprindeligt aktivitets-id %3. |
Diagnostic module %5 (%4) started resolving scenario %1, instance %2, original activity ID %3. |
| 0xB000007E | Diagnosticeringsmodul %5 (%4) blev sat i kø til senere start for scenariet %1, forekomst %2, oprindeligt aktivitets-id %3. |
Diagnostic module %5 (%4) was queued to start later for scenario %1, instance %2, original activity ID %3. |
| 0xB0000082 | Diagnosticeringsmodul %5 (%4) afsluttede løsning af scenariet %1, forekomst %2, oprindeligt aktivitets-id %3. |
Diagnostic module %5 (%4) finished resolving scenario %1, instance %2, original activity ID %3. |
| 0xB0000087 | Diagnosticeringspolitik kunne ikke oprette en værtsforekomst for diagnosticeringsmodul for diagnosticeringsmodul %6 (%5). Fejlkoden var %4. Scenariet %1, forekomst %2, oprindeligt aktivitets-id %3 bliver ignoreret. |
The Diagnostic Policy Service could not create a diagnostic module host instance for diagnostic module %6 (%5). The error code was %4. The scenario %1, instance %2, original activity ID %3 will be discarded. |
| 0xB000008C | Der opstod en fejl i tjenesten Diagnosticeringspolitik i filen %1, funktion %2, linje %3: %4. |
The Diagnostic Policy Service encountered an error in file %1, function %2, line %3: %4. |
| 0xB0000091 | Denne hændelse forekommer, når SCM indlæser tjeneste-DLL-filen |
This event is raised when the SCM loads the service DLL |
| 0xB0000096 | Denne hændelse forekommer, når tjenesten går i en SERVICE_RUNNING-tilstand |
This event is raised when the service enters a SERVICE_RUNNING state |
| 0xB000009B | Denne hændelse forekommer, når SCM'et signalerer, at tjenesten skal lukke |
This event is raised when the SCM signals the service to shut down. |
| 0xB00000A5 | Der opstod en fejl i tjenesten Diagnosticeringspolitikken under håndtering af scenariet %1 med diagnosticeringsmodul %6 (%5), forekomst %2, oprindeligt aktivitets-id %3. Fejlkoden var %4. |
The Diagnostic Policy Service encountered an error while handling scenario %1 with diagnostic module %6 (%5), instance %2, original activity ID %3. The error code was %4. |
| 0xB00000AA | Der opstod en fejl i diagnosticeringsmodulet %6 (%4) under håndtering af scenariet %1, forekomst %2, oprindeligt aktivitets-id %3. Fejlkoden var %5. |
Diagnostic module %6 (%4) encountered an error while handling scenario %1, instance %2, original activity ID %3. The error code was %5. |
| 0xB00000AF | Scenariet %1, forekomst %2, oprindeligt aktivitets-id %3 blev udeladt af diagnosticeringsmodul %6 (%4). Fejlkoden var %5. |
Scenario %1, instance %2, original activity ID %3 was dropped by diagnostic module %6 (%4). The error code was %5. |
| 0xB00000B4 | Diagnosticeringspolitik har netop opdateret gruppepolitikken. Denne hændelse giver diagnosticeringsmodulet besked om ændringerne i gruppepolitikken. |
The Diagnostic Policy Service just refreshed the Group Policy. This event notifies the diagnostic modules about the Group Policy changes. |
| 0xB00000B9 | Diagnosticeringsmodul %2 (%1) blev flyttet til en brudt tilstand. Fejlkoden var %3. |
Diagnostic module %2 (%1) was moved into a broken state. The error code was %3. |
| 0xB0001398 | Diagnosticeringspolitik skal foretages i en heapallokering |
The Diagnostic Policy Service just made a heap allocation |
| 0xB0001399 | Diagnosticeringspolitik har frigjort en tidligere foretaget heapallokering |
The Diagnostic Policy Service just freed a previously made heap allocation |
| 0xB1001398 | Diagnosticeringsinfrastruktur har foretaget en heapallokering |
The Diagnostic Infrastructure just made a heap allocation |
| 0xB1001399 | Diagnosticeringsinfrastruktur har frigjort en tidligere foretaget heapallokering |
The Diagnostic Infrastructure just freed a previously made heap allocation |