2016-04-30 9 views
0

突然私は自分のmvc4アプリケーションにアクセスできない。 私はコードを変更しませんでした。私はこの問題をどこでどのように解決することができますか?この問題を追跡するための詳細情報がありますか?System.Reflection.TargetInvocationException MVC 4アプリケーションを実行すると

私はまた、これらの記事に

  1. Stackoverflow
  2. Ms

をチェックし、数回私のPCを再起動彼らはこれを原因となるコードの一部を確認することをお勧めします。私の場合、私は自分のコードに到達することさえできません。

Intelitrace言及フォルダは空である:

C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files

内部例外メッセージ:

Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

エラー:

System.Reflection.TargetInvocationException was unhandled
HResult=-2146232828 Message=Exception has been thrown by the target of an invocation. Source=mscorlib StackTrace: at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor) at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments) at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture) at System.Reflection.MethodBase.Invoke(Object obj, Object[] parameters) at System.Web.Compilation.BuildManager.InvokePreStartInitMethodsCore(ICollection 1 methods, Func 1 setHostingEnvironmentCultures) at System.Web.Compilation.BuildManager.InvokePreStartInitMethods(ICollection`1 methods) at System.Web.Compilation.BuildManager.CallPreStartInitMethods(String preStartInitListPath, Boolean& isRefAssemblyLoaded) at System.Web.Compilation.BuildManager.ExecutePreAppStart() at System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters, PolicyLevel policyLevel, Exception appDomainCreationException) at System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters, PolicyLevel policyLevel) at System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters, PolicyLevel policyLevel) at System.Web.Hosting.ApplicationManager.CreateAppDomainWithHostingEnvironment(String appId, IApplicationHost appHost, HostingEnvironmentParameters hostingParameters) at System.Web.Hosting.ApplicationManager.CreateAppDomainWithHostingEnvironmentAndReportErrors(String appId, IApplicationHost appHost, HostingEnvironmentParameters hostingParameters) at System.Web.Hosting.ApplicationManager.GetAppDomainWithHostingEnvironment(String appId, IApplicationHost appHost, HostingEnvironmentParameters hostingParameters) at System.Web.Hosting.ApplicationManager.CreateObjectInternal(String appId, Type type, IApplicationHost appHost, Boolean failIfExists, HostingEnvironmentParameters hostingParameters) at System.Web.Hosting.ProcessHost.StartApplication(String appId, String appPath, Object& runtimeInterface) InnerException: System.AccessViolationException HResult=-2147467261 Message=Attempted to read or write protected memory. This is often an indication that other memory is corrupt. StackTrace: InnerException:

enter image description here

答えて

0

[OK]を、ここで

  1. アンインストールのVisual Studio 2012
  2. アンインストールはすべての.NET、私はこの問題を解決する方法です。
  3. 再起動
  4. インストールします。ネット
  5. インストールのVisual Studio 2012
最新
0

同様の問題は、アプリケーションの外にある問題になる可能性があり

Finally tracked this down with the help of WinDBG and SOS. Access violation was being thrown by some unknown DLL. Turns out a piece of software called "Nvidia Network Manager" was causing the problems. I'd read countless times how this issue can be caused by firewalls or antivirus, neither of which I am using so I dismissed this idea. Also, I was under the assumption that it was not environmental because it occurs on more than 1 server using different hardware. Turns out all the machines I tested this on were running "NVidia Network Manager". I believe it installs with the rest of the motherboard drivers.

hereを解決しました。この男の場合、彼のアプリケーションに影響を与える悪いソフトウェアがあります。あなたは彼が言及したツールでそれを追跡しようとするかもしれません。がんばろう!

関連する問題