I've had a check of this and get the same results, I can't see any issue with the strings being used so it looks to be an issue with that tool.
As a workaround you can run a Perpendicular report as below and extract the intersected point coordinates…