This sounds like the same as issue 62014, which was fixed in versions 10.1 and later, but after the RTM version of 10.3 (10.3.20103.1013) was released. So I think you should be able to fix this by upgrading to the latest SR for 10.3. If that doesn't fix the issue, let me know.