Replied 4 August 2017, 2:53 pm EST
The report may be throwing an error on this machine before reaching the Fetch Data event. Do any other events fire? By default, Active Reports uses the default pages settings of the default print driver for determining the dimensions to render the report in. If you are not setting the PrinterName property to a null string (which is recommended for web applications) and using a custom papersize than the report may work on your other machines which may have a print driver installed, and not on the 2000 machine, which may not have the print driver installed. Another problem could be related to permissions on this machine, or the assembly versions. There is not any reason why the Fetch Data would fire on one machine and not the others, unless an error is being thrown and the report is failing before this event.