Playback Main Topic | Previous
If the Replay directory or the log file(s) are not created, it is generally attributable to two problems:
To correct the second problem, for IIS version 4.0 or later, repeat the steps for configuring the recorder.dll in Installing Playback.
For IIS version 3.0, verify the path for the filter in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters\Filter DLLs.
This section lists several common problems and their solutions.
Site stops working with the Playback tool installed
Connection Errors
Playback.exe uses sockets to connect and make requests against the specified server. If you get errors connecting, it could be one of the following issues:
Playback reports that all the requests fail verification.
Verify that the content of the server you did the recording on is mirrored on the computer you are playing logs against.
If it is mirrored correctly try taking another snapshot, but reduce the recording time.
Playback reports that some of the requests fail verification.
The current client has problems with '100 CONTINUE' response, as during a PUT operation and won't always play the request back correctly. These will be counted as errors. Also, because the Playback client sends all the data from the original request without checking status, it is possible that IIS will return '100 CONTINUE' on large requests with the expected response embedded. The current client does not parse the '100 CONTINUE' message and will therefore count the response as a failure.
Future releases of the client will handle these issues for better and more accurate reporting.