An occasional instance has been observed where reports cannot be generated from the browser interface.  This is manifested by the report log stopping at or near the point where the log indicates "TFsvOps.SetCallback" and then "RptFormatSettings=M/d/yyyy" at which point the log halts with no apparent progress.   Reporting via the Captools/net Tasker is still operative, however indicating that this condition is a result of a problem with Windows "permission" settings on the Report folders.

 

If the above symptoms appear, first verify that all printers in your printer driver list on your Captools/net Server machine ("Start/Printers and faxes") are still valid printers.  If a printer driver appears for a printer that has been removed from the system, delete that driver and retry the report.  Next, we suggest that you sequentially uninstall and reinstall your printer driver(s) and try your reports.

 

If reports still do not run, check the "Permissions" for your printer driver (right click, select "Properties", then "Security").  Add the system "IUSR" and "Network", "Network Services"  and "System" as "users" if they are not already users with "full" permissions.

 

Finally, if the above does not resolve the problem, move copies of all your custom report templates (the folders with the User Id names) out of the \Webscripts\CTReports folder to a temporary location on your hard drive, then uninstall and the reinstall the entire Captools/net Server Suite (this will reapply folder permissions).

 

 

Report Generation Failure due to Other Causes

 

If a Captools/net report fails to generate after the report log has indicated that the report computation process has started, this is likely due to a reporting software bug.  Providing the log and the report template file (RTM file) to Captools Co. programming staff will enable them to determine the cause and provide the appropriate fix.