two issues in this one Mantis:

the script should check the array limits and skip test if not supported.

the second issues on error reporting should be broken out into it's own issue and applied in more general terms.

Script is now also allowing a BadEncodingLimitsExceeded as well as handling the StatusCode accordingly.

The CTT can't make use of the max. array size, because there is now way for a client to determine that limitation. Please note that the MaxArraySize in the ServerCapabilities Object is only intended for the limits of Variables not of the Server implementation itself.

The 500 items exceed the Stack Encoding Limits.
Therefore the session is closed with
registerNodes() returned failedBadEncodingLimitsExceeded (0x80080000)
function: Test574Err004
file: C:/temp/uaToolkitEmbedded_1.20.0/CTT/nano/maintree/View Services/View RegisterNodes/Test Cases/Err-004.js
line: 28
function:
file: C:/temp/uaToolkitEmbedded_1.20.0/CTT/nano/library/Base/safeInvoke.js
line: 95
function:
file: C:/temp/uaToolkitEmbedded_1.20.0/CTT/nano/maintree/View Services/View RegisterNodes/Test Cases/Err-004.js
line: 33

The script is now trying to connect to the server again, in case of an error message.
Unfortunately the CTT currently doesn't implement an opportunity to reuse the still available session after the reconnect. But this is a general issue which I created a separate MantisIssue (Id=4683) in order to implement a global reusable solution.
Fix is available in (1.03.341.386)

not fixed in 1.3.341.389
still:
Error: RegisterNodes failed with unexpected ServiceResult: BadEncodingLimitsExceeded (0x80080000)

(there is an improvement, since a new session is opened, the following test cases usually work)

This is a test.

Removed duplicated check.
The error code is already checked in the Helper and therefore we do not need to do that in the script again.

Review in CMP call

error text has been updated (just not noted in solution)