F
FL
Hi there,
I have come across a very peculiar problem, and haven't been able to find
anything on google nor MSFT resources on it.
Users are getting a 0x0000007F stop error (Kernel Mismatch) when they try to
print Word documents that have Visio diagrams embedded on Windows XP Pro SP2.
The stop error happens on machines with Office 2007 SMB Edition as well as on
machines with Office 2003 Professional. It may be important to note that the
diagrams are out of Visio 2007. We don't have Visio 2003, so I haven't been
able to test if embeded Visio 2003 diagrams cause the stop error as well.
I have ruled out print drivers as this happens with the following print
drivers installed: HP Laserjet 1320, Xerox Phaser 8560, and Brother MFC
7820N. I have successfully replicated this problem on VMs running in Virtual
Server 2005 R2 with any one of those drivers installed.
The current workaround is to export to PDF and then print the PDF.
Has anybody come across something similar to this before, and if so, what
was the fix? If this is something new, any idea for a fix/troubleshooting?
Thanks!
FL
I have come across a very peculiar problem, and haven't been able to find
anything on google nor MSFT resources on it.
Users are getting a 0x0000007F stop error (Kernel Mismatch) when they try to
print Word documents that have Visio diagrams embedded on Windows XP Pro SP2.
The stop error happens on machines with Office 2007 SMB Edition as well as on
machines with Office 2003 Professional. It may be important to note that the
diagrams are out of Visio 2007. We don't have Visio 2003, so I haven't been
able to test if embeded Visio 2003 diagrams cause the stop error as well.
I have ruled out print drivers as this happens with the following print
drivers installed: HP Laserjet 1320, Xerox Phaser 8560, and Brother MFC
7820N. I have successfully replicated this problem on VMs running in Virtual
Server 2005 R2 with any one of those drivers installed.
The current workaround is to export to PDF and then print the PDF.
Has anybody come across something similar to this before, and if so, what
was the fix? If this is something new, any idea for a fix/troubleshooting?
Thanks!
FL