Error codes

This section lists LoadRunner Enterprise errors that are displayed in the output messages window.

For information and suggested solutions for a message, search for the message or code number in the tables below.

Performance test error codes

This table lists performance test errors and their suggested solutions.

Error Code Problem Description / Suggested Solution
0x03000201

The project configuration does not permit the requested Post-Run Action.

Running a test configured to collate results during runtime is prohibited in a project with Post-Run Action set to Do not collate.

Solution: Change the option for collating the run results in Test Options to At end of the test run. For details, see Collate results.

Back to top

Host error codes

This table lists host errors and their suggested solutions.

Error Code Problem Description / Suggested Solution
4003 Failed to reconfigure the specified host machine.  
4010

The provided host is invalid.

Check the installation on the virtual machine. Make sure you have the LoadRunner Enterprise host or OneLG installed on that virtual machine.

4011 The host is already assigned to a tenant.  Make sure your host is not assigned to another tenant.
4012 Unable to create an Over Firewall host because the MI Listener field is empty.

Make sure that an MI Listener was created and assigned to the host. For details, see Specify MI Listeners.

4013 Private hosts (hosts that were added from the LoadRunner Enterprise application or the LoadRunner Enterprise REST API) can be assigned to one host pool only.  A private host cannot be added to multiple pools. Only public hosts can be assigned to multiple pools.
4014 Unable to create the host because a host already exists with the same name. Create the host with a unique name that has not been used in the project.
4015 Unable to edit the host because it is in a non-idle state. Wait until the host is in Idle state before trying to edit it.
4016 The host service is unreachable. Check that the host services are running on the virtual machine.
4017 Unable to change the machine identity.  
4018 No such host is known.  
4020 Failed to delete the selected host machines.  
4021 The selected host is not available.  
4022 Failed to get the selected host pool.  
4024 Unable to check the host ID (the host ID is -1).  
4025 Your Oracle software is missing or is not a supported version (it is earlier than Oracle 8.1.7). Install a supported Oracle version. For details of supported versions, see the Support Matrix.
4026 An error occurred. Check the Oracle settings. Check the Oracle settings.
4027 Failed to parse raw data from the host.  
4028 Failed to change the status for the host.  
4030 Failed to reconfigure this host.  
4031 Unavailable hosts can be changed only by reconfigure. Reconfigure the host to change the host status from Unavailable.
4032 Cannot Change Host that is not in Idle state. Wait until the host is in Idle state before trying to make changes to it.
4033 One or some of the selected hosts are not in "Idle" run-time state. Deselect those or wait for them to become idle. Make sure the selected hosts are in Idle state before trying to reconfiguring them.
4034 A host cannot be rebooted if it is not Idle. Make sure the host is in Idle state before rebooting it.
4035 Host could not be rebooted since there is another timeslot that reserved it in the near future. Make sure the host you want to reboot is not assigned to a timeslot. If it is, wait until the timeslot has finished before rebooting the host.
4036 You do not have permissions to change public hosts.

Tenant Admin users have some restrictions when using public hosts which they do not have when using private hosts.

These include not being able to perform the following:

  • Add, import, delete, or reboot hosts.

  • Configure the LoadRunner Enterprise agent.

  • Change host general settings.

  • Change any of the following host details: Purpose, Status, Host Installation, Source, Priority, Location, MI Listener, or SSL Enabled.

Back to top

Cloud error codes

This section lists errors and suggested solutions for the following types of cloud errors:

General cloud errors

