Hmm, yes I can see that assumption/expectation at the top of each of those files you specified.

In the case of scripts 5.9.4-007 and 5.9.4-010 you can adjust these scripts yourself to avoid the use of unsigned integers as follows:

5.9.4-007:
Find:
var linkedItemSetting = NodeIdSettings.GetAScalarNodeIdSetting( NodeIdSettings.ScalarStatic(), "u" );

Fix:
replace "u" with "d"; you are then replacing "unsigned" with "decimal".

5.9.4-010:
Find:
var linkedItemSetting = NodeIdSettings.GetAScalarNodeIdSetting( NodeIdSettings.ScalarStatic(), "u" );

Fix:
again, replace "u" with "d".

5.9.4-020:
Not quite so easy in this case. You may just need to force a specific node here instead of just acquiring a node of any type (as is currently the case).

Find:
var triggeringSetting = NodeIdSettings.GetAScalarNodeIdSetting( NodeIdSettings.ScalarStaticAll(), "u" );

Fix:
replace the one line (shown above) with these 2 lines (shown below)
var triggeringSetting = new NodeIdSetting();
triggeringSetting.name = "/Server Test/NodeIds/Static/All Profiles/Scalar/Int32";

I am giving you these quick-fixes to help you get back on-track. I will work on these scripts to make them more autonomous. I would like to send you the revised scripts as soon as they are ready, for you to test, if that is ok? I will not be able to start work on these until next week though.

Thank you for your answer.

I understood.

I will try to test our UA server using the scripts which I customized by the means of your answer.

I would like to send you the revised scripts as soon as they are ready, for
you to test, if that is ok?
Of course it is OK.

I've improved the specified scripts so that they will use unique settings. Please check the "Security" branch within SVN, revision 2993.

closed - was fixed in very old release - never reviewed, but code works correctly now