Document imaging and printing

[Olav]

Hi

We are running Office XP SP2 in a W2K SP3 terminal server
environment. We have also changed "My documents" to a
network drive.

One problem we have is printing TIF-files from Office
Document Imaging. Printing from other applications works
perfectly well. When we hit the printer-button in Office
Document Imaging it seems that it sends the print to the
printer, but nothing appears on the printer. It evens
seems that it sends some printfiles to the printer
spooler, but after that theese files goes into the black
hole.

The strange thing is that if we change "My documents" back
to default location it will print just fine.

Have you seen this problem before. And, the big question,
have you any solution for this???

Regards
Olav

 

[Mike Williams [MVP]]

Hi

We are running Office XP SP2 in a W2K SP3 terminal server
environment. We have also changed "My documents" to a
network drive.

One problem we have is printing TIF-files from Office
Document Imaging. Printing from other applications works
perfectly well. When we hit the printer-button in Office
Document Imaging it seems that it sends the print to the
printer, but nothing appears on the printer. It evens
seems that it sends some printfiles to the printer
spooler, but after that theese files goes into the black
hole.

The strange thing is that if we change "My documents" back
to default location it will print just fine.

Have you seen this problem before. And, the big question,
have you any solution for this???

I have seen this problem in a related context (the Journal Notewriter print
driver for Tablet PCs) - there is a subtle difference in the printer
permission contexts on network drives. I can't remember the exact difference
or what the fix was. Since you're running with Terminal Server there are
probably some added complications, but I do think it boils down to a
permissions issue.

Mike Williams - Office MVP
http://www.mvps.org/

Please respond in the same thread on this newsgroup. Make sure you
include details of your application and Windows versions, and whether
or not you have included any service pack updates.

 

[Kroksleiven]

After some research I found out that this is a bug in W2K SP3. You can
read about it in Q328020
(http://support.microsoft.com/default.aspx?scid=kb;en-us;328020)
MS say that this problem is solved in SP4

The workaround I have choosen is to set "My Documents" with UNC-path
instead of a drive letter. This because I'm not sure SP4 is god for my
Terminal Server environment.

Olav