The requested section was not present in the activation context.

The application has failed to start because its side-by-side configuration is incorrect. Please see the applic

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

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 inst

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-micro

The private manifest probed has crossed a path with an unsupported reparse point.

Two or more components referenced directly or indirectly by the application manifest have files by the same na

Two or more components referenced directly or indirectly by the application manifest have window classes with

Two or more components referenced directly or indirectly by the application manifest have the same COM server

Two or more components referenced directly or indirectly by the application manifest have proxies for the same

Two or more components referenced directly or indirectly by the application manifest have the same COM type li

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

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 : Whitespace 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.