InfoPath Dev

 Here is the background: Windows Server 2008R2 with SP1, IE9 on the server, office 2007 on the server with updates installed. We use EasyPrint on the server for printer redirection (print is redirected to the printer that is the default when the user logs on to Remote Desktop.

The user logs in to remote desktop, opens a form, and selects print, and without any visible errors, there is no printed output. The spools for the printer(s) are empty and we never see any kind of failure notification.

 There has been relatively little on the general web doing searches, and we've tried several potential fixes. We tried using export to pdf and printing the pdfs, but the pdfs are formatted VERY incorrectly (mostly margin and page break issues) in the pdfs that are created in this fashion. We currently have a third party "pdf printer" in place on the user machines. If that printer is the default when logging on to remote desktop, printing "works", that is the dialog box for saving a file from the pdf printer appears on the user machine as expected.

Due to user skill sets, we are trying to eliminate the special handling required to create these intermediate pdf files because they're getting confused about what to name the pdfs, and what to do with them after they're created. I am baffled about why print isn't working in this environment.

Here's a monkey-wrench: when I log in to remote desktop from home, the printer there is outside the normal set of printers we use in the enterprise. Unless things have recently changed, THAT CONDITION WORKED! That printer is a PCL6 printer, whereas we don't seem to be using PCL drivers in our enterprise remote desktop environment. shot in the dark there. I just checked and that printer has stopped working also.

I have also read during the course of my research, that there have been problems with the combination of InfoPath Print and either (or both) IE8 and IE9. The home computer has IE8 installed.

I would appreciate any help or helpful comments to get this working!

 

 Does anyone have any help? I'm not finding anyone anywhere else, either.

I'm sorry - I wish I knew something of use here -

I guess, in an attempt to help with troubleshooting, does an IE page or another format of Office document (Word, Excel) print as anticipated in your environment?

 Thanks for responding, Hilary! It's a pleasure to meet you!

We're using InfoPath 2007 in application (as opposed to web) mode. All of our other applications, even those based on MS Word 2007, are successfully sending their print via EasyPrint to the redirected printers at the user end. It's also working with a web page print on IE9 on that remote desktop server. In case I missed pointing it out, the InfoPath application I'm trying to get to print is Full Trust, which should eliminate security issues as the cause of the failure (although we're not seeing ANY messsages when we try to print, just NO PRINT!). Running this application locally (not using RDP) results in a print also. I'm trying to work around the problem now by installing Office 2010 on that RDP server, but in the process of doing so, I broke several WPF/VB.Net apps that open Word.Application and fill in word documents. We had to return to Office 2007 to keep the users working. I got that resolved now and recompiled the affected apps and they're working on both Office 2007 and 2010 machines. We're going to try a reinstall of Office 2010 on the RDP server tonight. In one of the Internet posts I read with similar problems to mine, someone hinted that they were only having the InfoPath print problem on 2007 servers, and not 2010 servers. I'm hoping that's true. I'll let you know.

Dennis

 

 Good morning!

The switch to office 2010 in the remote desktop environment took place last night, and as of this morning, InfoPath 2010 is printing through EasyPrint to the user's desktop as it should. This was not a fix to the 2007 print problem, but a circumvention, but we're satisfied that we can move forward again.

Thanks for checking in, Hilary!

Dennis

 

Hey, Dennis, I'm glad this worked out for you. Thanks so much for updating this thread. I'm sure you were frustrated trying to find a solution to your problem, and I really appreciate you posting here - this may help others with the same issue!

Here is another technique Remote desktop print and scan. TSPrint software one of the best because it no needed any driver install in your server and workstation. Tsscan is another cheapest solution of remote scan. You have to installing the TSPrint Server on your remote desktop server and TSPrint Client on your client workstations.This will automatically enable you and your users to start printing on their local printers without any problems. TSPrint also offers additional features that come very handy when working Terminal Services/Remote Desktop. List of features: 1.Print documents to your local printer 2.Send files to your local computer 3.Open files on your local computer You can also see http://terminalworks.com/tsprint.php You can now use your your local scanners on your remote desktop. No more transferring of PDF documents and other workarounds just to get your documents on your remote workstation and work with them. you have to do is install tsscan software on your client and server. Zero configuration required. It works just like a normal scanner. You can use it with any document editor, image editor or any other software product that uses scanning. You can also see the link http://terminalworks.com/tsscan.php