Share via

Troubleshooting Application Execution (SP Only)

  • Article

Application execution may fail due to the configuration of operating system security on Windows Mobile-based Smartphones, as follows:

  • If the application security configuration requires signed binary files and the application binary files are unsigned, the application does not run. You can sign the files or modify the security configuration by changing security policy settings to enable the application to run.

    You use the SecurityPolicy Configuration Service Provider to determine the current setting for a security policy. For information about the security configurations, see Application Security.

  • If you've signed the application binary files and either the files or the certificate used to sign the files is included in the revocation list, the application does not run. The revocation list contains the hashes of revoked certificates and binary files, as well as .cab files.

    You use the LoaderRevocation Configuration Service Provider to obtain a listing of the binary file and certificate hashes included in the revocation list and to remove a hash from the list. You generate the hash of a binary file or certificate using the Revoke.exe application. The application is located at C:\Program Files\Windows CE Tools\wce<version>\SMARTPHONE 2003\Tools.

  • If you've signed the application binary files and the certificate chain used to sign the file does not map to a root certificate in one of the following certificate stores, the application might not run, depending on the Unsigned Applications policy setting. You can add a matching root certificate to one of the stores to enable the application to run.

    • Privileged Execution Trust Authorities
    • Unprivileged Execution Trust Authorities

See Also

Creating the Provisioning XML for Signed Binary Files | Application Security

Last updated on Friday, April 22, 2005

© 2005 Microsoft Corporation. All rights reserved.

Send feedback on this topic to the authors.