Error Code Problem Description / Suggested Solution
0x04000301 Cloud Account with name <Name> already exists. Use a unique name for each cloud account. For details, see Cloud accounts.
0x05000E00 General error in Cloud Module Check the application logs for more details.
0x05000E01 Cloud Account with name <Name> already exists Use a unique name for each cloud account. For details, see Cloud accounts.
0x05000E05 Cloud Host Template with name <Name> already exists Use a unique name for each cloud host template. For details, see Create an elastic cloud host template.
0x05000E06 Missing Cloud Account ID <ID> Cloud host template validation failed because the referenced cloud account is missing. Make sure the template data is correct and up to date. For details, see Cloud accounts.
0x05000E07 Cloud Account <ID> does not exist Cloud host template validation failed because the referenced cloud account is missing. Make sure the template data is correct and up to date. For details, see Cloud accounts.
0x05000E08 Cloud Account <ID> does not contain any regions Cloud host template validation failed because the cloud account has no regions. Make sure the account data is up to date. For details, see Cloud accounts.
0x05000E09 Cloud Region with id <ID> does not exist Cloud host template validation failed because the referenced region is missing. Make sure the template data is correct and up to date. For details, see Create an elastic cloud host template.
0x05000E0A Cloud Region <Name> from Account <ID> does not contain any instance types Cloud host template validation failed because the referenced region contains no Instance Types (or Virtual Machine Sizes). Make sure the template data is correct and up to date. For details, see Create an elastic cloud host template.
0x05000E0B Instance Type <Name> is missing in Cloud Region <Name> Cloud host template validation failed because the referenced Instance Types (or Virtual Machine Size) is missing from the specified region. Make sure the template data is correct and up to date. For details, see Create an elastic cloud host template.
0x05000E0C Cloud Region <Name> from Account <ID> does not contain any key pairs Cloud host template validation failed because the referenced region contains no key pairs. Make sure the template data is correct and up to date. For details, see Create an elastic cloud host template.
0x05000E0D Missing Keypair ID Cloud Host Template validation failed because the referenced key pair is missing. Make the template data is correct and up to date. For details, see Create an elastic cloud host template.
0x05000E0E Key Pair <Name> is missing in Cloud Region <Name> Cloud host template validation failed because the referenced key pair is missing from the region. Make sure the template data is correct and up to date. For details, see Create an elastic cloud host template.
0x05000E0F Cloud Region <Name> from Account <ID> does not contain any security groups Cloud host template validation failed because the referenced region has no security groups. Make sure the template data is correct and up to date. For details, see Create an elastic cloud host template.
0x05000E10 Security Group <Name> is missing in Cloud Region <Name> Cloud host template validation failed because the referenced region does not contain the referenced security group. Make sure the template data is correct and up to date. For details, see Create an elastic cloud host template.
0x05000E11 Cloud Region <Name> from Account <ID> does not contain any images Cloud Host Template validation failed because the referenced region has no images. Make sure the template data is correct and up to date. For details, see Create an elastic cloud host template.
0x05000E12 Image <Name> is missing in Cloud Region <Name> Cloud host template validation failed because the referenced region does not contain the referenced image. Make sure the template data is correct and up to date. For details, see Create an elastic cloud host template.
0x05000E13 Cloud Region <Name> from Account <ID> does not contain any networks Cloud host template validation failed because the referenced region has no networks. Make sure the template data is correct and up to date. For details, see Create an elastic cloud host template.
0x05000E14 Missing Network ID Cloud host template validation failed because the referenced network is missing. Make sure the template data is correct and up to date. For details, see Create an elastic cloud host template.
0x05000E15 Cloud Network <Name> is missing in Region <Name> Cloud host template validation failed because the referenced region does not contain the referenced network. Make sure the template data is correct and up to date. For details, see Create an elastic cloud host template.
0x05000E16 Cloud Host template <Name> (id=<ID>) is missing Make sure the referenced cloud host template exists. For details, see Create an elastic cloud host template.

AWS errors

Error Code Problem Suggested Solution
0x05000100 General error in Cloud AWS Inspect application logs for more details.
0x05000101 Failed to retrieve AWS regions. Account: <ID>. Reason: <Error Reason>

Make sure the LoadRunner Enterprise server is connected to the network and the Cloud Network Settings are correct (see Configure cloud network settings). Check the error reason for more details.

0x05000102 Failed to retrieve AWS security groups. Region <Name>. Reason: <Error Reason>

Make sure the LoadRunner Enterprise server is connected to the network and the Cloud Network Settings are correct (see Configure cloud network settings). Check the error reason for more details.

0x05000103 Failed to retrieve AWS key pairs. Region <Name>. Reason: <Error Reason>

Make sure the LoadRunner Enterprise server is connected to the network and the Cloud Network Settings are correct (see Configure cloud network settings). Check the error reason for more details.

0x05000104 Failed to retrieve AWS instance types. Region. <Name>. Reason: <Error Reason>

Make sure the LoadRunner Enterprise server is connected to the network and the Cloud Network Settings are correct (see Configure cloud network settings). Check the error reason for more details.

0x05000105 Failed to retrieve AWS images. Region. <Name>. Reason: <Error Reason>

Make sure the LoadRunner Enterprise server is connected to the network and the Cloud Network Settings are correct (see Configure cloud network settings). Check the error reason for more details.

0x05000106 Failed to start AWS instance. Region <Name>. Reason: <Error Reason>

Make sure the LoadRunner Enterprise server is connected to the network and the Cloud Network Settings are correct (see Configure cloud network settings). Check the error reason for more details.

0x05000107 Failed to terminate AWS instance. Region <Name>. InstanceIds: <InstanceIds list>. Reason: <Error Reason>

Make sure the LoadRunner Enterprise server is connected to the network and the Cloud Network Settings are correct (see Configure cloud network settings). Check the error reason for more details.

0x05000108 Failed to get AWS instance. Region <Name> InstanceIds: <InstanceIds list>. Reason: <Error Reason>

Make sure the LoadRunner Enterprise server is connected to the network and the Cloud Network Settings are correct (see Configure cloud network settings). Check the error reason for more details.

