异步请求失败[ArgumentNullException]:值不能为null.参数名称:Microsoft.IdentityModel.Protocols.AuthenticationProtocolMessage.SetParameter处的参数(字符串参数,字符串值) [英] Async request failed [ArgumentNullException]: Value cannot be null. Parameter name: parameter at Microsoft.IdentityModel.Protocols.AuthenticationProtocolMessage.SetParameter(String parameter, String value)

查看:143
本文介绍了异步请求失败[ArgumentNullException]:值不能为null.参数名称:Microsoft.IdentityModel.Protocols.AuthenticationProtocolMessage.SetParameter处的参数(字符串参数,字符串值)的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我们当前正在将ASP.Net Web应用程序迁移到Azure Web App.在Infragistics Web数据网格中过滤数据时,我们面临以下错误. (Infragistics版本14.2)

We are currently migrating ASP.Net Web Application to Azure Web App. We are facing the below error while filtering data in Infragistics Web Data Grid. (Infragistics version 14.2)

本地主机:49404说

异步请求失败

[ArgumentNullException]:值不能为null.

参数名称:parameter

  在Microsoft.IdentityModel.Protocols.AuthenticationProtocolMessage.SetParameter(String parameter,String value)

  在Microsoft.IdentityModel.Protocols.OpenIdConnectMessage..ctor(IEnumerable`1个参数)

  在Microsoft.Owin.Security.OpenIdConnect.OpenIdConnectAuthenticationHandler.< AuthenticateCoreAsync> d__1a.MoveNext()

---从上一个引发异常的位置开始的堆栈跟踪---

  在System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(任务任务)处

   在System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(任务任务)

  在Microsoft.Owin.Security.Infrastructure.AuthenticationHandler.< BaseInitializeAsync> d__0.MoveNext()

---从上一个引发异常的位置开始的堆栈跟踪---

  在System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(任务任务)处

  在System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(任务任务)处

  在Microsoft.Owin.Security.Infrastructure.AuthenticationMiddleware`1.< Invoke> d__0.MoveNext()

---从上一个引发异常的位置开始的堆栈跟踪---

  在System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(任务任务)处

  在System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(任务任务)处

  在Microsoft.Owin.Host.SystemWeb.IntegratedPipeline.IntegratedPipelineContextStage中.< RunApp> d__5.MoveNext()

---从上一个引发异常的位置开始的堆栈跟踪---

  在System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(任务任务)处

  在System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(任务任务)处

  在Microsoft.Owin.Security.Infrastructure.AuthenticationMiddleware`1.< Invoke> d__0.MoveNext()

---从上一个引发异常的位置开始的堆栈跟踪---

  在System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(任务任务)处

  在System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(任务任务)处

  在Microsoft.Owin.Host.SystemWeb.IntegratedPipeline.IntegratedPipelineContextStage中.< RunApp> d__5.MoveNext()

---从上一个引发异常的位置开始的堆栈跟踪---

  在System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(任务任务)处

  在System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(任务任务)处

  在Microsoft.Owin.Host.SystemWeb.IntegratedPipeline.IntegratedPipelineContext中.< DoFinalWork> d__2.MoveNext()

---从上一个引发异常的位置开始的堆栈跟踪---

  在Microsoft.Owin.Host.SystemWeb.IntegratedPipeline.StageAsyncResult.End(IAsyncResult ar)

  在Microsoft.Owin.Host.SystemWeb.IntegratedPipeline.IntegratedPipelineContext.EndFinalWork(IAsyncResult ar)

  在System.Web.HttpApplication.AsyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()

  在System.Web.HttpApplication.ExecuteStep(IExecutionStep步骤,布尔值& completedSynchronously)

请帮助解决此问题.

谢谢.

Nandhakumar R

Nandhakumar R

推荐答案

Just to clarify, how exactly are you attempting to migrate the app?

只需突出显示,Azure App Service支持HTTP的端口80和HTTPS的端口443.如果您的网站使用其他任何网站 迁移到Azure App Service的端口后,请记住,这是将要使用的唯一端口.

Just to highlight, Azure App Service support port 80 for http and port 443 for HTTPS traffic. If you have sites using any other port after migration to Azure App Service, do remember that these are the only ports that will be used.

此外,Azure App默认情况下,服务支持匿名身份验证,并在需要时支持表单身份验证. Windows身份验证 了解 有关如何将本地目录与Azure Active Directory集成的更多信息 .

Also, Azure App Service supports anonymous authentication by default and Forms authentication when intended. Windows authentication can be used by integrating with Azure Active Directory and ADFS only. Learn more about how to integrate your on-premises directories with Azure Active Directory.

您可以使用Fiddler跟踪获取有关此问题的更多详细信息.一世 建议您查看清单 通过Azure应用服务迁移助手.

You could use Fiddler trace to fetch more details on the issue. I suggest you review the checklist Migration checklist when moving to Azure App Service and then migrate via Azure App Service Migration Assistant. 

如果您的应用无法直接迁移到App Service,考虑使用Windows容器的App Service,它可以使用GAC,COM组件, MSI,对.NET FX API,DirectX等的完全​​访问权限.

If your app cannot be migrated directly to App Service, consider App Service using Windows Containers, which enables usage of the GAC, COM components, MSIs, full access to .NET FX APIs, DirectX, and more.


这篇关于异步请求失败[ArgumentNullException]:值不能为null.参数名称:Microsoft.IdentityModel.Protocols.AuthenticationProtocolMessage.SetParameter处的参数(字符串参数,字符串值)的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