点击此处---> 群内免费提供SAP练习系统(在群公告中)加入QQ群:457200227(SAP S4 HANA技术交流) 群内免费提供SAP练习系统(在群公告中)嗨,我叫Christian,我是...
点击此处---> 群内免费提供SAP练习系统(在群公告中)加入QQ群:457200227(SAP S4 HANA技术交流) 群内免费提供SAP练习系统(在群公告中)嗨,我叫Christian,我是...
加入QQ群:457200227(SAP S4 HANA技术交流) 群内免费提供SAP练习系统(在群公告中)
嗨,我叫Christian,我是一名网络开发人员。 实际上,我正在使用 asp.net ERP产品。 我的开发遇到了一些麻烦。 暂时,我的应用程序死了,并断开了所有用户的连接。 我分析了使用WINDBG在服务器上生成的转储文件,并且知道崩溃了crpe32.dll。
-Visual Studio 2013
-Windows Server 2012 R2标准版
-适用于.NET Framework 4(64位)13.0.2.469v的SAP Crystal Reports运行时引擎
-Internet信息服务(IIS)8.5.9600.16384v
我该怎么做才能知道哪个报告或用户导致了彻底杀死我的应用程序的错误? 这仅发生几次并且是随机的。 我知道这是堆错误,但仅此而已。 由于存在大量可能的报告和配置,因此很难确定哪个报告导致了错误。 完成后,我将处理并关闭报表对象。
请帮帮我!
这是WINDBG中!analyze -v 命令的结果:
DUMP_CLASS:2 DUMP_QUALIFIER:400 上下文:(.ecxr) rax = 000000a303a1e918 rbx = 00000000c0000374 rcx = 00007ffe736da000 rdx = 0000000000000000 rsi = 0000000000000000 rdi = 00007ffe7520dd40 rip = 00007ffe751d0f20 rsp = 000000a303a1edb0 rbp = 0000000000000000 r8 = 0000000000000003 r9 = 00007ffe7520dda8 r10 = 00007ffe75133e07 r11 = 0000000000000000 r12 = 0000009e71f88b30 r13 = 0000000000000000 r14 = 0000000000000008 r15 = 0000000000000000 iopl = 0 nv up ei pl nz na po nc cs = 0033 ss = 002b ds = 002b es = 002b fs = 0053 gs = 002b efl = 00000206 ntdll!RtlReportCriticalFailure + 0x8c: 00007ffe`751d0f20 eb00 jmp ntdll!RtlReportCriticalFailure + 0x8e(00007ffe`751d0f22) 重置默认范围 FAULTING_IP: ntdll!RtlReportCriticalFailure + 8c 00007ffe`751d0f20 eb00 jmp ntdll!RtlReportCriticalFailure + 0x8e(00007ffe`751d0f22) EXCEPTION_RECORD:(.exr -1) 异常地址:00007ffe751d0f20(ntdll!RtlReportCriticalFailure + 0x000000000000008c) 异常代码:c0000374 异常标志:00000001 数字参数:1 参数[0]:00007ffe7520dd40 PROCESS_NAME:w3wp.exe ERROR_CODE:(NTSTATUS)0xc0000374-产品编号为mont的产品。 EXCEPTION_CODE:(NTSTATUS)0xc0000374-Se produjeron da os en un mont n。 EXCEPTION_CODE_STR:c0000374 EXCEPTION_PARAMETER1:00007ffe7520dd40 WATSON_BKT_PROCSTAMP:5215df96 WATSON_BKT_PROCVER:8.5.9600.16384 PROCESS_VER_PRODUCT:Internet信息服务 WATSON_BKT_MODULE:ntdll.dll WATSON_BKT_MODSTAMP:550f4336 WATSON_BKT_MODOFFSET:f0f20 WATSON_BKT_MODVER:6.3.9600.17736 MODULE_VER_PRODUCT:Microsoft®Windows®操作系统 BUILD_VERSION_STRING:6.3.9600.17415(winblue_r4.141028-1500) MODLIST_WITH_TSCHKSUM_HASH:f8aa0dbb3fea7d064008a7d8fc088a21bdd917a2 MODLIST_SHA1_HASH:11f38bde2c5795beffc565f06def44646c0a3e6a NTGLOBALFLAG:0 MISSING_CLR_SYMBOL:0 PRODUCT_TYPE:3 SUITE_MASK:272 DUMP_FLAGS:102c6 DUMP_TYPE:1 ANALYSIS_SESSION_HOST:CHRISTIAN-PC ANALYSIS_SESSION_TIME:2019年5月3日15:45:10.0484 ANALYSIS_VERSION:10.0.14321.1024 amd64fre MANAGED_CODE:1 MANAGED_ENGINE_MODULE:clr MANAGED_ANALYSIS_PROVIDER:SOS THREAD_ATTRIBUTES: LAST_CONTROL_TRANSFER:从00007ffe751d4162到00007ffe751d0f20 FAULTING_THREAD:ffffffff THREAD_SHA1_HASH_MOD_FUNC:d67d922f0cde5d566c967b08f99d31b955fa30d1 THREAD_SHA1_HASH_MOD_FUNC_OFFSET:7ffaec2a9ab8c27354e45273124068d3847f3957 OS_LOCALE:ESN PROBLEM_CLASSES: ACTIONABLE_HEAP_CORRUPTION 提示[0x3044] 帧[0x02]:ntdll!RtlpLogHeapFailure 字符串[heap_failure_block_not_busy] 失败桶 DOUBLE_FREE 提示[0x3044] 帧[0x02]:ntdll!RtlpLogHeapFailure BUGCHECK_STR:ACTIONABLE_HEAP_CORRUPTION_heap_failure_block_not_busy_DOUBLE_FREE DEFAULT_BUCKET_ID:ACTIONABLE_HEAP_CORRUPTION_heap_failure_block_not_busy STACK_TEXT: 00007ffe`7520dda8 00007ffe`7518af79 ntdll!RtlFreeHeap + 0x75e49 00007ffe`7520ddb0 00007ffe`72419b32 KERNELBASE!GlobalFree + 0x2e 00007ffe`7520ddb8 00007ffe`735c1bf6 kernel32!GlobalFreeStub + 0x26 00007ffe`7520ddc0 00000000`37c20850 crpe32 + 0x3f0850 00007ffe`7520ddc8 00000000`37c10084 crpe32 + 0x3e0084 00007ffe`7520ddd0 00000000`37c12991 crpe32 + 0x3e2991 00007ffe`7520ddd8 00000000`37c12cd7 crpe32 + 0x3e2cd7 00007ffe`7520dde0 00000000`37c06654 crpe32 + 0x3d6654 00007ffe`7520dde8 00000000`37b7bf6b crpe32 + 0x34bf6b 00007ffe`7520ddf0 00000000`37dd5646 crpe32 + 0x5a5646 00007ffe`7520ddf8 00000000`37dd5930 crpe32 + 0x5a5930 00007ffe`7520de00 00000000`37de6169 crpe32 + 0x5b6169 00007ffe`7520de08 00000000`37d19bd2 crpe32 + 0x4e9bd2 00007ffe`7520de10 00000000`37d38a44 crpe32 + 0x508a44 00007ffe`7520de18 00000000`37d39b6f crpe32 + 0x509b6f 00007ffe`7520de20 00000000`37d39e8c crpe32 + 0x509e8c 00007ffe`7520de28 00000000`37d3a53c crpe32 + 0x50a53c 00007ffe`7520de30 00000000`594915b5 mfc80u + 0xb15b5 00007ffe`7520de38 00000000`597937d7 msvcr80 + 0x37d7 00007ffe`7520de40 00000000`59793894 msvcr80 + 0x3894 00007ffe`7520de48 00007ffe`735c13d2 kernel32!BaseThreadInitThunk + 0x22 00007ffe`7520de50 00007ffe`750f5444 ntdll!RtlUserThreadStart + 0x34 STACK_COMMAND:dps 7ffe7520dda8; 千位 THREAD_SHA1_HASH_MOD:20e50adaaea6041752d35248bf2d34e905521ea9 FOLLOWUP_IP: crpe32 + 3f0850 00000000`37c20850 ?? ??? SYMBOL_STACK_INDEX:3 SYMBOL_NAME:crpe32 + 3f0850 FOLLOWUP_NAME:计算机所有者 MODULE_NAME:crpe32 IMAGE_NAME:crpe32.dll DEBUG_FLR_IMAGE_TIMESTAMP:4eb91936 FAILURE_BUCKET_ID:ACTIONABLE_HEAP_CORRUPTION_heap_failure_block_not_busy_c0000374_crpe32.dll!未知 BUCKET_ID:ACTIONABLE_HEAP_CORRUPTION_heap_failure_block_not_busy_DOUBLE_FREE_crpe32 + 3f0850 PRIMARY_PROBLEM_CLASS:ACTIONABLE_HEAP_CORRUPTION_heap_failure_block_not_busy_DOUBLE_FREE_crpe32 + 3f0850 FAILURE_EXCEPTION_CODE:c0000374 FAILURE_IMAGE_NAME:crpe32.dll BUCKET_ID_IMAGE_STR:crpe32.dll FAILURE_MODULE_NAME:crpe32 BUCKET_ID_MODULE_STR:crpe32 FAILURE_FUNCTION_NAME:未知 BUCKET_ID_FUNCTION_STR:未知 BUCKET_ID_OFFSET:3f0850 BUCKET_ID_MODTIMEDATESTAMP:4eb91936 BUCKET_ID_MODCHECKSUM:cf4f98 BUCKET_ID_MODVER_STR:13.0.2.469 BUCKET_ID_PREFIX_STR:ACTIONABLE_HEAP_CORRUPTION_heap_failure_block_not_busy_DOUBLE_FREE_ FAILURE_PROBLEM_CLASS:ACTIONABLE_HEAP_CORRUPTION_heap_failure_block_not_busy FAILURE_SYMBOL_NAME:crpe32.dll!未知 WATSON_STAGEONE_URL:https://watson.microsoft.com/StageOne/w3wp.exe/8.5.9600.16384/5215df96/ntdll.dll/6.3.9600.17736/550f4336/c0000374/000f0f20.htm?Retriage=1 TARGET_TIME:2019-05-02T19:41:56.000Z 内置:9600 OSSERVICEPACK:17415 SERVICEPACK_NUMBER:0 OS_REVISION:0 OSPLATFORM_TYPE:x64 操作系统名称:Windows 8.1 操作系统:Windows 8.1 Server TerminalServer SingleUserTS USER_LCID:0 OSBUILD_TIMESTAMP:2014-10-28 23:45:30 BUILDDATESTAMP_STR:141028-1500 BUILDLAB_STR:winblue_r4 BUILDOSVER_STR:6.3.9600.17415 ANALYSIS_SESSION_ELAPSED_TIME:2072a ANALYSIS_SOURCE:UM FAILURE_ID_HASH_STRING:um:actionable_heap_corruption_heap_failure_block_not_busy_c0000374_crpe32.dll!未知 FAILURE_ID_HASH:{5e08ac90-5f47-ca5c-e6e3-51b2a3011960} 后续行动:MachineOwner
您是否在应用程序中进行任何登录? 如果不是,你应该是。 每次访问报告时,都应包括一个日志条目,说明该报告是哪个报告。 而且,当您关闭/处置报告时,也应该记录下来。 如果特定报告有问题,此信息应有助于您确定引起问题的报告。
-Dell
一周热门 更多>