3

The SMTP server returned an invalid response. This error indicates that SRM could not recognize the response that the server returned. For more information, refer to any of the following error logs:

• %SystemRoot%\windows\system32\sysedge.log (Windows systems) or syslog files (UNIX)
• SystemEDGE-install-directory\sysedge\plugins\svcrsp\jcollector.log (Windows) or SystemEDGE-install-directory/plugins/svcrsp/jcollector.log (UNIX)

421

The domain service is not available. Closing the transmission channel. This error indicates that your SMTP server is not running.

432

A password transition is needed. This error indicates a problem with your SMTP server. Check the configuration settings. (SRM does not provide a password or user account for testing the SMTP service.)

450

Requested mail action not taken: mailbox unavailable; ATRN request refused. This error indicates that you specified an invalid mail recipient on the Modify Test page. For more information, refer to SMTP Tests.

451

Requested action aborted: local error in processing; Unable to process ATRN request now. This error indicates a problem with your SMTP server. Check the server configuration settings.

452

Requested action not taken: insufficient system storage. This error indicates that your SMTP server does not include enough disk space to store the messages the test is sending. Check the available space and, if necessary, add more, or configure your tests to use a different server.

453

You have no mail. This is an informational message. SRM does not check the mail in an SMTP account.

454

TLS not available temporarily; Encryption is required for the requested authentication mechanism. This error indicates a problem with your SMTP server configuration. SRM does not use authentication for the SMTP test.

458

Unable to queue messages for node. This error indicates a problem with your SMTP server configuration.

459

Node node not allowed: reason. This error indicates a problem with your SMTP server configuration.

500

Command not recognized: command; Syntax error. This error indicates that you are using a non-standard SMTP server that cannot recognize the SRM commands.

501

Syntax error. No parameters allowed. This error indicates that you are using a non-standard SMTP server that cannot recognize the SRM commands.

502

Command not implemented. This error indicates that you are using a non- standard SMTP server that cannot recognize the SRM commands.

503

Bad sequence of commands. This error indicates that you are using a non- standard SMTP server that cannot recognize the SRM commands.

504

Command parameter not implemented. This error indicates that you are using a non-standard SMTP server that cannot recognize the SRM commands.

521

Machine does not accept mail. This error indicates that you specified an invalid mail recipient on the Modify Test page. For more information, refer to SMTP Tests.

530

Must issue a STARTTLS command first; Encryption is required for the requested authentication mechanism. This error indicates a problem with your SMTP server configuration. SRM does not use authentication for the SMTP test.

534

The authentication mechanism is too weak. This error indicates a problem with your SMTP server configuration. SRM does not use authentication for the SMTP test.

538

Encryption is required for the requested authentication mechanism. This error indicates a problem with your SMTP server configuration. SRM does not use authentication for the SMTP test.

550

Requested action not taken: mailbox unavailable. This error may indicate that you specified an invalid mail recipient on the Modify Test page. For more information, refer to SMTP Tests.

551

User not local; please try forwardpath. This error may indicate that you specified an invalid mail recipient on the Modify Test page. For more information, refer to SMTP Tests.

552

Requested mail action aborted: exceeded storage allocation. This error may indicate that you need to delete mail from the account of the mail recipient you specified on the Modify Test page. For more information, refer to SMTP Tests.

553

Requested action not taken: mailbox name not allowed. This error indicates that you specified an invalid mail recipient on the Modify Test page. For more information, refer to SMTP Tests.

554

Transaction failed. This error indicates that you specified an invalid mail recipient on the Modify Test page, or that the SMTP server is experiencing difficulties. For more information, refer to SMTP Tests and check your SMTP server configuration.

1

Too big.

2

No such name. This error indicates that you specified an incorrect OID on the Modify Test page. For more information, refer to SNMP Tests.

3

Bad value. This error indicates that the object you are querying returned an invalid value. This indicates a problem with the object you are querying.

4

Read only. This error indicates that the object you are querying is read-only. This message is informational only. SRM does not attempt to set values for MIB objects.

5

General error. For more information, refer to any of the following error logs:

• %SystemRoot%\windows\system32\sysedge.log (Windows) or syslog files (UNIX)
• SystemEDGE-install-directory\sysedge\plugins\svcrsp\jcollector.log (Windows) or SystemEDGE-install-directory/plugins/svcrsp/jcollector.log (UNIX)

