| 0x64 | 安全性套件未快取向伺服器驗證所需的認證。%n%n套件名稱:%t%1%n使用者名稱:%t%2%n網域名稱:%t%3%n伺服器名稱:%t%4%n受保護的使用者:%t%5%n錯誤碼:%t%6%n |
The security package does not cache the credentials needed to authenticate to the server.%n%nPackage Name:%t%1%nUser Name:%t%2%nDomain Name:%t%3%nServer Name:%t%4%nProtected User:%t%5%nError Code:%t%6%n |
| 0xC8 | 在登出完成之後，安全性套件收到網路登入要求。%n%n使用者名稱:%t%1%n網域名稱:%t%2%n登入識別碼 :%t%3%n登出時間:%t%4%nPID:%t%5%n程式:%t%6%n主體名稱:%t%7%n伺服器名稱:%t%8%n套件名稱:%t%9%n呼叫類型:%t%10%n錯誤碼:%t%11%n |
A security package received a network logon request after the logoff completed.%n%nUser Name:%t%1%nDomain Name:%t%2%nLogon ID:%t%3%nLogoff Time:%t%4%nPID:%t%5%nProgram:%t%6%nPrincipal Name:%t%7%nServer Name:%t%8%nPackage Name:%t%9%nCall Type:%t%10%nError Code:%t%11%n |
| 0x12C | 群組已指派給新登入。%n%n新登入:%n%t安全性識別碼:%t%t%1%n%t帳戶名稱:%t%t%2%n%t帳戶網域:%t%t%3%n%t登入識別碼:%t%t%4%n%t登入 GUID:%t%t%5%n%n事件序列:%t%t%6 / %7%n%n群組成員資格:%t%t%8 |
Groups assigned to a new logon.%n%nNew Logon:%n%tSecurity ID:%t%t%1%n%tAccount Name:%t%t%2%n%tAccount Domain:%t%t%3%n%tLogon ID:%t%t%4%n%tLogon GUID:%t%t%5%n%nEvent in sequence:%t%t%6 of %7%n%nGroup Membership:%t%t%8 |
| 0x12D | 宣告已指派給新登入。%n%n新登入:%n%t安全性識別碼:%t%t%1%n%t帳戶名稱:%t%t%2%n%t帳戶網域:%t%t%3%n%t登入識別碼:%t%t%4%n%t登入 GUID:%t%t%5%n%n%n%t登入類型:%t%t%6%n%n%n%n事件序列:%t%t%7 / %8%n%n使用者宣告:%t%t%9%n%n裝置宣告:%t%t%10%n%n當建立新登入工作階段且與該登入工作階段關聯的使用者權杖包含使用者和/或裝置宣告時，會產生此事件。[新登入] 欄位指出已登入的帳戶。若無法在單一事件中包含使用者權杖中的所有使用者與裝置宣告，將產生多個此類事件。[事件序列] 欄位指出針對此登入工作階段產生的其他事件數目。每個使用者或裝置宣告都是以下列格式呈現:%n%n%tClaimID ClaimTypeID : Value1, Value2 … %n%n常見宣告類型為: 0 (無效的類型)、1 (64 位元整數、2 (不帶正負號的 64 位元整數)、3 (字串)、4 (FQBN)、5 (SID)、6 (布林值) 與 16 (Blob)。若宣告值超過允許的長度上限，則字串結尾為 ... |
Claims assigned to a new logon.%n%nNew Logon:%n%tSecurity ID:%t%t%1%n%tAccount Name:%t%t%2%n%tAccount Domain:%t%t%3%n%tLogon ID:%t%t%4%n%tLogon GUID:%t%t%5%n%n%n%tLogon Type:%t%t%6%n%n%n%nEvent in sequence:%t%t%7 of %8%n%nUser Claims:%t%t%9%n%nDevice Claims:%t%t%10%n%nThis event is generated when a new logon session is created and the user token associated with it contains user and/or device claims. The New Logon fields indicate the account that was logged on. If all the user and device claims in the user token cannot be accommodated in a single event, multiple such events are generated. The Event in sequence field indicates how many more events are generated for this logon session. Each user or device claim is represented in the following format:%n%n%tClaimID ClaimTypeID : Value1, Value2 … %n%nThe common claim types are: 0 (Invalid Type), 1 (64-bit Integer, 2 (Unsigned 64-bit Integer), 3 (String), 4 (FQBN), 5 (SID), 6 (Boolean) and 16 (Blob). If the claim value exceeds the max allowed length then the string is terminated by ... |
| 0x12E | 已收到使用者 %1 登出通知。%n%nLogonId:%t%2%nAuthorityName:%t%3%nAccountName:%t%4%n逾時: %t%5 秒%n |
User %1 logged off notification is received.%n%nLogonId:%t%2%nAuthorityName:%t%3%nAccountName:%t%4%nTimeout:%t%5 seconds%n |
| 0x12F | 安全性套件未快取使用者的登入認證。%n%n套件名稱:%t%1%n使用者名稱:%t%2%n網域名稱:%t%3%n受保護的使用者:%t%4%n |
The security package does not cache the user's sign on credentials.%n%nPackage Name:%t%1%nUser Name:%t%2%nDomain Name:%t%3%nProtected User:%t%4%n |
| 0x140 | 自動重新啟動登入已順利設定下列帳戶的自動登入認證:%n%n%t帳戶名稱:%t%t%1%n%t帳戶網域:%t%t%2 |
Automatic restart sign on successfully configured the autologon credentials for:%n%n%tAccount Name:%t%t%1%n%tAccount Domain:%t%t%2 |
| 0x141 | 自動重新啟動登入無法設定自動登入認證，錯誤:%n%n%1 |
Automatic restart sign on failed to configure the autologon credentials with error:%n%n%1 |
| 0x142 | 自動重新啟動登入已從 LSA 記憶體中順利刪除自動登入認證 |
Automatic restart sign on successfully deleted autologon credentials from LSA memory |
| 0x1388 | 安全性封裝 %1 產生例外狀況。例外狀況資訊為資料。 |
The security package %1 generated an exception. The exception information is the data. |
| 0x178B | 無法升級全域秘密 %1。請檢查系統內的所有服務狀態。 |
Could not upgrade the global secret %1. Please check the status of all services in the system. |
| 0x1791 | 某個從 %1 連線的匿名工作階段已嘗試開啟這台電腦上的 LSA 原則控制代碼。這個嘗試因為 STATUS_ACCESS_DENIED 被拒，以避免洩漏有安全性顧慮的資訊給匿名的呼叫者。%n 必須修正進行這個嘗試的應用程式。請連絡應用程式廠商。您可以將\\HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\Lsa\\TurnOffAnonymousBlock DWORD 值設定為 1，停用這個安全性方式，以做為暫時的解決方法。%n 這個訊息一天最多只會記錄一次。 |
An anonymous session connected from %1 has attempted to open an LSA policy handle on this machine. The attempt was rejected with STATUS_ACCESS_DENIED to prevent leaking security sensitive information to the anonymous caller.%n The application that made this attempt needs to be fixed. Please contact the application vendor. As a temporary workaround, this security measure can be disabled by setting the \\HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\Lsa\\TurnOffAnonymousBlock DWORD value to 1.%n This message will be logged at most once a day. |
| 0x1793 | 在登入嘗試過程中，使用者的資訊安全內容累積太多安全性識別碼。這是一個相當不尋常的狀況。請從一些全域或本機群組中移除使用者，來減少安全性識別碼的數目，以便併入資訊安全內容中。%n使用者的 SID 是 %1%n如果這是 Administrator 帳戶，在安全模式下登入將使 Administrator 可以經由自動限制群組成員資格來登入。 |
During a logon attempt, the user's security context accumulated too many security IDs. This is a very unusual situation. Remove the user from some global or local groups to reduce the number of security IDs to incorporate into the security context.%nUser's SID is %1%nIf this is the Administrator account, logging on in safe mode will enable Administrator to log on by automatically restricting group memberships. |
| 0x1794 | 呼叫 InitializeSecurityContext API 來初始化輸出 NTLM 資訊安全內容時，包含指定處理程序識別碼 %1 的程式 %2 提供了 NULL 或空目標名稱給 pszTargetName 參數。需要相互驗證時，這會產生安全性風險。%n %n 要協助防止惡意攻擊，請讓您的程式碼更安全。要這樣做，請變更程式，讓它在 pszTargetName 參數欄位指定目標名稱，然後重新編譯程式碼。 |
The program %2, with the assigned Process ID %1, supplied a NULL or empty target name for the pszTargetName parameter when calling the InitializeSecurityContext API to initiate an outbound NTLM security context. This is a security risk when mutual authentication is required.%n %n To help protect against a malicious attack, make your code more secure. To do this, change the program so that it specifies a target name in the pszTargetName parameter field, and then recompile the code. |
| 0x1795 | 包含指定處理程序識別碼 %1 的程式 %2，無法使用目標名稱 %3 來進行本機驗證。使用的目標名稱無效。目標名稱應該參照其中一個本機電腦名稱，例如，DNS 主機名稱。%n %n 請嘗試其他目標名稱。 |
The program %2, with the assigned process ID %1, could not authenticate locally by using the target name %3. The target name used is not valid. A target name should refer to one of the local computer names, for example, the DNS host name.%n %n Try a different target name. |
| 0x1796 | Microsoft Windows Server 偵測到用戶端與此伺服器之間目前正在使用 NTLM 驗證。用戶端第一次使用 NTLM 向伺服器驗證時，伺服器每次開機時都會發生一次此事件。%n %nNTLM 是較弱的驗證機制。請檢查:%n %n 哪些應用程式正在使用 NTLM 驗證?%n 是否有設定問題，導致無法使用較強的驗證 (例如 Kerberos 驗證)?%n 如果必須支援 NTLM，是否已設定「擴充保護」?%n %n您可以在 http://go.microsoft.com/fwlink/?LinkId=225699 找到如何完成這些檢查的詳細資訊。 |
Microsoft Windows Server has detected that NTLM authentication is presently being used between clients and this server. This event occurs once per boot of the server on the first time a client uses NTLM with this server.%n %nNTLM is a weaker authentication mechanism. Please check:%n %n Which applications are using NTLM authentication?%n Are there configuration issues preventing the use of stronger authentication such as Kerberos authentication?%n If NTLM must be supported, is Extended Protection configured?%n %nDetails on how to complete these checks can be found at http://go.microsoft.com/fwlink/?LinkId=225699. |
| 0x1798 | 封裝 %1 的驗證要求遭到拒絕，因為目標資訊無效。驗證要求不符合目標名稱 %2。 |
An authentication request for package %1 was rejected because the target information was invalid. The authentication request did not match the target name of %2. |
| 0x1800 | 用戶端查詢了 LSA 專屬的秘密物件。基於安全性因素，以加密格式傳回此物件。 |
A secret object private to LSA was queried by a client. This object was returned in encrypted format for security reasons. |
| 0x1801 | 抓取此電腦的新集中存取原則時發生錯誤。%n%n無法抓取下列 DN 的原則:%n%1 |
An error occurred while retrieving new Central Access Policies for this machine.%n%nCould not retrieve policies for the following DNs:%n%1 |
| 0x1802 | 處理此電腦的新集中存取原則時發生錯誤。由一或多個集中存取原則參照的下列集中存取規則驗證失敗:%n%n%t錯誤:%t%t%1%n%n%t名稱:%t%t%2%n%t描述:%t%3 |
An error occurred while processing new Central Access Policies for this machine. Validation failed for the following Central Access Rule referenced by one or more of the Central Access Policies:%n%n%tError:%t%t%1%n%n%tName:%t%t%2%n%tDescription:%t%3 |
| 0x1803 | Credential Guard 已設定為執行，但並未獲得授權。Credential Guard 未啟動。 |
Credential Guard is configured to run, but is not licensed. Credential Guard was not started. |
| 0x1FFF | MessageIdTypedef=DWORD |
MessageIdTypedef=DWORD |
| 0x2000 | NULL SID |
NULL SID |
| 0x2001 | Everyone |
Everyone |
| 0x2002 | LOCAL |
LOCAL |
| 0x2003 | CREATOR OWNER |
CREATOR OWNER |
| 0x2004 | CREATOR GROUP |
CREATOR GROUP |
| 0x2005 | NT Pseudo Domain |
NT Pseudo Domain |
| 0x2006 | NT AUTHORITY |
NT AUTHORITY |
| 0x2007 | DIALUP |
DIALUP |
| 0x2008 | NETWORK |
NETWORK |
| 0x2009 | BATCH |
BATCH |
| 0x200A | INTERACTIVE |
INTERACTIVE |
| 0x200B | SERVICE |
SERVICE |
| 0x200C | BUILTIN |
BUILTIN |
| 0x200D | SYSTEM |
SYSTEM |
| 0x200E | ANONYMOUS LOGON |
ANONYMOUS LOGON |
| 0x200F | CREATOR OWNER SERVER |
CREATOR OWNER SERVER |
| 0x2010 | CREATOR GROUP SERVER |
CREATOR GROUP SERVER |
| 0x2011 | ENTERPRISE DOMAIN CONTROLLERS |
ENTERPRISE DOMAIN CONTROLLERS |
| 0x2012 | SELF |
SELF |
| 0x2013 | Authenticated Users |
Authenticated Users |
| 0x2014 | RESTRICTED |
RESTRICTED |
| 0x2015 | Internet$ |
Internet$ |
| 0x2016 | TERMINAL SERVER USER |
TERMINAL SERVER USER |
| 0x2017 | PROXY |
PROXY |
| 0x2018 | LOCAL SERVICE |
LOCAL SERVICE |
| 0x2019 | NETWORK SERVICE |
NETWORK SERVICE |
| 0x201A | REMOTE INTERACTIVE LOGON |
REMOTE INTERACTIVE LOGON |
| 0x201B | USERS |
USERS |
| 0x201C | NTLM Authentication |
NTLM Authentication |
| 0x201D | Digest Authentication |
Digest Authentication |
| 0x201E | SChannel Authentication |
SChannel Authentication |
| 0x201F | This Organization |
This Organization |
| 0x2020 | Other Organization |
Other Organization |
| 0x2021 | IUSR |
IUSR |
| 0x2022 | Mandatory Label |
Mandatory Label |
| 0x2023 | Untrusted Mandatory Level |
Untrusted Mandatory Level |
| 0x2024 | Low Mandatory Level |
Low Mandatory Level |
| 0x2025 | Medium Mandatory Level |
Medium Mandatory Level |
| 0x2026 | High Mandatory Level |
High Mandatory Level |
| 0x2027 | System Mandatory Level |
System Mandatory Level |
| 0x202A | Protected Process Mandatory Level |
Protected Process Mandatory Level |
| 0x202B | OWNER RIGHTS |
OWNER RIGHTS |
| 0x202C | WRITE RESTRICTED |
WRITE RESTRICTED |
| 0x202D | ENTERPRISE READ-ONLY DOMAIN CONTROLLERS BETA |
ENTERPRISE READ-ONLY DOMAIN CONTROLLERS BETA |
| 0x202E | Medium Plus Mandatory Level |
Medium Plus Mandatory Level |
| 0x202F | CONSOLE LOGON |
CONSOLE LOGON |
| 0x2030 | This Organization Certificate |
This Organization Certificate |
| 0x2031 | ALL APPLICATION PACKAGES |
ALL APPLICATION PACKAGES |
| 0x2032 | APPLICATION PACKAGE AUTHORITY |
APPLICATION PACKAGE AUTHORITY |
| 0x2033 | 您的網際網路連線 |
Your Internet connection |
| 0x2034 | 您的網際網路連線，包括從網際網路傳入的連線 |
Your Internet connection, including incoming connections from the Internet |
| 0x2035 | 您的家用網路或工作場所網路 |
Your home or work networks |
| 0x2036 | 您的圖片媒體櫃 |
Your pictures library |
| 0x2037 | 您的視訊媒體櫃 |
Your videos library |
| 0x2038 | 您的音樂媒體櫃 |
Your music library |
| 0x2039 | 您的文件庫 |
Your documents library |
| 0x203B | 您的 Windows 認證 |
Your Windows credentials |
| 0x203C | 軟體與硬體憑證或智慧卡 |
Software and hardware certificates or a smart card |
| 0x203D | 抽取式存放裝置 |
Removable storage |
| 0x203E | 使用者模式驅動程式 |
USER MODE DRIVERS |
| 0x203F | 宣告有效 |
Claims Valid |
| 0x2040 | 複合身分識別存在 |
Compound Identity Present |
| 0x2041 | Microsoft Account Authentication |
Microsoft Account Authentication |
| 0x2042 | 驗證授權單位宣稱的識別身分 |
Authentication authority asserted identity |
| 0x2043 | 服務宣稱的識別身分 |
Service asserted identity |
| 0x2044 | 本機帳戶 |
Local account |
| 0x2045 | 本機帳戶與 Administrators 群組的成員 |
Local account and member of Administrators group |
| 0x2046 | 您的約會 |
Your Appointments |
| 0x2047 | 您的連絡人 |
Your Contacts |
| 0x2048 | DefaultAccount |
DefaultAccount |
| 0x2049 | System Managed Group |
System Managed Group |
| 0x204A | 雲端帳戶驗證 |
Cloud Account Authentication |
| 0x204B | 金鑰信任身分識別 |
Key trust identity |
| 0x204C | 金鑰屬性多重要素驗證 |
Key property multi-factor authentication |
| 0x204D | 金鑰屬性證明 |
Key property attestation |
| 0x204E | 新的公用金鑰身分識別 |
Fresh public key identity |
| 0x204F | 所以受限制的應用程式封包 |
ALL RESTRICTED APPLICATION PACKAGES |
| 0x00004000 | LsaSetupDomain |
LsaSetupDomain |
| 0x00008005 | 搜尋要求需要連線到網域 %1 的網域控制站。LSA 在網域上找不到網域控制站，所以無法處理要求。請檢查從這個網域控制站到網域 %2 的連線狀態及安全性通道安裝程式。 |
A lookup request was made that required connectivity to a domain controller in domain %1. The LSA was unable to find a domain controller in the domain and thus failed the request. Please check connectivity and secure channel setup from this domain controller to the domain %2. |
| 0x00008006 | 搜尋要求需要連線到網域控制站 %1。本機 LSA 無法連絡遠端網域控制站的 LSA。請檢查從這個網域控制站到網域控制站 %2 的連線狀態及安全性通道設定。 |
A lookup request was made that required connectivity to the domain controller %1. The local LSA was unable to contact the LSA on the remote domain controller. Please check connectivity and secure channel setup from this domain controller to the domain controller %2. |
| 0x00008007 | 搜尋要求需要遠端網域控制站 %1 上的搜尋服務。遠端網域控制站無法處理要求，所以本機 LSA 無法處理原始搜尋要求。請檢查從這個網域控制站到網域控制站 %2 的連線狀態及安全性通道設定。 |
A lookup request was made that required the lookup services on the remote domain controller %1. The remote domain controller failed the request thus the local LSA failed the original lookup request. Please check connectivity and secure channel setup from this domain controller to the domain controller %2. |
| 0x00008009 | LSA 無法透過 TCP/IP 介面登錄它的 RPC 介面。請確定通訊協定是否正確安裝。 |
The LSA was unable to register its RPC interface over the TCP/IP interface. Please make sure that the protocol is properly installed. |
| 0x0000800C | 在啟動期間，LSA 無法通知 UBPM，狀態為 %1。 |
The LSA was unable to notify UBPM during startup with status %1. |
| 0x00009000 | Schannel 安全性封裝已經成功載入。 |
The schannel security package has loaded successfully. |
| 0x00009001 | 開啟系統 %1 密碼編譯模組時發生嚴重錯誤。需要 SSL 或 TLS 密碼編譯通訊協定的操作將無法正常運作。錯誤碼為 %2。 |
A fatal error occurred while opening the system %1 cryptographic module. Operations that require the SSL or TLS cryptographic protocols will not work correctly. The error code is %2. |
| 0x00009003 | 正在建立 TLS %1 認證。 |
Creating a TLS %1 credential. |
| 0x00009004 | TLS %1 認證的私密金鑰有以下內容:%n%n CSP 名稱: %2%n CSP 類型: %3%n 金鑰名稱: %4%n 金鑰類型: %5%n 金鑰旗標: %6%n%n 附加的資料中包含憑證。 |
The TLS %1 credential's private key has the following properties:%n%n CSP name: %2%n CSP type: %3%n Key name: %4%n Key Type: %5%n Key Flags: %6%n%n The attached data contains the certificate. |
| 0x00009005 | TLS %1 認證的憑證並未附加私密金鑰資訊內容。當您使用錯誤的方式備份憑證而後再還原時，通常會發生此問題。此訊息可能也表示憑證註冊失敗。 |
The TLS %1 credential's certificate does not have a private key information property attached to it. This most often occurs when a certificate is backed up incorrectly and then later restored. This message can also indicate a certificate enrollment failure. |
| 0x00009006 | 嘗試存取 TLS %1 認證私密金鑰時發生嚴重錯誤。從密碼編譯模組傳回的錯誤碼為 %2。 內部錯誤狀態為 %3。 |
A fatal error occurred when attempting to access the TLS %1 credential private key. The error code returned from the cryptographic module is %2. The internal error state is %3. |
| 0x00009007 | 建立 TLS %1 認證時發生嚴重錯誤。內部錯誤狀態為 %2。 |
A fatal error occurred while creating a TLS %1 credential. The internal error state is %2. |
| 0x00009008 | 無法抓取 TLS %1 指定的憑證鏈結:%n%n 失敗狀態: %2%n 旗標: %3%n%n 附加的資料中包含憑證。 |
The TLS %1 specified certificate's chain could not be retrieved:%n%n Failure Status: %2%n Flags: %3%n%n The attached data contains the certificate. |
| 0x00009009 | 起始 TLS 連線時發現不受支援的加密套件。這表示用戶端應用程式和/或安裝的密碼編譯模組發生設定問題。TLS 連線要求失敗。 |
No supported cipher suites were found when initiating a TLS connection. This indicates a configuration problem with the client application and/or the installed cryptographic modules. The TLS connection request has failed. |
| 0x0000900A | 收到來自遠端用戶端應用程式的 %1 連線要求，但伺服器不支援用戶端應用程式支援的加密套件。TLS 連線要求失敗。 |
An %1 connection request was received from a remote client application, but none of the cipher suites supported by the client application are supported by the server. The TLS connection request has failed. |
| 0x0000900B | 遠端伺服器已經要求 TLS 用戶端驗證，但是找不到適合的用戶端憑證。將嘗試匿名連線。視伺服器的原則設定而定，此 TLS 連線要求可能成功或失敗。 |
The remote server has requested TLS client authentication, but no suitable client certificate could be found. An anonymous connection will be attempted. This TLS connection request may succeed or fail, depending on the server's policy settings. |
| 0x0000900C | 從遠端伺服器收到的憑證未經正確驗證。錯誤碼為 %1。TLS 連線要求失敗。附加的資料中包含伺服器憑證。 |
The certificate received from the remote server has not validated correctly. The error code is %1. The TLS connection request has failed. The attached data contains the server certificate. |
| 0x0000900D | 從遠端用戶端應用程式收到的憑證未經正確確認。錯誤碼為 %1。附加的資料中包含用戶端憑證。 |
The certificate received from the remote client application has not validated correctly. The error code is %1. The attached data contains the client certificate. |
| 0x0000900E | 從遠端用戶端應用程式收到的憑證不適合直接對應到用戶端系統帳戶，可能因為發行憑證的授權單位不完全受信任。錯誤碼為 %1。附加的資料中包含用戶端憑證。 |
The certificate received from the remote client application is not suitable for direct mapping to a client system account, possibly because the authority that issuing the certificate is not sufficiently trusted. The error code is %1. The attached data contains the client certificate. |
| 0x0000900F | 從遠端用戶端應用程式收到的憑證未正確對應到用戶端系統帳戶。錯誤碼為 %1。這不一定是嚴重錯誤，因為伺服器應用程式還是可能接受這個憑證。 |
The certificate received from the remote client application was not successfully mapped to a client system account. The error code is %1. This is not necessarily a fatal error, as the server application may still find the certificate acceptable. |
| 0x00009010 | 已順利完成 TLS %1 交握。交涉的密碼編譯參數如下。%n%n 通訊協定版本: %2%n CipherSuite: %3%n 交換強度: %4 位元%n 內容控制代碼: %5%n 目標名稱: %6%n 本機憑證主體名稱: %7%n 遠端憑證主體名稱: %8 |
A TLS %1 handshake completed successfully. The negotiated cryptographic parameters are as follows.%n%n Protocol version: %2%n CipherSuite: %3%n Exchange strength: %4 bits%n Context handle: %5%n Target name: %6%n Local certificate subject name: %7%n Remote certificate subject name: %8 |
| 0x00009011 | 從遠端伺服器收到的憑證已到期或尚未生效。TLS 連線要求失敗。附加的資料中包含伺服器憑證。 |
The certificate received from the remote server has either expired or is not yet valid. The TLS connection request has failed. The attached data contains the server certificate. |
| 0x00009012 | 從遠端伺服器收到的憑證是由未受信任的憑證授權單位所簽發。因此，無法驗證憑證中包含的資料。TLS 連線要求失敗。附加的資料中包含伺服器憑證。 |
The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. |
| 0x00009013 | 從遠端伺服器收到的憑證已被撤銷。這表示簽發憑證的憑證授權單位已經將它作廢。TLS 連線要求失敗。附加的資料中包含伺服器憑證。 |
The certificate received from the remote server has been revoked. This means that the certificate authority that issued the certificate has invalidated it. The TLS connection request has failed. The attached data contains the server certificate. |
| 0x00009014 | 從遠端伺服器收到的憑證並未包含預期的名稱。因此無法判斷我們是否連線到正確的伺服器。我們預期的伺服器名稱是 %1。TLS 連線要求失敗。附加的資料中包含伺服器憑證。 |
The certificate received from the remote server does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The server name we were expecting is %1. The TLS connection request has failed. The attached data contains the server certificate. |
| 0x00009015 | 當要求用戶端驗證時，這台伺服器傳送受信任的憑證授權單位清單給用戶端。用戶端使用這個清單來選擇伺服器所信任的用戶端憑證。目前，這台伺服器信任許多憑證授權單位，所以造成清單太長。因此，這個清單已被截斷。這台電腦的系統管理員應該檢查受信任可以進行用戶端驗證的憑證授權單位，並移除那些並非真正需要信任的憑證授權單位。 |
When asking for client authentication, this server sends a list of trusted certificate authorities to the client. The client uses this list to choose a client certificate that is trusted by the server. Currently, this server trusts so many certificate authorities that the list has grown too long. This list has thus been truncated. The administrator of this machine should review the certificate authorities trusted for client authentication and remove those that do not really need to be trusted. |
| 0x00009016 | 這個系統不存在適合的預設伺服器認證。這樣會防止預期利用系統預設認證的伺服器應用程式接受 SSL 連線。目錄伺服器就是這種應用程式的範例。管理自己認證的應用程式，例如 Internet Information Server，則不受影響。 |
No suitable default server credential exists on this system. This will prevent server applications that expect to make use of the system default credentials from accepting SSL connections. An example of such an application is the directory server. Applications that manage their own credentials, such as the internet information server, are not affected by this. |
| 0x00009017 | 收到來自遠端端點的嚴重警示。TLS 通訊協定定義的嚴重警示代碼為 %1。 |
A fatal alert was received from the remote endpoint. The TLS protocol defined fatal alert code is %1. |
| 0x00009018 | 已產生嚴重警示，並傳送給遠端端點。這可能會導致連線終止。TLS 通訊協定定義的嚴重錯誤碼為 %1。%n%n 目標名稱: %3%n%n您可以在 http://www.iana.org/assignments/tls-parameters/tls-parameters.xhtml#tls-parameters-6 找到 TLS 警示登錄 |
A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal alert code is %1.%n%n Target name: %3%n%nThe TLS alert registry can be found at http://www.iana.org/assignments/tls-parameters/tls-parameters.xhtml#tls-parameters-6 |
| 0x00009019 | TLS %1 指出憑證鏈結不完整:%n%n 失敗狀態: %2%n%n 這可能導致信任驗證失敗或互通性問題。如需詳細資訊，請參閱 KB 954755%n 附加的資料中包含憑證。 |
The TLS %1 specified certificate's chain is incomplete:%n%n Failure Status: %2%n%n This can cause trust validation failures or interoperability problems. For more information see KB 954755%n The attached data contains the certificate. |
| 0x0000A000 | 安全性系統偵測出伺服器 %1 的驗證錯誤。來自驗證通訊協定 %2 的失敗碼為 %3。 |
The Security System detected an authentication error for the server %1. The failure code from authentication protocol %2 was %3. |
| 0x0000A001 | 安全性系統無法建立與伺服器 %1 的安全連線。沒有可用的驗證通訊協定。 |
The Security System could not establish a secured connection with the server %1. No authentication protocol was available. |
| 0x0000A002 | 安全性系統無法驗證伺服器 %1，因為伺服器已完成驗證，但用戶端驗證通訊協定 %2 尚未完成驗證。 |
The Security System was unable to authenticate to the server %1 because the server has completed the authentication, but the client authentication protocol %2 has not. |
| 0x0000A004 | 安全性系統收到一個不明驗證通訊協定的驗證嘗試。要求已經失敗。 |
The Security System received an authentication attempt with an unknown authentication protocol. The request has failed. |
| 0x0000A005 | 安全性系統已經選取 %2 做為伺服器 %1 的驗證通訊協定。 |
The Security System has selected %2 for the authentication protocol to server %1. |
| 0x0000A006 | 安全性系統已收到驗證嘗試，並判定用戶端喜好的通訊協定 %1 是可接受的。 |
The Security System has received an authentication attempt, and determined that the protocol %1 preferred by the client is acceptable. |
| 0x0000A007 | 安全性系統已收到驗證通訊協定 %1 的直接驗證要求。 |
The Security System has received an authentication request directly for authentication protocol %1. |
| 0x0000A008 | 安全性系統收到一個無法解碼的驗證要求。要求已經失敗。 |
The Security System has received an authentication request that could not be decoded. The request has failed. |
| 0x0000A009 | 安全性系統已收到驗證嘗試，並判定通訊協定 %1 是公用通訊協定。 |
The Security System has received an authentication attempt, and determined that the protocol %1 is the common protocol. |
| 0x0000B000 | 已經停用登入快取。網路延遲或中斷期間，可能會發生暫時性驗證失敗。請連絡您的系統管理員。 |
Logon cache was disabled. Intermittent authentication failures may result during periods of network latency or interrupts. Please contact your system administrator. |
| 0x0000B001 | 登入嘗試失敗造成使用者 %1 登入快取項目的刪除。驗證封裝是 %2，錯誤訊息為 %3。 |
A failed logon attempt has caused a logon cache entry for user %1 to be deleted. The authentication package was %2, and the error message was %3. |
| 0x0000B002 | 使用者 %1 的登入快取項目是最舊的項目而且已經移除。此項目的時間戳記是 %2。 |
A logon cache entry for user %1 was the oldest entry and was removed. The timestamp of this entry was %2. |
| 0x01009020 | 驗證 DTLS 連線要求失敗。 |
Verification of the DTLS connection request failed. |
| 0x01009021 | 已拒絕 DTLS 記錄，因為該記錄不在目前的接收視窗內。 |
DTLS record was rejected because it is outside of current receive window. |
| 0x01009022 | 已拒絕 DTLS 記錄，因為該記錄是先前所接收記錄的重複項。 |
A DTLS record was rejected because it is a duplicate of a previously received record. |
| 0x01009023 | 已要求重新傳輸 DTLS 交握訊息。 |
The retransmission of DTLS handshake messages has been requested. |
| 0x01009030 | 在 %1 找不到用來保護 TLS 工作階段票證的金鑰內容。 |
The key material used to protect TLS Session Tickets was not found at %1. |
| 0x30000001 | 開始 |
Start |
| 0x30000002 | 停止 |
Stop |
| 0x50000001 | 重大 |
Critical |
| 0x50000002 | 錯誤 |
Error |
| 0x50000003 | 警告 |
Warning |
| 0x50000004 | 資訊 |
Information |
| 0x70000001 | 安全性封裝管理員 |
Security Package Manager |
| 0x70000002 | 尋找程式 |
Locator |
| 0x70000003 | SPNEGO (交涉程式) |
SPNEGO (Negotiator) |
| 0x70000004 | 登入快取 |
Logon Cache |
| 0x70000005 | LSA 登入 |
LSA Logon |
| 0x70000006 | LSA SID-Name 查詢 |
LSA SID-Name Lookup |
| 0x70000007 | 最大值 |
Max |
| 0x80009080 | 用戶端 |
client |
| 0x80009081 | 伺服器 |
server |
| 0x8000C000 | 企業認證資料 |
Enterprise Credential Data |
| 0x8000C001 | 本機認證資料 |
Local Credential Data |
| 0x90000001 | Microsoft-Windows-LSA |
Microsoft-Windows-LSA |
| 0x90000002 | System |
System |
| 0x90000003 | Operational |
Operational |
| 0x90000004 | Diagnostic |
Diagnostic |
| 0x92000001 | Microsoft-Windows-Authentication |
Microsoft-Windows-Authentication |
| 0x92000002 | Microsoft-Windows-Authentication/ProtectedUser-Client |
Microsoft-Windows-Authentication/ProtectedUser-Client |
| 0x92000003 | Microsoft-Windows-Authentication/ProtectedUserFailures-DomainController |
Microsoft-Windows-Authentication/ProtectedUserFailures-DomainController |
| 0x92000004 | Microsoft-Windows-Authentication/ProtectedUserSuccesses-DomainController |
Microsoft-Windows-Authentication/ProtectedUserSuccesses-DomainController |
| 0x92000005 | Microsoft-Windows-Authentication/AuthenticationPolicyFailures-DomainController |
Microsoft-Windows-Authentication/AuthenticationPolicyFailures-DomainController |
| 0xB0001826 | LogonSession 在互動使用者登出後仍為使用中狀態。這表示其中一個服務可能有權杖洩漏的情況。%n登入識別碼:%1%n帳戶名稱:%2%n網域名稱:%3%n |
LogonSession alive after interactive user logoff. Indicates a possible token leak in one of the services. %nLogon ID:%1%nAccount Name:%2%nDomain Name:%3%n |