This post is somewhat related to my previous post with a similar error message but the detailed error on that one says "you have reached the maximum number of user quota". Please see that post if that is your ASP.NET error when trying to login to Microsoft CRM.
In this case, the users aren't able to login to CRM 4.0, they get an error saying "Invalid User Authentication".
This was a test/demo CRM installation on a virtual server that hadn't been used in a while. The only clue I found was an ASP.NET error in the Application event log. Source = ASP.NET 18.104.22.1687.0. Event ID 1309.
Digging thru the error details, I found this...
Exception type: CrmException
Exception message: Your registration period has expired
Since this test/demo system had sat idle for a while, it had passed it's 30 day trial period and the registration wizard was never run. So once I ran the CRM Registration Wizard, this error went away! But I'm wondering why it wouldn't simply provide a user prompt telling them this issue when they try to login via the browser, rather than making me dig through ASP.Net error logs???
Also, as I mentioned above, once I fixed this issue, I ran into another similar CrmException error that still prevented users from logging in, it said "You have reached the maximum number of user quota". Then I had to manually edit some SQL tables to fix this issue. Please see this post if you are also having this issue.
Office 365 - Can't Display Online Services - Sorry we had a server issue and can't display your connected services. Please try again.
Working with a client running Windows 10 1803 and the latest Office 365 Business software suite with a click-to-run installation. We'v...
The other day I wanted to have a look at the mailbox usage for one of my Office 365 clients. I wanted to see all 35 users and find out if ...
Edit : August 2011 - This post is over 6 years old and it's the most popular post I've ever made. Still going strong! It's one ...
Recently after upgrading one Office 365 user from Lync 2010 to Lync 2013 , his Outlook 2010 was no longer displaying the "presence&qu...