0x05000109 Failed to get AWS instance status. Region <Name>, InstanceIds: <InstanceIds list>. Reason: <Error Reason>

Make sure the LoadRunner Enterprise server is connected to the network and the Cloud Network Settings are correct (see Configure cloud network settings). Check the error reason for more details.

0x0500010A Failed to retrieve AWS elastic ips. Region <Name>. Reason: <Error Reason>

Make sure the LoadRunner Enterprise server is connected to the network and the Cloud Network Settings are correct (see Configure cloud network settings). Check the error reason for more details.

0x0500010B Failed to associate AWS elastic ips with instance. Region <Name>, associationId: <ID>, PublicIP: <IP>. Reason: <Error Reason>

Make sure the LoadRunner Enterprise server is connected to the network and the Cloud Network Settings are correct (see Configure cloud network settings). Check the error reason for more details.

0x0500010C Failed to disassociate AWS elastic ips with instance. Region <Name>, associationId: <ID>, PublicIP: “IP’. Reason: <Error Reason>

Make sure the LoadRunner Enterprise server is connected to the network and the Cloud Network Settings are correct (see Configure cloud network settings). Check the error reason for more details.

0x0500010D Failed to retrieve AWS subnets. Region <Name>, subnetIds: <ID>. Reason: <Error Reason>

Make sure the LoadRunner Enterprise server is connected to the network and the Cloud Network Settings are correct (see Configure cloud network settings). Check the error reason for more details.

0x0500010E Account validation failed due to connection failure. Contact your system administrator to verify your cloud network settings certificates validation, or other required network configurations

Make sure the LoadRunner Enterprise server is connected to the network and the Cloud Network Settings are correct (see Configure cloud network settings). Check the error reason for more details.

Azure errors

Error Code Problem Suggested Solution
0x05000301 Azure Network Communication Error. Reason: <Error Reason>

Make sure the LoadRunner Enterprise server is connected to the network and the Cloud Network Settings are correct (see Configure cloud network settings). Verify the license is issued for the current account GUID details.

0x05000302 Failed to retrieve Azure regions. Reason: <Error Reason>

Make sure the LoadRunner Enterprise server is connected to the network and the Cloud Network Settings are correct (see Configure cloud network settings). Check the error reason for more details.

0x05000303 Failed to retrieve Azure virtual machine sizes. Reason: <Error Reason>

Make sure the LoadRunner Enterprise server is connected to the network and the Cloud Network Settings are correct (see Configure cloud network settings). Check the error reason for more details.

0x05000304 Failed to retrieve Azure images. Reason: <Error Reason>

Make sure the LoadRunner Enterprise server is connected to the network and the Cloud Network Settings are correct (see Configure cloud network settings). Check the error reason for more details.

0x05000305 Failed to retrieve Azure virtual networks. Reason: <Error Reason>

Make sure the LoadRunner Enterprise server is connected to the network and the Cloud Network Settings are correct (see Configure cloud network settings). Check the error reason for more details.

0x05000306 Failed to retrieve Azure network security groups. Reason: <Error Reason>

Make sure the LoadRunner Enterprise server is connected to the network and the Cloud Network Settings are correct (see Configure cloud network settings). Check the error reason for more details.

0x05000307 Failed to provision Azure virtual machines. Reason: <Error Reason>. Region: <Name>. Virtual Machine Size: <Name>. Image: <Name>. Tags: <Tags List>

Make sure the LoadRunner Enterprise server is connected to the network and the Cloud Network Settings are correct (see Configure cloud network settings). Make sure the account licenses provide enough credits for the requested performance test setup.

0x05000308 Failed to delete Azure virtual machines. Reason: <Error Reason>. Resource Group: <Name>

Make sure the LoadRunner Enterprise server is connected to the network and the Cloud Network Settings are correct (see Configure cloud network settings). Check the error reason for more details.

0x05000309 Failed to retrieve Azure virtual machines. Reason: <Error Reason>. Resource Group: <Name>

Make sure the LoadRunner Enterprise server is connected to the network and the Cloud Network Settings are correct (see Configure cloud network settings). Check the error reason for more details.

0x0500030A Failed to retrieve Azure virtual machines. Reason: <Error Reason>

Make sure the LoadRunner Enterprise server is connected to the network and the Cloud Network Settings are correct (see Configure cloud network settings). Check the error reason for more details.

0x0500030B Failed to retrieve Azure public ip addresses. Reason: <Error Reason>

Make sure the LoadRunner Enterprise server is connected to the network and the Cloud Network Settings are correct (see Configure cloud network settings). Check the error reason for more details.

0x0500030C Failed to define Azure virtual machine in region <Name>. Reason: <Error Reason>

Make sure the LoadRunner Enterprise server is connected to the network and the Cloud Network Settings are correct (see Configure cloud network settings). Check the error reason for more details.

