Login | Sign Up
ErrorKey - Search engine for Error codes and messages     
  HTTP:Client Error  [ 45 result(s) ]
CISCO IOS HTTP MICROSOFT ORACLE SYMBIAN 
 ORA-29268 - HTTP client error string  ORACLE
The HTTP response indicated that the HTTP client error occurred.
Fix the HTTP client error and retry the HTTP request.
Comments
 
0x6 KDC_ERR_C_PRINCIPAL_UNKNOWN - Client not found in Kerberos database  MICROSOFT
Associated internal Windows error code STATUS_NO_SUCH_USER Corresponding debug output messages • D_DebugLog(“KLIN(%x) No principal name supplied to AS request - not allowed\n”) • DebugLog(“KdcGetS4UTicketInfo normalize returned referral for S4U client\n”) • DebugLog(“Failed Authz check\n”)
This error can occur if the domain controller cannot find the account name in Active Directory. This can occur in three scenarios: • The actual account does not exist. Verify that the name is in the Active Directory. If the principal name is not in the local Active Directory, but you know the account should exist and the user was recently added to the domain, verify that Active Directory replication is current. • A new account has been created and has not yet replicated to the KDC that the client is using for authentication. It could be that the updates have not yet reached the domain controller that is acting as the KDC for that user. For information about how to manually initiate an update, see “Initiating Replication between Active Directory Direct Replication Partners” in the Microsoft Knowledge Base at http://go.microsoft.com/fwlink/?LinkId=23063. • The user’s account has expired and the Enforce user logon restrictions Group Policy object (GPO) setting is enabled. If the user name is in Active Directory, determine whether the account has expired. Enforce user logon restrictions forces the domain controller to check the user’s account each time a TGT is presented and account expiration will cause the domain controller to refuse an otherwise valid TGT.
Kerberos Errors
Comments
 
0x3C KRB_ERR_GENERIC - Generic error  MICROSOFT
Associated internal Windows error codes • STATUS_INSUFFICIENT_RESOURCES Corresponding debug output messages • DebugLog(“SpInitLsaModeContext failed to verify AP reply: 0x%x\n”) • DebugLog(“Failed to decrypt AP reply: 0x%x. %ws, line %d\n”) • DebugLog(“Failed to encode data: %d\n”) • DebugLog(“KerbUnpackData Trying to unpack NULL data\n”) • D_DebugLog(“Failed to unmarshal pac\n”) • DebugLog(“Failed to get CLIENT Principal : 0x%x\n”) • DebugLog(“Failed to get Client principal name: 0x%x\n”) • DebugLog(“Failed to acquire KDC certificate private key: 0x%x\n”) • DebugLog(“Trying S4UProxy w/ no PAC\n”) • D_DebugLog(“KdcUnpackAdditionalTickets KLIN(%x) Trying to unpack null ticket or more than one ticket\n”) • D_DebugLog(“The client of kpasswd did not ask for a sub key.\n”) • DebugLog(“Failed to create token from ticket: 0x%x\n”) • D_DebugLog(“No logon info for PAC - not adding resource groups\n”) • DebugLog(“Failed to query domain info for %wZ: 0x%x. %ws, line %d\n”) • DebugLog(“Failed to decrypt old password: 0x%x\n”) • DebugLog(“KdcGetTicketInfo can’t restrict user accounts if USER_EXTENDED_FIELD_SPN is not requested\n”)
• Group membership has overloaded the PAC. For information about how to resolve this issue, see Group Membership Overloads PAC earlier in this white paper. • Multiple recent password changes have not propagated. You can wait for the changes to replicate, or you can force replication. To manually initiate replication see “Initiating Replication Between Active Directory Direct Replication Partners” in the Microsoft Knowledge Base at http://go.microsoft.com/fwlink/?LinkId=23063. • Crypto subsystem error caused by running out of memory. Restart system or end processes to free memory. • SPN too long. Use Network Monitor to capture network data. Examine the SPN being requested. Verify that it is a correctly formed SPN and is registered to a service on the network. • SPN has too many parts. Use Network Monitor to capture network data. Examine the SPN being requested. Verify that it is a correctly formed SPN and is registered to a service on the network.
Kerberos Errors
Comments
 
