Matching log messages to application pool failures
You can find out how many users were affected by an UNICOM Intelligence Interviewer application pool crash.
The log scope field in each log entry is used to identify the log message origin. The log scope is a string that consists of the process and the logger sequence IDs. Using the log scope, it is possible to determine the number of users who were affected by an application pool crash. For example:
1 In the Windows Event log, find the process ID by examining the application crash event log entries. For example, the following application event was created for the engine crash:
Level Date and Time Source EventID Task Category
Error 2013/4/16 1:42:50 Application Error 000 Application Crashing Events
The general information for this event is provided as follows:
Faulting application name: w3wp.exe, version: 7.5.7601.17514, time stamp: 0x4ce7afa2
Faulting module name: Qsamp.dll, version: 1.1.1.8352, time stamp: 0x4fc3943e
Exception code: 0xc0000005
Fault offset: 0x0000000000019cfc
Faulting process id: 0x19c8
Faulting application start time: 0x01ce397e563dbf67
Faulting application path: c:\windows\system32\inetsrv\w3wp.exe
Faulting module path: C:\Program Files\Common Files\IBM\SPSS\DataCollection\<version>\IOM\Qsamp.dll
In this example, the process ID is 0x19c8.
2 Find the number of users who logged into and out of the Phone Participants activity on the affected engine before its crash:
The log entry in the IVW* logs for a Phone Participants login is of the form:
...Interviewer session '@O-y/WvPz09OkoXfpyahg7gb3Ks' created...
The log entry in the IVW* logs for a Phone Participants login is of the form:
...Interviewer session '@O-y/WvPz09OkoXfpyahg7gb3Ks' closed
By querying the logs in the DMQuery application, it is possible to determine the number of interviewers who were affected by the crash. For example, suppose the crashed engine's process ID, from the Windows Event Log, is 0x860. Find out how many interviewers logged in with the following statement:
select Sum(LogEntry Like 'Interviewer session%created%' ) - Sum(LogEntry like '%Interviewer session%closed') from
VDATA where LogScope like '%0x860'
This calculation is based on the available logs; the count will not be accurate if log files are missing.
3 Similar steps can be used on the Accessories sever to determine the number of users who were affected by an UNICOM Intelligence Interviewer - Server Admin application pool crash.
“Logging on” identifies user log ins to the Phone Participants activity’s CIV* logs.
“Logging off” identifies user log offs from the Phone Participants activity’s CIV* logs.
See also