Troubleshooting

This page discusses possible issues encountered in using the TestDriver in various stages, and suggests how to resolve them.

Installation errors

The following table lists some of the expected issues encountered while installing the TestDriver and the possible solution:

Error codeProblemSolution

-1

Certificate store missing

-6

Not enough capabilities given to the certificate

Use a certificate allowing your capabilities or remove capabilities from your binaries.

-11

Invalid UID

Ensure that all the binaries have valid UIDs (unique and not 0).

-12

UID already exists

Make sure the UID is not in use and uninstall it properly if required.

-20

The SIS file is corrupted

-70320

certificate missing in the certificate store

Check your certificate is registered in the certificate store.

-1010

No vendor found

-10147

The SIS file would overwrite

See Migrating from TestDriver v1.0 for the solution.

-10254

Security error (not signed normally)

Ensure that the SIS package has been properly signed.

-10257

Binary eclipsing

See Migrating from TestDriver v1.0 for the solution.

TEF and STAT installation issues

You can install TEF and STAT by creating one SIS file or by creating two SIS files. The following are some of the TEF and STAT installation issues:

  • Both TEF and STAT depend on INIparser.dll. To install TEF or STAT separately, you must ensure that INIparser.dll is also installed.

  • TEF has no published .pkg file. To install TEF and STAT by creating two SIS files, you must ensure whether INIparser.dll exists in your .pkg file or not to avoid the File Eclipse Error.

    if NOT exists("z:\sys\bin\IniParser.dll") AND NOT exists("c:\sys\bin\IniParser.dll")
    "Z:\EPOC32\RELEASE\ARMV5\UREL\iniparser.dll"-"!:\sys\bin\iniparser.dll"
    endif
  • If you install TEF and STAT by creating two SIS files, you must uninstall them with the last in first out sequence. For example, if you install TEF after installing STAT then you must uninstall TEF first, else uninstalling of STAT removes INIparser.dll, and TEF can not work.

STAT issues

The following are some of the STAT related issues.

  • Ensure that stat.dll and SymbianUsb.dll files are copied to your path at least from Symbian OS v9.2 onwards.

  • When running the TestDriver on Symbian OS v8.1b and v9.1, ensure that you use Symbian OS v9.2 or above.

    Note: Do not use the stat.dll from v8.1b and v9.1 versions.

  • Look for the error codes header file for a list of potential STAT errors.

WINTAP issues

The following are some of the issues encountered while installing the WINTAP.

  • A device driver and the CommDB to be set up on the device

  • For each new baseline, the WinTap must be reinstalled on the device.

BuildROM issues

The following are some of the issues encountered while building the ROM.

  • Use the following build command to run the TestDriver:

    buildrom -D_EABI=ARMV5 -DRVCT -D_STARTUPMODE2 -DUSE_STRONG_CRYPTOGRAPHY h2 techview_statapi platsec
  • When you include testexecute.iby, or similar in the ROM, switch TestExec to OFF by running the following command:

    TestDriver.cmd config --testexec OFF

    If testexecute.iby is not included in the ROM, run the following command:

    TestDriver.cmd config --testexec ON

TEF issue

TestExecute stops running when panic, -263 is reported. This is because TEF is unable to connect to the Domain Manager when used with S60 development kits, as S60 development kits do not support domain startup libraries. You can avoid this panic, by setting the SystemStarter option to OFF in the testexecute.ini file so that TEF does not read or check system state at startup. For more information, see SystemStarter option in TEF Configuration section.

Configuration issues

To avoid the common errors while configuring TestDriver, ensure the following conditions are met:

  • Configure the TestDriver and the logging.properties file

  • Use PlatSec: ON and Kernel: EKA2 for all builds from v9.1 onwards

  • Use PlatSec: OFF and Kernel: EKA1 for all 8.1b- builds

  • Use sysbin: ON only with STATLite

  • Use TestDriver.cmd --clear to clear your configuration

  • Use TestDriver.cmd --export aFile.xml to save or export your configuration to a file

  • Use TestDriver.cmd --import aFile.xml to import a previously saved configuration