I have seen similar behavior and resolved by using an ADO.NET connection instead and calling the procedure like this:

CALL LOAD_ADP_HIERARCHY()

Note: I leave the IsStoredProcedure property set to False.