none
Application Error - Faulting application name: BTSNTSvc.exe - WCF Custom Binding and WS-Addressing

    Question

  • Today, I was testing my BizTalk orchestration that was exposed as wcf services with custom binding "TestMessageEncoding = Soap11WSAddressingAugust2004"

    I notice that BizTalk Server throughts unhandled exception and biztalk services stop wth the following error logs:

    Event Type: Error
    Event Source: Application Error
    Event Category: (100)
    Event ID: 1000
    Date:  9/1/2010
    Time:  5:24:49 PM
    User:  N/A
    Computer: gsbconnect2.mcsdomain
    Description:
    Faulting application name: BTSNTSvc.exe, version: 3.8.368.0, time stamp: 0x49b1dadf
    Faulting module name: KERNELBASE.dll, version: 6.1.7600.16385, time stamp: 0x4a5bdbdf
    Exception code: 0xe0434f4d
    Fault offset: 0x0000b727
    Faulting process id: 0x17d8
    Faulting application start time: 0x01cb49e14738995e
    Faulting application path: C:\Program Files (x86)\Microsoft BizTalk Server 2009\BTSNTSvc.exe
    Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
    Report Id: ad4df625-b5d4-11df-ae4d-0026554d65c8

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


    Event Type: Information
    Event Source: Windows Error Reporting
    Event Category: None
    Event ID: 1001
    Description:
    Fault bucket , type 0
    Event Name: APPCRASH
    Response: Not available
    Cab Id: 0

    Problem signature:
    P1: BTSNTSvc.exe
    P2: 3.8.368.0
    P3: 49b1dadf
    P4: KERNELBASE.dll
    P5: 6.1.7600.16385
    P6: 4a5bdbdf
    P7: e0434f4d
    P8: 0000b727
    P9:
    P10:

    Attached files:
    C:\Users\BizTalkHost\AppData\Local\Temp\WER4E75.tmp.appcompat.txt
    C:\Users\BizTalkHost\AppData\Local\Temp\WER4EE3.tmp.WERInternalMetadata.xml
    C:\Users\BizTalkHost\AppData\Local\Temp\WER4EE4.tmp.hdmp
    C:\Users\BizTalkHost\AppData\Local\Temp\WER5838.tmp.mdmp

    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_BTSNTSvc.exe_5776ef849297ef921f278486ebd9636893756e8_cab_14275a09

    Analysis symbol:
    Rechecking for solution: 0
    Report Id: ad4df625-b5d4-11df-ae4d-0026554d65c8
    Report Status: 4

     

    Error Log entry 2:

    Event Type: Information
    Event Source: Windows Error Reporting
    Event Category: None
    Event ID: 1001
    Description:
    Fault bucket , type 0
    Event Name: APPCRASH
    Response: Not available
    Cab Id: 0

    Problem signature:
    P1: BTSNTSvc.exe
    P2: 3.8.368.0
    P3: 49b1dadf
    P4: KERNELBASE.dll
    P5: 6.1.7600.16385
    P6: 4a5bdbdf
    P7: e0434f4d
    P8: 0000b727
    P9:
    P10:

    Attached files:
    C:\Users\BizTalkHost\AppData\Local\Temp\WER9E97.tmp.appcompat.txt
    C:\Users\BizTalkHost\AppData\Local\Temp\WER9F06.tmp.WERInternalMetadata.xml
    C:\Users\BizTalkHost\AppData\Local\Temp\WER9F07.tmp.hdmp
    C:\Users\BizTalkHost\AppData\Local\Temp\WERA7ED.tmp.mdmp

    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_BTSNTSvc.exe_5776ef849297ef921f278486ebd9636893756e8_cab_039ba9be

    Analysis symbol:
    Rechecking for solution: 0
    Report Id: b98816dc-b5d4-11df-ae4d-0026554d65c8
    Report Status: 4

     

     

    I noticed that if the clients send invalid WS-Addressing <to> element that causes to above fault.

     

    I think this is a bug and need to be submitted to MSFT.

    If Dev. team need more attached files I will be happy to share.

     

    Thursday, September 02, 2010 11:34 AM

