We have a production process that uses an HTTP_GET.  The process has been in place since late last year, and it runs hundreds to thousands of times a day with no issue.  The SQL stored procedure that does the HTTP_GET is coded to handle if an SQLSTATE 38501 occurs there and sends us a message about that if it does, although that error very rarely occurs.  The profiles running that process have the necessary permissions.  Can someone tell me what other reasons there could be for this SQLSTATE 38501 to sometimes occur?

That's a pretty generic SQL error state. I'd suggest looking at the job log for additional details the next time that it occur.

If you're at 7.4 or above, you could use the SQL Error Logging Facility to try & grab more point-in-time failure details.

Thank you.  Our stored procedure is coded with an exit handler for SQLSTATE 38501, so I'm not sure that an error is getting logged for that.  I'll watch for the next time the issue occurs to check the logs for more information.  Maybe a change to the exit handler could be done to get additional details with that.