Home General
New Blog Posts: Merging Reports - Part 1 and Part 2

Strange printer error (v15.04)

edited January 2015 in General

Any ideas on what may cause this error message?


operating system : Windows 7 x64 Service Pack 1 build 7601
system language : English
system up time : 3 days 10 hours
program up time : 5 hours 37 minutes
processors : 4x Intel(R) Core(TM) i3-2120 CPU @ 3.30GHz
physical memory : 2034/3982 MB (free/total)
free disk space : (C:) 362.90 GB
display mode : 1920x1080, 32 bit
process id : $114c
allocated memory : 330.91 MB
largest free block : 1.02 GB
executable : HireTrackNX.exe
exec. date/time : 2014-12-23 14:11
version : 3.0.1.224
compiled with : Delphi 2007
madExcept version : 4.0.9
callstack crc : $5a6eda05, $fab807f6, $eda1cac2
exception number : 2
exception class : EAccessViolation
exception message : Access violation at address 770E09CB in module
'ntdll.dll'. Read of address 72657361.

main thread ($b9c):
770e09cb +02f ntdll.dll _strnicmp
75d57c41 +013 GDI32.dll CreateICA
00a8b349 +0a9 HireTrackNX.exe ppPrintr 4448 +23
TppCustomPrinter.GetPrinterIC
00a8a410 +064 HireTrackNX.exe ppPrintr 3624 +14
TppCustomPrinter.GetDC
00e73c42 +35e HireTrackNX.exe ppPDlg 842 +100
TppPrintDialog.btnOKClick

Comments

  • edited January 2015
    Hi Paul,

    This could be a number of issues. Are you able to test with another
    printer? Does the problem happen every time you print? Have you tested
    with RB 15.05?

    Any more information about the circumstances of this issue would be very
    helpful in tracking the problem down.

    Best Regards,

    Nico Cizik
    Digital Metaphors
    http://www.digital-metaphors.com
  • edited January 2015
    Its from a customer. One off. And its 15.05 (sorry). Was a long shot
    asking you...just wondered if anyone would have a "Ah, you can get this
    if..." moment. We have to tell 'em something and today it was, "I'll ask
    the authors of the reporting engine" :)


  • edited January 2015
    Hi Paul,

    I understand. From the call stack it is clear that the application
    cannot retrieve the printer's device context. If they are able to print
    to a different printer successfully, it may be an access issue (network
    printer issue, incorrect printer name, etc.).

    Best Regards,

    Nico Cizik
    Digital Metaphors
    http://www.digital-metaphors.com
This discussion has been closed.