Forefront UAG Troubleshooting: Event ID 151: User Could Not Be Signed In

Forefront UAG Troubleshooting: Event ID 151: User Could Not Be Signed In

SymptomsWhen end users attempt to access the Forefront UAG portal, they may receive the following message "An authentication error occurred when signing in." There may also be an event 151 in the event viewer or in the Web Monitor with the description "WS-FAM: User with lead user claim value [user_name] could not be signed in. Session ID: [session_ID], Trunk name: [trunk_name]."

CauseAn unknown error occurred when the user attempted to sign in.

SolutionThe user should attempt to sign in to the Forefront UAG portal again. If they continue to receive this error, you should collect traces from the InternalSite and troubleshoot any problems that occur in InternalSite. For information about collecting traces, download the Forefront UAG Tracing Symbols (http://www.microsoft.com/downloads/en/details.aspx?FamilyID=fc052e67-2a04-4058-b326-9d92aa67b2c4) and follow the instructions in the guide.

Leave a Comment
  • Please add 5 and 7 and type the answer here:
  • Post
Wiki - Revision Comment List(Revision Comment)
Sort by: Published Date | Most Recent | Most Useful
Comments
  • Ed Price MSFT edited Revision 1. Comment: Clarified an external link.

Page 1 of 1 (1 items)
Wikis - Comment List
Sort by: Published Date | Most Recent | Most Useful
Posting comments is temporarily disabled until 10:00am PST on Saturday, December 14th. Thank you for your patience.
Comments
  • Ed Price MSFT edited Revision 1. Comment: Clarified an external link.

Page 1 of 1 (1 items)