These FAQ posts explains why you may be receiving that error message for some users during login and some solutions to try to resolve it - some Rule/Action/Hook/Custom DB script is most likely causing the issue.
In addition to the solutions provided in the FAQ post, you can try using the Real-time Webtask Logs Extension to try to figure out the issue for this particular user.
