Messages 27261 Through 27280

Message Code 27262

Pending concurrent group detected and reset at the end of the Init section

The Init section includes the web_start_concurrent_group call, but is missing the web_end_concurrent_group call. The pending concurrent group is reset.

Troubleshooting

• Add the web_end_concurrent_group call to the relevant place in the Init section.

Message Code 27266

Pending web requests detected at the end of iteration number 'iteration number', but there is no active concurrent group

The specified iteration number ended, but there are still active web requests that were not performed during the iteration. This situation is allowed within a concurrent group, but there is no concurrent group active.

Troubleshooting

• Check which requests were not performed. If a pending (unperformed) request is not critical, include "Resource=1" in one of its parameters, or delete the request from the script.
• If an unperformed request is critical, contact customer support.

Message Code 27267

Pending web requests detected at the end of the Virtual User but there is no active concurrent group

The Virtual User run ended, but there are still active web requests that were not performed during replay. This situation is allowed within a concurrent group, but there is no concurrent group active.

Troubleshooting

• Check which requests were not performed. If a pending (unperformed) request is not critical, include "Resource=1" in one of its parameters, or delete the request from the script.
• If an unperformed request is critical, contact customer support.

Message Code 27268

Pending web requests detected at the end of the Init section, but there is no active concurrent group

The Init section ended, but there are still active web requests that were not performed during the Init Section. This situation is allowed within a concurrent group but there is no concurrent group active.

Troubleshooting

• Check which requests were not performed. If a pending (unperformed) request is not critical, include "Resource=1" in one of its parameters, or delete the request from the script.
• If an unperformed request is critical, contact customer support.

Message Code 27269

A concurrent group is active at the end of iteration number 'iteration number'

The iteration number ended, but a section of the script that includes the web_start_concurrent_group call is missing the web_end_concurrent_group call.

Troubleshooting

• Add the web_end_concurrent_group call to the relevant section in the script.

Message Code 27270

A concurrent group is active at the end of the Virtual User run

The script contains a web_start_concurrent_group call, but is missing the web_end_concurrent_group call.

Troubleshooting

• Add the web_end_concurrent_group call to the appropriate place in the script.

Message Code 27271

A concurrent group is active at the end of the Init Section

The Init section contains a web_start_concurrent_group call, but is missing the web_end_concurrent_group call.

Troubleshooting

• Add a web_end_concurrent_group call to the Init section where the logic concurrent group ends.

Message Code 27272

The 'argument' argument is missing or empty

The specified argument is missing, or its value is an empty string.

Troubleshooting

• If logging is enabled, check that it is set at the required level. Check the log file for messages that may help resolve the error.
• Enable the logging option: In VuGen, select Replay > Runtime Settings > General: Log. Select the Enable logging check box, click Extended log, and select all the extended logging options. Rerun the script, and check the Execution log for messages that may help resolve the error.

Message Code 27273

See the message(s) for these condition(s) in file 'filename'

Troubleshooting

• If logging is enabled, check that it is set at the required level. Check the log file for messages that may help resolve the error.
• Enable the logging option: In VuGen, select Replay > Runtime Settings > General: Log. Select the Enable logging check box, click Extended log, and select all the extended logging options. Rerun the script, and check the Execution log for messages that may help resolve the error.

Message Code 27274

To see the message(s) for these condition(s), rerun with logging enabled for this severity

Additional information is only available if the logging option is enabled.

Troubleshooting

• Enable the logging option: In VuGen, select Replay > Runtime Settings > General: Log. Select the Enable logging check box, click Extended log, and select all the extended logging options. Rerun the script, and check the Execution log for messages that may help resolve the error.

Message Code 27275

Condition(s) of severity 'severity level' raised for a virtual user in the current PROCESS, but not necessarily in the current THREAD

There was a problem that raised the severity level for the current user.

Troubleshooting

• If logging is enabled, check the log file for messages that may help resolve the error.
• If logging is disabled, enable it: In VuGen, select Replay > Runtime Settings > General: Log. Select the Enable logging check box, click Extended log, and select all the extended logging options. Rerun the script, and check the Execution log for messages that may help resolve the error.

Message Code 27276

Could not create Controller sync file

Failed to create Controller sync file. This file is required for activating the runtime viewer feature. The file should be created in the Vuser result directory. Possible causes:

• The iteration directory was obtained by another process.
• The iteration directory was locked for writing.
• Internal error.

Troubleshooting

• Check for other processes using the iteration directory.
• Check that the iteration directory has the correct write permissions.
• Disable the runtime viewer: In VuGen, select Tools > Options > Scripting > Replay, and clear the Show runtime viewer during replay check box.

Message Code 27277

Result directory already exists

The result directory already exists and cannot be overwritten. The result directory is used for one (or more) of the following features: Correlations, runtime viewer, and the Summary report. Possible causes:

• The iteration directory was obtained by another process.
• The iteration directory was locked for writing.
• Internal error.

Troubleshooting

• Check for other processes using the iteration directory.
• Check that the iteration directory has the correct write permissions.
• Disable correlation: Edit the settings under Record > Recording Options > Correlations > Configuration.
• Disable the runtime viewer: In VuGen, select Tools > Options > Scripting > Replay, and clear the Show runtime viewer during replay check box.

Message Code 27278

Cannot obtain result directory name

Unable to obtain the result directory name. The result directory is used for one (or more) of the following features: Correlations, runtime viewer, and the Summary report. Possible causes:

• The iteration directory was obtained by another process.
• The iteration directory was locked for writing.
• Internal error.

Troubleshooting

See the troubleshooting suggestions for Message Code 27277

Message Code 27280

os_mkdir failed (rc='return code') for iteration number 'iteration number'

Failed to create the iteration directory for the specified iteration number. The iteration directory is located under the Vuser result directory. The result directory is used for one (or more) of the following features: Correlations, runtime viewer, and the Summary report. Possible causes:

• The iteration directory was obtained by another process.
• The iteration directory was locked for writing.
• Internal error.

Troubleshooting

See the troubleshooting suggestions for Message Code 27277