RPC over HTTP not configuring after Office 2007 SP2 install

If you know the name of the DC/GC, then you can give this article a shot.
http://support.microsoft.com/kb/319206

Other than that and my best recommendation is to contact the Exchange host
provider to see if they are aware of this change in SP2 for Office/Outlook
2007 and/or verify that the KB article applies/resolves the issue. Sooner
or later, other customers they have should be run into this if it is the
cause.

"Brian Abram" wrote in message
...
It's a hosted email provider, so I do not have acess to change the
Exchange
settings. In addition, I checked the IP address of both the RPC and
exchange
server; both IP addresses are routable through nslookup (tried on multiple
machines from different locations).

I do believe that this KB post alludes to the issue. Not only does it
recognize difficulty connecting to the exchange server with the same error
message I see, but also notes that "After this initial connection is
made...Outlook caches the version of Exchange that hosts your mailbox".

I also stumbled upon testexchangeconnectivity.com from a link on
Microsoft's
site. The process errored out at "Testing the Referral Service on
Exchange
Mailbox Server". Deails are that "An Error occured while calling
RfrGetNewDSA". Additional details: "An RPC Error was thrown by the RPC
Runtime. Error 1717 UnknownIf"

With this previous part in mind, is there a way to "trick" Outlook 2007
SP2
into what it needs to know? Is it possible to find the address for the
global catalog server and insert this into a .PRF for importing into
Outlook?


"neo [mvp outlook]" wrote:

Hmm... lets look at this from a different direction since Office 2007 SP2
did include a code change in Outlook 2007 that I just became aware of....

http://support.microsoft.com/default...b;en-us;969519

I haven't tested this scenario yet, but look thru this and could it apply
to
the configuration on the exchange server(s) in your site? (Note: The
method
that caught my eye was method #2 as I know of some that have implemented
the
"No RFR Service" registry value on their exchange server and this could
come
as quite a shock after implementing Office 2007 SP2.)

"Brian Abram" wrote in message
...
No dice - running the netsh command below and rebooting did not allow
Outlook
to connect to the Exchange server. I've tried to eliminate every other
variable from this equation, including a clean installation of Office
2007
SP2 (slipstreamed) and upgraded to SP2. In either case, once SP2 is
installed, RPC doesn't work.

"neo [mvp outlook]" wrote:

Sounds like our configurations are similar as I am running Vista x64
w/
SP2
and Office 2007 SP2. I don't have this issue when configuring outlook
profiles to connect to Exchange 2003 SP2 on Windows 2003 SP2. When
things
went wiggy with RPC under Outlook 2003 on Windows XP, one possible fix
whas
to uninstall/reinstall the networking components of the operating
system.
Have you tried resetting Vista's network configuration using NETSH?

Just in case you are not familiar with NETSH... open an elevated
command
prompt and type:

netsh winsock reset

I believe you will have to reboot after the above....


"Brian Abram" wrote in message
...
No such registry key exists. I can only confirm this on one
computer
though
(Vista SP2, Office 2007 SP2). This particular computer worked
before
Office
2007 SP2; as before, once I installed SP2, it still worked. When I
tried
to
tinker with my email settings - while debugging this issue - the
configuration broke and I'm no longer able to configure for RPC.

"neo [mvp outlook]" wrote:

Weird... is your site using the UseWindowsUserCredentials registry
value
located at:

HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\O utlook\RPC


"Brian Abram" wrote in
message
...
In addition, I've also created a PRF file and imported into these
Outlook
instances. With this, I've removed all profiles, imported the
PRF
into
Outlook 2007, and attempted connection.

Same results:
Post-SP2, PRF imports but cannot connect to Check Name or access
Exchange.
Pre-SP2, PRF imports and can connect (and can continue to connect
post
SP2
installation).

"Brian Abram" wrote:

In all cases, I'm attempting configuration while accessing the
internet,
but
not on the corporate network. And I've also tried the below
trick
of
creating the profile within the control panel, and the same
issues
apply.
This all has also be done on clean installs of OSes and Office
2007.
If
I
try to create the profile after SP2 is installed, the process
stalls.
If
I
create it before SP2 (and install SP2 afterwards), the account
works.

"neo [mvp outlook]" wrote:

When you go to configure the RPC/HTTPS (aka Outlook Anywhere)
properties,
are you on the corporate network, internet, or have no network
connection at
all? FWIW and using an old Outlook 2003 trick, I would try
creating
the
mail profile when there is no network connection at all. Once
the
profile
is created, reconnect the network and try launching Outlook to
see
if
it
will connect to Exchange.

"Brian Abram" wrote in
message
...
If I configure my Exchange connect after installing Office
2007
SP2,
I
always
get connection errors. Once I configure my account and
click
[Check
Name],
Outlook hangs and responds: "The action cannot be completed.
The
connection
to Microsoft Exchange is unavailable. Outlook must be online
or
connected
to
complete this action."

I've tested on three OSes (XP, Vista, 7 RC) installing
Office
2007
RTM or
SP1. In these cases, I can configure and connect to
Exchange
2003
via RPC
with no issue. Once I install SP2 on these machines, I can
still
connect
via
RPC. If I remove the account, however, and attempt to
recreate,
Outlook
hangs as above.

In all cases, the common thread is that configuring the
account
with
RPC
hangs when SP2 is installed.