Troubleshooting Installation Errors
From Symbian Developer Community
This article is aimed at application developers. It provides general checklist, for preparing your application for installation, and a troubleshooting guide for the most common native software installer errors.
General Checklist
To prepare your device and application for installation, you need to make sure that:
- the device date is correct.
- the installation package is Symbian OS 9.x compatible.
- the binaries in the installation package are suitable for the target environment (i.e. there are no winscw binaries).
- the installation package is signed (self-signed or certified). You can check the signature by running signsis.exe with the "-o" option.
- the installation package file does not contain invalid paths or file names. These include:
- paths to private folders belonging to other processes
- paths to read-only drives (namely Z:\)
- file names which match (or are likely to match) the name of a binary already on the device (file name clash).
- the target drive has enough space for installation.
- the installation package does not attempt to install a file that is already in ROM.
- the installation package does not attempt to install file that was installed by another package.
- the installation package does not install an EXE with a SID with the value of 0.
- the installation package does not install an EXE with a SID which is already in use by other EXE.
- the use a suitable device to install a package signed with a developer certificate.
- the installation package is certified (i.e. not self-signed) if your device's security policy only allows installation of certified applications.
- the installation package is certified if it installs an EXE or DLL with capabilities that cannot be granted by the user.
- the the package UID (pUID) is from the correct range.
Error Messages & Possible Reasons
If you satisfy all of the requirments in the checklist your application might install with no errors. However, Symbian is an open environment and every device is unique.
To make the best use of this guide, and to avoid translation errors, we suggest that you set your device to use use the English language when troubleshooting installation errors. Note: Manufacturers may customize their error messages slightly so the wording might vary slightly between devices. The meaning, however, should remain essentially the same.
"Update error"
This error occurs when an illegal attempt is made to modify an exising file
- The installation package is attempting to overwrite a file that doesn't belong to it.
- A Standard Application (SA) package has the same UID as an already installed one, but uses a different package name (Note: this does not refer to the file name of the SIS file, but the user-visible package name declared inside the PKG file).
- A shared file, such as a resource shared between two applications, is already installed.
- A Partial Upgrade (PU) installation package is attempting to upgrade a pre-installed package.
- A pre-installed app is attempting to overwrite another application that shares same package UID.
- An upgrade package is not trusted to upgrade its base package.
- An augmentation package (SP type) is using same package name as a base package.
- An installation package is attempting to overwrite or save a binary and the security policy doesn't allow it.
"File is corrupted!"
- The installation package is corrupted.
- The installation package contains invalid file name(s).
- A file needed to proceed cannot be found.
- A file to be installed is not a recognized, valid SISX file.
- A version number contains "*" or "-1"
"Unable to install"
- The installation package is attempting to copy a file to a protected location.
- There is more than one executable with the same SECUREID.
- The minimum EPOCHEAPSIZE is bigger than maximum EPOCHEAPSIZE.
- Attempting to install a binary which is not in a valid E32Image format. This may happen if instead of installing the binary from \epo32\release\[armv5|gcce]\[udeb|urel]\ one tries to install the intermediary binary generated under \epoc32\BUILD\...\[armv5|gcce]\[udeb|urel]\ or if WINSCW binaries are packaged for install on device.
"Unable to install. Component is built-in."
- The installation package is attempting to install a file that is already present in firmware and for which eclipsing is not enabled or eclipsing rules have not been follwed.
"Unable to install. Disk not present."
- The target drive is not present.
- The wrong drive has been specified.
"Cannot read file!"
- A file which is needed for installation to proceed cannot be read.
"Cannot delete file!"
- A File cannot be deleted during un/installation. The file to be deleted might be locked by another processes.
"Cannot grant capabilities"
- The installation package has EXEs or DLLs with capabilities that cannot be granted by the signing certificate.
"Certificate check failed. Contact application supplier."
- The installation package is not signed.
- The certificate has an extended key usage (EKU) extension that does not have CodeSigning usage.
- The installation package has been signed with a Publisher ID, and not yet processed by Symbian Signed.
- The signature cannot be validated.
- The certificate chain validation failed.
"Certificate expired"
- The installation package is signed with expired certificate. Make sure that the device has correct date and time set. You might need to format the phone and/or boot it with a SIM card inside.
"Certificate validity dates do not match with the phone's date. Check your date settings."
- The certificate date is invalid (future date). This could be caused by maintenance work on the Symbian Signed web site.
- The device's clock is behind the PC's clock. To play safe always set it a few seconds ahead the PC time.
"Online certificate check could not be conducted. Check your settings."
- The Application Manager settings list an incorrect URL for Online Certificate Status Protocol (OCSP).
- OCSP response signature cannot be validated.
- Invalid OCSP response.
"Online certificate check failed."
- OCSP transport error (request failure).
- OCSP server internal error.
- No OCSP server is specified in Application Manager settings ("Application Manager->Options->Settings->Default web address").
- Client internal error.
- OCSP check is set to "Must be passed" in ("Application Manager->Options->Settings->Online certificate check") and is OCSP response indicates that certificate status in "unknown".
- Certificate is self-signed.
"Certificate revoked"
- OCSP status indicates that certificate is revoked.
"Cannot install. Access denied."
- The target directory/file path is not legal. This usually happens while attempting to install files to a private folder that belongs to another process.
- The installation package uses the FILENULL (FN) option to delete a private folder that belongs to other anprocess.
"Unable to install. Install the base package first."
- The installation packate is attempting to install an upgrade package for a base package that has not been installed.
"Cannot install a protected application from untrusted supplier"
- A self-signed installation package uses a package UID from a protected range ( < 0x80000000 ).
- A self-signed installation package has an EXE that uses a SID from a protected range ( < 0x80000000 ).
- A self-signed installation package has an EXE or DLL that has a non-zero VID (VendorID).
"Unable to install. Constrained by the certificate."
- A Symbian Signed developer certificate constrains device IMEIs, SIDs and VIDs. This specific error message is shown in certain cases such as attempting to install package on a device with different IMEI.
"Application is not compatible with phone. Continue Anyway?"
- Hardware or platform dependency missing. Even passive content compatible with any device must have a hardware dependency statement in the PKG, otherwise this warning appears.
External links
Comments
Sign in to comment…
