Microsoft Dynamics 365 portal - error

(1) Share

Report

Posted on by Community Member

Microsoft Dynamics 365 portal started showing this error - no restart helps. Do you have any tip what is wrong?

Server Error in '/' Application.
Value cannot be null.
Parameter name: context
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. 

Exception Details: System.ArgumentNullException: Value cannot be null.
Parameter name: context

Source Error: 

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace: 


[ArgumentNullException: Value cannot be null.
Parameter name: context]
   Microsoft.AspNet.Identity.Owin.OwinContextExtensions.Get(IOwinContext context) +222
   Adxstudio.Xrm.Web.Routing.<>c__DisplayClass21_0.<GetApplicationPathForSiteMarker>b__0() in G:\Agents\BA4504\_wap\12\s\Framework\Adxstudio.Xrm\Web\Routing\SiteMarkerRoute.cs:280
   Adxstudio.Xrm.Web.Routing.SiteMarkerRoute.GetApplicationPathForSiteMarker(IDictionary cache, Func`1 getApplicationPath) in G:\Agents\BA4504\_wap\12\s\Framework\Adxstudio.Xrm\Web\Routing\SiteMarkerRoute.cs:345
   Adxstudio.Xrm.Web.Routing.SiteMarkerRoute.GetRouteData(HttpContextBase httpContext) in G:\Agents\BA4504\_wap\12\s\Framework\Adxstudio.Xrm\Web\Routing\SiteMarkerRoute.cs:140
   System.Web.Routing.RouteCollection.GetRouteData(HttpContextBase httpContext) +228
   System.Web.Routing.UrlRoutingModule.PostResolveRequestCache(HttpContextBase context) +70
   System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +139
   System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step) +195
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +88

Thank you very much

*This post is locked for comments

I have the same question (0)

All responses (3)

Answers (0)

Suggested answer

Community Member on at

Like (0)

Report

Update: This is solved automatically. As I asked for a provisioning of a new Dynamics 365 portal, it took up more than 14 hours to provision. I did not expected such a long time.

Was this reply helpful? Yes No
Suggested answer

mwm 58 on at

Like (0)

Report

Just wanted to say that we were getting this error in setting up a new portal. (Actually, I think we'd got it to the point where it was working but then we added a custom URL which seemed to break it.)

Restarting hadn't worked.

The portal checker said the "URL of the Dynamics 365 organization connected to this portal" was the issue, but it already looked correct in the portal admin screens.

In the end I created myself a new Website record in the CRM (we only had the Customer Self-Service record in existence). I just gave it a name and clicked save, then went to the front page of the portal admin screen and switched the Update Portal Binding setting to my new record. It took a few seconds to take effect but then the portal started giving me a "Not Found" message. (Fine - I'd only created the Website record with a name and nothing else so I was expecting errors.)

I then switched back to the Customer Self-Service and the portal came up happily :-)

Mike.

Was this reply helpful? Yes No
urklnme 439 on at

Like (3)

Report

old post but I did discover why I was getting this.

The web authentication for my portals had expired. They are good for 2 years apparently.

I had my global admin update them from the PPAC/resources/power pages/<each portal>

and click on Website Authentication on the right side of the screen

Also notice that M$ gives no other notice of this. :( figures.

1 people found this reply helpful.

Was this reply helpful? Yes No