|
|||
|
|||
Do the same forms print differently when using the Windows client? E.g. do these include the demographics?
In general the Web interface should inherit from the same settings as used by the Windows client. You can configure reports headings under Tools > Options Window, the Reports tab. |
|
|||
|
|||
the tickets we print from the client show all our demographics. The tickets we print from the web interface are a bit different format and have no demographics. Just our logo. In looking under tools/options/reports it shows our name and demographics, but these don't print from the web interface
|
|
|||
|
|||
It seems that you may be using the Web only, 'Print Preview' option that prints the service form that is a built-in format of the Web Interface and not based on the Ticket form reports.
This service form prints header and footer defined in the Web Interface. In case you need more information to be printed in this form, you can update the header via Tools > Options > Web Interface tab. Restart 'RangerMSP Web Interface' service after updating the logo. As alternative, you can print Ticket details using 'Print to PDF' button and select one of the Technician Service Forms. This will print the report in exact same way as in application - with logo defined for Reports. Hope this helps. |
|
|||
|
|||
I am having a problem with "Print to PDF" and "Sign & Print to PDF" for Tickets from web access also. All our custom reports show up, but when I select a report to print to PDF, I get the error message "1001 Operation aborted. Printing to archive file REPD7JHP0FUVB0MR61ZZ failed."
Any ideas how to fix this? I am using Safari 9.0.1 on an iMac. All reports printed correctly before this upgrade. |
|
|||
|
|||
If this helps anyone, great. Be very careful if you want to do this, and backup, backup, backup. This looks like a Windows registry issue.
Exception_Msg=System Error. Code: 8. Not enough storage is available to process this command We've found the following thread and the resolution may help here too as the error is the same: http://answers.microsoft.com/en-us/w...0-b52e99b69fab Carefully follow the instructions there, AFTER backing up your registry. Then - RESTART your server and see how it goes. |