BPS Wins ED Correspondence Tracking System Software Upgrade PM Support Contract

(October 30, 2018) Business Performance Systems was awarded a contract with the U.S. Department of Education for the acquisition, implementation, and maintenance of the Correspondence Tracking System.  For this effort, BPS will provide IT project management support to help the Executive Secretariat successfully navigate federal IT requirements and agency IT management processes.  This includes coordinating all project activities, managing all lifecycle deliverables, supporting communications and collaboration with stakeholders in both the Exec Sec and the OCIO, supporting the security assessment and ATO process, and supporting software implementation and data migration.

BPS Wins ED On-Line Application System O&M Contract

(September 12, 2018) Business Performance Systems was awarded a task order with the U.S. Department of Education for operations, maintenance, and enhancement of the On-Line Application System (OLAS).  For this effort, BPS provides periodic updates to meet new program requirements, supports the Department’s Lifecycle Management and continuous monitoring processes, and ensures compliance with federal security requirements. Under this award, BPS ensures that OLAS continues to meet the functionality, performance, availability, and security requirements of the Presidential Scholars Program, School Ambassador Fellowship Program, and Student Volunteer Internship Program.

Recovering Corrupted LoadRunner Results

Mastering a tool like LoadRunner requires familiarity not only with its features and functions, but also its quirks and issues.  For example, LoadRunner occasionally runs into a problem while a test scenario is running and any attempt to open the results file throws an error.  We have identified recovery procedures that can save many hours of retesting.  Here are four methods, from simple to complex, that you can try.  Be sure to back up your .lrr folder before attempting any of them.

The first method is to force re-collation of the results.  This can be done by changing “Completed” from 0 to 1 (as needed) in Collate.txt, then invoking the Collate Results controller action.

The second method is to copy the .eve and .map files and log folders from each load generator to the controller .lrr folder, then running Collate Results.

The third method is to manually repair the .lrr file to add missing section separator lines, fix the FullData flag, and add a stop time or scenario duration as needed.

The forth method is to run the same test for a short duration to record control information, then replacing the results with those from the original run.  This requires saving the results in a separate folder, patching the start time to match the original full-length run, replacing the .eve and .map files and log folder with the original results from the load generators, and copying the data from the original .lrr folder to the new one.  It should now be possible to analyze the results.

We love sharing our expertise in LoadRunner.  If you are interested in detailed procedures, please feel free to contact us using our Contact Form.