• If the server's MaxNodesPerWrite is the same as the MaxArrayLength, the server side stack will reject the request and return BadEncodingLimitsExceeded; this should be expected by the script in addition to BadTooManyOperations ("Write() failed, status: BadEncodingLimitsExceeded (0x80080000)")
• If the server returns BadTooManyOperations, the CTT should not expect the number of results to be equal to the number of requests (the server returns no results if the service level result is bad) ("The number of results does not match the number of NodesToWriteService.")

ALEX: We actually see this as an error in the server. The server shall only expose a MaxNoderPerWrite which it is capable of doing. The client doesn't need to take additional operation limits into consideration.

HANNES: We don‘t agree, as the server exposes the exact value it is capable of doing. It is only the error code which is different when exceeding this value, there the CTT should also accept OpcUa_BadEncodingLimitsExceeded