Loadtester Incorporated have a wide collection of articles, whitepapers, PowerPoint's, Word Documents and PDF files all dealing with load testing, stress testing, and capacity planning.  You need not be unexperienced LoadRunner or Performance Tester to fully appreciate the articles.  Some of the resources that I find particularly useful are articles that cover counters for MS SQL 2000, Citrix, RDP Protocol Basics, WinSock Protocol and VTS. There are two links of resources to be precise, one to the articles written by the company.  The other to the library.  Click the below link to access the resources.

• Article
• Library

To configure Sybase database monitoring, we will require ASE Monitoring Server (not the ASE) to be installed on the Controller (refer to "How does the monitoring work in LoadRunner?" for monitoring concepts). Furthermore, we will require an additional DLL in Controller for it to work. From the Monitor Reference, the DLL is named, libct.dll. That is for version 12. While in version 15, it's named libsybct.dll. ASE in short for Adaptive Server Enterprise is a database product from Sybase. To get the latest copy of the ASE server can be obtained from the Sybase website.

Error -27740: Overlapped transmission of request to "www.url.com" for URL "http://www.url.com/ProdApp/" failed: WSA_IO_PENDING

What is WSA_IO_PENDING? WSA_IO_PENDING 997, is a Windows Socket error that is returned by the WSAGetLastError function. It is non-LoadRunner error like "Error -27728: Step download timeout (999 seconds) has expired when downloading non-resource(s)" or "Connection to load generator failed. Error: Process "lr_bridge.exe" was not created. Reason: - communication error. [MsgId: MERR-29996]", etc. The error means the overlapped operations will complete later. From Windows Socket perspective, the application has initiated an overlapped operation that cannot be completed immediately.

The NoClassDefFoundError for Java-RMI protocol. There are several possibilities that this error occur such as (a) incomplete configuration of the Java environment requirements (refer to "Working with RMI-Java"), (b) incomplete reference to the Java libraries (usually located in {loadrunner-installation}\classes and {loadrunner-installation}\classes\srv after the required copy of the application's Java classes are placed in them) and (c) incorrect -Xbootclasspath to inform VUgen to point to the Java libraries for recording.

The error message that is thrown upon when the bootclasspath was not specified in the recording options is shown below: