printing watermarks on TAM forms from XP Pro

[Lynn Stillings]

I am not exactly sure if this is the correct forum for this post, so if not please forgive the blunder. . .

As of last week, suddenly for no apparent reason, printing watermarks on TAM forms (such as a Certificate) is not working, but only on workstations that have the XP OS (Windows 7 are fine). It does not matter what printer is used (local or network or the various models of printers). Watermarks work outside of TAM, and even inside of TAM on a formletter. Conversly, if we change the printer properties default to USE watermarks (through Settings/Printer & Devices/Printer Properties), and try to print a form but select "none" for watermarks, they still print. It seems as if the printer is not recognizing the printer property change when done from within TAM forms.

We have rolled back to prior restore points thinking maybe an MS update broke it, but no luck. Applied has no clue. We have resintalled printer drivers, turned off our AV. Nothing seems to make a difference. Has anyone else experienced this?  I'm stumped.

[Bob]

Could you install this printer a second time on server with different name.  On this printer, on server go to properties, change settings to use watermark, save.  Then it would always print the watermark when chosen as it's locked in at the server.   Actually a tip I used from Mark that he does.   Changing from duplexing to normal a pain for users so same printer installed twice on server.  One is set to print all jobs two sided and one is set to print normal.

Can't explain why you lost watermark and only on XP other than a Word update but you restored back so unsure.   

More a work around than solution.  Sorry..       

[Jeff Zylstra]

Not sure if a rollback to an earlier system restore point would affect files that were written over in a Windows update or not.  I've always thought that this was just for registry changes.  I would be interested to know everyone else's take on this, as it affects not only Windows updates, but also malware issues and other software updates as well. 

You can check an XP machine to see when Windows updates were made by going to add/remove programs and checking the box at the top to include Windows updates in the listing.  My guess is that either a Windows update or printer update may have done this.  Not sure though.

[Lynn Stillings]

Bob...this is happening on all the printers that are available to the users. We do not install Office updates, only Windows updates. I guess we could set one network printer up as you suggested for a workaround, that may be our only option if we can't figure out what caused it.

Jeff...we did look to see when the last Windows updates were, which dictated the restore point we rolled back to. Our network admin had the same concern as you mentioned, that rollback doesn't necessarily put the computer back to the way it was prior. We don't do printer updates, so nothing else has changed on these computers except MS updates.

These kinds of issues that just happen overnight for no apparent reason make me crazy. And especially, why does it only happen in TAM forms but works in other areas? 

[Jeff Zylstra]

I have had to delete everything in the print queue because of corrupted files in the queue.   I remember that everything reinstalled automatically, or with little time or effort.  Unfortunately, I don't remember how I did it.  I'd use that as a last resort at this point.

Silly question, but have you "rebooted" the printer(s) and computers?   You might even go so far as to change the IP address of the port that the printers are on.  And I know this is even sillier yet, but also delete all temp files on the XP machines and try again after a reboot.  The only advice I can give is to start with a clean slate through temp file deletions and reboots of the printers and workstation(s), and then go through a process of elimination until you reduce it to the bare necessities.  Maybe even reboot an XP machine into safe mode to see if anything else is conflicting.  You may also want to turn off print spooling to further reduce it down and eliminate things.  You can add them back in after you've had success.  Sorry, but it's time consuming and frustrating process.  The sooner you begin, the sooner you might be done. 

I know that we have had a few issues with printing ever since TAM started using .NET in the print routines.  I don't know much about .NET, other than it causes slow and sometimes erratic printing.  HTH.

P.S.  Modified to take out the "which printer" question after I re-read your post.

[Lynn Stillings]

Jeff...it is happening on all the printers that are available to the users. The network printers are on the server, and the desktop printers are connected via TCP/IP. The network printers are Xerox and the desktop printers are HP and Lexmark. This is an equal opportunity problem 

[Jeff Zylstra]

Jeff...it is happening on all the printers that are available to the users. The network printers are on the server, and the desktop printers are connected via TCP/IP. The network printers are Xerox and the desktop printers are HP and Lexmark. This is an equal opportunity problem 

OK, that being the case, I'm thinking .NET.  Anyone speak .NET out there?

[Lynn Stillings]

Yes, we have rebooted the devices/PCs, also tried running asupdate, but have not gone so far as taking a machine down to a clean slate. Ugh, I have a half dozen computers that are exhibiting this behavior (more than that actually, but not all those users need the watermarks feature).  Never thought about .NET and don't know much about it at all. That being said, I am more likely to try out Bob's suggestion for the workaround.

Thanks for all the ideas. If we figure out I'll post it here!

[Lynn Stillings]

We were able to determine it was caused by MS updates (long story), although we couldn't identfy the precise one. As Jeff eluded to, rolling back to a restore point does not seem to "undo" whatever the update did. Cutting to the chase; we decided to try out Bob's (and Mark's) workaround suggestion. Worked slick! I never would have thought of that myself. Now the affected users have a new printer option named WATERMARK!

Thanks to Bob (and Mark) for the workaround suggestion 
Thanks also to Jeff for all the ideas (our network admin also thought it might be related to .NET, perhaps included in MS updates somehow...who knows).

Anyway, that is one of the great things about the newsgroups, sometimes you might not get the exact answer you were looking for, but other suggestions and ideas may lead to a resolution by taking a different path around the barn  I still even have a few hairs left on my head!

[Bob]

Glad it worked!  Sometimes easy to create a fix than keep fighting the issue.  What I learned from Mark P as I had an existing network printer that was fighting me. 

Our users love the fact dedicated printer for duplexing (even though same printer for normal jobs too)  no changing properties then switching back.  Your users too will appreciate just switching printer and having watermark vs. editing job to do so.  Win win!   

+1 for AU!  lol

[Jeff Zylstra]

Excellent!  Glad you were able to find such a nifty work around.  And yes, that's where these forums shine.  I always enjoy working on someone ELSE'S problems for a change!  I get much less complaints and much less pressure that way . 

[Billy Welsh]

I always enjoy working on someone ELSE'S problems for a change!  I get much less complaints and much less pressure that way . 

So true!  Here the effort is appreciated, even if problem not solved.  Outside of AU, you MUST somehow resolve the problem.

[Ben Thoele]

This is the same problem as referenced in this post. http://appliedusers.ca/forums/index.php/topic,3415.0.html

Basically the Windows update KB2656369 and possibility other updates from that update Tuesday break the ability of TAM to select any setting in a printer that isn't default.  Watermark, trays, etc...  There are a couple of work arounds,  you can make an additional print queue that defaults to a commonly used option (Ex: tray 2),  you could make the option default in Printers and Faxes before you print in TAM, or use the watermark feature in Adobe Acrobat or other image printer.

[Lynn Stillings]

Ben,
Thank you for the information. I would not have associated the paper tray issue with what we are experiencing. I appreciate the validation of which update broke it, and that we weren't crazy when trying to rollback with no success! Again, I appreciate the follow up! Another mystery unraveld!