This is part of the Quest/Spotlight SQL Monitoring suite. Ever figure out what was causing the issue, I'm having it too but I know the user ID is active that it is running under and is able to log into SQL. The one thing I did find in the job was that the database was not selected on the step to call the procedure and I can't locate the stored procedure anywhere on the server.