10

General error. 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)

11

Cannot bind to a socket. This error indicates that the socket on the mail server you are testing is unavailable.

12

Socket timeout on receive. This error indicates that the socket on the mail server you are testing is unavailable.

13

Login failed. This error may indicate a problem with the IMAP mail server, or it may indicate that the user name and password you have configured are incorrect. You can specify a different user name and password on the Modify Test page. For more information, refer to IMAP Tests.

14

Selecting the inbox failed. This error may indicate a problem with the IMAP mail server, or it may indicate that the user name and password you have configured for the account you are testing are incorrect. You can specify a different user name and password on the Modify Test page. For more information, refer to IMAP Tests.

15

The inbox is empty. This error indicates that you have not sent mail to your test account, so the test cannot download any emails. Reconfigure your test email account so that it contains email. If you selected Delete All Messages when you configured the test, you must ensure that you are sending more email to the account before the next time you run the test.

16

Reading from the inbox failed. This error may indicate a problem with the IMAP mail server.

17

Message flag change failed. This error indicates that the email did not appear as read or deleted, depending on the operation you were performing. Check the configuration of your IMAP mail server.

18

Message removal failed. This error indicated that the test was not able to delete messages, even though you selected Delete Downloaded Messages on the Modify Test page. Check the configuration of your IMAP mail server.

19

Cannot find message by subject. This error indicates either that the mail server cannot perform filtering or that a message with the subject on which you are searching does not exist. Check your IMAP mail server and the user account.

20

Cannot connect to the server.

50

Bad arguments; Internal jcollector error.

200

Bad hostname. DNS lookup failed. This error may indicate that you provided an incorrect MAPI server name when you created the test. You can modify the name on the Modify Test page. For more information, refer to MAPI Tests.

210

MAPI login failed. This error may indicate that you provided an incorrect user name or password when you created the test. You can modify the name on the Modify Test page. For more information, refer to MAPI Tests.

211

MAPI logoff failed. This error may indicate a MAPI server problem.

220

Failed to initialize MAPI. This error may indicate a problem with your MAPI server. Check your server configuration.

221

Failed to open user's Message Store. This error may indicate a problem with your MAPI server. Check your server configuration.

222

Failed to open user's Content table. This error may indicate a problem with your MAPI server. Check your server configuration.

223

Failed to open Global Message Store table. This error may indicate a problem with your MAPI server. Check your server configuration.

224

Failed to set search columns. This error may indicate a problem with your MAPI server. Check your server configuration.

225

Query table columns failed. This error may indicate a problem with your MAPI server. Check your server configuration.

226

Unable to get row count. This error may indicate a problem with your MAPI server. Check your server configuration.

227

Unable to find default received folder. This error may indicate a problem with your MAPI server. Check your server configuration.

228

Unable to open folder. This error may indicate a problem with your MAPI server. Check your server configuration.

229

Memory allocation (malloc) failed. Check your server configuration.

230

Message store is NULL. This error may indicate a problem with your MAPI server. Check your server configuration.

231

Unable to reset row position. Check your server configuration.

240

User's mailbox not found. This error may indicate that you provided an incorrect user name or password on the Modify Test page. For more information, refer to MAPI Tests.

241

User has no mail to read. This error may indicate that you did not create mail for the account that is being tested or that you did not send new mail after the test deleted all messages in the account. Verify that you are sending mail to the account that the test can download. For more information, refer to MAPI Tests.

242

Message not found. SRM does not search for specific messages. This error may indicate a problem with your MAPI server. Check your server configuration.

243

Test timed out. You can set a different timeout value on the Modify Test page. For more information, refer to MAPI Tests.

250

Unable to delete mail. This error may indicate a problem with the MAPI server or with the user account permissions. Check your MAPI server settings and user account administration.

260

MAPI profile exists. This error may indicate a problem with your MAPI server. Check your server configuration.

261

Unable to create dynamic profile. This error may indicate a problem with your MAPI server. Check your server configuration.

262

Unable to delete dynamic profile. This error may indicate a problem with your MAPI server. Check your server configuration.

1

General error. 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)

2

The nis.jar file may not be installed in jre/lib/ext. Check the jre/lib/ext directory. If the nis.jar file is not there, copy it to that directory.

3

The domain may not be correct. You can specify a different domain name on the Modify Test page. For more information, refer to NIS Tests.

4