All replies

  • Yeah, any time I see kernelbase.dll or "faulting application" I usually report these to MS Support. It sounds like their issue so they will probably not charge you anything.

    Windows Error Reporting got it so they may already be working on a hotfix. But if you need the fix ASAP definitely contact them directly.

    Thanks,


    If this answers your question, please use the "Answer" button to say so | Ben Cline
    Thursday, September 02, 2010 12:38 PM
    Moderator
  • How do I submit it? the log file are hugh, 300 MB !!!
    Friday, September 03, 2010 12:00 PM
  • The entry page into the submit a support incident is at http://support.microsoft.com/common/international.aspx?RDPATH=dm;en-us;select&target=assistance. If this issue is not high priority I would gladly report it for you through the MVP channels. If you need a fix ASAP then you should definitely work with MS support.

    If you want me to submit the issue, please zip up the log and post it somewhere (like on a Skydrive) that I can download it. Just reply back here on where it is posted.

    Thanks,


    If this answers your question, please use the "Answer" button to say so | Ben Cline
    Friday, September 03, 2010 2:23 PM
    Moderator
  •  

    Hi,

    This happens when your machine.config file is corrupt .

    You can find the file at the following location ,C:\Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG

    open the file with browser and see if it is in valid structure or not.If not correct it and should work

    without the error message.

     

    Thanks....

    SPN

    Saturday, September 04, 2010 2:35 AM
  • There is no error in the machine .config file, it is a bug in BizTalk, when client send invalid address.to element.
    Saturday, September 04, 2010 10:07 AM
  • I will upload it and let you know.

    Saturday, September 04, 2010 10:08 AM
  • I uploaded the file to my skydrive:

    http://cid-345254b10979bb00.office.live.com/embedicon.aspx/.Public/AppCrash^_BTSNTSvc.exe^_5776ef849297ef921f278486ebd9636893756e8^_cab^_054e6fc4.rar

    Monday, September 06, 2010 10:24 AM
  • Bin,

    Have you report that bug?

    Tuesday, September 14, 2010 10:47 PM
  • Hi did you manage to get some response from Microsoft about this issue.  It would seem that it does happen to others like me as well with software unrelated to yours.  Seems like a Windows 7 issue, when running a .NET application on a Windows 7.   I got the following error when the storage space on the machine was below the recommended minimum of 300Mb on the root directory that windows 7 resides on.

    Below is the extract taken from the Windows application log:-

    Faulting application name: INNOBATE Antivirus.exe, version: 1.0.0.11, time stamp: 0x4c9b2d79

    Faulting module name: KERNELBASE.dll, version: 6.1.7600.16385, time stamp: 0x4a5bdbdf

    Exception code: 0xe0434f4d

    Fault offset: 0x0000b727

    Faulting process id: 0x27d4

    Faulting application start time: 0x01cb5b0ba112d3af

    Faulting application path: C:\Program Files (x86)\INNOBATE Limited\INNOBATE® AntiVirus 2011 Home\1.0.0.0\INNOBATE Antivirus.exe

    Faulting module path: C:\Windows\syswow64\KERNELBASE.dll

    Report Id: 44a2d8f1-c6ff-11df-88ee-001d7d99d5fa

     

    Fault bucket 2039362628, type 1

    Event Name: APPCRASH

    Response: Not available

    Cab Id: 0

    Problem signature:

    P1: INNOBATE Antivirus.exe

    P2: 1.0.0.11

    P3: 4c9b2d79

    P4: KERNELBASE.dll

    P5: 6.1.7600.16385

    P6: 4a5bdbdf

    P7: e0434f4d

    P8: 0000b727

    P9:

    P10:

    Attached files:

    C:\Users\PCX\AppData\Local\Temp\WER564D.tmp.WERInternalMetadata.xml

    These files may be available here:

    C:\Users\PCX\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_INNOBATE Antivir_64c1975bd6fee9fd4d6050ca3ff88ae0134d5bfd_2ff3e37e

    Analysis symbol:

    Rechecking for solution: 0

    Report Id: 44a2d8f1-c6ff-11df-88ee-001d7d99d5fa

    Report Status: 1

    Saturday, September 25, 2010 9:13 PM
  • Ben, Can you please submit the bug?
    Sunday, September 26, 2010 5:23 AM
  • This error seems to happen when a strong named dll (signed assembly with strong name)  gets updated, i.e. its version number in my case was incremented and the older version of the dll was automatically updated and replaced by the updater. What this meant is that the application manifest that was used by the application could not verify the dll or its dependencies, and would fail, and this in turn would raise a crash report. The crash report would indicate that KernelBase.dll has failed.

    Anyway to fix, recompile the Application with the newer version of the strong named dll and updating both seems to have fixed the problem in my case. Hope this helps someone else.

    What is alarming is that this error with KERNELBASE.DLL seems to make Windows 7 behave unresponsive and sluggish and I started to remember my nighmares about infamous DLL ____. Rebooting the system seems to bring life back to Windows 7 as no system files were damaged.

    Thursday, September 30, 2010 1:31 PM
  • Sorry Tareq, I missed your posts back to me. I will submit it today.

    Thanks,


    If this answers your question, please use the "Answer" button to say so | Ben Cline
    Thursday, September 30, 2010 6:08 PM
    Moderator
  • Yeah please, this is caused to stop our UAT, client refused to sign :(
    Thursday, September 30, 2010 9:58 PM
  • But just so you know, it usually takes a week or two to get a real response for submitting issues. They do respond but it just takes a while. It sounds like you need support ASAP. I would contact MS Support directly yourself.

    FYI, they usually do not charge you if it is their issue.

    Thanks,


    If this answers your question, please use the "Answer" button to say so | Ben Cline
    Thursday, September 30, 2010 10:22 PM
    Moderator
  • Ben, got response?
    Saturday, October 09, 2010 3:42 PM