406  - Not Acceptable HTTP
The 406 status code means that, although the server understood and processed the request, the response is of a form the client cannot understand. A client sends, as part of a request, headers indicating what types of data it can use, and a 406 error is returned when the response is of a type not i that list.
Client Error
Comments
 
 AG_E_CONNECTION_ERROR -  MICROSOFT
Error raised from a call to Send. This error occurs before accessing the server when a failure to connect to the Internet occurs on the client side. (http://msdn.microsoft.com/en-us/library/bb979896(VS.95).aspx)
SilverLight DownloadFailed Event Error Table
Comments
 
0x7 KDC_ERR_S_PRINCIPAL_UNKNOWN - Server not found in Kerberos database  MICROSOFT
Associated internal Windows error codes • STATUS_NO_TRUST_SAM_ACCOUNT • STATUS_OBJECT_NAME_NOT_FOUND • STATUS_KDC_UNABLE_TO_REFER Corresponding debug output messages • D_DebugLog(“Wrong S4UProxytarget %wZ %wZ\n”) • DebugLog(“KdcFindReferralTarget KLIN(%x) Needed exact match and got a transitively-trusted domain.\n”) • D_DebugLog(“No referral info for %wZ\n”) • D_DebugLog(“Got UPN w/ uknown trust path %x\n”) • DebugLog(“No auth info for this trust: %wZ. %ws, line %d\n”)
This error can occur if the domain controller cannot find the server’s name in Active Directory. This error is similar to KDC_ERR_C_PRINCIPAL_UNKNOWN except that it occurs when the server name cannot be found. This might be because: • The actual name is missing. Verify that the service is registered and has an SPN set. For more information about setting SPNs, see Need an SPN Set earlier in this white paper. • A new computer account has been created and has not yet replicated to the KDC that the client is using for authentication. It could be that the updates have not yet reached the domain controller that is acting as the KDC for that client. For information about how to manually initiate an update, see “Initiating Replication between Active Directory Direct Replication Partners” in the Microsoft Knowledge Base at http://go.microsoft.com/fwlink/?LinkId=23063. • UDP fragmentation is occurring. If the SPN is set, or if the request failed for an initial TGT (requesting a TGT does not require any SPNs to be set manually), then UDP fragmentation might be causing the failure. Capture a network trace with Network Monitor and compare it to the sample trace associated with UDP fragmentation in Appendix A. If you determine that the cause is UDP fragmentation, see UDP Fragmentation earlier in this white paper for information about how to resolve the issue. • A trust path has been incorrectly configured. If the SPN is set correctly and this error
Kerberos Errors
Comments
 
405  - Method Not Allowed HTTP
A 405 status code is returned when the client has tried to use a request method that the server does not allow. Request methods that are allowed should be sent with the response (common request methods are POST and GET).
Client Error
Comments
 
407  - Proxy Authentication Required HTTP
The 407 status code is very similar to the 401 status code, and means that the client must be authorised by the proxy before the request can proceed.
Client Error
Comments
 
408  - Request Timeout HTTP
A 408 status code means that the client did not produce a request quickly enough. A server is set to only wait a certain amount of time for responses from clients, and a 408 status code indicates that time has passed.
Client Error
Comments
 
401  - Unauthorized HTTP
A 401 status code indicates that before a resource can be accessed, the client must be authorised by the server.
Client Error
Comments
 
 

 
Cisco IOS (1)
Kerberos Errors (6)
Client Error (18)
SilverLight DownloadFailed Event Error Table  (1)
HTTP Error Codes  (1)
 
  Prev   1  2  3  4  5  Next