Cannot find the host. This error can indicate that the NIS server you are querying is unavailable, or that the test is using an incorrect server name. You can modify the NIS server name on the Modify Test page. For more information, refer to NIS Tests.

5

The map file name may be incorrect. You can specify a different map file on the Modify Test page. For more information, refer to NIS Tests.

400

Service discontinued. This error indicates that the NNTP service was discontinued on this server. Check the server configuration settings.

411

No such news group. SRM does not query specific news groups, so this error indicates a problem that is unrelated to SRM.

412

No newsgroup has been selected. SRM does not query specific news groups, so this error indicates a problem that is unrelated to SRM.

420

No current article has been selected. SRM does not query specific news groups, so this error indicates a problem that is unrelated to SRM.

421

No next article in this group. SRM does not query specific news groups, so this error indicates a problem that is unrelated to SRM.

422

No previous article in this group. SRM does not query specific news groups, so this error indicates a problem that is unrelated to SRM.

423

No such article number in this group. SRM does not query specific news groups, so this error indicates a problem that is unrelated to SRM.

430

No such article found. SRM does not query specific news groups, so this error indicates a problem that is unrelated to SRM.

435

Article not wanted; do not send it. SRM does not query specific news groups, so this error indicates a problem that is unrelated to SRM.

436

Transfer failed; try again later. SRM does not transfer data for the NNTP test, so this error indicates a problem that is unrelated to SRM.

437

Article rejected; do not try again. SRM does not query specific news groups, so this error indicates a problem that is unrelated to SRM.

440

Posting not allowed. SRM does not post information for the NNTP test, so this error indicates a problem that is unrelated to SRM.

441

Posting failed. SRM does not post information for the NNTP test, so this error indicates a problem that is unrelated to SRM.

500

Command not recognized. This error may indicate that you are using a non-standard NNTP server that SRM does not support.

501

Command syntax error. This error may indicate that you are using a non- standard NNTP server that SRM does not support.

502

Access restriction, or permission denied. This error may indicate that the NNTP service is not running on the port you specified on the Modify Test page. For more information, refer to NNTP Tests.

The error may also indicate that your NNTP server requires a login, which the SRM test does not perform. Check the system settings on your NNTP server.

503

Program fault; command not performed. This error may indicate that you are using a non-standard NNTP server that SRM does not support.

1

Negative payload. This error indicates that the payload you specified for the ping test is an invalid (negative) number. You can modify this value on the Modify Test page. For more information, refer to Ping Tests.

0

The POP3 server returned +OK. This message indicates the query worked. It is informational only.

1

The POP3 server returned -ERR. This error indicates that the query did not work. 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)

2

The POP3 server returned an invalid response. This error indicates that SRM could not recognize the response that the server returned (whether the test succeeded or failed). 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)

101

A structural error in the configuration file detected.

102

Value of plugin is not equal to svcrsp.

103

The passed configuration file could not be opened for reading.

104

Value of path is empty.

105

Decryption of the configuration file failed.

106

Unspecified error during file processing.

107

Unsupported parameter found.

108

Unexpected value of the mode parameter.

109

The given configuration file does not exist.

110

Launching Jcollector failed.

111

The given Java executable is missing.

112

Value of the parameter is too long. It will be cut during processing.

113

There is no version indication in the configuration file.

114

Unsupported version of the configuration file.

201

Duplicate monitor index found (in the test definition block) .

202

Duplicate monitor template definition name found (in the monitor template definition block).

203 (1)

Invalid value of the parameter monAttribute. Not all attributes are allowed to be monitored.

205 (2)

Invalid value of the parameter monOperator.

206 (3)

Invalid value of the parameter monSeverity.

208

Monitor template name (monName) is missing.

209

Monitor template threshold (monThreshold) is missing.

210

Monitor template operator (monOperator) is missing.

211

Monitor template attribute (monAttribute) is missing.

301

Duplicate test index found.

302

Test interval is lower than the pre-defined minimum. Test interval will be adjusted to the pre-defined minimum.

303

Non-existent monitor template referred from a test.

304

Invalid value of another parameter within test definition.

305

Not allowed value of the parameter “samples”; must be an integer.

306

Not allowed value of the parameter “status”.

307

Not allowed value of the parameter “timeout”; must be an integer, smaller or equal to the value of “interval”.

308

Not allowed value of the parameter “window”; must be an integer.

309

Destination attribute missing.

310

Test name missing.

311

Test type missing.

312

Test index missing.

313

Invalid reserved range of test indices.

314

Invalid test index.