Getting w3wp.exe dmp file continuously on exchange server 2019

Question

Getting w3wp.exe dmp file continuously on exchange server 2019

Rishi Kesh Singh 175

Getting w3wp.exe dmp file continuously. can any one help here.

DMP log mentioned below.

!analyze -v
................................................................
................................................................
................................................................
................................................................
...........................................................
Loading unloaded module list
........................................................
*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************

*** WARNING: Check Image - Checksum mismatch - Dump: 0x2a8d3b, File: 0x2a16aa - C:\Symbols\KERNELBASE.dll\296284F529E000\KERNELBASE.dll
DEBUG_FLR_EXCEPTION_CODE(80070002) and the ".exr -1" ExceptionCode(e0434352) don't match

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 7796

    Key  : Analysis.Elapsed.mSec
    Value: 68587

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 1

    Key  : Analysis.IO.Write.Mb
    Value: 1

    Key  : Analysis.Init.CPU.mSec
    Value: 2812

    Key  : Analysis.Init.Elapsed.mSec
    Value: 62977

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 217

    Key  : Analysis.Version.DbgEng
    Value: 10.0.29457.1000

    Key  : Analysis.Version.Description
    Value: 10.2506.23.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2506.23.1

    Key  : CLR.BuiltBy
    Value: NET48REL1LAST_B

    Key  : CLR.Engine
    Value: CLR

    Key  : CLR.Exception.System.IO.FileNotFoundException._fileName
    Value: Newtonsoft.Json, Version=13.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed

    Key  : CLR.Exception.System.IO.FileNotFoundException._message
    Value: Could not load file or assembly 'Newtonsoft.Json, Version=13.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed' or one of its dependencies. The system cannot find the file specified.

    Key  : CLR.Exception.System.TypeInitializationException._message
    Value: The type initializer for 'Microsoft.Exchange.Data.Storage.Extensions.JsonExtensionSerializer' threw an exception.

    Key  : CLR.Exception.System.TypeInitializationException._typeName
    Value: Microsoft.Exchange.Data.Storage.Extensions.JsonExtensionSerializer

    Key  : CLR.Exception.Type
    Value: System.IO.FileNotFoundException

    Key  : CLR.Version
    Value: 4.8.4795.0

    Key  : Failure.Bucket
    Value: CLR_EXCEPTION_System.IO.FileNotFoundException_CLRSETUP_MISSINGASSEMBLY_Newtonsoft.Json_80070002_Microsoft.Exchange.Data.Storage.dll!Microsoft.Exchange.Data.Storage.Extensions.JsonExtensionSerializer..cctor

    Key  : Failure.Exception.Code
    Value: 0x80070002

    Key  : Failure.Exception.IP.Address
    Value: 0x7ffceb351b39

    Key  : Failure.Exception.IP.Module
    Value: KERNELBASE

    Key  : Failure.Exception.IP.Offset
    Value: 0x41b39

    Key  : Failure.Exception.Record
    Value: 0xa10cb36620

    Key  : Failure.Hash
    Value: {5c5c287f-db74-d897-5c16-c428bbc2b298}

    Key  : Failure.ProblemClass.Primary
    Value: CLR_EXCEPTION

    Key  : Timeline.OS.Boot.DeltaSec
    Value: 1988056

    Key  : Timeline.Process.Start.DeltaSec
    Value: 53

    Key  : WER.OS.Branch
    Value: rs5_release

    Key  : WER.OS.Version
    Value: 10.0.17763.1

    Key  : WER.Process.Version
    Value: 10.0.17763.1


FILE_IN_CAB:  w3wp.exe.29384.dmp

NTGLOBALFLAG:  0

APPLICATION_VERIFIER_FLAGS:  0

CONTEXT:  00007ffcee7588d1 -- (.cxr 0x7ffcee7588d1)
rax=480000021e850f0f rbx=8341d23300000086 rcx=894800000098838b
rdx=850f00007d830845 rsi=0327840ff8b54148 rdi=483cfe24068a0000
rip=0ffda817418d0000 rsp=000003e6830f02fd rbp=3e80d68b48ff3345
 r8=0a8a00000341840f  r9=0f583cc52241c18a r10=4cc18a0000052884
