Support Center

Error printing from FaxMan4 on Windows Server 2008 Terminal Server

Mike Bertenshaw Dec 07, 2011 04:37AM EST

I have a problem generating fax files when using Windows Server 2008 as a Terminal Server.

Fax files can be generated by local admin accounts without any issues, but if I attempt to generate a fax file using a domain account, I get an error "invalid path". I believe this could be occuring as we use home folder redirection to a S.A.N. If I switch off folder redirection for domain accounts, the problem goes away, but this is not feasible in the organisation.

The problem appears to be caused due to a file called "FaxMan" which appears to exist in c users documents folder and is timestamp updated for each fax file generation, although filesize is always 0 bytes. PrintFiles Path is specified to a different location so unsure why any files are being updated in the users documents folder.

Here is the windows error message related to this issue;
The document Test Page, owned by jbloggs, failed to print on printer Ais Fax. Try to print the document again, or restart the print spooler.

Data type NT EMF 1.008. Size of the spool file in bytes: 109104. Number of bytes printed 0. Total number of pages in the document: 1. Number of pages printed: 0. Client computer: \\SACRDS3. Win32 error code returned by the print processor: 161. The specified path is invalid.

1 Data Techniques Response

Up 1 Rated Down
DTI Support  Data Techniques Employee Dec 08, 2011 10:05AM EST


You can resolve this issue by setting the port name associated with the FaxMan printer driver to NUL instead of Faxman. In the printer properties just create a new Local Port and call it NUL, then set the printer to use this new port.

That resolves an issue with the spooler when redirection is enabled.

Thanks for your interest in our products and please let us know if you have any questions.

Data Techniques Support

This question is closed to new answers.

Contact Us