1 of 1 people found this helpful
the os user running nsh doesn't have permission to the secure file on the system nsh is launched from, as noted in the error.
one way this can happen is if you install the rcp or nsh after installing the rscd on the same system. or someone has altered permissions on the file for some reason. one way to correct this is to enable permission inheritance on the secure file:
if inheritance is disabled, what i've circled will say 'enable inheritance', and then you should see that the os 'users' group has read access to the file.
Thank you Bill.
The problem was with the permissions of the agent files.
NSH Here works fine now.