Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2022 Release Wave 1 PlanDynamics 365 release plan for the 2022 release wave 1 describes all new features releasing from April 2022 through September 2022.
2022 release wave 1 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
We've had an issue with a particular User getting an error message when trying to log in.
I've seen plenty of other forum questions about this particular error in regards of Report development and SDK Development but haven't seen any for when this occurs while logging in. Any thoughts? TIA
Hey Crumbs (as I hope you don't mind being called),
The more detailed error is present under the "ArgumentOutOfRange" block with the "Expected UniqueId..." line.
Are you able to copy that entire line and paste it in? I can see that the URL the CRM is trying to load has "main.aspx?etc=4201&id=... but can't read the rest. It seems to be trying to load in the appointment entity (etc 4201 = appointment) but don't know much more than that based on the screenshot.
Please send the remainder of the error and I'll hopefully be able to get a resolution for you!
I'm working on getting in touch with the user. Right now the error you see is a screen shot that was sent to me.
What do you mean by "when trying to log in"?
On the other hand, since it is a on-premises environment, you can check the eventviewer of the CRM server for more details about the error.
This helped point me to the issue. It appeared that he had a bad link set up as his shortcut to the site. I had him try to log in on another device and even my device successfully. When pulling the error logs I used the same URL that was in the logs and was able to duplicate the error on my end. I had him update the Link to the actual domain and he was able to successfully log in. I guess the link he was trying to use was directly to an appointment.
Business Applications communities