It seems to be the combination of "Security None/007.js" and following tests.

It is fact that this test case does NOT close all opened secure channels and I doubt whether this is intended.

I would replace (in the good case) the line
for( var i=0; i<5; i++ ) if( !CloseSecureChannelHelper.Execute ...
with
for( var i=0; i<createResults.length; i++ ) {
if( createResults[i] ) {
CloseSecureChannelHelper.Execute( { Channel: channels[i],
ServiceResult: new ExpectedAndAcceptedResults( StatusCode.Good ) } );
}
}
for( var i=0; i<createResults.length; i++ ) {
if( !createResults[i] ) {
CloseSecureChannelHelper.Execute( { Channel: channels[i],
ServiceResult: new ExpectedAndAcceptedResults(
StatusCode.BadSecureChannelIdInvalid) } );
}
}

Added a function that will add a delay between each test-script execution. This is checked-into source control and will be in the next release.

The current CTT (1.3.340.380) still has this issue.
The DoS tests (006 and 007 of Security None) still dont wait after test execution.

A simple
UaDateTime.CountDown( { Seconds: 10, Message: "Wait after DoS attack to stabilize system..." } );
in cleanup.js would do...

Some other tests do wait (using PostTestFunctions, e.g. "Security Basic 128Rsa15 / initialize.js"), but here this delay is invoked even if initialize fails (and cleanup is not inbvoked) - different mantis.

Compliance Group Meeting: Adding a wait in the cleanup script.

There were two reasons for this error code. One reason was, when the CTT was exceeding its own channel limitations and the other was when the server didn't get a chance to clean up the SecureChannels from before. Therefore we added some waits and are catching the limitation of the CTT now.

Reviewed in CMP call