I have found a solve for my particular issue. And, hopefully the same issue listed above from other users. An initial trace of the procedure call: aspnet_Membership_GetUserByUsername showed the paramater @ApplicationName = N’-1’ which was the host paramater. Changing this to ‘0’, which was the Portal level, returned rows. Which then pointed me to the User tables to find the issue. It would be best to query all users where ApplicaitonName = ‘-1’ to find any that are corrupt. There was a user in the aspnet_Users table that was tied somehow to the Superuser account. I feel this user was created with the host login. I removed the user procedurally using the aspnet_Users_DeleteUser proc. Passing in the parameters for @TablesToDeleteFrom = (1,2,4,8) Doing this now returns rows when the aspnet_Membership_GetUserByUsername is called. In a nutshell, the error: Error: User Accounts is currently unavailable, is caused by no rows being returned from: aspnet_Membership_GetUserByUsername. Trace back from that procedure, and/or, remove users with Host level access until the procedure returns rows.