0x50000002 | 錯誤 |
Error |
0x50000004 | 資訊 |
Information |
0x90000001 | Microsoft-Windows-DeviceManagement-Pushrouter |
Microsoft-Windows-DeviceManagement-Pushrouter |
0xB0000064 | MDM PushRouter 服務: 無法建立 ConfigManager 鎖定服務繫結。結果: (%1)。 |
MDM PushRouter Service: Failed to create ConfigManager lock service binding. Result: (%1). |
0xB0000065 | MDM PushRouter 服務: 已順利建立「RPC 伺服器介面」群組。結果: (%1)。 |
MDM PushRouter Service: Successfully created RPC Server Interface group. Result: (%1). |
0xB0000066 | MDM PushRouter 服務: 無法建立「RPC 伺服器介面」群組。結果: (%1)。 |
MDM PushRouter Service: Failed to create RPC Server Interface group. Result: (%1). |
0xB0000067 | MDM PushRouter 服務: 無法啟用「RPC 伺服器介面」群組,因為有重複的端點存在。結果: (%1)。 |
MDM PushRouter Service: Failed to activate RPC Server Interface group because a duplicate end point exists. Result: (%1). |
0xB0000068 | MDM PushRouter 服務: 已順利啟用「RPC 伺服器介面」群組。結果: (%1)。 |
MDM PushRouter Service: Successfully activated RPC Server Interface group. Result: (%1). |
0xB0000069 | MDM PushRouter 服務: 無法啟用「RPC 伺服器介面」群組。結果: (%1)。 |
MDM PushRouter Service: Failed to activate RPC Server Interface group. Result: (%1). |
0xB000006A | MDM PushRouter 服務: 已順利停用「RPC 伺服器介面」群組。結果: (%1)。 |
MDM PushRouter Service: Successfully deactivated RPC Server Interface group. Result: (%1). |
0xB000006B | MDM PushRouter 服務: 無法停用「RPC 伺服器介面」群組。結果: (%1)。 |
MDM PushRouter Service: Failed to deactivate RPC Server Interface group. Result: (%1). |
0xB000006C | MDM PushRouter 服務: 已順利關閉「RPC 伺服器介面」群組。結果: (%1)。 |
MDM PushRouter Service: Successfully closed RPC Server Interface group. Result: (%1). |
0xB000006D | MDM PushRouter 服務: 無法關閉「RPC 伺服器介面」群組。結果: (%1)。 |
MDM PushRouter Service: Failed to close RPC Server Interface group. Result: (%1). |
0xB000006E | MDM PushRouter 服務: PushRouter RPC 介面閒置狀態已變更。群組是否閒置: (%1)。 |
MDM PushRouter Service: PushRouter RPC interface Idle status changed. Is group idle: (%1). |
0xB000006F | MDM PushRouter 服務: 剩餘的 PushRouter 用戶端數目: (%2)。作業: (%1)。 |
MDM PushRouter Service: Number of PushRouter clients remaining: (%2). Operation: (%1). |
0xB0000070 | MDM PushRouter 服務: 已處理所有用戶端。剩餘的 PushRouter 用戶端數目: (%1)。 |
MDM PushRouter Service: All clients handled. Number of PushRouter clients remaining: (%1). |
0xB0000071 | MDM PushRouter 服務: 已變換的作用中用戶端計數數目。剩餘的 PushRouter 用戶端數目: (%1)。 |
MDM PushRouter Service: Number of active client count rolled over. Number of PushRouter clients remaining: (%1). |
0xB0000072 | MDM PushRouter 服務: 發生 PushRouter RPC 耗盡。 |
MDM PushRouter Service: PushRouter RPC run down occured. |
0xB0000073 | MDM PushRouter 服務: PushRouter::Open 已由需要 PushRouter 控制代碼的用戶端呼叫。 |
MDM PushRouter Service: PushRouter::Open called by a client needing a handle to PushRouter. |
0xB0000074 | MDM PushRouter 服務: PushRouter::Open 由需要與 PushRouter 互動的用戶端呼叫成功。用戶端識別碼: (%1),內容類型: (%2):,App 識別碼: (%3),結果: (%4)。 |
MDM PushRouter Service: PushRouter::Open called by a client needing to interact with PushRouter succeeded. Client id: (%1), Content Type: (%2):, App Id: (%3), Result: (%4). |
0xB0000075 | MDM PushRouter 服務: PushRouter::Open 由需要與 PushRouter 互動的用戶端呼叫失敗。內容類型: (%1):,App 識別碼: (%2),結果: (%3)。 |
MDM PushRouter Service: PushRouter::Open called by a client needing to interact with PushRouter failed. Content Type: (%1):, App Id: (%2), Result: (%3). |
0xB0000076 | MDM PushRouter 服務: PushRouter 已從與 PushRouter 執行所在服務相同的服務提交訊息。訊息來源: (%1)。 |
MDM PushRouter Service: PushRouter was submitted a message from the same service PushRouter is running in. Message origin: (%1). |
0xB0000077 | MDM PushRouter 服務: PushRouter 已從與 PushRouter 執行所在服務相同的服務提交訊息。訊息提交成功。傳送者位址: (%1),內容類型: (%2),App 識別碼: (%3),結果: (%4)。 |
MDM PushRouter Service: PushRouter was submitted a message from the same service PushRouter is running in. Message submission succeeded. Sender Address: (%1), Content Type: (%2), App Id: (%3), Result: (%4). |
0xB0000078 | MDM PushRouter 服務: PushRouter 已從與 PushRouter 執行所在服務相同的服務提交訊息。訊息提交失敗。傳送者位址: (%1),內容類型: (%2),App 識別碼: (%3),結果: (%4)。 |
MDM PushRouter Service: PushRouter was submitted a message from the same service PushRouter is running in. Message submission failed. Sender Address: (%1):, Content Type: (%2),App Id: (%3), Result: (%4). |
0xB0000079 | MDM PushRouter 服務: PushRouter 已收到由 RPC 用戶端提交的訊息。訊息提交成功。訊息來源: (%1),結果: (%2)。 |
MDM PushRouter Service: PushRouter was submitted a message by a RPC client. Message submission succeeded. Message origin: (%1), Result: (%2). |
0xB000007A | MDM PushRouter 服務: RPC 用戶端已提交訊息給 PushRouter。訊息提交失敗。訊息來源: (%1),結果: (%2)。 |
MDM PushRouter Service: PushRouter was submitted a message by a RPC client. Message submission failed. Message origin: (%1), Result: (%2). |
0xB000007B | MDM PushRouter 服務: 已順利建立 PushRouter。結果: (%1)。 |
MDM PushRouter Service: PushRouter was created successfully. Result: (%1). |
0xB000007C | MDM PushRouter 服務: 無法建立 PushRouter。結果: (%1)。 |
MDM PushRouter Service: PushRouter could not be created successfully. Result: (%1). |
0xB000007D | MDM PushRouter 服務: 開啟「服務控制管理員」以變更 PushRouter 啟動類型失敗。結果: (%1)。 |
MDM PushRouter Service: Opening Service Control Manager to change PushRouter startup type failed. Result: (%1). |
0xB000007E | MDM PushRouter 服務: 開啟服務控制代碼以變更 PushRouter 啟動類型失敗。結果: (%1)。 |
MDM PushRouter Service: Opening service handle to change PushRouter startup type failed. Result: (%1). |
0xB000007F | MDM PushRouter 服務: 將 PushRouter 啟動類型變更為「自動啟動」失敗。結果: (%1)。 |
MDM PushRouter Service: Changing PushRouter start up type to auto start failed. Result: (%1). |
0xB0000080 | MDM PushRouter 服務: 將 PushRouter 啟動類型變更為「延遲自動啟動」失敗。結果: (%1)。 |
MDM PushRouter Service: Changing PushRouter start up type to delayed auto start failed. Result: (%1). |
0xB0000081 | MDM PushRouter 服務: PushRouter 關閉已由與其互動的用戶端成功呼叫。用戶端識別碼: (%1),結果: (%2)。 |
MDM PushRouter Service: PushRouter close called by a client interacting with it succeeded. Client id: (%1), Result: (%2). |
0xB0000082 | MDM PushRouter 服務: PushRouter 關閉由與其互動的用戶端呼叫失敗。用戶端識別碼: (%1),結果: (%2)。 |
MDM PushRouter Service: PushRouter close called by a client interacting with it failed. Client id: (%1), Result: (%2). |
0xB0000083 | MDM PushRouter 服務: 用戶端已起始從 PushRouter 取得訊息的作業。 |
MDM PushRouter Service: A client initiated a get message operation from PushRouter. |
0xB0000084 | MDM PushRouter 服務: 用戶端已順利從 PushRouter 取得訊息。內容類型: (%1),App 識別碼: (%2),來源位址: (%3),用戶端識別碼: (%4)。安全性帳戶: (%5),訊息來源: (%6),結果: (%7)。 |
MDM PushRouter Service: A client was able to successfully get a message from PushRouter. Content Type: (%1), App Id: (%2), Source Address: (%3), Client ID: (%4), Security Account: (%5), Message origin: (%6), Result: (%7). |
0xB0000085 | MDM PushRouter 服務: 用戶端無法從 PushRouter 取得訊息。內容類型: (%1),App 識別碼: (%2),來源位址: (%3),用戶端識別碼: (%4),訊息來源: (%5),結果: (%6)。 |
MDM PushRouter Service: A client failed to get a message from PushRouter. Content Type: (%1), App Id: (%2), Source Address: (%3), Client ID: (%4), Message origin: (%5), Result: (%6). |
0xB0000086 | MDM PushRouter 服務: PushRouter 已具現化。 |
MDM PushRouter Service: PushRouter was instantiated. |
0xB0000087 | MDM 訊息持續性: 發現持續性訊息。位置: (%1)。 |
MDM Message Persistence: Persisted message found. Location: (%1). |
0xB0000088 | MDM 訊息持續性: 無法載入持續性訊息檔案。位置: (%1),結果: (%2)。 |
MDM Message Persistence: Failed to load persisted message file. Location: (%1), Result: (%2). |
0xB0000089 | MDM 訊息持續性: 找到持續性訊息的佇列識別碼。位置: (%1),佇列識別碼: (%2)。 |
MDM Message Persistence: Queue Id found for persisted message. Location: (%1), Queue Id: (%2). |
0xB000008A | MDM 訊息持續性: 針對持續性訊息找不到佇列識別碼的用戶端。位置: (%1),佇列識別碼: (%2),結果: (%3)。 |
MDM Message Persistence: No client found for queue Id for persisted message. Location: (%1), Queue Id: (%2), Result: (%3). |
0xB000008B | MDM 訊息持續性: 針對持續性訊息找到佇列識別碼的用戶端。位置: (%1),佇列識別碼: (%2),結果: (%3)。 |
MDM Message Persistence: Client found for queue Id for persisted message. Location: (%1), Queue Id: (%2), Result: (%3). |
0xB000008C | MDM 訊息持續性: 用戶端無法針對持續性訊息的佇列識別碼啟動。位置: (%1),用戶端: (%2),佇列識別碼: (%3),結果: (%4)。 |
MDM Message Persistence: Client failed to launch for queue Id for persisted message. Location: (%1), Client: (%2), Queue Id: (%3), Result: (%4). |
0xB000008D | MDM 訊息持續性: 發現非持續性訊息。位置: (%1)。 |
MDM Message Persistence: No persisted message found.Location: (%1). |
0xB000008E | MDM 訊息持續性: 無法刪除訊息檔案。佇列名稱: (%1),結果: (%2)。 |
MDM Message Persistence: Failed to delete messages file. Queue name: (%1), Result: (%2). |
0xB000008F | MDM 訊息持續性: 無法處理持續性訊息。結果: (%1)。 |
MDM Message Persistence: Failed to process persisted messages. Result: (%1). |
0xB0000090 | MDM 訊息持續性: 已順利處理持續性訊息。結果: (%1)。 |
MDM Message Persistence: Successfully processed persisted messages. Result: (%1). |
0xB0000091 | MDM PushRouter 服務: PushRouter 已開始路由傳送訊息。 |
MDM PushRouter Service: PushRouter started routing a message. |
0xB0000092 | MDM PushRouter 服務: 路由傳送訊息失敗。內容: (%1),應用程式: (%2),傳送者: (%3),用戶端: (%4),佇列識別碼: (%5),結果: (%6)。 |
MDM PushRouter Service: Routing a message failed. Content: (%1), Application: (%2), Sender: (%3), Client: (%4), Queue Id: (%5), Result: (%6). |
0xB0000093 | MDM PushRouter 服務: 已順利路由傳送訊息。內容: (%1),應用程式: (%2),傳送者: (%3),用戶端: (%4),佇列識別碼: (%5),結果: (%6)。 |
MDM PushRouter Service: Message routed successfully. Content: (%1), Application: (%2), Sender: (%3), Client: (%4), Queue Id: (%5), Result: (%6). |
0xB0000094 | MDM PushRouter 服務: PushRouter 已開始路由傳送新訊息。 |
MDM PushRouter Service: PushRouter started routing a new message. |
0xB0000095 | MDM PushRouter 服務: 無法路由傳送新訊息。結果: (%1)。 |
MDM PushRouter Service: Failed to route a new message. Result: (%1). |
0xB0000096 | MDM PushRouter 服務: 已順利路由傳送新訊息。結果: (%1)。 |
MDM PushRouter Service: Successfully routed a new message. Result: (%1). |
0xB0000097 | MDM 訊息持續性: 無法載入未驗證的訊息檔案。佇列名稱: (%1),結果: (%2)。 |
MDM Message Persistence: Failed to load unauthenticated messages file.Queue name: (%1), Result: (%2). |
0xB0000098 | MDM PushRouter 驗證: 已載入驗證提供者。名稱: (%1)。 |
MDM PushRouter Authentication: Loaded an authentication provider. Name: (%1). |
0xB0000099 | MDM PushRouter 驗證: 取得驗證提供者失敗。名稱: (%1),結果: (%2)。 |
MDM PushRouter Authentication: Getting authentication provider failed. Name: (%1), Result: (%2). |
0xB000009A | MDM PushRouter 驗證: 已載入的驗證提供者無法驗證訊息。名稱: (%1),結果: (%2)。 |
MDM PushRouter Authentication: Loaded authentication provider failed to authenticate message. Name: (%1), Result: (%2). |
0xB000009B | MDM PushRouter 驗證: 已順利驗證訊息。名稱: (%1),安全性帳戶名稱: (%2),訊息標頭: (%3),傳送者位址: (%4),角色: (%5),結果: (%6)。 |
MDM PushRouter Authentication: Message authenticated successfully. Name: (%1), Security account name: (%2), Message headers: (%3), Sender address: (%4), Role: (%5), Result: (%6). |
0xB000009C | MDM PushRouter 驗證: 無法驗證訊息。結果: (%1)。 |
MDM PushRouter Authentication: Message could not be authenticated. Result: (%1). |
0xB000009D | MDM PushRouter Proxy: 從 PushRouter 取得訊息的 RPC 呼叫失敗。結果: (%1)。 |
MDM PushRouter Proxy: RPC call to get a message from PushRouter failed. Result: (%1). |
0xB000009E | MDM PushRouter Proxy: 從 PushRouter 取得訊息的 RPC 呼叫成功。結果: (%1)。 |
MDM PushRouter Proxy: RPC call to get a message from PushRouter succeeded. Result: (%1). |
0xB000009F | MDM PushRouter Proxy: 從 PushRouter 提交訊息的 RPC 呼叫失敗。結果: (%1)。 |
MDM PushRouter Proxy: RPC call to submit a message from PushRouter failed. Result: (%1). |
0xB00000A0 | MDM PushRouter Proxy: 從 PushRouter 提交訊息的 RPC 呼叫成功。結果: (%1)。 |
MDM PushRouter Proxy: RPC call to submit a message from PushRouter succeeded. Result: (%1). |
0xB00000A1 | MDM PushRouter 驗證: 無法取得共用網路密碼,因為 ICCID 是 Null。 |
MDM PushRouter Authentication: Failed to get network shared secret because ICCID is null. |
0xB00000A2 | MDM PushRouter 驗證: WAP 驗證成功。安全性參數: (%1),已指派的安全性角色: (%2),結果: (%3)。 |
MDM PushRouter Authentication: WAP Verification succeeded. Security param: (%1), Security role assigned: (%2), Result: (%3). |
0xB00000A3 | MDM PushRouter 驗證: WAP 驗證失敗。安全性參數: (%1),已指派的安全性角色: (%2),結果: (%3)。 |
MDM PushRouter Authentication: WAP Verification failed. Security param: (%1), Security role assigned: (%2), Result: (%3). |
0xB00000A4 | MDM PushRouter 驗證: WAP 驗證失敗。安全性參數: (%1),原則值: (%2),已指派的安全性角色: (%3),結果: (%4)。 |
MDM PushRouter Authentication: WAP Authentication failed. Security param: (%1), Policy Value: (%2), Security role assigned: (%3), Result: (%4). |
0xB00000A5 | MDM PushRouter 驗證: WAP 驗證成功。安全性參數: (%1),原則值: (%2),已指派的安全性角色: (%3),結果: (%4)。 |
MDM PushRouter Authentication: WAP Authentication succeeded. Security param: (%1), Policy Value: (%2), Security role assigned: (%3), Result: (%4). |
0xB00000A6 | MDM PushRouter 驗證: SyncMl 驗證失敗。標頭: (%1),訊息本文大小: (%2),結果: (%3)。 |
MDM PushRouter Authentication: SyncMl Authentication failed. Headers: (%1), Message Body size: (%2), Result: (%3). |
0xB00000A7 | MDM PushRouter 驗證: SyncMl 驗證成功。標頭: (%1),訊息本文大小: (%2),結果: (%3)。 |
MDM PushRouter Authentication: SyncMl Authentication succeeded. Headers: (%1), Message Body size: (%2), Result: (%3). |
0xB00000A8 | MDM PushRouter 驗證: 從觸發程序取得 ServerID 失敗。結果: (%1)。 |
MDM PushRouter Authentication: Getting ServerID from the trigger failed. Result: (%1). |
0xB00000A9 | MDM PushRouter 驗證: 從觸發程序取得 ServerID 成功。結果: (%1)。 |
MDM PushRouter Authentication: Getting ServerID from the trigger succeeded. Result: (%1). |
0xB00000AA | MDM PushRouter 驗證: 驗證觸發程序失敗。結果: (%1)。 |
MDM PushRouter Authentication: Validating trigger failed. Result: (%1). |
0xB00000AB | MDM PushRouter 驗證: 驗證觸發程序成功。結果: (%1)。 |
MDM PushRouter Authentication: Validating trigger succeeded. Result: (%1). |
0xB00000AC | MDM PushRouter 驗證: 驗證 nonce 失敗。nonce 類型: (%1),結果: (%2)。 |
MDM PushRouter Authentication: Validating nonce failed. Type of nonce: (%1), Result: (%2). |
0xB00000AD | MDM PushRouter 驗證: 驗證 nonce 成功。nonce 類型: (%1),結果: (%2)。 |
MDM PushRouter Authentication: Validating nonce succeeded. Type of nonce: (%1), Result: (%2). |
0xB00000AE | MDM PushRouter 驗證: 使用預設 nonce 重新同步已設定為 False。 |
MDM PushRouter Authentication: Using default nonce resync is set to false. |
0xB00000AF | MDM PushRouter 驗證: 找不到預設 nonce。 |
MDM PushRouter Authentication: Default nonce not found. |
0xB00000B0 | MDM PushRouter: 正在將 dmwappushservice 啟動類型變更為「手動啟動」。結果: (%1)。 |
MDM PushRouter: Changing dmwappushservice startup type to demand started. Result: (%1). |
0xB00000B1 | MDM PushRouter: 將 dmwappushservice 啟動類型變更為「手動器動」失敗。結果: (%1)。 |
MDM PushRouter: Changing dmwappushservice startup type to demand started failed. Result: (%1). |
0xB000012C | MDM 原則通用公用程式: 原則查詢。原則識別碼: (%1),原則值: (%2),結果: (%3)。 |
MDM Common Utility for Policies: Policy query. Policy ID: (%1), Policy Value: (%2), Result: (%3). |
0xB000012D | MDM 原則通用公用程式: 原則設定。原則識別碼: (%1),原則值: (%2),結果: (%3)。 |
MDM Common Utility for Policies: Policy set. Policy ID: (%1), Policy Value: (%2), Result: (%3). |
0xB00001F4 | DmWapPushService: 無法擷取接收訊息所在位置上的 SIM 卡 ICCID。結果: (%1)。 |
DmWapPushService: Failed to retrieve ICCID of the SIM on which the message was received. Result: (%1). |
0xB00001F5 | DmWapPushService: 無法將 WAP 訊息複製為 PushRouter 可辨識的格式。ICCID: (%1),結果: (%2)。 |
DmWapPushService: Failed to copy WAP message into a format that PushRouter understands.ICCID: (%1), Result: (%2). |
0xB00001F6 | DmWapPushService: 已順利將 WAP 訊息複製為 PushRouter 可辨識的格式。ICCID: (%1),結果: (%2)。 |
DmWapPushService: Successfully copied WAP message into a format that PushRouter understands.ICCID: (%1), Result: (%2). |
0xB00001F7 | DmWapPushService: 無法擷取 WAP 訊息的本文。結果: (%1)。 |
DmWapPushService: Failed to retrieve body of WAP message. Result: (%1). |
0xB00001F8 | DmWapPushService: 已順利擷取 WAP 訊息的本文。結果: (%1)。 |
DmWapPushService: Successfully retrieved body of WAP message. Result: (%1). |
0xB00001F9 | DmWapPushService: 目前的 SECPOLICY_WSPNOTIFICATIONS 值是: (%1)。 |
DmWapPushService: The current value of SECPOLICY_WSPNOTIFICATIONS is: (%1). |
0xB00001FA | DmWapPushService: 無法針對 SMS 路由器接收的 WAP 訊息向 EventAggregator 註冊 WNF。結果: (%1)。 |
DmWapPushService: Failed to register WNF with EventAggregator for WAP messages received by SMS Router. Result: (%1). |
0xB00001FB | DmWapPushService: 已順利針對 SMS 路由器接收的 WAP 訊息向 EventAggregator 註冊 WNF。結果: (%1)。 |
DmWapPushService: Successfully registered WNF with EventAggregator for WAP messages received by SMS Router. Result: (%1). |
0xB00001FC | DmWapPushService: 已接收處理新 WAP 訊息的回呼。 |
DmWapPushService: Callback to handle a new WAP message received. |
0xB00001FD | DmWapPushService: 目前有擱置中的 RPC 用戶端。 |
DmWapPushService: There are pending RPC clients currently. |
0xB00001FE | DmWapPushService: 沒有剩餘的擱置中 RPC 用戶端。 |
DmWapPushService: No pending RPC clients remain. |
0xB00001FF | DmWapPushService: 正在設定計時器以在 (%1) 秒後檢查是否已處理所有要引發的 RPC 用戶端。 |
DmWapPushService: Setting the timer to check if all RPC clients are handled to fire after (%1) seconds. |
0xB0000200 | DmWapPushService: DmWapPushService 的閒置逾時目前已設定為 (%1) 秒。 |
DmWapPushService: Idle timeout of DmWapPushService is currently set to (%1) seconds. |
0xB0000201 | DmWapPushService: 已針對 DmWapPushService 初始化閒置 stop-start。 |
DmWapPushService: Initialized idle stop-start for DmWapPushService. |
0xB0000202 | DmWapPushService: 已更新服務狀態。目前的狀態: (%1),結束代碼: (%2),等候提示: (%3)。 |
DmWapPushService: Service status updated. Current state: (%1), Exit code: (%2), Wait hint: (%3). |
0xB0000203 | DmWapPushService: 無法初始化服務。結果: (%1)。 |
DmWapPushService: Failed to initialize service. Result: (%1). |
0xB0000204 | DmWapPushService: 已順利初始化服務。結果: (%1)。 |
DmWapPushService: Successfully initialized service. Result: (%1). |
0xB0000205 | DmWapPushService: 無法登錄服務的 RPC 介面。結果: (%1)。 |
DmWapPushService: Failed to register service's RPC interface. Result: (%1). |
0xB0000206 | DmWapPushService: 已順利登錄服務的 RPC 介面。結果: (%1)。 |
DmWapPushService: Successfully registered service's RPC interface. Result: (%1). |
0xB0000207 | DmWapPushService: 無法解除初始化服務。結果: (%1)。 |
DmWapPushService: Failed to uninitialize service. Result: (%1). |
0xB0000208 | DmWapPushService: 已順利解除初始化服務。結果: (%1)。 |
DmWapPushService: Successfully uninitialized service. Result: (%1). |
0xB0000209 | DmWapPushService: 無法解除登錄服務的 RPC 介面。結果: (%1)。 |
DmWapPushService: Failed to unregister service's RPC interface. Result: (%1). |
0xB000020A | DmWapPushService: 已順利解除初始化服務的 RPC 介面。結果: (%1)。 |
DmWapPushService: Successfully unregistered service's RPC interface. Result: (%1). |
0xB000020B | DmWapPushService: 已叫用服務處理常式。Opcode: (%1),目前的狀態: (%2)。 |
DmWapPushService: Service handler invoked. Opcode: (%1), Current state: (%2). |
0xB000020C | DmWapPushService: 正在初始化 DmWapPushService。 |
DmWapPushService: DmWapPushService is being initialized. |
0xB000020D | DmWapPushService: 停止已登錄的服務處理常式。狀態: (%1),結果: (%2)。 |
DmWapPushService: Stop Service handler registered. Status: (%1), Result: (%2). |