PC SOFT

FORUMS PROFESSIONNELS
WINDEVWEBDEV et WINDEV Mobile

Accueil → WINDEV 2024 → [WD19] Access Violation (GPF) on iPrintReport()
[WD19] Access Violation (GPF) on iPrintReport()
Débuté par Stefan Bentvelsen, 05 oct. 2015 10:29 - 8 réponses
Posté le 05 octobre 2015 - 10:29
Hi All,

a client of me sometimes got the following error when trying to print a report.
In this case the error is triggered on the line where iPrintReport() is called:



Anyone who can imagine what the reason could be for this runtime error ?
The report is based on a memory table in the calling window and this memory table is filled, for sure ! Following the complete error message:

WL call:
Process of 'Click BTN_PrintAanvoer' (frm_PrintRittenplanning.BTN_PrintAanvoer), line 276, thread 0
What happened?
Unexpected system error.
If this error systematically occurs in the same conditions, contact PC SOFT Hot Line and specify:
- the error circumstances,
- a window, a project or the code lines used to replicate the problem,
- the details below.
Details techniques :
Module : ntdll.dll
Adresse de base : 77B70000
Erreur systeme : Access violation (GPF)
EIP = 77BA8E19
OS : Windows 7 Service Pack 1(6.1.7601)
Error code: 1020
Level: fatal error (EL_FATAL)
Dump of the error of 'wd190vm.dll' module (19.0.176.4).
Identifier of detailed information (.err): 1020
Debugging information:
Details techniques :
Module : ntdll.dll
Adresse de base : 77B70000
Erreur systeme : Access violation (GPF)
EIP = 77BA8E19
OS : Windows 7 Service Pack 1(6.1.7601)
Registres :
EIP = 77BA8E19 EBP = 0018D6DC
EAX = 00000000 EBX = FFFFFFFC
ECX = 00000000 EDX = 00000004
ESI = 090D2FBC EDI = 090D2FC0
Pile des appels :
[ntdll.dll (77B70000)]77BA8B1D : RtlIntegerToUnicodeString() + 764 bytes
[ntdll.dll (77B70000)]77BA8B1D : RtlIntegerToUnicodeString() + 523 bytes
[wd190obj.dll (05BF0000), 19.0.356.39, 01A190056s]05C915A6 : pclCreateFactory() + 188330 bytes
[wd190obj.dll (05BF0000), 19.0.356.39, 01A190056s]05C915A6 : pclCreateFactory() + 101120 bytes
[wd190obj.dll
Posté le 05 octobre 2015 - 10:46
Hi Stefan,

I am also getting a similar runtime error with my application crashing when trying to print a report. Only 20% of my clients are affected and this doesn't seem to be OS specific.


Quote

WL call:

Process of 'Click BTN_ReportsGo' (IW_Reports.BTN_ReportsGo), line 109, thread 0



What happened?

Unexpected system error.

If this error systematically occurs in the same conditions, contact PC SOFT Hot Line and specify:

- the error circumstances,

- a window, a project or the code lines used to replicate the problem,

- the details below.



Détails techniques :



Module : wd180etat.dll

Version du module : 18.0.87.0

VI : 01A180062j

Adresse de base : 26C60000

Erreur système : Access violation (GPF)

EIP = 26CC80BD

OS : Windows 2008 R2 Service Pack 1(6.1.7601)



Error code: 1020

Level: fatal error (Fatal Application Crash)



Dump of the error of 'wd180vm.dll' module (18.0.150.7).

Identifier of detailed information (.err): 1020 Debugging information:



Détails techniques :



Module : wd180etat.dll

Version du module : 18.0.87.0

VI : 01A180062j

Adresse de base : 26C60000

Erreur système : Access violation (GPF)

EIP = 26CC80BD

OS : Windows 2008 R2 Service Pack 1(6.1.7601) Registres :



EIP = 26CC80BD EBP = 0012EAA8

EAX = 00000000 EBX = 00000001

ECX = 0012EA88 EDX = 000002C8

ESI = 0012EA88 EDI = 14442BE0



Pile des appels :



[wd180etat.dll (26C60000), 18.0.87.0, 01A180062j] 26C7A842 : pQueryProxy() + 317563 bytes

[wd180etat.dll (26C60000), 18.0.87.0, 01A180062j] 26C7A842 : pQueryProxy() + 86624 bytes

[wd180etat.dll (26C60000), 18.0.87.0, 01A180062j] 26C7A842 : pQueryProxy() + 28476 bytes

[wd180vm.dll (25E60000), 18.0.150.7, 01A180063c] 26074270 : pQueryProxy() + 422652 bytes

[wd180vm.dll (25E60000), 18.0.150.7, 01A180063c] 25EE5120 : EXT_bSetVariableCollection() + 365376 bytes

[wd180vm.dll (25E60000), 18.0.150.7, 01A180063c] 25EA0CA0 : Execution() + 82320 bytes

[wd180vm.dll (25E60000), 18.0.150.7, 01A180063c] 25E78A90 : OBJ_pclGetTauxDeChange() + 21584 bytes

[wd180vm.dll (25E60000), 18.0.150.7, 01A180063c] 25F76AA0 : InfoVersionWeb() + 574304 bytes

[wd180vm.dll (25E60000), 18.0.150.7, 01A180063c] 25F76AA0 : InfoVersionWeb() + 594160 bytes

[wd180vm.dll (25E60000), 18.0.150.7, 01A180063c] 25F76AA0 : InfoVersionWeb() + 596032 bytes

[wd180vm.dll (25E60000), 18.0.150.7, 01A180063c] 25F76AA0 : InfoVersionWeb() + 596592 bytes

[wd180vm.dll (25E60000), 18.0.150.7, 01A180063c] 25F76AA0 : InfoVersionWeb() + 600800 bytes

[wd180vm.dll (25E60000), 18.0.150.7, 01A180063c] 25F76AA0 : InfoVersionWeb() + 600960 bytes

[wd180vm.dll (25E60000), 18.0.150.7, 01A180063c] 25F76AA0 : InfoVersionWeb() + 601024 bytes

[wd180vm.dll (25E60000), 18.0.150.7, 01A180063c] 25F76AA0 : InfoVersionWeb() + 606640 bytes

[wd180vm.dll (25E60000), 18.0.150.7, 01A180063c] 25F76AA0 : InfoVersionWeb() + 607232 bytes

[wd180vm.dll (25E60000), 18.0.150.7, 01A180063c] 25F76AA0 : InfoVersionWeb() + 608400 bytes

[wd180vm.dll (25E60000), 18.0.150.7, 01A180063c] 25F76AA0 : InfoVersionWeb() + 607776 bytes

[wd180vm.dll (25E60000), 18.0.150.7, 01A180063c] 25F76AA0 : InfoVersionWeb() + 609008 bytes

[wd180vm.dll (25E60000), 18.0.150.7, 01A180063c] 25F76AA0 : InfoVersionWeb() + 606704 bytes

[wd180vm.dll (25E60000), 18.0.150.7, 01A180063c] 260168E0 : EXT_pszGetMessageErreurDelegue() + 37296 bytes



The line of code that causes it for me is iInitReportQuery, just before iPrintReport.

I'm interested to see if anybody has any ideas that might help.

Thanks
Ned!
Posté le 05 octobre 2015 - 11:32
Hi Ned!,

nice to know that I'm not the only one with this kind of error(s), sometimes.
Posté le 05 octobre 2015 - 14:04
i have this problem sometimes also
for 80% is the solution an bad field

i have this with date not correct

try to check if your date is correct before printing like:

lddate = edt_slachtdatum
if datevalid(lddate) then iprintrerport....
Posté le 07 octobre 2015 - 11:05
Hi Stefan,

Did you find a fix for your problem?

Thanks,
Ned!
Posté le 09 octobre 2015 - 12:23
"Erreur système : Access violation (GPF) "
if am not mistaken these are crashes caused by faulty memory.
or in otherwords, the actual problem that is causing it could be anywhere in the code from the start of the program to the print of the report.
as the fault in the memory could be introduced anywhere but only becomes apparent later on
when debugging somthing like this.
as far as i know there is no good way to do this. only tactic i know is to look trough ALL the code from start program up to the printing of the report.
i've had this type of bug twice , and it's realy a nightmare to debug
Posté le 09 octobre 2015 - 12:30
Hi,

I have managed to find a solution to the error I was getting.

I have replaced iInitReportQuery with iInitReportQueryConnection - My application no longer crashes when I print reports.

Hopefully this info will help sombody else.

Thanks
Ned!
Posté le 12 octobre 2015 - 13:01
Hi Ned!,

not yet.
Posté le 12 octobre 2015 - 21:28
The problem is that I cannot reproduce these errors on my development-pc.
It happens sometimes at clients, but not consequent.