r11=0f403cf02401428d r12=f2f9800000022484 r13=418d000a321a840f
r14=000282860f013c3e r15=0565840ff3f98000
iopl=2         nv dn di ng nz na pe cy
cs=3439  ss=1065  ds=000a  es=8b44  fs=0870  gs=8b4c             efl=00006583
0ffda817`418d0000 ??              ???
Resetting default scope

EXCEPTION_RECORD:  000000a10cb36620 -- (.exr 0xa10cb36620)
ExceptionAddress: 0000023bf8353c38
   ExceptionCode: fffffffe
  ExceptionFlags: ffffffff
NumberParameters: -2030272256
   Parameter[0]: 0000000000000003
   Parameter[1]: 00007ffce15e1ad8
   Parameter[2]: 00001fa00010004f
   Parameter[3]: 0053002b002b0033
   Parameter[4]: 00000206002b002b
   Parameter[5]: 00007ffcca7a47de
   Parameter[6]: 0000023ac1d41d60
   Parameter[7]: 0000000000000000
   Parameter[8]: 000000a10cb36cd0
   Parameter[9]: 0000023bf8353c18
   Parameter[10]: 0000000000000000
   Parameter[11]: 000000a10cb37004
   Parameter[12]: 000000a100000000
   Parameter[13]: 0000000000000003
   Parameter[14]: 00000000e0434352

PROCESS_NAME:  w3wp.exe

EXCEPTION_CODE_STR:  80070002

FAULTING_THREAD:  ffffffff

IP_ON_HEAP:  0ffda817418d0000
The fault address in not in any loaded module, please check your build's rebase
log at <releasedir>\bin\build_logs\timebuild\ntrebase.log for module which may
contain the address if it were loaded.

UNALIGNED_STACK_POINTER:  000003e6830f02fd

STACK_TEXT:  
000000a1`0cb397d0 00000000`00000000 Microsoft_Exchange_Data_Storage!Microsoft.Exchange.Data.Storage.Extensions.JsonExtensionSerializer..cctor+0x1


SYMBOL_NAME:  Microsoft_Exchange_Data_Storage!Microsoft.Exchange.Data.Storage.Extensions.JsonExtensionSerializer..cctor

MODULE_NAME: Microsoft_Exchange_Data_Storage

IMAGE_NAME:  Microsoft.Exchange.Data.Storage.dll

STACK_COMMAND: !c:\symbols\SOS_AMD64_AMD64_4.8.4795.00.dll\6837CE52B35000\SOS_AMD64_AMD64_4.8.4795.00.dll.pe 0x23b48ed8020 ; dt ntdll!LdrpLastDllInitializer BaseDllName ; dt ntdll!LdrpFailureData ; ** Pseudo Context ** ManagedPseudo ** Value: ffffffff ** ; kb

FAILURE_BUCKET_ID:  CLR_EXCEPTION_System.IO.FileNotFoundException_CLRSETUP_MISSINGASSEMBLY_Newtonsoft.Json_80070002_Microsoft.Exchange.Data.Storage.dll!Microsoft.Exchange.Data.Storage.Extensions.JsonExtensionSerializer..cctor

OS_VERSION:  10.0.17763.1

BUILDLAB_STR:  rs5_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

IMAGE_VERSION:  15.2.1748.36

FAILURE_ID_HASH:  {5c5c287f-db74-d897-5c16-c428bbc2b298}

Followup:     MachineOwner

0 comments

3 answers

Your answer

Answer 1

Rishi kesh Singh 0

Thank you for the update.

There are multiple web.config files. can you confirm the web.config path where I need to update binding redirect.

Austin-H 8,380 Reputation points Microsoft External Staff Moderator

2025-12-31T06:59:21.8766667+00:00

Hello Rishi kesh Singh
My apology for late reply.
Could you check on this directory: C:\SomePath\MyWebApp?
As I mentioned earlier, I do not have access to the testing environment to check on this path to see if you could find the web.config file.
I am looking forward to your response.

Answer 2

Hi Rishi Kesh Singh,

Thank you for posting question to Microsoft Q&A Forum.

According to this issue, please have a look at this part in your dump file's report.
User's image

Key : CLR.Exception.System.IO.FileNotFoundException._message Value: Could not load file or assembly 'Newtonsoft.Json, Version=13.0.0.0, Culture=neutral, PublicKeyToken=xxxx4fe6b2a6aeed' or one of its dependencies. The system cannot find the file specified.

Based on my understanding, that message means the application is trying to load Newtonsoft.Json v13.0.0.0 and cannot find it in any of the expected locations.
My suggestion for this is to deploy the DLL with your web application.

Get the correct version of Newtonsoft.Json.dll (v13.0.0.0, PublicKeyToken 30ad4fe6b2a6aeed) from the NuGet package or your build output.
Place it in the bin\ folder of the IIS site or application that’s crashing.

Then you could add binding redirect in web.config


<configuration>
  <runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="Newtonsoft.Json"
                          publicKeyToken="30ad4fe6b2a6aeed"
                          culture="neutral"/>
        <bindingRedirect oldVersion="0.0.0.0-13.0.0.0"
                         newVersion="13.0.0.0"/>
      </dependentAssembly>
    </assemblyBinding>
  </runtime>

After that, recycle your app pool in IIS (IIS Manager > Application Pools > Right-click your app pool > Recycle.)

As I do not have access to specific environment, please check on my suggestions and check on your end. I tried to download the Newtonsoft.Json from GitHub and found the DLL file.
User's image

Please check this and let me know if the w3wp dmp file still returns the error or not.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 3

The continuous generation of w3wp.exe dump files on your Exchange Server 2019 seems to be related to a FileNotFoundException for the Newtonsoft.Json assembly, as indicated in the dump log you provided. The specific error message states that the system cannot find the file or assembly Newtonsoft.Json, Version=13.0.0.0. This issue is likely causing the w3wp.exe process to crash repeatedly.

To resolve this issue, consider the following steps:

Check for Missing Assemblies: Ensure that the Newtonsoft.Json assembly is correctly installed and available in your application's bin directory or in the Global Assembly Cache (GAC).
Reinstall or Update the Assembly: If the assembly is missing or corrupted, reinstall or update the Newtonsoft.Json package to the required version.
Review Application Configuration: Check your application's configuration files to ensure that they correctly reference the Newtonsoft.Json assembly and that there are no version mismatches.
Monitor for Other Dependencies: Ensure that any other dependencies required by your application are also present and correctly configured.
Check Event Logs: Review the Windows Event Viewer logs for additional errors or warnings that may provide more context about the crashes.
Debugging: If the issue persists, consider using debugging tools like DebugDiag or ProcDump to capture more detailed information about the crashes for further analysis.

By addressing the missing assembly issue, you should be able to reduce or eliminate the continuous generation of dump files for w3wp.exe.

References:

Troubleshoot application pool crashes on a Cloud Services virtual machine