For the Appeon .NET version, after errors occur at runtime, the scenario cannot run correctly as before.
Phenomena: The following errors are reported in the server log:
2006-08-17 14:41:36.609 : Object reference not set to an instance of an object. at Appeon.Server.Commands.CommitCommand.Execute() at Appeon.Server.Commands.Command.ConstructAndExecute(CommandData commandData) at Appeon.Server.Services.Controller.JRouterImpl.ExecuteInTransaction (CommandData commandData) at Appeon.Server.Services.Controller.JRouterImpl.ExecuteCommand (HttpResponse response, CommandData superCommand, SessionAccessInfo session) at Appeon.Server.Services.Controller.JRouterImpl.Call(CommandData superCommand, HttpRequest request, HttpResponse response) at Appeon.Server.Services.Controller.JRouterImpl.Call(Int32 clientType, Object requestData, Hashtable clientContext)
LoadRunner will report the following error:
Action1.c(190): Error: Page download timeout (120 seconds) has expired.
Solution: Restart IIS, SQL Server, and LoadRunner.
Check the PowerBuilder source code and change autocommit=false to autocommit=true, or move the Commit operation after the Retrieve operation, so as to ensure the commit operation will be executed for every retrieval.