Support Center

FaxPrint - Driver Issues/Windows 7

Mike Apr 18, 2013 03:52PM EDT

Hi -
We seem to be having intermittent problems with Windows 7 installs when using the FaxPrint drivers. In a small number of installs the FaxPrint driver appears to install correctly, but attempting to print causes an error in the OS, and the job never makes it as far as the print queue.

The initial error states "PrintIsolationHost.exe" has crashed. A full print of the windows error log is below. Digging through the error logs, the "PrintIsolationHost.exe" error is always followed by "Fax4Driver EventID 7 BeginWrite Failed". If you display the information which would be sent to Microsoft, the system displays the following message:

"Files that help describe the problem:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_PrintIsolationHo_194a15938e91e6bb993477c7d73e716bbc1967_cab_165a52fc\WER52AE.tmp.appcompat.txt
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_PrintIsolationHo_194a15938e91e6bb993477c7d73e716bbc1967_cab_165a52fc\WER52AF.tmp.WERInternalMetadata.xml
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_PrintIsolationHo_194a15938e91e6bb993477c7d73e716bbc1967_cab_165a52fc\WER52E0.tmp.mdmp
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt"


None of the files listed appear to actually exist on the system.

A little more background: This does not happen on every windows 7 install. The user account is an administrator, and UAC is turned off. The system is 64 bit, but we have working installs on other x64 Windows 7 Machines. The system is up to date on patches. I've checked the driver isolation level - it appears the systems that are working are set to 'None', but changing it on the failed systems doesn't appear to make a difference.

Any ideas where we should start troubleshooting this?

Thanks -
Mike

ERROR REPORT:


Log Name: Application
Source: Application Error
Date: 4/18/2013 10:18:48 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: DTm-07
Description:
Faulting application name: PrintIsolationHost.exe, version: 6.1.7600.16385, time stamp: 0x4a5bd3b1
Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec4aa8e
Exception code: 0xc0000374
Fault offset: 0x00000000000c40f2
Faulting process id: 0x1af0
Faulting application start time: 0x01ce3c58ca3900a7
Faulting application path: C:\Windows\system32\PrintIsolationHost.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 07e96bce-a84c-11e2-bc68-4437e6a9a994
Event Xml: (Will provide if needed, contains invalid characters)

2 Data Techniques Responses and 1 Community Responses

Up -4 Rated Down
DTI Support  Data Techniques Employee Apr 18, 2013 03:58PM EDT

Hello,

If the BeginWrite is failing it sounds like the driver is getting an exception trying to write the fax file into the configured directory.

If you are specifying a Print Files path then make sure the user has read/write/modify permissions in that directory. Otherwise if you dont specify a path the path will default to the users TEMP dir.

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

Sincerely,
Sean
Data Techniques Support

Up 2 Rated Down
Mike  Data Techniques Employee Apr 18, 2013 04:56PM EDT

Interesting. Looks like that got it.

We were using the default temp file location, but it appears a security setting on these machines was making that un-writeable.

Thanks!

Up 1 Rated Down
DTI Support  Data Techniques Employee Apr 18, 2013 05:36PM EDT

Your welcome, I've written this up however since it should return more gracefully than causing an exception in the process.

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

Sincerely,
Sean
Data Techniques Support

This question is closed to new answers.

Contact Us