The transaction in question spent p2pk outputs, so I'm guessing that the tool that you've tried simply doesn't support p2pk scriptSig.

For r and S of that particular txn, you can get it from the input's scriptSig since it is a valid DER-encoded ECDSA signature;
For the first input:

• r: 64bfde07ac93d16f8559d89831e11ac461cc448486f6b7304a379f4aab4fc96f
• S: 5e2f0f6aed03a6338ab66bd9ad11496ff9ac91f6b134c918f74bf7ded699849f

The Z-value however isn't in the signature, it has to be computed.

I've tried other p2pk transactions and it resulted with the same error.
So try to find another tool that supports it.