|
The requested section was not present in the activation context. This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem. The application binding data format is invalid. The referenced assembly is not installed on your system. The manifest file does not begin with the required tag and format information. The manifest file contains one or more syntax errors. The application attempted to activate a disabled activation context. The requested lookup key was not found in any active activation context. A component version required by the application conflicts with another component version already active. The type requested activation context section does not match the query API used. Lack of system resources has required isolated activation to be disabled for the current thread of execution. An attempt to set the process default activation context failed because the process default activation context was already set. The encoding group identifier specified is not recognized. The encoding requested is not recognized. The manifest contains a reference to an invalid URI. The application manifest contains a reference to a dependent assembly which is not installed. The manifest for an assembly used by the application has a reference to a dependent assembly which is not installed. The manifest contains an attribute for the assembly identity which is not valid. The manifest is missing the required default namespace specification on the assembly element. The manifest has a default namespace specified on the assembly element but its value is not "urn:schemas-microsoft-com:asm.v1". The private manifest probe has crossed the reparse-point-associated path. Two or more components referenced directly or indirectly by the application manifest have files by the same name. Two or more components referenced directly or indirectly by the application manifest have window classes with the same name. Two or more components referenced directly or indirectly by the application manifest have the same COM server CLSIDs. Two or more components referenced directly or indirectly by the application manifest have proxies for the same COM interface IIDs. Two or more components referenced directly or indirectly by the application manifest have the same COM type library TLBIDs. Two or more components referenced directly or indirectly by the application manifest have the same COM ProgIDs. Two or more components referenced directly or indirectly by the application manifest are different versions of the same component which is not permitted. A component's file does not match the verification information present in the component manifest. The policy manifest contains one or more syntax errors. Manifest Parse Error : A string literal was expected, but no opening quote character was found. Manifest Parse Error : Incorrect syntax was used in a comment. Manifest Parse Error : A name was started with an invalid character. Manifest Parse Error : A name contained an invalid character. Manifest Parse Error : A string literal contained an invalid character. Manifest Parse Error : Invalid syntax for an XML declaration. Manifest Parse Error : An invalid character was found in text content. Manifest Parse Error : Required white space was missing. Manifest Parse Error : The character '>' was expected. Manifest Parse Error : A semi colon character was expected. Manifest Parse Error : Unbalanced parentheses. Manifest Parse Error : Internal error. Manifest Parse Error : White space is not allowed at this location. Manifest Parse Error : End of file reached in invalid state for current encoding. Manifest Parse Error : Missing parenthesis. Manifest Parse Error : A single or double closing quote character (\' or \") is missing. Manifest Parse Error : Multiple colons are not allowed in a name. Manifest Parse Error : Invalid character for decimal digit. Manifest Parse Error : Invalid character for hexadecimal digit. Manifest Parse Error : Invalid Unicode character value for this platform. Manifest Parse Error : Expecting white space or '?'. Manifest Parse Error : End tag was not expected at this location. Manifest Parse Error : The following tags were not closed: %1. Manifest Parse Error : Duplicate attribute. Manifest Parse Error : Only one top level element is allowed in an XML document. Manifest Parse Error : Invalid at the top level of the document. Manifest Parse Error : Invalid XML declaration. Manifest Parse Error : XML document must have a top level element. Manifest Parse Error : Unexpected end of file. Manifest Parse Error : Parameter entities cannot be used inside markup declarations in an internal subset. Manifest Parse Error : Element was not closed. Manifest Parse Error : End element was missing the character '>'. Manifest Parse Error : A string literal was not closed. Manifest Parse Error : A comment was not closed. Manifest Parse Error : A declaration was not closed. Manifest Parse Error : A CDATA section was not closed. Manifest Parse Error : The namespace prefix is not allowed to start with the reserved string "xml". Manifest Parse Error : System does not support the specified encoding. Manifest Parse Error : Switch from current encoding to specified encoding not supported. Manifest Parse Error : The name 'xml' is reserved and must be lower case. Manifest Parse Error : The standalone attribute must have the value 'yes' or 'no'. Manifest Parse Error : The standalone attribute cannot be used in external entities. Manifest Parse Error : Invalid version number. Manifest Parse Error : Missing equals sign between attribute and attribute value. The specified quick mode policy already exists. The specified quick mode policy was not found. The specified quick mode policy is being used. The specified main mode policy already exists. The specified main mode policy was not found. The specified main mode policy is being used. The specified main mode filter already exists. The specified main mode filter was not found. The specified transport mode filter already exists. The specified transport mode filter does not exist. The specified main mode authentication list exists. The specified main mode authentication list was not found. The specified quick mode policy is being used. The specified main mode policy was not found. The specified quick mode policy was not found. The manifest file contains one or more syntax errors. The application attempted to activate a disabled activation context. The requested lookup key was not found in any active activation context. The Main Mode filter is pending deletion. The transport filter is pending deletion. The tunnel filter is pending deletion. The Main Mode policy is pending deletion. The Main Mode authentication bundle is pending deletion. The Quick Mode policy is pending deletion. IKE authentication credentials are unacceptable. IKE security attributes are unacceptable. IKE Negotiation in progress. General processing error. Negotiation timed out. IKE failed to find valid machine certificate. IKE SA deleted by peer before establishment completed. IKE SA deleted before establishment completed. Negotiation request sat in Queue too long. Negotiation request sat in Queue too long. Negotiation request sat in Queue too long. Negotiation request sat in Queue too long. No response from peer. Negotiation took too long. Negotiation took too long. Unknown error occurred. Certificate Revocation Check failed. Invalid certificate key usage. Invalid certificate type. No private key associated with machine certificate. Failure in Diffie-Helman computation. Invalid header. No policy configured. Failed to verify signature. Failed to authenticate using Kerberos. Peer's certificate did not have a public key. Error processing error payload. Error processing SA payload. Error processing Proposal payload. Error processing Transform payload. Error processing KE payload. Error processing ID payload. Error processing Cert payload. Error processing Certificate Request payload. Error processing Hash payload. Error processing Signature payload. Error processing Nonce payload. Error processing Notify payload. Error processing Delete Payload. Error processing VendorId payload. Invalid payload received. Soft SA loaded. Soft SA torn down. Invalid cookie received.. Peer failed to send valid machine certificate. Certification Revocation check of peer's certificate failed. New policy invalidated SAs formed with old policy. There is no available Main Mode IKE policy. Failed to enabled TCB privilege. Failed to load SECURITY.DLL. Failed to obtain security function table dispatch address from SSPI. Failed to query Kerberos package to obtain max token size. Failed to obtain Kerberos server credentials for ISAKMP/ERROR_IPSEC_IKE service. Kerberos authentication will not function. The most likely reason for this is lack of domain membership. This is normal if your computer is a member of a workgroup. Failed to determine SSPI principal name for ISAKMP/ERROR_IPSEC_IKE service (QueryCredentialsAttributes). Failed to obtain new SPI for the inbound SA from Ipsec driver. The most common cause for this is that the driver does not have the correct filter. Check your policy to verify the filters. Given filter is invalid. Memory allocation failed. Failed to add Security Association to IPSec Driver. The most common cause for this is if the IKE negotiation took too long to complete. If the problem persists, reduce the load on the faulting machine. Invalid policy. Invalid DOI. Invalid situation. Diffie-Hellman failure. Invalid Diffie-Hellman group. Error encrypting payload. Error decrypting payload. Policy match error. Unsupported ID. Hash verification failed. Invalid hash algorithm. Invalid hash size. Invalid encryption algorithm. Invalid authentication algorithm. Invalid certificate signature. Load failed. Deleted via RPC call. Temporary state created to perform reinitialization. This is not a real failure. The lifetime value received in the Responder Lifetime Notify is below the Windows 2000 configured minimum value. Please fix the policy on the peer machine. SA reaped because QM limit was reached. Key length in certificate is too small for configured security requirements. Max number of established MM SAs to peer exceeded. IKE received a policy that disables negotiation. Reached maximum quick mode limit for the main mode. New main mode will be started. |
|
|
