Printing fails on Vista/Outlook 2007 and Server 2008/Exchange 07

rlintner · 07-30-2009, 10:48 AM

Hi All,

Been fighting with this issue for over a week, now I come to you for help.

We're running Exchange 2007 on Windows Server 2008, its been configured to allow RPC over HTTPS as there are several remote offices.
The user having issues is running Vista with Outlook 2007, configured for RPC with cached exchange mode.

While disconnected from the VPN, I can open outlook and it shows as connected to MS Exchange, outlook receives and sends emails etc, but when you try to print, it prompts the error: The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action.

Here's what I've tried and found:
-If connected to the VPN, or after disconnecting from the VPN but keeping outlook open, emails can print. If I exit and reopen, print jobs fail.
-Configured profile on virtual vista using users credentials, able to print
-Disabled IPv6 on Vista
-Ping the webmail site from her computer, it replies Destination Net Unreachable with an occasional Request Time Out, from my system I just get RTO (Cisco configured to deny ping reply).
-Added Registry entries HKCU\Software\Microsoft\Office\12.0\Outlook\RPC and DWORD: DefConnectOpts = 0
-Created a new profile for the user, same issue.
-Removed and reinstalled the certificate
-Moved exchange emails to a PST file, same print error comes up.
-Tried printing to physical device as well as PDF conversion apps
-Ran repair of Office 2007

Printing from all other applications and the rest of the office suite work ok.

David Lundin · 11-16-2009, 03:42 AM

Hi!
I have an identical problem with an identical setup.

A customer has two users which work with our hosted exchange over RPC och HTTPS. They both run Vista and Outlook 2007, and the Exchange is a 2007 on Server 2008 R2. All software is fully updated.

Did you ever solve this, or does anyone else know of a possible solution?

Regards,
/David Lundin

07-30-2009, 10:48 AM	#1 (permalink)
rlintner Registered User Join Date: Jul 2009 Posts: 1 OS: Windows 7 RC	Printing fails on Vista/Outlook 2007 and Server 2008/Exchange 07 Hi All, Been fighting with this issue for over a week, now I come to you for help. We're running Exchange 2007 on Windows Server 2008, its been configured to allow RPC over HTTPS as there are several remote offices. The user having issues is running Vista with Outlook 2007, configured for RPC with cached exchange mode. While disconnected from the VPN, I can open outlook and it shows as connected to MS Exchange, outlook receives and sends emails etc, but when you try to print, it prompts the error: The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action. Here's what I've tried and found: -If connected to the VPN, or after disconnecting from the VPN but keeping outlook open, emails can print. If I exit and reopen, print jobs fail. -Configured profile on virtual vista using users credentials, able to print -Disabled IPv6 on Vista -Ping the webmail site from her computer, it replies Destination Net Unreachable with an occasional Request Time Out, from my system I just get RTO (Cisco configured to deny ping reply). -Added Registry entries HKCU\Software\Microsoft\Office\12.0\Outlook\RPC and DWORD: DefConnectOpts = 0 -Created a new profile for the user, same issue. -Removed and reinstalled the certificate -Moved exchange emails to a PST file, same print error comes up. -Tried printing to physical device as well as PDF conversion apps -Ran repair of Office 2007 Printing from all other applications and the rest of the office suite work ok.

11-16-2009, 03:42 AM	#2 (permalink)
David Lundin Registered User Join Date: Nov 2009 Posts: 81 OS: Windows Vista SP2	Re: Printing fails on Vista/Outlook 2007 and Server 2008/Exchange 07 Hi! I have an identical problem with an identical setup. A customer has two users which work with our hosted exchange over RPC och HTTPS. They both run Vista and Outlook 2007, and the Exchange is a 2007 on Server 2008 R2. All software is fully updated. Did you ever solve this, or does anyone else know of a possible solution? Regards, /David Lundin