0x10000001 | Udviklerfejlfinding: Isoler fejl i levering af toastbesked i skyen |
Developer Debug: Isolate Failures in Cloud Toast Notification Delivery |
0x10000002 | Udviklerfejlfinding: Isoler fejl i levering af lokal toastbesked |
Developer Debug: Isolate Failures in Local Toast Notification Delivery |
0x10000003 | Udviklerfejlfinding: Foretager fejlfinding ved levering af råbesked |
Developer Debug: Debugging Raw Notification Delivery Errors |
0x10000004 | Udviklerfejlfinding: Isoler fejl i levering af råbesked |
Developer Debug: Isolate Failures in Raw Notification Delivery |
0x10000009 | Forbindelsesstyring |
Connection Manager |
0x1000000A | Slutpunktsstyring |
Endpoint Manager |
0x1000000B | Trådgruppe |
Threadpool |
0x1000000C | API for præsentationslag |
Presentation Layer API |
0x1000000D | Platform |
Platform |
0x1000000E | Fejlfinding |
Debug |
0x1000000F | Forbindelsesprovider |
Connection Provider |
0x10000010 | Ydeevnescenarie: Første skybesked |
Performance Scenario: First cloud notification |
0x10000011 | Ydeevnescenarie: Første skybesked med hentning af skybillede |
Performance Scenario: First cloud notification with cloud image download |
0x10000012 | Ydeevnescenarie: Der kommer ny skybesked |
Performance Scenario: New cloud notification arrives |
0x10000013 | Ydeevnescenarie: Der kommer ny skybesked, der refererer til skybilleder |
Performance Scenario: New cloud notification refering cloud images arrives |
0x10000014 | Ydeevnescenarie: MoGo panorerer |
Performance Scenario: MoGo is panning |
0x10000015 | Ydeevnescenarie: MoGo panorerer med hentning af skybilleder |
Performance Scenario: MoGo is panning with downloading cloud images |
0x10000016 | Ydeevnescenarie: Lukning af Windows Push-besked |
Performance Scenario: The Windows Push Notification shutdown |
0x10000017 | WNP-transportlag |
WNP Transport Layer |
0x10000019 | Udviklerfejlfinding: Isoler fejl i levering af feltbesked i skyen |
Developer Debug: Isolate Failures in Cloud Tile Notification Delivery |
0x1000001A | Udviklerfejlfinding: Foretager fejlfinding i skyforbindelse |
Developer Debug: Debugging Cloud Connectivity |
0x1000001B | Udviklerfejlfinding: Foretager fejlfinding i skyforbindelse: Er enheden tilsluttet? |
Developer Debug: Debugging Cloud Connectivity - Is device connected? |
0x1000001C | Udviklerfejlfinding: Foretager fejlfinding i skyforbindelse: fejl |
Developer Debug: Debugging Cloud Connectivity - errors |
0x1000001D | Udviklerfejlfinding: Foretager fejlfinding i ændringer af platformindstilling |
Developer Debug: Debugging Platform Setting Changes |
0x1000001E | Udviklerfejlfinding: Isoler fejl i levering af lokal feltbesked |
Developer Debug: Isolate Failures in Local Tile Notification Delivery |
0x1000001F | Udviklerfejlfinding: Foretager fejlfinding ved levering af pollingbesked |
Developer Debug: Debugging Polling Notification Delivery Errors |
0x10000020 | Udviklersupport: End-to-End-sporing af ny besked |
Developer Support: End-to-End trace for new notification |
0x10000031 | Svartid |
Response Time |
0x30000000 | Oplysninger |
Info |
0x30000001 | Start |
Start |
0x30000002 | Stop |
Stop |
0x50000002 | Fejl |
Error |
0x50000003 | Advarsel |
Warning |
0x50000005 | Detaljeret |
Verbose |
0x90000001 | Microsoft-Windows-PushNotifications-Platform |
Microsoft-Windows-PushNotifications-Platform |
0x90000002 | Microsoft-Windows-PushNotifications-Platform/Operational |
Microsoft-Windows-PushNotifications-Platform/Operational |
0x90000003 | Microsoft-Windows-PushNotifications-Platform/Debug |
Microsoft-Windows-PushNotifications-Platform/Debug |
0x90000004 | Microsoft-Windows-PushNotifications-Platform/Admin |
Microsoft-Windows-PushNotifications-Platform/Admin |
0xB0000001 | Windows Push-beskedplatformen har registreret en fejl i filen: %1, funktionen %2, linjen %3: %4. |
The Windows Push Notification Platform has encountered an error in file: %1, function %2, line %3: %4. |
0xB0000002 | Windows Push-beskedplatformen har startet indlæsningen. |
The Windows Push Notification Platform has started loading. |
0xB0000003 | Windows Push-beskedplatformen er blevet fjernet. |
The Windows Push Notification Platform has been unloaded. |
0xB0000004 | Windows Push-beskedplatformen er blevet deaktiveret på grund af indstillinger for gruppepolitikken. |
The Windows Push Notification Platform has been disabled due to Group Policy settings. |
0xB0000005 | Windows Push-beskedplatformen er blevet indlæst. |
The Windows Push Notification Platform has been loaded. |
0xB0000006 | Windows Push-beskedplatformen har startet fjernelsen. |
The Windows Push Notification Platform has started unloading. |
0xB0000007 | Windows Push-beskedplatformen blev startet som %1 med %2-rettighed. |
The Windows Push Notification Platform has launched as %1 with %2 privilege. |
0xB0000008 | Windows Push-beskedplatformen skifter til ny %1-rettighed. |
The Windows Push Notification Platform is switching into new %1 privilege. |
0xB0000009 | Windows Push-beskedplatformen er skiftet med fejlkoden %2, og den aktuelle rettighed er %1. |
The Windows Push Notification Platform has switched with error code %2, and current privilege is %1. |
0xB000000A | Windows Push-beskedplatformen har startet defragmentering af lager. |
The Windows Push Notification Platform has started defragging storage. |
0xB000000B | Windows Push-beskedplatformen har afsluttet defragmentering af lager. |
The Windows Push Notification Platform has finished defragging storage. |
0xB000000C | Windows Push-beskedplatformen har fastlagt det nye maksimale antal programmer %2 på basis af antallet af aktuelle programmer %1. Det gamle maksimale antal programmer er %3. |
The Windows Push Notification Platform has determined new maximum number of applications %2 based on count of current applications %1. Old maximum number of applications is %3. |
0xB000000D | Windows Push-beskedplatformen har udvidet det permanente headerlager, så der er plads til %1 programmer. |
The Windows Push Notification Platform has expanded its persistent header storage to accommodate %1 Applications. |
0xB000000E | Windows Push-beskedplatformen har skiftet til at bruge en udvidet fastholdelsesbuffer. |
The Windows Push Notification Platform has switched to using an expanded persistence buffer. |
0xB000000F | Windows Push-beskedplatformen har startet indlæsning af fildata: antal programmer %1, antal allokerede poster %2 og maksimalt antal %3. |
The Windows Push Notification Platform has started loading file data: count applications %1, count allocated entries %2, max count %3. |
0xB0000010 | Windows Push-beskedplatformen har oprettet en ny fil, der er knyttet til hukommelsen. |
The Windows Push Notification Platform has created a new memory-mapped file. |
0xB0000011 | Windows Push-beskedplatformen har registreret, at fastholdelsesbufferen ikke er synkroniseret. |
The Windows Push Notification Platform has detected that its persistent buffer is out of sync. |
0xB0000012 | Windows Push-beskedplatformen har registreret indbakkeprogrammer. |
The Windows Push Notification Platform has registered inbox applications. |
0xB0000014 | Windows Push-beskedplatformen har registreret en fejl %2 under åbning af filen %1. |
The Windows Push Notification Platform has encountered error %2 opening file %1. |
0xB0000015 | Windows Push-beskedplatformen er begyndt at behandle indstillinger for feltopdatering for %1 indbakke og %2 forudinstallationsapps. |
The Windows Push Notification Platform has started processing tile update settings for %1 inbox and %2 preinstall apps. |
0xB0000016 | Windows Push-beskedplatformen er stoppet med at behandle indstillinger for feltopdatering. |
The Windows Push Notification Platform has stopped processing tile update settings. |
0xB0000017 | Windows Push-beskedplatformen angiver URI %2 med gentagelsen %3 for AppUserModelId %1. |
The Windows Push Notification Platform is setting URI %2 with recurrence %3 for AppUserModelId %1. |
0xB0000018 | Windows Push-beskedplatformen har startet en WNS-forbindelse. |
The Windows Push Notification Platform has initiated a WNS connection. |
0xB0000019 | Windows Push-beskedplatformen afbryder forbindelsen til WNS. |
The Windows Push Notification Platform is disconnecting from WNS. |
0xB000001A | ThreadPool: [%1] (%2) er blevet planlagt. |
ThreadPool: [%1] (%2) has been scheduled. |
0xB000001B | ThreadPool: [%1] (%2) sluttede med fejlkoden [%3] |
ThreadPool: [%1] (%2) finished with error code [%3] |
0xB000001C | ResourceManager har modtaget en meddelelse: kode [%1] |
ResourceManager has recevied a message: code [%1] |
0xB000001D | Windows Push-beskedplatformen er begyndt at rense billedcachen. |
The Windows Push Notification Platform has started scavenging the image cache. |
0xB000001E | Windows Push-beskedplatformen har afsluttet rensningen af billedcachen. |
The Windows Push Notification Platform has finished scavenging the image cache. |
0xB000001F | Windows Push-beskedplatformen har %1 poster i billedcachen. |
The Windows Push Notification Platform has %1 entries in the image cache. |
0xB0000020 | Enheden har skiftet til strømsparetilstand: BATTERY_SAVINGS_ON |
The Device has entered battery saver state: BATTERY_SAVINGS_ON |
0xB0000021 | Enheden har afsluttet strømsparetilstanden: BATTERY_SAVINGS_OFF |
The Device has exited battery saver state: BATTERY_SAVINGS_OFF |
0xB0000022 | DcpProvider blev indlæst. |
The DcpProvider has been loaded successfully. |
0xB0000023 | WNS-platformen afsluttede TraceLogging-registreringen med koden %1. |
WNS Platform finished TraceLogging registration with code %1. |
0xB0000024 | WNS-forbindelsesprovideren afsluttede TraceLogging-registreringen med koden %1. |
WNS Connection Provider finished TraceLogging registration with code %1. |
0xB0000025 | Windows Push-beskedplatformen er påkrævet for at kunne oprette forbindelse under start, ValidChannelsExist : %1. |
The Windows Push Notification Platform is required to connect on startup, ValidChannelsExist : %1. |
0xB0000026 | PDC-initialiseringen blev afsluttet med fejlkoden %1. |
PDC intialization finished with ErrorCode: %1. |
0xB0000027 | PDC-afinitialiseringen blev afsluttet med fejlkoden %1. |
PDC unintialization finished with ErrorCode: %1. |
0xB0000028 | PDC-aktivering blev afsluttet med fejlkoden %1, PdcType: %2, PdcScenario: %3, PdcNetRef: %4, PdcPlatRef: %5. |
PDC activation finished with ErrorCode: %1, PdcType: %2, PdcScenario: %3, PdcNetRef: %4, PdcPlatRef: %5. |
0xB0000029 | PDC-deaktivering blev afsluttet med fejlkoden %1, PdcType: %2, PdcNetRef: %3, PdcPlatRef: %4. |
PDC deactivation finished with ErrorCode: %1, PdcType: %2, PdcNetRef: %3, PdcPlatRef: %4. |
0xB00003E8 | Der er registreret en forbindelsesprovider på Windows Push-beskedplatformen med følgende parametre: %1 [CLSID] %2 [Aktiveret] %3 [CLSCTX-flag]. |
A Connection Provider is registered with Windows Push Notification Platform using the following parameters: %1 [CLSID] %2 [Enabled] %3 [CLSCTX Flags]. |
0xB00003E9 | Følgende forbindelsesprovider er aktiveret med parametrene: %1 [CLSID] %2 [CLSCTX-flag]. |
The following Connection Provider is enabled with the parameters: %1 [CLSID] %2 [CLSCTX Flags]. |
0xB00003EA | Forbindelsesprovideren med CLSID %1 blev instantieret med følgende flag %2 og afsluttet med fejlkoden %3. |
The Connection Provider with CLSID %1 was instantiated with the following flags %2 and finished with ErrorCode %3. |
0xB00003EB | Der blev sendt en forbindelsesanmodning til forbindelsesprovideren. |
Connect request sent to the Connection Provider. |
0xB00003EC | Der blev sendt en afbrydelsesanmodning til forbindelsesprovideren. |
Disconnect request sent the Connection Provider. |
0xB00003ED | Status for forbindelsesprovideren blev ændret til %1. |
The Connection Provider status changed to %1. |
0xB00003EE | Sender en kanalforespørgsel til forbindelsesprovideren med parametrene: %1 [PackageFullName] %2 [Properties] %3 [Cookie] %4 [TransactionId]. |
Sending a channel request to the Connection Provider with parameters: %1 [PackageFullName] %2 [Properties] %3 [Cookie] %4 [TransactionId]. |
0xB00003EF | Forbindelsesprovideren afsluttede kanalforespørgslen om transaktions-id %1. %2 [ChannelId] %3 [ChannelUri] %4 [Expiry]. |
The Connection Provider completed the channel request for transaction id %1. %2 [ChannelId] %3 [ChannelUri] %4 [Expiry]. |
0xB00003F0 | Sender en kanaltilbagekaldelsesanmodning til forbindelsesprovideren for kanal-id %1. |
Sending a channel revoke request to the Connection Provider for channel id %1. |
0xB00003F2 | %1 blev modtaget for ChannelId %2 og AppUserModelId %3 med TrackingId %4, X-WNS-MSG-ID %5, tidsstempel %6 og udløb %7 tag: %8, gruppe: %9, handling: %10, bundt: count=%11;missed=%12;Id=%13. |
%1 received for ChannelId %2 and AppUserModelId %3 with TrackingId %4, X-WNS-MSG-ID %5, timestamp %6 and expiration %7 tag: %8, group: %9, action: %10, bundle: count=%11;missed=%12;Id=%13. |
0xB00003F3 | Sender en anmodning til forbindelsesprovideren om at forny en kanal med parametrene: %1 [ChannelId] %2 [PackageFullName] %3 [Properties] %4 [Cookie] %5 [TransactionId]. |
Sending a request to the Connection Provider to renew a channel with parameters: %1 [ChannelId] %2 [PackageFullName] %3 [Properties] %4 [Cookie] %5 [TransactionId]. |
0xB00003F4 | Angiver batchkonfigurationen til følgende tilstand: %1. |
Setting batching configuration to the following state: %1. |
0xB00003F5 | Konfigurerer beskedlevering for AppUserModelId %4 med kanal-id %1. %2 [NotificationType] %3 [Enabled]. |
Configuring notification delivery for AppUserModelId %4 with channel id %1. %2 [NotificationType] %3 [Enabled]. |
0xB00003F6 | Ressourcestyringen har fået besked om, at visningstilstanden blev ændret til %1. |
The Resource Manager was notified that display state changed to %1. |
0xB00003F7 | Konfigurerer meddelelsespolitik for %1 [NotificationType] %2 [Enabled]. |
Configuring notification policy for %1 [NotificationType] %2 [Enabled]. |
0xB00003F8 | Ressourcestyringen har fået besked om en opdatering af netværksomkostningerne. %1 [Cost] %2 [Costly]. |
The Resource Manager was notified of an update to the network cost. %1 [Cost] %2 [Costly]. |
0xB00003F9 | Ressourcestyringen har fået besked om en opdatering til dataabonnementet. %1 [Source] %2 [BillingCycle]. |
The Resource Manager was notified of an update to the data plan. %1 [Source] %2 [BillingCycle]. |
0xB00003FA | Ressourcestyringen har nulstillet statistikkerne for anvendelse af mobilbredbånd. |
The Resource Manager reset the Mobile Broadband Usage statistics. |
0xB00003FB | Ressourcestyringen har fået besked om, at tilstanden for brugersessionen blev ændret til %1 for sessions-id %2. Det aktuelle sessions-id er %3. |
The Resource Manager was notified that user session state changed to %1 for session id %2. The current session id is %3. |
0xB00003FC | Status for Forbindelsesprovider skiftede til en fejltilstand: %1. |
The Connection Provider status changed to a failure state: %1. |
0xB00003FD | Forbindelsesstyringen kunne ikke oprette forbindelse: %1. |
The Connection Manager has failed to connect: %1. |
0xB00003FE | ConnectWork anmoder ConnectionManager om at oprette forbindelse. |
ConnectWork is requesting ConnectionManager to connect. |
0xB00003FF | Der er ingen internetforbindelse. %1 er sat i kø til næste ændring af netværksstatussen. |
No internet connection available, %1 is queued for next network status change. |
0xB0000400 | Statussen for internetforbindelsen blev ændret til Oprettet forbindelse (sidst kendte status var %1). Sender ventende arbejdselementer. |
Internet connection status changed to Connected (last known status was %1), submitting pending workitems. |
0xB000044C | Opretter forbindelse til Windows Push-beskedtjenesten. %1 [UserId] %2 [UserType] %3 [FeatureSet] %4 [AuthType] %6 [AuthPayload] %8 [BindPayload]. |
Connecting to the Windows Push Notification Service. %1 [UserId] %2 [UserType] %3 [FeatureSet] %4 [AuthType] %6 [AuthPayload] %8 [BindPayload]. |
0xB000044D | Tilslutningsresultat for Windows Push-beskedtjeneste: %1. |
Windows Push Notification Service connection result: %1. |
0xB000044E | Sender kanalkommando for WNP-protokol: %1 [TransactionId] %2 [ChannelId] %3 [PackageFullName] %4 [Properties] %6 [Command] %7 [Namespace] %8 [ContextId] %10 [Payload] %11 [UserId]. |
Sending Channel WNP Protocol command: %1 [TransactionId] %2 [ChannelId] %3 [PackageFullName] %4 [Properties] %6 [Command] %7 [Namespace] %8 [ContextId] %10 [Payload] %11 [UserId]. |
0xB000044F | Sporingsoplysninger for kanalkommando for WNP-protokol: %1 [TransactionId] %2 [TrID]. |
Channel WNP Protocol command tracking information: %1 [TransactionId] %2 [TrID]. |
0xB0000450 | Sender tilbagekaldelseskommando for WNP-protokol: %1 [ChannelId] %3 [Command] %4 [Namespace] %5 [ContextId] %7 [Payload] %8 [UserId]. |
Sending Revoke WNP Protocol command: %1 [ChannelId] %3 [Command] %4 [Namespace] %5 [ContextId] %7 [Payload] %8 [UserId]. |
0xB0000451 | Sender kommando om blokering/fjernelse af blokering for WNP-protokol: %1 [ChannelId] %2 [NotificationType] %3 [Enabled] %5 [Command] %6 [Namespace] %7 [ContextId] %9 [Payload] %10 [UserId]. |
Sending Block/Unblock WNP Protocol command: %1 [ChannelId] %2 [NotificationType] %3 [Enabled] %5 [Command] %6 [Namespace] %7 [ContextId] %9 [Payload] %10 [UserId]. |
0xB0000452 | Sender indstillingskommando for WNP-protokol: %1 [State] %3 [Command] %4 [Namespace] %5 [ContextId] %7 [Payload]. |
Sending Options WNP Protocol command: %1 [State] %3 [Command] %4 [Namespace] %5 [ContextId] %7 [Payload]. |
0xB0000453 | Kommandosvar for WNP-protokol: %1 [TrID] %2 [Error] %3 [ContextId] %4 [UserId]. |
WNP Protocol command response: %1 [TrID] %2 [Error] %3 [ContextId] %4 [UserId]. |
0xB0000454 | Leveret besked for WNP-protokol: %1 [Namespace] %2 [UserId] %3 [PayloadSize] %4 [MsgId] %5 [Ack]. |
WNP Protocol delivered notification: %1 [Namespace] %2 [UserId] %3 [PayloadSize] %4 [MsgId] %5 [Ack]. |
0xB0000455 | Afbryder forbindelse til Windows Push-beskedtjeneste. |
Disconnecting from the Windows Push Notification Service. |
0xB0000456 | Resultat af afbrydelse af forbindelse til Windows Push-beskedtjeneste: %1. |
Windows Push Notification Service disconnection result: %1. |
0xB0000458 | Anmoder om Device Compact Ticket til %1. |
Requesting Device Compact Ticket for the %1. |
0xB0000459 | Anmodningen om Device Compact Ticket blev udført med enheds-id'et %1 for %2. |
Device Compact Ticket request completed with Device Id %1 for the %2. |
0xB000045A | Sender kommando om filtrering/fjernelse af filtrering for WNP-protokol: %1 [NotificationType] %2 [Enabled] %4 [Command] %5 [Namespace] %6 [ContextId] %8 [Payload] %9 [UserId]. |
Sending Filter/Unfilter WNP Protocol command: %1 [NotificationType] %2 [Enabled] %4 [Command] %5 [Namespace] %6 [ContextId] %8 [Payload] %9 [UserId]. |
0xB000045B | Sender bekræftelseskommando for WNP-protokol: %1 [MsgId] %3 [Command] %4 [Namespace] %6 [Payload]. |
Sending Ack WNP Protocol command: %1 [MsgId] %3 [Command] %4 [Namespace] %6 [Payload]. |
0xB000045C | Device Compact Ticket-anmodning mislykkedes med fejlen %1 for %2. |
Device Compact Ticket request failed with error %1 for the %2. |
0xB000045D | Forbindelsen til Windows Push-beskedtjenesten blev afbrudt pga. af fejlen %1, og forbindelsen blev ikke oprettet igen. |
Windows Push Notification Service was disconnected due to error: %1 and will now enter reconnect mode. |
0xB000045E | Sender Challenge/Response-kommando for WNP-protokollen: %1 [Nonce] %2 [Response] %4 [Command] %5 [Namespace] %6 [ContextId] %8 [Payload]. |
Sending Challenge Response WNP Protocol command: %1 [Nonce] %2 [Response] %4 [Command] %5 [Namespace] %6 [ContextId] %8 [Payload]. |
0xB00004B1 | Tilslutningsopkald for WNP-transportlag blev startet for %1. |
WNP Transport Layer Connect call initiated for the %1. |
0xB00004B2 | Tilslutningsopkald for WNP-transportlag blev fuldført for %1. |
WNP Transport Layer Connect call completed for the %1. |
0xB00004B3 | Send kommando-kald for WNP-transportlag blev startet for TrID %1 på %2. |
WNP Transport Layer SendCommand call initiated for TrID %1 on the %2. |
0xB00004B4 | Send kommando-kald for WNP-transportlag blev fuldført for TrID %1 på %2. |
WNP Transport Layer SendCommand call completed for TrID %1 on the %2. |
0xB00004B5 | Kald om afbrydelse af forbindelse for WNP-transportlag blev startet for %1. |
WNP Transport Layer Disconnect call initiated for the %1. |
0xB00004B6 | Kald om afbrydelse af forbindelse for WNP-transportlag blev fuldført for %1. |
WNP Transport Layer Disconnect call completed for the %1. |
0xB00004B7 | Fortolkning af DNS for WNP-transportlag blev startet for værten %2 for %1. |
WNP Transport Layer resolving DNS initiated for host %2 for the %1. |
0xB00004B8 | Fortolkning af DNS for WNP-transportlag blev fuldført for %1 med koden %2. |
WNP Transport Layer resolving DNS completed for the %1 with code %2. |
0xB00004BB | Tilslutning til standardserver for WNP-transportlag blev startet til serveren %2 på porten %3 for %1. |
WNP Transport Layer initial server connection initiated to server %2 on port %3 for the %1. |
0xB00004BC | Tilslutning til standardserver for WNP-transportlag blev fuldført til serveren %2 på porten %3 for %1. |
WNP Transport Layer initial server connection completed to server %2 on port %3 for the %1. |
0xB00004BD | Proxyforbindelse for WNP-transportlag blev startet for %1. |
WNP Transport Layer proxy connection initiated for the %1. |
0xB00004BE | Proxytilslutning for WNP-transportlag blev fuldført til serveren %2 for %1. |
WNP Transport Layer proxy connection completed to server %2 for the %1. |
0xB00004BF | Proxyforhandling for WNP-transportlag blev startet for %1. |
WNP Transport Layer proxy negotiation initiated for the %1. |
0xB00004C0 | Proxyforhandling for WNP-transportlag blev fuldført for %1. |
WNP Transport Layer proxy negotiation completed for the %1. |
0xB00004C1 | TLS-forhandling for WNP-transportlag blev startet for %1. |
WNP Transport Layer TLS negotiation initiated for the %1. |
0xB00004C2 | TLS-forhandling for WNP-transportlag blev fuldført for %1 med koden %2. |
WNP Transport Layer TLS negotiation completed for the %1 with code %2. |
0xB00004C3 | WNP-transportlag sendte %1 byte på %2. |
WNP Transport Layer sent %1 bytes on the %2. |
0xB00004C4 | WNP-transportlag modtog %1 byte på %2. |
WNP Transport Layer received %1 bytes on the %2. |
0xB00004C7 | WNP-transportlag sendte kommando til %6 med verbet: %1, Trid: %2, Navneområde: %3, der indeholder %4 byte data: %5. |
WNP Transport Layer sent command for the %6 with Verb: %1, Trid: %2, Namespace: %3 containing %4 bytes of payload: %5. |
0xB00004C8 | WNP-transportlag modtog %1 byte data: %2. |
WNP Transport Layer received %1 bytes of payload: %2. |
0xB00004C9 | WNP-transportlag modtog kommando til %6 med verbet: %1, Trid: %2, Navneområde: %3, der indeholder %4 byte data: %5. |
WNP Transport Layer received command for the %6 with Verb: %1, Trid: %2, Namespace: %3 containing %4 bytes of payload: %5. |
0xB00004CA | WNP-transportlag modtog proxyserversvar til %3 på %1 byte med dataene: %2. |
WNP Transport Layer received proxy server response for the %3 of %1 bytes with payload: %2. |
0xB00004CB | WNP-transportlag modtog kommando ved afbrydelse af forbindelse til %6 med verbet: %1, Trid: %2, Navneområde: %3, der indeholder %4 byte data: %5. |
WNP Transport Layer received command when disconnected for the %6 with Verb: %1, Trid: %2, Namespace: %3 containing %4 bytes of payload: %5. |
0xB00004CC | Keep alive-detektor for WNP modtog OnConnected-hændelse fra testforbindelsen med fejlen: %1 |
WNP Keep Alive Detector received OnConnected event from the test connection with Error: %1 |
0xB00004CD | Keep alive-detektor for WNP modtog OnReconnecting-hændelse fra testforbindelsen med fejlen: %1 |
WNP Keep Alive Detector received OnReconnecting event from the test connection with Error: %1 |
0xB00004CE | Keep alive-detektor for WNP modtog OnDisconnected-hændelse fra testforbindelsen med fejlen: %1 |
WNP Keep Alive Detector received OnDisconnected event from the test connection with Error: %1 |
0xB00004CF | Keep alive-detektor for WNP modtag KA-tip fra serveren: %1 sekunder |
WNP Keep Alive Detector received KA hint from server: %1 seconds |
0xB00004D0 | Keep alive-detektor for WNP opdaterer KA-tiden med værdien: %2 sekunder, typen: %1 |
WNP Keep Alive Detector updating cached Ka time with value: %2 seconds; type: %1 |
0xB00004D1 | Hurtig genoprettelse blev udløst for tidligere WNS-session (%1) på %3. Der er gået %2 sekunder siden sidste pakke. |
Fast reconnect triggered for previous WNS session (%1) on the %3. It has been %2 seconds since last packet. |
0xB00004D2 | %2 TCP-forbindelse blev etableret over %1. |
%2 TCP connection established over %1. |
0xB00004D3 | Keep alive-detektor for WNP nulstiller interval for fejl i inaktivitet. Det seneste interval for inaktivitet fuldført på %1 sekunder er større end intervallet for fejl i inaktivitet på %2 sekunder |
WNP Keep Alive Detector resetting Idle Failed Interval. Last Idle-Succeeded interval %1 seconds is larger than Idle-Failed interval %2 seconds |
0xB00004D4 | Keep alive-detektor for WNP forøgede tallet for inaktivitet fuldført til %1 |
WNP Keep Alive Detector incrementing Idle-Succeeded count to %1 |
0xB00004D5 | Keep alive-detektor for WNP registrerede et interval for fejl i inaktivitet på %1 sekunder |
WNP Keep Alive Detector encountered failed idle interval of %1 seconds |
0xB00004D6 | Keep alive-detektor for WNP starter testforbindelse |
WNP Keep Alive Detector starting Test Connection |
0xB00004D7 | Keep alive-detektor for WNP starter KA-måling med værdien: %2 sekunder, typen: %1, min. grænse: %3 sekunder |
WNP Keep Alive Detector starting KA measurement with value: %2 seconds; type: %1; Min Limit: %3 seconds |
0xB00004D8 | Keep alive-detektor for WNP stopper KA-måling |
WNP Keep Alive Detector stopping KA measurement |
0xB00004D9 | Keep alive-detektor for WNP mistede netværk over %1. |
WNP Keep Alive Detector lost network over %1. |
0xB00004DA | WNP-transportlag modtog strømstyringshændelse med typen %1 på %2. |
WNP Transport Layer received Power Management event with type %1 on the %2. |
0xB00004DB | WNP-transportlag modtog strømstyringshændelse med typen %1 på %2. Meddelelsen ignoreres. |
WNP Transport Layer received Power Management event with type %1 on the %2. Message is ignored |
0xB00004DC | Der kunne ikke forbindes til Windows Push-beskedtjenesten (%1:%2), da den registrerede proxyvært (%3) ikke kunne bruges til at forbinde. Kontrollér proxykonfigurationen på klienten, og kontrollér, at den registrerede proxyvært fungerer korrekt. |
Connection to the Windows Push Notification Service (%1:%2) failed because proxy host detected (%3) could not be used to establish the connection. Please check the proxy configuration on the client as well as verify that the proxy host detected is operating correctly. |
0xB00004DD | Der kunne ikke forbindes til Windows Push-beskedtjenesten (%1:%2), da den registrerede proxyvært (%3) udtrykkeligt kræver brugergodkendelse. Det er kun proxyer, der er konfigureret med NTLM-godkendelse, som understøttes. |
Connection to the Windows Push Notification Service (%1:%2) failed because the proxy host detected (%3) explicitly requires user authentication. Only proxies configured with NTLM authentication are supported. |
0xB00004DE | WNP-transportlag blev afbrudt fra Windows Push-beskedtjenesten, fordi netværksforbindelsen blev afbrudt. |
WNP Transport Layer was disconnected from the Windows Push Notification Service due to a loss of network connectivity. |
0xB00004DF | Der opstod fejl i forbindelsen til Windows Push-beskedtjenesten, fordi forbindelsen ikke blev konfigureret til at køre korrekt i strømbesparelsestilstande. Kontrollér, at alle netværksdrivere er opdateret. |
Connection to the Windows Push Notification Service failed because of a failure to configure the connection to run properly in low-power states. Please ensure all network drivers are up to date. |
0xB00004E0 | Der kan ikke forbindes til Windows Push-beskedtjenesten (%1:%2), fordi der ikke kan forbindes til den registrerede proxyvært (%3). HTTP-anmodningen blev ikke gennemført med HTTP-status: %4. |
Connection to the Windows Push Notification Service (%1:%2) failed because the proxy host detected (%3) could not be connected to. The HTTP request failed with HTTP Status: %4. |
0xB00004E1 | StopKeepAliveMeasurement blev kaldt fra meddelelsesløkken. |
StopKeepAliveMeasurement was called from message loop. |
0xB00004E2 | KA-målingen blev aldrig startet. |
The KA measurement was never started. |
0xB00004E3 | Testforbindelsen blev ikke afbrudt synkront på grund af fejl: %1 |
The test connection disconnect failed synchronously due to error: %1 |
0xB00004E4 | KA-værdien er konvergeret. Afbryd nu testforbindelsen. |
The KA value has converged. Now disconnect test connection. |
0xB00004E5 | Testforbindelsen afbrydes på grund af inaktivitet. |
The test connection will be disconnected due to idle failure. |
0xB00004E6 | WNP-transportlaget for %1 registrerede en foretrukken grænsefladeændring. Gammelt indeks %2, gammel adressefamilie %3. Nyt indeks %4, ny adressefamilie %5, NDIS_PHYSICAL_MEDIUM %6. |
WNP Transport Layer for %1 detected preferred interface change. Old index %2, old address family %3. New index %4, new address family %5, NDIS_PHYSICAL_MEDIUM %6. |
0xB00004E7 | WNP-transportlaget for %1 reagerede på foretrukken grænsefladeændring. Forbindelsen blev afbrudt og oprettet igen med det samme. |
WNP Transport Layer for %1 reacting to preferred interface change, disconnect and immediately reconnect. |
0xB00004E8 | WNP-transportlaget for %1 reagerede på foretrukken grænsefladeændring. Forbindelsen blev oprettet med det samme igen. |
WNP Transport Layer for %1 reacting to preferred interface change, immediately reconnect. |
0xB00004E9 | WNP-transportlaget for %1 kaldte InitializeSecurityContext og fik returkoden %2. |
WNP Transport Layer for %1 called InitializeSecurityContext and got return code %2. |
0xB00004EA | WNP-transportlaget for %1 modtog en asynkron forbindelsesfejl %2. |
WNP Transport Layer for %1 received asynchronous connection error %2. |
0xB00004EB | WNP-transportlaget for dataforbindelsen sender Keep Alive-anmodning (PNG) uden for båndbredde. |
WNP Transport Layer for the Data Connection sending out of band keep alive (PNG) request. |
0xB00004EC | WNP-transportlaget for dataforbindelsen modtog WNF-event for ændring af mobiltilstand. |
WNP Transport Layer for the Data Connection received cellular state change WNF event. |
0xB00004ED | Føjer en ny bruger til Windows Push-beskedtjenesten. %1 [DeviceId] %2 [UserId] %3 [UserType]. |
Adding new user to the Windows Push Notification Service. %1 [DeviceId] %2 [UserId] %3 [UserType]. |
0xB00004EE | Fjerner eksisterende bruger fra Windows Push-beskedtjenesten. %1 [DeviceId] %2 [UserId] %3 [UserType]. |
Removing existing user from the Windows Push Notification Service. %1 [DeviceId] %2 [UserId] %3 [UserType]. |
0xB00004EF | Erstatter eksisterende bruger fra Windows Push-beskedtjeneste. %1 [DeviceId] %2 [OldUserId] %3 [OldUserType] %4 [NewUserId] %5 [NewUserType]. |
Replacing existing user from the Windows Push Notification Service. %1 [DeviceId] %2 [OldUserId] %3 [OldUserType] %4 [NewUserId] %5 [NewUserType]. |
0xB00004F0 | Den nye bruger blev føjet til Windows Push-beskedtjenesten. %1 [DeviceId] %2 [UserId] %3 [ErrorCode]. |
Adding new user to the Windows Push Notification Service completed. %1 [DeviceId] %2 [UserId] %3 [ErrorCode]. |
0xB00004F1 | En eksisterende bruger blev fjernet fra Windows Push-beskedtjenesten. %1 [DeviceId] %2 [UserId] %3 [ErrorCode]. |
Removing existing user from the Windows Push Notification Service completed. %1 [DeviceId] %2 [UserId] %3 [ErrorCode]. |
0xB00004F2 | En eksisterende bruger blev erstattet i Windows Push-beskedtjenesten. %1 [DeviceId] %2 [OldUserId] %3 [NewUserId] %4 [ErrorCode]. |
Replacing existing user from the Windows Push Notification Service completed. %1 [DeviceId] %2 [OldUserId] %3 [NewUserId] %4 [ErrorCode]. |
0xB00004F3 | WNP-transportlaget sendte en kommando for %6 med Verbum: %1, Trid: %2, Navneområde: %3, som kun indeholder %4 bytes data. De samlede data inklusive headeren er: %5. |
WNP Transport Layer sent command for the %6 with Verb: %1, Trid: %2, Namespace: %3 containing %4 bytes of payload only. However, full payload including header is: %5. |
0xB00004F4 | WNP-transportlager modtog en kommando for %6 med Verbum: %1, Trid: %2, Navneområde: %3, som kun indeholder %4 bytes data. De samlede data inklusive headeren er: %5. |
WNP Transport Layer received command for the %6 with Verb: %1, Trid: %2, Namespace: %3 containing %4 bytes of payload only. However, full payload including header is: %5. |
0xB0000514 | Startede sporing af forbindelsens ydeevne. |
Started tracking connection establishment performance. |
0xB0000515 | Afsluttede sporing af forbindelsens ydeevne. |
Finished tracking connection establishment performance. |
0xB0000516 | PDC-initialiseringen blev afsluttet med fejlkoden [%1], og initialiseringsantallet er [%2]. |
PDC Intialization finished with error code [%1] and Initialization Count is [%2]. |
0xB0000517 | PDC-afinitialiseringen blev afsluttet med fejlkoden [%1], og initialiseringsantallet er [%2]. |
PDC Unintialization finished with error code [%1] and Initialization Count is [%2]. |
0xB0000518 | PDC-aktiveringen blev afsluttet med fejlkoden [%1], initialiseringsantallet er [%2], og årsagen er [%3] for %4. |
PDC Activation finished with error code [%1], Initialization Count is [%2], and Reason is [%3] for the %4. |
0xB0000519 | PDC-deaktiveringen blev afsluttet med fejlkoden [%1], initialiseringsantallet er [%2], og årsagen er [%3] for %4. |
PDC Deactivation finished with error code [%1], Initialization Count is [%2], and Reason is [%3] for the %4. |
0xB000051A | WNP-protokoltilstand for enheds-id %1 er tilstanden %2 for %3. |
WNP protocol state for Device Id %1 is State %2 for the %3. |
0xB000051B | WNP-forbindelsestilstand for forbindelses-id %1 er tilstanden %2 for %3. |
WNP Connector state for Connector Id %1 is State %2 for the %3. |
0xB000051C | WNP-transportlag for forbindelses-id %1 anmodede om NCSI-test for %2, men fik fejlkoden %3. |
WNP Transport Layer for Connector Id %1 requested NCSI probe for the %2 and got error code %3. |
0xB000051D | WNP-transportlag for Auth Manager anmodede om NCSI-test for %1, men fik fejlkode %2. |
WNP Transport Layer for Auth Manager requested NCSI probe for the %1 and got error code %2. |
0xB000051E | WNP-transportlaget for %1 registrerede den første fallback-grænsefladeændring. Gammelt indeks %2, gammel adressefamilie %3. Nyt indeks %4, ny adressefamilie %5, NDIS_PHYSICAL_MEDIUM %6. |
WNP Transport Layer for %1 detected first fallback interface change. Old index %2, old address family %3. New index %4, new address family %5, NDIS_PHYSICAL_MEDIUM %6. |
0xB000051F | WNP-transportlaget for %1 registrerede den anden fallback-grænsefladeændring. Gammelt indeks %2, gammel adressefamilie %3. Nyt indeks %4, ny adressefamilie %5, NDIS_PHYSICAL_MEDIUM %6. |
WNP Transport Layer for %1 detected second fallback interface change. Old index %2, old address family %3. New index %4, new address family %5, NDIS_PHYSICAL_MEDIUM %6. |
0xB0000520 | WNP-transportlaget registrerede et lavt niveau for WIFI-signalkvaliteten (værdi = %1) og udsender derfor en band keep alive-anmodning (PNG). |
WNP Transport Layer detected low WIFI signal quality level (value = %1); and hence sending out of band keep alive (PNG) request. |
0xB0000521 | WNP-transportlaget registrerede et markant fald i WIFI-signalkvaliteten (deltag = %1) og udsender derfor en band keep alive-anmodning (PNG). |
WNP Transport Layer detected a significant drop in WIFI signal quality (delta = %1); and hence sending out of band keep alive (PNG) request. |
0xB0000522 | WNP-transportlaget registrerede en ændring i tilgængeligheden af WIFI-grænsefladen (hændelse = %1) og udsender derfor en band keep alive-anmodning (PNG). |
WNP Transport Layer detected a change in WIFI interface availability (event %1); and hence sending out of band keep alive (PNG) request. |
0xB0000523 | WNP-transportlaget registrerede en ændring i forbindelsesstatussen for WIFI-grænsefladen (hændelse = %1) og udsender derfor en band keep alive-anmodning (PNG). |
WNP Transport Layer detected a change in WIFI interface connectivity status (event %1); and hence sending out of band keep alive (PNG) request. |
0xB00007D0 | Windows Push-beskedplatformen har modtaget en kanalanmodning med følgende parametre: %1 [PackageFullName] %2 [AppUserModelId]. |
The Windows Push Notification Platform has received a channel request with the following parameters: %1 [PackageFullName] %2 [AppUserModelId]. |
0xB00007D1 | Kanaltabellen har tilføjet en gyldig kanaltilknytning: %1 [ChannelId] %2 [AppUserModelId] %3 [ErrorCode]. |
The channel table has added a valid channel mapping: %1 [ChannelId] %2 [AppUserModelId] %3 [ErrorCode]. |
0xB00007D2 | Kanaltabellen har fjernet en kanaltilknytning: %1 [ChannelId] %2 [AppUserModelId] %3 [ErrorCode]. |
The channel table has removed a channel mapping: %1 [ChannelId] %2 [AppUserModelId] %3 [ErrorCode]. |
0xB00007D3 | Kanaltabellen har opdateret en kanaltilknytning: %1 [ChannelId] %2 [AppUserModelId] %3 [ErrorCode]. |
The channel table has updated a channel mapping: %1 [ChannelId] %2 [AppUserModelId] %3 [ErrorCode]. |
0xB00007D4 | Kanaltabellen har returneret en cachelagret kanaltilknytning: %1 [ChannelId] %2 [AppUserModelId] %3 [ErrorCode]. |
The channel table has returned a cached channel mapping: %1 [ChannelId] %2 [AppUserModelId] %3 [ErrorCode]. |
0xB00007D5 | Der blev tilføjet et tilbagekald for en skybesked: %1 [AppUserModelId]. |
A cloud notification callback was added: %1 [AppUserModelId]. |
0xB00007D6 | Der blev fjernet et tilbagekald for en skybesked: %1 [AppUserModelId]. |
A cloud notification callback was removed: %1 [AppUserModelId]. |
0xB00007D7 | En skybesked kunne ikke leveres til et tilbagekald på grund af en fejl: %1 [AppUserModelId] %2 [ErrorCode]. |
A cloud notification could not be delivered to a callback due to an error: %1 [AppUserModelId] %2 [ErrorCode]. |
0xB00007D8 | En skybesked blev leveret til et tilbagekald: %1 [AppUserModelId] %2 [NotificationType] %3 [NotificationTrackingId]. |
A cloud notification was delivered to a callback: %1 [AppUserModelId] %2 [NotificationType] %3 [NotificationTrackingId]. |
0xB00007D9 | En lokal meddelelse blev modtaget gennem et slutpunkt for et program: %1 [AppUserModelId] %2 [NotificationType] %3 [NotificationTrackingId] %4 [NotificationSource]. |
A local notification was received through an application endpoint: %1 [AppUserModelId] %2 [NotificationType] %3 [NotificationTrackingId] %4 [NotificationSource]. |
0xB00007DA | Der blev modtaget en meddelelse om at rydde et felt fra et slutpunkt for et program: %1 [AppUserModelId]. |
A clear tile message was received from an application endpoint: %1 [AppUserModelId]. |
0xB00007DB | Der blev modtaget en meddelelse om at rydde et badge fra et slutpunkt for et program: %1 [AppUserModelId]. |
A clear badge message was received from an application endpoint: %1 [AppUserModelId]. |
0xB00007DC | Der blev modtaget en meddelelse om at annullere toast fra et slutpunkt for et program: %1 [AppUserModelId] %2 [NotificationTrackingId]. |
A cancel toast message was received from an application endpoint: %1 [AppUserModelId] %2 [NotificationTrackingId]. |
0xB00007DD | Der blev modtaget en meddelelse om at rydde toast fra et slutpunkt for et program: %1 [AppUserModelId]. |
A clear toast message was received from an application endpoint: %1 [AppUserModelId]. |
0xB00007DE | Der blev modtaget en besked om at fjerne toast fra et programslutpunkt: %1 [AppUserModelId] for %2 [Tag] og %3 [Group]. |
A remove toast message was received from an application endpoint: %1 [AppUserModelId] for %2 [Tag] and %3 [Group]. |
0xB00007DF | En kanalanmodning blev ikke udført pga. fejl: %1 [AppUserModelId] %2 [ErrorCode]. |
A channel request failed due to an error: %1 [AppUserModelId] %2 [ErrorCode]. |
0xB00007E9 | Der blev tilføjet et toasttilbagekald: %1 [NotificationTrackingId]. |
A toast feedback callback was added: %1 [NotificationTrackingId]. |
0xB00007EA | Der blev fjernet et toasttilbagekald: %1 [NotificationTrackingId]. |
A toast feedback callback was removed: %1 [NotificationTrackingId]. |
0xB00007EB | Der blev aktiveret et toasttilbagekald: %1 [NotificationTrackingId]. |
A toast feedback callback was invoked: %1 [NotificationTrackingId]. |
0xB00007EC | Der blev tilføjet en planlagt toast: %1 [PackageFullName] %2 [AppUserModelId]. |
A scheduled toast was added: %1 [PackageFullName] %2 [AppUserModelId]. |
0xB00007ED | Der blev fjernet en planlagt toast: %1 [PackageFullName] %2 [AppUserModelId]. |
A scheduled toast was removed: %1 [PackageFullName] %2 [AppUserModelID]. |
0xB00007EE | En planlagt toast er ved at blive aktiveret: %1 [AppUserModelID] %2 [TimerId] %3 [Duetime]. |
A scheduled toast is about to be raised: %1 [AppUserModelID] %2 [TimerId] %3 [Duetime]. |
0xB00007EF | Der er tilføjet et baggrundsjob til applikationstilknytning: %1 [AppUserModelID] %2 [EventId]. |
A background task to application mapping has been added: %1 [AppUserModelID] %2 [EventId]. |
0xB00007F0 | Der er fjernet et baggrundsjob til applikationstilknytning: %1 [AppUserModelID] %2 [EventId]. |
A background task to application mapping has been removed: %1 [AppUserModelID] %2 [EventId]. |
0xB00007F1 | En råbesked har aktiveret et baggrundsjob: %1 [AppUserModelID] %2 [EventId] %3 [NotificationID]. |
A raw notification has activated a background task: %1 [AppUserModelID] %2 [EventId] %3 [NotificationID]. |
0xB00007F2 | En råbesked har aktiveret en systemopgave: %1 [AppUserModelID]. |
A raw notification has activated a system task: %1 [AppUserModelID]. |
0xB00007F3 | Et planlagt felt blev tilføjet: %1 [PackageFullName] %2 [AppUserModelId] %3 [Cookie]. |
A scheduled tile was added: %1 [PackageFullName] %2 [AppUserModelId] %3 [Cookie]. |
0xB00007F4 | Et planlagt felt blev fjernet: %1 [PackageFullName] %2 [AppUserModelId] %3 [Cookie]. |
A scheduled tile was removed: %1 [PackageFullName] %2 [AppUserModelId] %3 [Cookie]. |
0xB00007F5 | Et planlagt felt hæves: %1 [AppUserModelId] %2 [Cookie]. |
A scheduled tile is being raised: %1 [AppUserModelId] %2 [Cookie]. |
0xB00007F6 | Et planlagt felt blev fjernet, fordi antallet af planlagte felter pr. app overskred den maksimale køstørrelse: %1 [AppUserModelId] %2 [Cookie]. |
A scheduled tile was removed because the number of scheduled tiles per app exceeded maximum queue size: %1 [AppUserModelId] %2 [Cookie]. |
0xB00007F7 | En periodisk opdatering er indstillet: %1 [PackageFullName] %2 [AppUserModelId] %3 [Type]. |
A periodic update has been set: %1 [PackageFullName] %2 [AppUserModelId] %3 [Type]. |
0xB00007F8 | En periodisk opdatering er nulstillet: %1 [PackageFullName] %2 [AppUserModelId] %3 [Type]. |
A periodic update has been reset: %1 [PackageFullName] %2 [AppUserModelId] %3 [Type]. |
0xB00007F9 | En periodisk opdatering har startet polling af URL: %1 [AppUserModelId] %2 [Type]. |
A periodic update has started polling URL: %1 [AppUserModelId] %2 [Type]. |
0xB00007FA | En periodisk opdatering har afsluttet polling af URL: %1 [AppUserModelId] %2 [Type]. |
A periodic update has finished polling URL: %1 [AppUserModelId] %2 [Type]. |
0xB00007FB | En periodisk opdatering har afvist polling af URL, fordi størrelsen af meddelelsen overskred den maksimale størrelse: %1 [AppUserModelId] %2 [Type] %3 [URL]. |
A periodic update has rejected polling URL because size of notification exceeded maximum: %1 [AppUserModelId] %2 [Type] %3 [URL]. |
0xB00007FC | En periodisk opdatering har afvist polling af URL på grund af mobilbredbåndsforbindelsen, f.eks. roaming eller overskridelse af kvoten: %1 [AppUserModelId] %2 [Type]. |
A periodic update has rejected polling URL due to mobile broadband connection such as roaming or reaching quota : %1 [AppUserModelId] %2 [Type]. |
0xB00007FD | En periodisk opdatering kunne ikke foretage polling af URL. Se i fejlbeskrivelsen for at få flere oplysninger: %1 [AppUserModelId] %2 [Type] %3 [URL] %4 [Error]. |
A periodic update has failed polling URL. Please refer error description for detail: %1 [AppUserModelId] %2 [Type] %3 [URL] %4 [Error]. |
0xB00007FE | En tilknytningspost for et baggrundsopgaveprogram er blevet fjernet: %1 [AppUserModelID]. |
A background task application mapping entry has been removed: %1 [AppUserModelID]. |
0xB00007FF | Besked-API-kald til %1 [AppUserModelId] lykkedes ikke. Hvis du er logget på flere sessioner som den samme bruger, skal du logge af og bruge en enkelt brugersession. Hvis du bruger Visual Studio-fejlfindingssimulatoren, kan du løse problemet ved at afslutte simulatoren. |
Notification API call for %1 [AppUserModelId] failed. If you are logged into multiple sessions as the same user, please logoff and use a single user session. If you are using the Visual Studio debugging simulator, exit the simulator to resolve this error. |
0xB0000800 | En råbesked kunne ikke aktivere en baggrundsopgave: %1 [AppUserModelID] %2 [EventId] %3 [ErrorCode]. |
A raw notification has failed to activate a background task: %1 [AppUserModelID] %2 [EventId] %3 [ErrorCode]. |
0xB0000801 | En periodisk opdatering registrerede en HTTP-statuskode, der ikke var 200: %1 [AppUserModelId] %2 [Type] %3 [URL-adresse] %4 [HTTP-statuskode]. |
A periodic update has found HTTP Status Code rather than 200: %1 [AppUserModelId] %2 [Type] %3 [URL] %4 [HTTP Status Code]. |
0xB0000802 | En periodisk opdatering kunne ikke forespørge om URL-adressen, fordi X-WNS-TAG-headeren er ugyldig: %1 [AppUserModelId] %2 [Type] %3 [URL-adresse]. |
A periodic update has failed polling URL because X-WNS-TAG header is invalid: %1 [AppUserModelId] %2 [Type] %3 [URL]. |
0xB0000803 | En periodisk opdatering kunne ikke forespørge om URL-adressen, fordi X-WNS-EXPIRY-headeren er ugyldig: %1 [AppUserModelId] %2 [Type] %3 [URL-adresse]. |
A periodic update has failed polling URL because X-WNS-EXPIRY header is invalid: %1 [AppUserModelId] %2 [Type] %3 [URL]. |
0xB0000804 | En periodisk opdatering af typen %2 for AppUserModelId %1 på URL-adressen %3 blev sprunget over pga. indstillingerne. Fejlkode: %4 |
A periodic update of Type %2 for AppUserModelId %1 at URL %3 has been skipped due to settings. Error Code: %4 |
0xB0000805 | En periodisk opdatering kunne ikke foretage polling af URL. Det skyldes, at X-WNS-GROUP-headeren er ugyldig: %1 [AppUserModelId] %2 [Type] %3 [URL]. |
A periodic update has failed polling URL because X-WNS-GROUP header is invalid: %1 [AppUserModelId] %2 [Type] %3 [URL]. |
0xB0000834 | En skybesked gik tabt, fordi følgende kanal ikke er gyldig: %1 [ChannelId]. |
A cloud notification was dropped because the following channel is not valid: %1 [ChannelId]. |
0xB0000835 | En besked gik tabt, fordi udløbstidspunktet var passeret: %1 [NotificationTrackingId]. |
A notification was dropped because the expiration time was in the past: %1 [NotificationTrackingId]. |
0xB0000836 | En besked gik tabt på grund af de globale indstillinger: %1 [PolicyLevel] %2 [NotificationTrackingId] %3 [NotificationType]. |
A notification was dropped because of global settings: %1 [PolicyLevel] %2 [NotificationTrackingId] %3 [NotificationType]. |
0xB0000837 | En besked gik tabt, for skybeskeder er deaktiveret globalt: %1 [PolicyLevel] %2 [NotificationTrackingId]. |
A notification was dropped because cloud notifications are disabled globally: %1 [PolicyLevel] %2 [NotificationTrackingId]. |
0xB0000838 | En besked gik tabt på grund af programindstillingerne: %1 [AppUserModelId] %2 [NotificationTrackingId] %3 [NotificationType]. |
A notification was dropped because of application settings: %1 [AppUserModelId] %2 [NotificationTrackingId] %3 [NotificationType]. |
0xB0000839 | En besked gik tabt, da programmet ikke har netværksegenskab %1 [AppUserModelId] %2 [NotificationTrackingId]. |
A notification was dropped because the application does not have the network capability: %1 [AppUserModelId] %2 [NotificationTrackingId]. |
0xB000083A | En besked gik tabt, fordi programmet ikke har egenskaben til typen: %1 [AppUserModelId] %2 [NotificationTrackingId] %3 [NotificationType]. |
A notification was dropped because the application does not have the capability for the type: %1 [AppUserModelId] %2 [NotificationTrackingId] %3 [NotificationType]. |
0xB000083B | En besked gik tabt, fordi det aktuelle netværk er krævende: %1 [AppUserModelId] %2 [NotificationTrackingId] %3 [NotificationType]. |
A notification was dropped because the current network is costly: %1 [AppUserModelId] %2 [NotificationTrackingId] %3 [NotificationType]. |
0xB000083C | En besked gik tabt, fordi kapacitetsgrænsen for mobilbredbåndet blev nået: %1 [AppUserModelId] %2 [NotificationTrackingId] %3 [NotificationType]. |
A notification was dropped because the mobile broadband cap has been reached: %1 [AppUserModelId] %2 [NotificationTrackingId] %3 [NotificationType]. |
0xB000083D | Netværkstrafik, der har relation til beskeder, tillægges følgende AppUserModelId: %1. %2 [NotificationType] %3 [Size] %4 [NetworkType]. |
Network traffic related to notifications was attributed to the following AppUserModelId: %1. %2 [NotificationType] %3 [Size] %4 [NetworkType]. |
0xB000083E | En besked gik tabt, fordi beskeder er deaktiveret for programmet: %1 [AppUserModelId] %2 [NotificationTrackingId] %3 [NotificationType]. |
A notification was dropped because cloud notifications are disabled for the application: %1 [AppUserModelId] %2 [NotificationTrackingId] %3 [NotificationType]. |
0xB000083F | En besked gik tabt, fordi programmet ikke er registreret: %1 [AppUserModelId] %2 [NotificationType] |
A notification was dropped because the application is not registered: %1 [AppUserModelId] %2 [NotificationType] |
0xB0000840 | En %3-besked med sporings-id %2 bliver sendt for programmet %1 med tilsidesættelse af indstillinger. |
A %3 notification with trackingid %2 is getting posted for the application %1 with setting override. |
0xB0000866 | En programindstilling blev ændret: %1 [AppUserModelId] %2 [SettingType] %3 [Enabled]. |
An application setting was changed: %1 [AppUserModelId] %2 [SettingType] %3 [Enabled]. |
0xB0000867 | En indstilling for gruppepolitik blev ændret. Forbindelse til beskedtjeneste blev opdateret: %1 [Enabled]. |
A group policy setting was changed. Notification Service connection was updated: %1 [Enabled]. |
0xB0000868 | Der blev forespurgt på en programindstilling: %1 [AppUserModelId] %2 [SettingType] %3 [Enabled]. |
An application setting was queried: %1 [AppUserModelId] %2 [SettingType] %3 [Enabled]. |
0xB0000869 | En global indstilling blev ændret: %1 [SettingType] %2 [Enabled] %3 [PolicyLevel]. |
A global setting was changed: %1 [SettingType] %2 [Enabled] %3 [PolicyLevel]. |
0xB000086A | Der blev forespurgt på en global indstilling blev ændret: %1 [SettingType] %2 [Enabled] %3 [PolicyLevel]. |
A global setting was queried: %1 [SettingType] %2 [Enabled] %3 [PolicyLevel]. |
0xB000086B | Der blev anmodet om listen over programmer med egenskaben: %1 [SettingType]. |
The list of apps with capability: %1 [SettingType] was requested. |
0xB000086C | Der blev registreret tilbagekald for %1 [SettingType] med cookien %2 [Cookie Value]. |
Callback registered for %1 [SettingType] with Cookie %2 [Cookie Value]. |
0xB000086D | Registrering af tilbagekald blev fjernet: %1 [Cookie Value]. |
Callback unregistered : %1 [Cookie Value]. |
0xB000086E | Afslutning på rydning af feltbeskedkøer og billedcache. |
End of clearing Tile Notification Queues and Image Cache. |
0xB000086F | Der blev forespurgt på feltkapacitet for mobilbredbånd: %1 [Cap Value (Bytes)]. |
Mobile Broadband Tile Cap Queried: %1 [Cap Value (Bytes)]. |
0xB0000870 | Feltkapacitet for mobilbredbånd blev ændret: %1 [Cap Value (Bytes)]. |
Mobile Broadband Tile Cap Changed: %1 [Cap Value (Bytes)]. |
0xB0000871 | Der blev forespurgt på feltanvendelse for mobilbredbånd: %1 [Usage Value (Bytes)]. |
Mobile Broadband Tile Usage Queried: %1 [Usage Value (Bytes)]. |
0xB0000872 | Der blev forespurgt på nulstillingsdatoer for mobilbredbånd. |
Mobile Broadband Reset Dates Queried. |
0xB0000873 | Der blev anmodet om listen over programmer med egenskaben: %1 [SettingType] i pakken: %2 [PackageFamilyName]. |
The list of apps with capability: %1 [SettingType] in Package: %2 [PackageFamilyName] was requested. |
0xB0000874 | Start på rydning af feltbeskedkøer og billedcache. |
Start of clearing Tile Notification Queues and Image Cache. |
0xB0000875 | Tilbagekald om forøgelse af kapacitet for mobilbredbånd blev aktiveret: %1 [Enabled]. |
Mobile Broadband Cap Enforcement Callback invoked: %1 [Enabled]. |
0xB0000876 | Toasts er midlertidigt suspenderet indtil %1 [UTC FILETIME]. |
Toasts have been Temporarily Suspended until %1 [UTC FILETIME]. |
0xB0000877 | Der blev sendt en forespørgsel om tiden for midlertidig suspendering af toast: Er den suspenderet? %2 opvækningstid? %1 [UTC FILETIME]. |
Toast Temporary Suspend Time was queried: Is Suspended? %2 wakeupTime? %1 [UTC FILETIME]. |
0xB0000878 | Opvågningstimeren for toast blev aktiveret. |
Toast Wakeup Timer has fired. |
0xB0000879 | Der blev anmodet om listen over forespørgselsapps i pakken: %1 [PackageFamilyName]. |
The list of Polling apps in Package: %1 [PackageFamilyName] was requested. |
0xB000087A | Der var planlagt en indstillingssynkronisering: %1 [PackageFamilyName] %2 [Samlings-id]. |
A Setting Sync was scheduled: %1 [PackageFamilyName] %2 [Collection ID]. |
0xB000087B | Et kald til indstillingsslutpunktet fjernede blokeringen af alle kanaler for alle typer. |
A call to the settings endpoint happened to unblock all channels for all types. |
0xB0000898 | En kanalanmodning blev ikke tilladt på grund af globale indstillinger: %1 [PolicyLevel] %2 [AppUserModelId]. |
A channel request was not allowed because of global settings: %1 [PolicyLevel] %2 [AppUserModelId]. |
0xB0000899 | En kanalanmodning blev ikke tilladt, da programmet ikke har netværksegenskaben: %1 [AppUserModelId]. |
A channel request was not allowed because the application does not have the network capability: %1 [AppUserModelId]. |
0xB000089A | En %2-besked med NotificationTrackingId %1 gik tabt, fordi den ikke har den relevante rettighed. Kontrollér, at Mosh Debugger kører på computeren. |
A %2 notification with NotificationTrackingId %1 was dropped because appropriate privilege is not held. Please check out Mosh Debugger is running on your machine. |
0xB000089B | Der sendes en %3-besked med NotificationTrackingId %2 til programmet %1. |
A %3 notification with NotificationTrackingId %2 is being delivered to application %1. |
0xB00008CA | De beskedkanaler, der er knyttet til en pakke, kan ikke modtage råbeskeder: [PackageFullName] %1 |
Notification channels associated with a package are able to receive raw notifications: [PackageFullName] %1 |
0xB00008FC | Følgende program blev føjet til låseskærmen: %1 [PackageFullName] %2 [PackageRelativeApplicationId]. |
The following application was added to the lock screen: %1 [PackageFullName] %2 [PackageRelativeApplicationId]. |
0xB00008FD | Følgende program blev fjernet fra låseskærmen: %1 [PackageFullName] %2 [PackageRelativeApplicationId]. |
The following application was removed from the lock screen: %1 [PackageFullName] %2 [PackageRelativeApplicationId]. |
0xB0000960 | Systemprogrammet blev registreret med følgende parametre: %1 [PackageFullName] %2 [AppUserModelId] %3 [Indstillinger] %5 [WNFEventName]. |
System application was registered with the following paramaeters: %1 [PackageFullName] %2 [AppUserModelId] %3 [Settings] %5 [WNFEventName]. |
0xB0000961 | Registreringen af systemprogrammet blev fjernet med følgende parametre: %1 [AppUserModelId] |
System application was unregistered with the following parameters: %1 [AppUserModelId] |
0xB0000964 | VoIP-telefonprogram blev registreret med følgende parametre: %1 [AppUserModelId] %2 [PhoneVoipAgentId]. |
Phone VoIP application was registered with the following parameters: %1 [AppUserModelId] %2 [PhoneVoipAgentId]. |
0xB0000965 | Registreringen af et VoIP-telefonprogram blev fjernet med følgende parametre: %1 [AppUserModelId]. |
Phone VoIP application was unregistered with the following parameters: %1 [AppUserModelId]. |
0xB0000966 | Platformen til Windows Push-beskeder har modtaget en PhoneLegacy-kanalanmodning med følgende parametre: %1 [PackageFullName] %2 [AppUserModelId] %3 [ChannelName] %4 [ServiceName]. |
The Windows Push Notification Platform has received a phone legacy channel request with the following parameters: %1 [PackageFullName] %2 [AppUserModelId] %3 [ChannelName] %4 [ServiceName]. |
0xB0000967 | PhoneLegacy-pushbeskeder behandles: Kanal-id [%1], beskedtype [%2], sporings-id [%3], appid [%4] |
PhoneLegacy push notification is being processed: ChannelId [%1], NotificationType [%2], TrackingId [%3] AppId [%4] |
0xB0000968 | PhoneLegacy VoIP-beskeder behandles: Kanal-id [%1], beskedtype [%2], sporings-id [%3], appid [%4], PhoneVoip-agent-id [%5] |
PhoneLegacy voip notification is being processed: ChannelId [%1], NotificationType [%2], TrackingId [%3] AppId [%4], PhoneVoipAgentId [%5] |
0xB0000969 | Der blev tilføjet et tilbagekald for forbindelsstatussen: %1 [AppUserModelId]. |
A connection status callback was added: %1 [AppUserModelId]. |
0xB000096A | Et tilbagekald for forbindelsesstatussen blev fjernet: %1 [AppUserModelId]. |
A connection status callback was removed: %1 [AppUserModelId]. |
0xB000096B | Et tilbagekald for forbindelsesstatussen blev opdateret: %1 [AppUserModelId]. |
A connection status callback was updated: %1 [AppUserModelId]. |
0xB000096C | Der blev leveret en forbindelsesstatus til et tilbagekald: %1 [AppUserModelId] %2 [IsConnected] %3 [ErrorCode]. |
A connection status was delivered to a callback: %1 [AppUserModelId] %2 [IsConnected] %3 [ErrorCode]. |
0xB000096D | Et program blev registreret med følgende parametre: %1 [PackageFullName] %2 [AppUserModelId] %3 [Settings] %4 [AppType] %5 [ErrorCode]. |
An application was registered with the following parameters: %1 [PackageFullName] %2 [AppUserModelId] %3 [Settings] %4 [AppType] %5 [ErrorCode]. |
0xB000096E | En programregistrering blev opdateret med følgende parametre: %1 [PackageFullName] %2 [AppUserModelId] %3 [Settings] %4 [AppType] %5 [ErrorCode]. |
An application resgistration was updated with the following parameters: %1 [PackageFullName] %2 [AppUserModelId] %3 [Settings] %4 [AppType] %5 [ErrorCode]. |
0xB000096F | Registreringen af et program blev fjernet med følgende parametre: %1 [AppUserModelId] %2 [ErrorCode] |
An application was unregistered with the following parameters: %1 [AppUserModelId] %2 [ErrorCode] |
0xB0000BB8 | Der blev anmodet om feltsessionsoprettelse for %2-slutpunktet %1. |
Tile session creation is requested for %2 endpoint %1. |
0xB0000BB9 | Feltsessionsoprettelsen er afsluttet for %4 fra slutpunktet %1 med resultatet %3, og %2 er tildelt som sessions-id. Køstillede afslutninger = %5, Køstillede oprydninger = %6 |
Tile session creation is finished for %4 from endpoint %1 with result %3, and %2 is assigned as session id. Queued Closes = %5, Queued Cleanups = %6 |
0xB0000BBA | Feltsessionen %1 opdateres. |
Tile session %1 is being updated. |
0xB0000BBB | Feltsessionen %1 opdateres med fejlkoden %3. |
Tile session %1 is updated with error code %3. |
0xB0000BBC | Feltsessionen %1 lukkes |
Tile session %1 is being closed |
0xB0000BBD | Feltsessionen %1 lukkes med fejlkoden %2. |
Tile session %1 is closed with error code %2. |
0xB0000BBE | Oprettelse af toastsession er anmodet for %2 fra slutpunktet %1. |
Toast session creation is requested for %2 from endpoint %1. |
0xB0000BBF | Oprettelse af toastsession er afsluttet for %4 fra slutpunktet %1 med resultatet %3, og %2 er tildelt som sessions-id. |
Toast session creation is finished for %4 from endpoint %1 with result %3, and %2 is assigned as session id. |
0xB0000BC0 | Toastsessionen %1 afbrydes |
Toast session %1 is being closed |
0xB0000BC1 | Toastsessionen %1 er afbrudt med fejlkode %2. |
Toast session %1 is closed with error code %2. |
0xB0000BC2 | Startede sporing af ydeevnen for beskedanmodning. |
Started tracking Notification Request performance. |
0xB0000BC3 | Afsluttede sporing af ydeevnen for beskedanmodning. |
Finished tracking Notification Request performance. |
0xB0000BC4 | Toast med beskedsporings-id'et %1 er leveret til %2 i sessionen %3. |
Toast with notification tracking id %1 is delivered to %2 on session %3. |
0xB0000BC5 | %1 med sporings-id'et %2 er leveret til %3. |
%1 with notification tracking id %2 is delivered to %3. |
0xB0000BC6 | Der blev oprettet en feltforespørgselspost for %1. |
Tile queue entry is created for %1. |
0xB0000BC7 | Feltbesked-id'et %2 for %1 er lagret ved %3 i køen. |
Tile notification id %2 for %1 is stored at %3 in queue. |
0xB0000BC8 | Feltbesked-id'et %2 tilsidesatte det eksisterende besked-id %1. |
Tile notification id %2 overrided existing notification id %1. |
0xB0000BC9 | Dette er en detaljeret fejlfindingshændelse, der sletter oplysninger om feltforespørgsel. |
This is a verbose debug event that dumps Tile Queue information. |
0xB0000BCA | Badgebesked-id'et %2 er lagret for %1. |
Badge notification id %2 is stored for %1. |
0xB0000BCB | Feltbilledanmodningen %1 blev startet. |
Tile image request %1 has started. |
0xB0000BCC | Feltbilledanmodningen %1 blev annulleret på grund af en ny anmodning. |
Tile image request %1 has been canceled due to new request. |
0xB0000BCD | Feltbilledanmodningen for beskeden %3 i %2 indeholder URL-adressen %4. |
Tile image request for notification %3 in %2 contains %4 URL. |
0xB0000BCE | Anmodning om hentning af afbildning behandles første gang: ressource-id [%1], URL-adresse [%2] |
Image download request is being processed for first time: resource id [%1], URL [%2] |
0xB0000BCF | Hentning af afbildning er fuldført for en enkelt URL-adresse: besked-id [%1], ressource-id [%2], lokal sti [%3], fejlkode [%4], flag [%5] |
Image download is complete for a single URL: notification id [%1], resource id [%2], local path [%3], error code [%4], flags [%5] |
0xB0000BD0 | Hentning af afbildning er fuldført for alle URL-adresser med besked-id'et [%1] |
Image download is complete for all URL with notification id [%1] |
0xB0000BD1 | Behandler første batch på afbildningsanmodning for toast: AppUserModelId [%1], besked-id [%2], antal URL-adresser [%3], flag [%4] |
Processing initial batch on Image request for toast: AppUserModelId [%1], Notification Id [%2], UrlCount [%3], Flags [%4] |
0xB0000BD2 | Behandler URL-adresse til anmodning om afbildning for toast: ressource-id [%1], URL-adresse [%2] |
Processing Toast Image request URL: Resource Id [%1], URL [%2] |
0xB0000BD3 | Planlægger opgave til hentning af afbildning: [slotindeks] %1, [besked-id] %2, [prioritet] %3, [IsTile] %4, [URL-adresse] %5 |
Scheduling Image Download Task: [Slot Index] %1, [Notification Id] %2, [Priority] %3, [IsTile] %4, [URL] %5 |
0xB0000BD4 | Opgave til hentning af afbildning er fuldført: [besked-id] %1, [IsTile] %2, [sti] %3 |
Completed Image Download Task: [Notification Id] %1, [IsTile] %2, [Path] %3 |
0xB0000BD5 | Det lykkedes ikke at hente afbildning: [besked-id] %1 [felt] %2 [ErrorCode] %3 [URL-adresse] %4 |
Download image has failed: [Notification Id] %1 [Tile] %2 [ErrorCode] %3 [URL] %4 |
0xB0000BD6 | Billedressourcen behandles. |
Image resource is being processed. |
0xB0000BD7 | Billedressourcen er blevet behandlet. |
Image resource has been processed. |
0xB0000BD8 | Rydning af alle feltbeskeder behandles. |
Clearing all tile notifiction is being processed. |
0xB0000BD9 | Rydning af alle feltbeskeder er blevet behandlet. |
Clearing all tile notifiction has been processed. |
0xB0000BDA | Rydning af alle billeder behandles. |
Clearing all images is being processed. |
0xB0000BDB | Rydning af alle billeder er blevet behandlet. |
Clearing all images has been processed. |
0xB0000BDC | Politik for billedfilhentning er ændret til %1. |
Image Download Manager policy is changed to %1. |
0xB0000BDD | Opdatering af detaljehændelse for feltsession %1. |
Detail event for tile session %1 update. |
0xB0000BDE | Detaljehændelse ved start af sporing af ydeevne for beskedanmodning. |
Detail event at start of Notification Request performance tracking. |
0xB0000BDF | Anmodning af stop af billedfilhentning på grund af modtagelse af nyere anmodning. |
Image Download Manager drop request due to newer request arrival. |
0xB0000BE0 | Billedet blev ikke hentet, fordi protokollen ikke understøttes: URL-adresse [%1] |
Downloading image has failed because protocol is not supported: URL [%1] |
0xB0000BE1 | Billedet blev ikke hentet, fordi det hentede billede er over maksimumstørrelsen på 150 KB: URL-adresse [%1] |
Downloading image has failed because downloaded image it too big over maximum 150KB: URL [%1] |
0xB0000BE2 | Billedet kunne ikke hentes, fordi det er tomt: URL-adresse [%1] |
Downloading image has failed because downloaded image is empty: URL [%1] |
0xB0000BE3 | Beskeden om nyt felt var en dublet af en tidligere besked: nyt besked-id [%1], tidligere besked-id [%2] |
The new tile notification was found to be a duplicate of a previous notification: new notification id [%1], previous notification id [%2] |
0xB0000BE4 | Beskeden om nyt badge var en dublet af en tidligere besked: nyt besked-id [%1], tidligere besked-id [%2] |
The new badge notification was found to be a duplicate of a previous notification: new notification id [%1], previous notification id [%2] |
0xB0000BE5 | Startede sporing af ydeevnen for anmodning om toastbesked. |
Started tracking Toast Notification Request performance. |
0xB0000BE6 | Afsluttede sporing af ydeevnen for anmodning om toastbesked. |
Finished tracking Toast Notification Request performance. |
0xB0000BE9 | Slutpunktet %1 ryddes op |
Endpoint %1 is being cleanedup |
0xB0000BEA | Toastbesked-id'et %2 for %1 er lagret ved %3 i køen. |
Toast notification id %2 for %1 is stored at %3 in queue. |
0xB0000BEB | Toastbesked-id'et %2 tilsidesatte det eksisterende besked-id %1. |
Toast notification id %2 overrided existing notification id %1. |
0xB0000BEE | Toast med beskedsporings-id'et %1 blev annulleret af %2 - oplyst session %3. |
Toast with notification tracking id %1 is canceled by %2 - informed session %3. |
0xB0000BEF | Nogle toastbeskeder er blevet ryddet - oplyst session %1. |
Some toast notifications have been cleared - informed session %1. |
0xB0000BF0 | %1 bliver ryddet for %2 - oplyst session %3. |
%1 are being cleared for %2 - informed session %3. |
0xB0000BF1 | Præsentationsslutpunktet modtog et kald om at lukke sessionen %1. |
Presentation Endpoint received a call to close session %1. |
0xB0000BF2 | Præsentationsslutpunktet afsluttede et kald for at lukke sessionen %1. |
Presentation Endpoint ended a call to close session %1. |
0xB0000C1C | Startede sporing af ydeevnen for rydning af toastbesked. |
Started tracking Clear Toast Notification performance. |
0xB0000C1D | Sporing af ydeevnen for rydning af toastbesked blev afsluttet. |
Finished tracking Clear Toast Notification performance. |
0xB0000C1E | Startede sporing af ydeevnen for rydning af toastbeskeder. |
Started tracking Clear Toast Notifications performance. |
0xB0000C1F | Sporing af ydeevnen for rydning af toastbeskeder blev afsluttet. |
Finished tracking Clear Toast Notifications performance. |
0xB0000C20 | Toasten med besked-id'et [%1] er udløbet og fjernes fra køen. |
Toast with notification id [%1] has expired and will be removed from the queue. |
0xB0000C21 | Startede sporing af ydelsen for fjernelse af toastbeskeder. |
Started tracking Remove Toast Notifications performance. |
0xB0000C22 | Afsluttede sporing af ydelsen for fjernelse af toastbeskeder. |
Finished tracking Remove Toast Notifications performance. |
0xB0000C23 | Pushbeskeder blev ikke behandlet: Kanal-id [%1], beskedtype [%2], sporings-id [%3], appid [%4], fejlkode [%5] |
Processing of push notification has failed: ChannelId [%1], NotificationType [%2], TrackingId [%3] AppId [%4], ErrorCode [%5] |
0xB0000C24 | Startede sporing af ydelsen for Ryd toastbeskedovergang. |
Started tracking Clear Toast Notification Rollover performance. |
0xB0000C25 | Afsluttede sporing af ydelsen for Ryd toastbeskedovergang. |
Finished tracking Clear Toast Notification Rollover performance. |
0xB0000C26 | Globale indstillinger for videresendelse af toastbesked: isFwToCdpEnabled = %1 isMirrorMasterSwitchEnabled = %2 MirroringDisabled = %3 |
Toast Notification Forwarding Global Settings: isFwToCdpEnabled = %1 isMirrorMasterSwitchEnabled = %2 MirroringDisabled = %3 |
0xB0000C27 | Start aktivitet for videresendelse af toastbesked |
Start Toast Notification Forwarding activity |
0xB0000C28 | Stop aktivitet for videresendelse af toastbesked |
Stop Toast Notification Forwarding activity |
0xB0000C29 | Lokale indstillinger for videresendelse af toastbesked: isDeveloperAppMirroringEnabled = %1 isMirrorMasterSwitchEnabled = %2 isGroupPolicyEnabled = %3 |
Toast Notification Forwarding Local Settings: isDeveloperAppMirroringEnabled = %1 isMirrorMasterSwitchEnabled = %2 isGroupPolicyEnabled = %3 |
0xB0000C2A | Start videresendelse af toastbesked. Videresend til AFC |
Start Toast Notification Forwarding Do Forward To AFC |
0xB0000C2B | Stop videresendelse af toastbesked. Videresend til AFC |
Stop Toast Notification Forwarding Do Forward To AFC |
0xB0000C2C | Start af videresendelse af toastbesked medfører aktivitet fra meddelelse |
Start Toast Notification Forwarding Make Activity from Notification |
0xB0000C2D | Stop af videresendelse af toastbesked medfører aktivitet fra meddelelse |
Stop Toast Notification Forwarding Make Activity from Notification |
0xB0000C2E | Videresendelse af toastbesked blev færdig med at udsmykke data |
Toast Notification Forwarding Finished Decorating Payload |
0xB0000C2F | Videresendelse af toastbesked blev færdig med at indlæse data for aktivitet |
Toast Notification Forwarding Finished Loading Payload onto Activity |
0xB0000C30 | Videresendelse af toastbesked blev færdig med at angive attributter for aktivitet |
Toast Notification Forwarding Finished setting attributes onto activity |
0xB0000C31 | Start løsning for aktiv ved videresendelse af toastbesked |
Start Toast Notification Forwarding Asset Resolution |
0xB0000C32 | Vellykket løsning for aktiv ved videresendelse af toastbesked |
Toast Notification Forwarding Asset Resolution Successful |
0xB0000C33 | Videresendelse af toastbesked medfører sporings-id for aktivitet = %1 AppUserModelId = %2 |
Toast Notification Forwarding Making Activity TrackingId = %1 AppUserModelId = %2 |
0xB0000C34 | Videresendelse af toastbesked har publiceret aktivitet med resultatet = %1 |
Toast Notification Forwarding Published Activity with Result = %1 |
0xB0000C35 | %1 |
%1 |
0xB0000C36 | Afvis synkronisering: Start afvisning af aktiviteter for app |
Sync Dismiss: Dismiss Activities for App Start |
0xB0000C37 | Afvis synkronisering: Stop afvisning af aktiviteter for app |
Sync Dismiss: Dismiss Activities for App Stop |
0xB0000C38 | Afvis synkronisering: Start afvisning af aktiviteter |
Sync Dismiss: Dismiss Activities Start |
0xB0000C39 | Afvis synkronisering: Stop afvisning af aktiviteter |
Sync Dismiss: Dismiss Activities Stop |
0xB0000C3C | Afvis synkronisering: Start fjernelse af besked ved hjælp af aktivitet |
Sync Dismiss: Remove Notification using Activity Start |
0xB0000C3D | Afvis synkronisering: Stop fjernelse af besked ved hjælp af aktivitet |
Sync Dismiss: Remove Notification using Activity Stop |
0xB0000C3E | Afvis synkronisering: Start hentning af aktiviteter |
Sync Dismiss: Get Activities Start |
0xB0000C3F | Afvis synkronisering: Stop hentning af aktiviteter |
Sync Dismiss: Get Activities Stop |
0xB0000C40 | Afvis synkronisering: Start CDPGetPlatformDeviceId |
Sync Dismiss: CDPGetPlatformDeviceId Start |
0xB0000C41 | Afvis synkronisering: Stop CDPGetPlatformDeviceId |
Sync Dismiss: CDPGetPlatformDeviceId Stop |
0xB0000C43 | Afvis synkronisering: Aktivitet fjernet med resultatet = %1 |
Sync Dismiss Removed Activity with Result = %1 |
0xB0000C44 | Afvis synkronisering: Besked fjernet med resultatet = %1 |
Sync Dismiss Removed Notification with Result = %1 |
0xB0000C45 | SyncDismissRemoveNotificationUsingActivityParams: MatchOnNotificationId = %1 Besked-id = %2 Aktivitets-id = %3 |
SyncDismissRemoveNotificationUsingActivityParams: MatchOnNotificationId = %1 NotificationId = %2 ActivityId = %3 |
0xB0000C46 | Afvis synkronisering: Aktivitet sammenlignet ved hjælp af besked! |
Sync Dismiss: Matched Activity using Notification! |
0xB0000C47 | Afvis synkronisering: Besked sammenlignet ved hjælp af aktivitet! |
Sync Dismiss: Matched Notification using Activity! |
0xB0000C48 | Modtaget WNF_CDP_CDPUSERSVC_READY |
Received WNF_CDP_CDPUSERSVC_READY |
0xB0002710 | DebugTrace: %1 |
DebugTrace: %1 |
0xD0000001 | Ukendt |
Unknown |
0xD0000002 | Modern(XAML,WWA,SL81) |
Modern(XAML,WWA,SL81) |
0xD0000003 | Desktop(Win32) |
Desktop(Win32) |
0xD0000004 | System |
System |
0xD0000005 | PhoneLegacy(SL80,SPLASH) |
PhoneLegacy(SL80,SPLASH) |
0xD0000006 | PdcNetwork |
PdcNetwork |
0xD0000007 | PdcSystem |
PdcSystem |
0xD0000008 | PdcTimer |
PdcTimer |
0xD000000A | AppEndpointPostNotification |
AppEndpointPostNotification |
0xD000000B | NotificationAvailableWorkInvoke |
NotificationAvailableWorkInvoke |
0xD000000C | ConnectionManagerNotificationReceived |
ConnectionManagerNotificationReceived |
0xD000000D | DownloadTaskManagerLaunchJob |
DownloadTaskManagerLaunchJob |
0xD000000E | Forbindelsen er oprettet |
Connected |
0xD000000F | Godkendelsen mislykkedes |
Authentication Failed |
0xD0000010 | Forbindelsen blev ikke oprettet |
Connect Failed |
0xD0000011 | Forbindelsen er afbrudt |
Disconnected |
0xD0000012 | Uventet afbrydelse |
Unexpected Disconnect |
0xD0000013 | Godkendelse er ikke tilgængelig |
Authentication Unavailable |
0xD0000014 | Feltbesked |
Tile Notification |
0xD0000015 | Badgebesked |
Badge Notification |
0xD0000016 | Toastbesked |
Toast Notification |
0xD0000017 | Råbesked |
Raw Notification |
0xD0000018 | Handlingen Levér |
Deliver Action |
0xD0000019 | Handlingen Ryd alle |
Clear All Action |
0xD000001A | Handlingen Fjern |
Remove Action |
0xD000001B | Gruppepolitik |
Group Policy |
0xD000001C | Administrator |
Administrator |
0xD000001D | Bruger |
User |
0xD000001E | Batchkørsel er deaktiveret |
Batching Disabled |
0xD000001F | Batterisparetilstand |
Battery Save Mode |
0xD0000020 | Passiv tilstand |
Passive Mode |
0xD0000021 | Fra |
Off |
0xD0000022 | Til |
On |
0xD0000025 | Indstilling for felt |
Tile Setting |
0xD0000026 | Badgeindstilling |
Badge Setting |
0xD0000027 | Toastindstilling |
Toast Setting |
0xD0000028 | Lydindstilling |
Audio Setting |
0xD0000029 | Indstilling for felt på låseskærm |
Lock Screen Tile Setting |
0xD000002A | Badgeindstilling for låseskærm |
Lock Screen Badge Setting |
0xD000002B | Toastindstilling for låseskærm |
Lock Screen Toast Setting |
0xD000002C | Tickleindstilling |
Tickle Setting |
0xD000002D | Stop skyindstilling |
Stop Cloud Setting |
0xD000002E | Skyegenskab |
Cloud Capability |
0xD000002F | Feltegenskab |
Tile Capability |
0xD0000030 | Toastegenskab |
Toast Capability |
0xD0000031 | Internetegenskab |
Internet Capability |
0xD0000032 | Badgeegenskab |
Badge Capability |
0xD0000033 | Ringeegenskab |
Ringing Capability |
0xD0000034 | Tickleegenskab |
Tickle Capability |
0xD0000035 | Feltbilledanmodning |
Tile Image Request |
0xD0000036 | Toastbilledanmodning |
Toast Image Request |
0xD0000037 | Ikke begrænset |
Unrestricted |
0xD0000038 | Begrænset |
Restricted |
0xD0000039 | Standard for meddelelsesplatform |
Notification Platform Default |
0xD000003A | Angivet netværksprovider |
Network Provider Specified |
0xD000003B | Standard |
Default |
0xD000003C | Måling i gang |
Measurement In Progress |
0xD000003D | Konvergeret |
Converged |
0xD000003E | Testforbindelse |
Test Connection |
0xD000003F | Dataforbindelse |
Data Connection |
0xD0000040 | IPv4 |
IPv4 |
0xD0000041 | IPv6 |
IPv6 |
0xD0000042 | Vært |
Host |
0xD0000043 | Simulator |
Simulator |
0xD0000044 | Fuld |
Full |
0xD0000045 | Skrivebeskyttet |
ReadOnly |
0xD0000046 | Automatisk genoptagelse |
Automatic Resume |
0xD0000047 | Fortsæt i strømsvag tilstand |
Resume Low-Power |
0xD0000048 | Stop midlertidigt |
Suspend |
0xD0000049 | Strømstatus er ændret |
Power Status Changed |
0xD000004A | Strømindstilling er ændret |
Power Setting Changed |
0xD000004B | Lokal |
Local |
0xD000004C | Planlagt |
Scheduled |
0xD000004D | Polling |
Polling |
0xD000004E | Fjernforbundet |
Remote Connected |
0xD000004F | Fjernforbindelsen er afbrudt |
Remote Disconnected |
0xD0000050 | Sessionslogon |
Session Logon |
0xD0000051 | Sessionslogoff |
Session Logoff |
0xD0000052 | Sessionslås |
Session Lock |
0xD0000053 | Sessionsoplåsning |
Session Unlock |
0xD0000054 | Fjernstyring af session |
Session Remote Control |
0xD0000055 | Opret session |
Session Create |
0xD0000056 | Afslut session |
Session Terminate |
0xD0000057 | Billeddownload |
Image Download |