on 2023 Jul 31 11:43 AM
I was creating an application running on Windows XP Embedded using UltraLite10.
The programming language I used is C# and the development environment is Visual Studio 2005. The created application was running without any problems.
Recently, it became necessary to convert to Windows 10 LTSC, so we converted to UltraLite 17 using C# as the programming language and Visual Studio 2019 as the development environment.
I can compile and link without any problems, but when I run the program, I get a runtime error with ulnet17.dll.
Also, run-time errors do not always occur during program execution.
(The following is an excerpt from the Windows event log when a runtime error occurred)
[2023/07/12 8:36:14] , EntryType : Error , EventID : 1000 , Contents : Faulting Application Name: JBOX_0020.exe, Version: 0.0.21.131, Time Stamp: 0x63e5ca58
Faulting module name: ulnet17.dll, version: 17.0.4.2053, time stamp: 0x5734d52c
Exception code: 0xc0000409
Fault offset: 0x00000000000bf32c
Faulting process ID: 0x19fc
Faulting application start time: 0x01d9b4196b57f2dc
Faulting application path: C:\Release\JBOX_0020.exe
Faulting module path: C:\Release\ulnet17.dll
Report ID: a05b736d-dc89-4ddc-86d6-8492bfec59e9
Full name of the failing package:
Application ID associated with failing package:
* "JBOX_0020.exe" is the name of the application using ultra light17.
*The file version of ultra light17 is 17.0.4.2053.
There are no major changes in the converted program.
Only fixes for UltraLite versions and Windows OS differences.
That's all there is to know about the error.
Please let me know if you have any related information.
Request clarification before answering.
Thank you so much for your prompt reply.
The current status of the investigation is as follows.
・I have confirmed that the same phenomenon occurs on Windows 10 Pro.
・The same phenomenon was confirmed with the latest version of the Developer Edition, 17.0.11.7058.
About the latest patch
There is a description that "the correction patch can be downloaded from the dedicated page for customers who have signed a paid support contract",
I was not able to download the patch because I did not have a paid support contract.
About the dump file
I found the following files to help explain the problem.
Is the following file a dump file?
File address:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_JBOX_0020.exe_dd58153d3f205e2399b11dba374caaf1de5d471_8d1ce46c_1d433d55
file name:
Report.wer
File address:
C:\Users\user\AppData\Local\Temp\WER3F0C.tmp
file name:
AppCompat.txt
memory.csv
memory.hdmp
minidump.mdmp
sysinfo.txt
WERInternalMetadata.xml
WERInternalRequest.xml
Below is the log when the same phenomenon occurs in the latest version of the Developer Edition.
Faulting application name: JBOX_0020.exe, version: 0.0.21.144, time stamp: 0x64c383fa
Faulting module name: ulnet17.dll, version: 17.0.11.7058, time stamp: 0x628fb7cc
Exception code: 0xc0000409
Fault offset: 0x0000000000257388
Faulting process ID: 0x1880
Faulting application start time: 0x01d9c4fe99c30ec8
Faulting application path: C:\Release\JBOX_0020.exe
Faulting module path: C:\Release\ulnet17.dll
Report ID: f985a183-70b6-43d7-a915-70dc786c4722
Full name of the failing package:
Application ID associated with failing package:
failure bucket , type 0
Event name: BEX64
Response: Not available
Cab ID: 0
Problem signature:
P1: JBOX_0020.exe
P2: 0.0.21.144
P3: 64c383fa
P4: ulnet17.dll
P5: 17.0.11.7058
P6: 628fb7cc
P7: 0000000000257388
P8: c0000409
P9: 0000000000000007
P10:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
41 | |
15 | |
10 | |
9 | |
6 | |
5 | |
5 | |
4 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.