Nico, We are unable to replicate this error on our development machines, therefore are unable to debug, unless there is another method we can use to "trap it" in a production environment.
This happens on our clients running the application under Windows Server 2008, 2007, 2003 standard server edition with Terminal Services, OR, Small Business Edition, stand-alone Windows 7. It is not always the same report, nor the same user, different printers - (enterprise class laser printers, or local printers - no matter the make/mdel).
Printer drivers are all up to date both on the servers and the local PCs. It happens when printing to a printer, and sometimes when printing to PDF. The reports are called from an .rtm file It does not always happen, it randomly happens.
We use Advantage Remote Server DB v10.1, develop in Delphi XE Enterprise, and have the current Enterprise RB.
If there is a way we can trap the events in a production environment, please let me know. Many thanks, Diana
Which version and edition of ReportBuilder are you using?
Since you are unable to recreate this issue yourself, you may need to work with your customer to isolate the issue. Are you able to recreate this with a minimal (single label) report? If not, take a report that does cause the issue and try simplifying it to find the component(s) or code that causes the problem.
I would also suggest running your application through a resource utility such as FastMM or AutomatedQA to see if there are any memory or resource leaks.
Many of our customers use an external debugger such as MadExcept to log errors outside Delphi. You may be able to use a tool (which I believe compiles directly into your app executable) like this to track where exactly the exception is occurring.
Comments
Does this happen with every report you run or only specific report(s).
Do you get this behavior when printing to every printer or only a
specific one?
If you set your application to stop on exceptions and add
RBuilder\Source to your library path, where in the RB source is the
error occurring?
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com
We are unable to replicate this error on our development machines, therefore
are unable to debug, unless there is another method we can use to "trap it"
in a production environment.
This happens on our clients running the application under Windows Server
2008, 2007, 2003 standard server edition with Terminal Services, OR, Small
Business Edition, stand-alone Windows 7. It is not always the same report,
nor the same user, different printers - (enterprise class laser printers, or
local printers - no matter the make/mdel).
Printer drivers are all up to date both on the servers and the local PCs.
It happens when printing to a printer, and sometimes when printing to PDF.
The reports are called from an .rtm file
It does not always happen, it randomly happens.
We use Advantage Remote Server DB v10.1, develop in Delphi XE Enterprise,
and have the current Enterprise RB.
If there is a way we can trap the events in a production environment, please
let me know.
Many thanks,
Diana
Which version and edition of ReportBuilder are you using?
Since you are unable to recreate this issue yourself, you may need to
work with your customer to isolate the issue. Are you able to recreate
this with a minimal (single label) report? If not, take a report that
does cause the issue and try simplifying it to find the component(s) or
code that causes the problem.
I would also suggest running your application through a resource utility
such as FastMM or AutomatedQA to see if there are any memory or resource
leaks.
Many of our customers use an external debugger such as MadExcept to log
errors outside Delphi. You may be able to use a tool (which I believe
compiles directly into your app executable) like this to track where
exactly the exception is occurring.
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com