Silk Performer reports "Webengine: 42-operation timed out, received second attempt"?
This is an error reported by SilkPerformer when a response has not been received within an expected time.
The likely cause of this is either:
1. The network across which the request / response is delivered was congested or;
2. The server was either too busy, down, did not send a response in time or actively rejected the connection.
To help trouble-shoot this you should first of all monitor the server under test using SilkPerformer's Server Analysis Module. This will help identify is the server's performance under load is the reason for the responses not being received by the client (in this case SilkPerformer).
If the server shows poor performance (e.g high CPU and/or Memory utilization) then you may need to speak to the server administrator in order to tune the server.
If the server shows that it was performing fine under load then the next step is to look at the network.
A tsd file from the LoadTest will provide information in the Summary Internet and Summary Web sections on whether connections were dropped and need to be retried etc.
As any device in the System Under Test (SUT) can cause problems then ideally you should try to bypass one device at a time and try running the test again. This will help identify if one specific device is causing the problem.