Settings for the Interviewing activity
The Interviewing activity’s Web.config file is in the following folder:
C:\InetPub\wwwroot\SPSSMR\CatiReports
Specifying that reports should not include time filters
Add the report name to the NoFilterReports key. For example:
<appSettings>
<add key="NoFilterReports"
value="InterviewerStatisticsCrossProject;
BusyWaitIdleCrossProject;OverallDisposition;
DialerStatistics"/>
</appSettings>
Avoiding SQL connectivity issues
SQL connectivity issues that cause frequent connection problems might cause partial records in the database, even though the records are complete in the local cache files. This can occur when restarting a survey that was originally started without a respondent database connection. To avoid this problem, especially for projects that require multiple attempts to complete, such as diary studies, you can configure interviews so that they can be started only if the data connection is available.
To use this feature, set the RequireDataModelForInterviews property. It can be set at site level and project level.
▪To allow interviews to start even if the data connection is unavailable, set RequireDataModelForInterviews to 0. In this case, the interview is started from the cache is available. This is the default value.
▪To prevent interviews from starting if the data connection is unavailable, set RequireDataModelForInterviews to 1. In this case, an error is returned:
|
Scenario
|
Result
|
|
Start or restart an interview using a URL that includes authentication sample fields
|
HTTP 500: Participant record authenticated and then moved to the FAILED queue
|
|
Start or restart an interview using a URL that will require the authentication page
|
HTTP 503: Participant record authenticated and then moved to the FAILED queue
|
|
Restart an interview from the cache file. A cache file is used for cases where the respondent presses the Next button after the interview times out.
|
HTTP 503: Participant record not authenticated or changed
|
To customize the HTTP error pages, see
Customizing web service tier error pages.
See also