We ran into this issue today when we renewed our cert using SHA 2. We
reissued the cert using SHA 1 and this eliminated our errors. If it is
true that Authorize.net is using 2003 Windows servers, I hope they know
that these servers reach end of life ...
