SYMPTOM:
When a user tries to login to a project (using Developer or Web), the login attempt hangs or reaches a timeout resulting in the user being unable to login. The issue is known to occur in 3-tier connections and not in 2-tier connections. If the user is able to login successfully after waiting a while, browsing through Developer could be very slow and unresponsive.
CAUSE:
One of the causes of this issue is that there is a lock in the History List database when the user is trying to login. The lock occurs because multiple users are attempting to hit the same table in the History List database during login as a user's History List Inbox is populated when a user logs in to the Intelligence Server. The most common tables where this lock will occur are DSSCSCONTENT and DSSCSMSGINFO.
ACTION:
The user should contact their Database Administrator to check the History List database for locks on the DSSCSCONTENT and DSSCSMSGINFO tables when the user is trying to login.
