The null machine was the problem, since it is actually a machine with its own CDL file.
Starting with NX 8 you no longer need a null machine and it was bad practice in the past.
There is now the ability to remove a machine and get back to the default setup starting with NX 8.
Production: NX10.0.3, VERICUT 8.2, FBM, MRL 3.1.7 | TcUA 10.1 MP7 Patch 0 (10.1.7.0) | TcVis 11.4Development: C (ITK), .NET, Tcl/Tk Testing: NX12.0 | AWC 3.4 Preparing: NX12.0Employees of the customers, together we are strong How to Get the Most from Your Signature in the CommunityNX Customization - Best Practice Guide
Glad to see you have a "solution".
It was not the setup libray or configuration - I think you are correct about the machine tool.
We added the command to Remove Machine, which makes it GENERIC_MACHINE..
Prior to that you had to replace the machine with the NULL machine, but it was not the same as never having had a machine.
So perhaps the fact that there is a machine present (even a NULL machine) has something to do with it.