6

General error. For more information, refer to any of the following error logs:

• %SystemRoot%\windows\system32\sysedge.log (Windows) or syslog files (UNIX)
• SystemEDGE-install-directory\sysedge\plugins\svcrsp\jcollector.log (Windows) or SystemEDGE-install-directory/plugins/svcrsp/jcollector.log (UNIX)

7

Cannot bind to a socket. This error may result from invalid permissions for the registry on the target system. Check the system configuration settings.

8

Socket timeout on receive. This error may result from invalid permissions for the registry on the target system. Check the system configuration settings.

9

Cannot create outgoing packet. This error indicates a problem with SRM. For more information, refer to the system log files: %SystemRoot%\windows\system32\sysedge.log (Windows) or syslog files (UNIX).

10

Cannot decode incoming packet. This error indicates a problem with SRM. For more information, refer to the system log files: %SystemRoot%\windows\system32\sysedge.log (Windows) or syslog files (UNIX).

1

General error. For more information, refer to any of the following error logs:

• %SystemRoot%\windows\system32\sysedge.log (Windows) or syslog files (UNIX)
• SystemEDGE-install-directory\sysedge\plugins\svcrsp\jcollector.log (Windows) or SystemEDGE-install-directory/plugins/svcrsp/jcollector.log (UNIX)

2

The JDBC driver may not be installed in jre/lib/ext. Verify that the JDBC driver for your database exists in the jre/lib/ext directory. If not, copy it there.

3

Java SLQ exception occurred. For more information, refer to the jcollector.log file, which is located in the SystemEDGE-install-directory\sysedge\plugins\svcrsp (Windows) or SystemEDGE-install-directory/plugins/svcrsp directory (UNIX)

1

General error. For more information, refer to any of the following error logs:

• %SystemRoot%\windows\system32\sysedge.log (Windows) or syslog files (UNIX)
• SystemEDGE-install-directory\sysedge\plugins\svcrsp\jcollector.log (Windows) or SystemEDGE-install-directory/plugins/svcrsp/jcollector.log (UNIX)

2

Socket timeout on receive. This error may result from invalid permissions for the registry on the target system. Check the system configuration settings.

3

Operation on TFTP client failed. This error could indicate that you specified an incorrect path to the file you want to read or write on the Modify Test page, or that the configuration on the TFTP server is incorrect. For more information, refer to TFTP Tests, or check your system configuration settings on the TFTP server.

300

Unable to get process token. This error indicates that SRM cannot communicate with the system where the test should run. The problem may be with Service Availability attempt to log in as another user. For more information, refer to any of the following error logs:

• %SystemRoot%\windows\system32\sysedge.log
• SystemEDGE-install-directory\sysedge\plugins\svcrsp\sarunas.log
• SystemEDGE-install-directory\sysedge\plugins\svcrsp\jcollector.log

301

Unable to adjust token privileges. This error indicates that SRM cannot communicate with the system where the test should run. For more information, refer to any of the following error logs:

• %SystemRoot%\windows\system32\sysedge.log
• SystemEDGE-install-directory\sysedge\plugins\svcrsp\sarunas.log
• SystemEDGE-install-directory\sysedge\plugins\svcrsp\jcollector.log

302

Unable to log in user. This error indicates that sarunas.exe file is not installed in the drive:sysedge\plugins\svcrsp\sarunas.log directory, or that you specified an incorrect user name or password on the Modify Test page. For more information, refer to Virtual User Tests and the SystemEDGE-install-directory\sysedge\plugins\svcrsp\sarunas.log file.

303

Unable to give user desktop access. This error indicates that you did not enable SNMP to interact with the desktop. For more information, refer to Enabling the SNMP Service to Interact with the Desktop.

304

Process creation failed. For more information, refer to any of the following error logs:

• %SystemRoot%\windows\system32\sysedge.log
• SystemEDGE-install-directory\sysedge\plugins\svcrsp\sarunas.log
• SystemEDGE-install-directory\sysedge\plugins\svcrsp\jcollector.log

Custom

The fourth argument that is returned from the custom test script. (The first three arguments are the DNS resolution time, connection time, and transaction time.)

HTTP and HTTPS

If the test specifies a value for Search Expression, this field provides the number of times that the test matched the search expression on the target page.

Virtual User

If the value of the Error Codes field is 2, this field indicates the exit code that the taskexec.exe application returned.