Trace

The first information for each trace row is the process and thread id.

This example has two processes 1000 and 2000. It is always useful to search for the Calling application string, to find the real application, this example iid.exe and iidxadm.exe.

Multiple applications calling in the same time may cause some confusion when trying to understand the trace, see 0

Trace Split how to separate the trace for easier understanding.

There are also scenarios where a single application will spawn several threads:

Understanding the difference between processes and threads is not part of this document, but the information is at least available in the trace.

Second part of the trace is the execution time and this information is useful in identifying performance issues.

The example below shows 1 hour, 23 minutes and 45 milliseconds between the trace rows. This time used with functions below will show execution time for each function.

If UseLocalTime is enabled execution time is presented in local time. The example below shows function executed between 1:12 PM and 1:24 PM local time.

Each PKCS#11 function call will start with the function name and end with a standard return value:

From the documentation you will learn C_Initialize is the startup function and CKR_OK means success, everything is as expected. There may be errors instead:

The return value is not CKR_OK, so this means an error. Is this a problem? From the documentation you will learn that this return value actually is more like a warning message, no initialize needed, since already initialized.

Each CSP function call will start with the function name and end with the function name and a Microsoft return value string.

The string OK means success and all other strings mean some kind of failure. The return value from CSP is always true or false, and Windows last error is eventually updated with some error value. If the string is not OK, the string is from Microsoft translation of the Windows last error.

This means an error, despite the text says operation completed successfully. There are scenarios where this is perfectly normal; information will be available from the CSP documentation.

Each minidriver function call will start with the function name and end with the function name and a return value and Microsoft translation of return value.

The value 0x00000000 means success. The difference between CSP and Minidriver is that the return value and return string is always connected, Minidriver calls return the real value compared with CSP which return true or false and update Windows last error.

Each property plugin function call will start with information about the function and the same information string ended with ‘done’ string.

The return value is always done.

The invoke plugin function will start with information about the operation and the same string ended with return value.

The return value is a number and the meaning is documented in chapter 6 Plugin of the Net iD Enterprise Developer’s Guide, see section 6.3 Operations, for each operation.

The trace parse functionality will take a trace file as input and try to parse the content to a more readable format. The functionality is available on all operating systems by calling the application loader:

The result will be a local web site, with starting index.html in same location as the original trace file.

The trace split functionality will take a trace file as input and split the content to one file for each process. The functionality is available on all operating systems by calling the application loader:

The result will be one or more files with name iid_<pid>.txt in same location as the original trace file.

The result will be one or more files with name iid_<pid>_<tid>.txt in same location as the original trace file.