Closed senyordiaz closed 6 years ago
What versions of the various features in the system requirements are you using? Operating system, Dynamics 365 version, .NET framework, Visual Studio, etc.
I'm using, Windows Server 2012 R2, Microsoft Dynamics CRM 2016 (8.1.1.1005) (DB 8.1.1.1005), .NET 4.5.2, and Built Using Visual Studio 2017 Community Edition.
I tried before in CRM 2016 (8.1.0.359) (DB 8.1.0.359) no problem like this happened, successfully portal displayed after configuration. Could it be incompatible with this version (Microsoft Dynamics CRM 2016 (8.1.1.1005) (DB 8.1.1.1005))?
I'll test on the same versions and see if I can reproduce the error.
Please update your CRM 2016 installation to the newest supported build of 8.1, Bing Maps AJAX Upgrade for Microsoft Dynamics 2016 Service Pack 1, version 8.1.1.1100. If there are any issues we'd only be able to address them against the newest version.
I've successfully tested with Windows Server 2012 R2 and CRM 2016 version 8.1.1.1100, hopefully you find the same as well.
just update the crm into 8.1.1.1100, and still get the same error, did i miss something?
It's hard to say, most information I can find on this error has to do with using old CRM assemblies that need to be updated, but those assemblies should already be coming from NuGet packages that work fine.
We need to try isolate the issue. Assuming your CRM organization loads fine when accessing it directly in your web browser, my guess is something is missing on the web server hosting the portal. I would try to host the portal from some other machines and different operating systems to see if the issue occurs on the other ones as well. A simple test would be to deploy the MasterPortal project to an Azure web app. The free tier should work and I've deployed to azure web apps without issues. If the error still occurs there could be an issue with the CRM server. If the issue goes away, something about your web server could be the cause of the problem.
I'm closing this due to inability to reproduce.
Hi, i tried to set up portal followed the documentation, it was happened in configuration, after i set the address and, user name and password, also choose the portal. And then this error showed up.
Is there anything wrong with configuration or missed something?