0x0500030D Failed to define Azure virtual network interface in region <Name>. Reason: <Error Reason>

Make sure the LoadRunner Enterprise server is connected to the network and the Cloud Network Settings are correct (see Configure cloud network settings). Check the error reason for more details.

0x0500030E Failed to get Azure resource group by tag. Reason: <Error Reason>

Make sure the LoadRunner Enterprise server is connected to the network and the Cloud Network Settings are correct (see Configure cloud network settings). Check the error reason for more details.

0x0500030F Failed to get Azure SKUs. Reason: <Error Reason>  
0x05000310 Failed to process Azure SKUs. Reason: <Error Reason>

Make sure the LoadRunner Enterprise server is connected to the network and the Cloud Network Settings are correct (see Configure cloud network settings). Check the error reason for more details.

0x05000311 Failed to associate Public IP <IP> with Virtual Machine <Name>. Reason: <Error Reason>

Make sure the LoadRunner Enterprise server is connected to the network and the Cloud Network Settings are correct (see Configure cloud network settings). Check the error reason for more details.

0x05000312 Failed to get Virtual Machine by resource group <Name> and id <ID>. Reason: <Error Reason>

Make sure the LoadRunner Enterprise server is connected to the network and the Cloud Network Settings are correct (see Configure cloud network settings). Check the error reason for more details.

CloudBurst errors

Error Code Problem Suggested Solution
0x05000201 Failed to add license. Please, make sure the license is valid and the server is accessible. Account: <ID>

Make sure the LoadRunner Enterprise server is connected to the network and the Cloud Network Settings are correct (see Configure cloud network settings). Verify the license is issued for the current account GUID details.

0x05000204 Failed to allocate elastic ips, Count: <Elastic IPs number>, Layout: <Name>. Reason: <Error Reason>

Make sure the LoadRunner Enterprise server is connected to the network and the Cloud Network Settings are correct (see Configure cloud network settings). Check the error reason for more details.

0x05000205 Failed to retrieve elastic ip <IP>. Reason: <Error Reason>

Make sure the LoadRunner Enterprise server is connected to the network and the Cloud Network Settings are correct (see Configure cloud network settings). Check the error reason for more details.

0x05000206 Failed to release elastic ip <IP>. Reason: <Error Reason>

Make sure the LoadRunner Enterprise server is connected to the network and the Cloud Network Settings are correct (see Configure cloud network settings). Check the error reason for more details.

0x05000207 Failed to retrieve transactions. Reason: <Error Reason>

Make sure the LoadRunner Enterprise server is connected to the network and the Cloud Network Settings are correct (see Configure cloud network settings). Check the error reason for more details.

0x05000208 Failed to retrieve purchases. Reason: <Error Reason>

Make sure the LoadRunner Enterprise server is connected to the network and the Cloud Network Settings are correct (see Configure cloud network settings). Check the error reason for more details.

0x05000209 Not enough credits to create instances. Available credits: <Number>. Required credits: <Number>. Host amount: <Number>. Duration: <Number>(min). Account: <ID>

Make sure the LoadRunner Enterprise server is connected to the network and the Cloud Network Settings are correct (see Configure cloud network settings). Check the error reason for more details. Make sure the account licenses provide enough credits for the requested performance test setup.

0x0500020A Failed to update session token. Reason: <Error Reason>

Make sure the LoadRunner Enterprise server is connected to the network and the Cloud Network Settings are correct (see Configure cloud network settings). Check the error reason for more details.

0x0500020B Failed to calculate credit estimation, Query: <String>. Reason: <Error Reason>

Make sure the LoadRunner Enterprise server is connected to the network and the Cloud Network Settings are correct (see Configure cloud network settings). Check the error reason for more details.

0x0500020F Remote server returned error: <Error Reason>

Make sure the LoadRunner Enterprise server is connected to the network and the Cloud Network Settings are correct (see Configure cloud network settings). Check the error reason for more details.

0x05000210 Failed to retrieve layouts. Reason: <Error Reason>

Make sure the LoadRunner Enterprise server is connected to the network and the Cloud Network Settings are correct (see Configure cloud network settings). Check the error reason for more details.

0x05000211 Failed to retrieve layout <Name>. Reason: <Error Reason>

Make sure the LoadRunner Enterprise server is connected to the network and the Cloud Network Settings are correct (see Configure cloud network settings). Check the error reason for more details.

0x05000212 Failed to retrieve elastic ips. Reason: <Error Reason>

Make sure the LoadRunner Enterprise server is connected to the network and the Cloud Network Settings are correct (see Configure cloud network settings). Check the error reason for more details.

0x05000213 Failed to retrieve regions. Reason: <Error Reason>

Make sure the LoadRunner Enterprise server is connected to the network and the Cloud Network Settings are correct (see Configure cloud network settings). Check the error reason for more details.

Back to top