Since you are in version 6.10.41, most likely cause is that you are affected by this
bug fixed on 6.10.51
Checking the content of the u_frrv60.dta file content should be able to confirm it.
Please feel free to reach out to Support if needed for confirmation with a uxtrace of the node.