Outlook 2003 RPC Config error

[Paul Stemper]

Has anybody seen this error using Outlook 2003 &
Exchange2k?

"A system component, RPC, required by Outlook to connect
to the e-mail server is not configured properly. For
more information, contact your system administrator."

This is occuring on a single PC (right now), with
serveral other PCs working without a hitch (also using
O2k3.)

We have not noticed any other problems with this PC.

Paul

 

[Paul Stemper]

Never mind. I found the answer by modifying my search of
this newsgroup.

Thanks.

Paul

 

[Don]

What is the solution? One of my users is having this same
problem.

 

[Diane Poremsky [MVP]]

probably...

Check for the presence of these keys and add them if they are missing:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\ClientProtocols]
"ncacn_np"="rpcrt4.dll"
"ncacn_ip_tcp"="rpcrt4.dll"
"ncadg_ip_udp"="rpcrt4.dll"
"ncacn_http"="rpcrt4.dll"

--
Diane Poremsky [MVP - Outlook]
Author, Teach Yourself Outlook 2003 in 24 Hours

http://www.poremsky.com - http://www.cdolive.com

Expert Zone http://www.microsoft.com/windowsxp/expertzone

Search for answers: http://groups.google.com
Most recent posts to the Outlook newsgroups:
http://groups.google.com/groups?as_ugroup=microsoft.public.outlook.*&num=30

 

[Joshua Moyer]

I was missing 3 of the 4 suggested registry values on my Windows XP SP1
machine. After adding the missing values I am still experiencing the
symptoms described below.

I've verified connectivity to my Exchange 2000 server with ping, ping -a,
and RPC Ping. Any ideas?

Regards,
- Josh

--
Josh Moyer lives in Washington state. Please be advised that correspondance
sent jmoyer at nodomain dot net is subject to RCW 19.190, an anti-spam law.

probably...

Check for the presence of these keys and add them if they are missing:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\ClientProtocols]
"ncacn_np"="rpcrt4.dll"
"ncacn_ip_tcp"="rpcrt4.dll"
"ncadg_ip_udp"="rpcrt4.dll"
"ncacn_http"="rpcrt4.dll"

--
Diane Poremsky [MVP - Outlook]
Author, Teach Yourself Outlook 2003 in 24 Hours

http://www.poremsky.com - http://www.cdolive.com

Expert Zone http://www.microsoft.com/windowsxp/expertzone

Search for answers: http://groups.google.com
Most recent posts to the Outlook newsgroups:
http://groups.google.com/groups?as_ugroup=microsoft.public.outlook.*&num=30

What is the solution? One of my users is having this same
problem.

 

[chris]

probably...

Check for the presence of these keys and add them if they are missing:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\ClientProtocols]
"ncacn_np"="rpcrt4.dll"
"ncacn_ip_tcp"="rpcrt4.dll"
"ncadg_ip_udp"="rpcrt4.dll"
"ncacn_http"="rpcrt4.dll"

I was missing 3 of the 4 suggested registry values on my Windows XP SP1
machine. After adding the missing values I am still experiencing the
symptoms described below.

I've verified connectivity to my Exchange 2000 server with ping, ping -a,
and RPC Ping. Any ideas?

I also get the error message after adding those registry keys. Can
this possibly be related to the recent rpc hotfixes? Just a thought.

- Chris

 

[Joshua Moyer]

Chris,
That's a good question. One of the other XP SP1 machines that I tested also
has the RPC fixes and it worked fine though... :-\

Guess I'll have to remove them and see what happens...

Regards,
- Josh

--
Correspondance sent to jmoyer at nodomain dot net is subject to RCW 19.190,
an anti-spam law.

probably...

Check for the presence of these keys and add them if they are missing:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\ClientProtocols]
"ncacn_np"="rpcrt4.dll"
"ncacn_ip_tcp"="rpcrt4.dll"
"ncadg_ip_udp"="rpcrt4.dll"
"ncacn_http"="rpcrt4.dll"

"Joshua Moyer" <See Message Footer> wrote in message

I was missing 3 of the 4 suggested registry values on my Windows XP SP1
machine. After adding the missing values I am still experiencing the
symptoms described below.

I've verified connectivity to my Exchange 2000 server with ping, ping -a,
and RPC Ping. Any ideas?

I also get the error message after adding those registry keys. Can
this possibly be related to the recent rpc hotfixes? Just a thought.

- Chris

 

[exchangesupport]

Hello,

We were able to get our users to connect to Exchange by exporting the
registry key [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\ClientProtocols]
from another Windows XP machine (that had no problems or that didn't
have Office 2003 installed) and then importing it to the affected
machine. This seemed to have fixed the problem.

Chris,
That's a good question. One of the other XP SP1 machines that I tested also
has the RPC fixes and it worked fine though... :-\

Guess I'll have to remove them and see what happens...

Regards,
- Josh

--
Correspondance sent to jmoyer at nodomain dot net is subject to RCW 19.190,
an anti-spam law.

probably...

Check for the presence of these keys and add them if they are missing:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\ClientProtocols]
"ncacn_np"="rpcrt4.dll"
"ncacn_ip_tcp"="rpcrt4.dll"
"ncadg_ip_udp"="rpcrt4.dll"
"ncacn_http"="rpcrt4.dll"

"Joshua Moyer" <See Message Footer> wrote in message

I was missing 3 of the 4 suggested registry values on my Windows XP SP1
machine. After adding the missing values I am still experiencing the
symptoms described below.

I've verified connectivity to my Exchange 2000 server with ping, ping -a,
and RPC Ping. Any ideas?

I also get the error message after adding those registry keys. Can
this possibly be related to the recent rpc hotfixes? Just a thought.

- Chris

 

[Joshua Moyer]

Wow. Thanks so much for the reg import suggestion! I was ready to go crazy
over this one!

There must of been an error in my data-entry that I wasn't seeing. How
embarrasing!

Regards,
- Josh

--
Correspondance sent to jmoyer at nodomain dot net is subject to RCW 19.190,
an anti-spam law.

Hello,

We were able to get our users to connect to Exchange by exporting the
registry key [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\ClientProtocols]
from another Windows XP machine (that had no problems or that didn't
have Office 2003 installed) and then importing it to the affected
machine. This seemed to have fixed the problem.



"Joshua Moyer" <See Message Footer> wrote in message

Chris,
That's a good question. One of the other XP SP1 machines that I tested also
has the RPC fixes and it worked fine though... :-\

Guess I'll have to remove them and see what happens...

Regards,
- Josh

--
Correspondance sent to jmoyer at nodomain dot net is subject to RCW 19.190,
an anti-spam law.

probably...

Check for the presence of these keys and add them if they are missing:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\ClientProtocols]
"ncacn_np"="rpcrt4.dll"
"ncacn_ip_tcp"="rpcrt4.dll"
"ncadg_ip_udp"="rpcrt4.dll"
"ncacn_http"="rpcrt4.dll"

"Joshua Moyer" <See Message Footer> wrote in message

I was missing 3 of the 4 suggested registry values on my Windows XP SP1
machine. After adding the missing values I am still experiencing the
symptoms described below.

I've verified connectivity to my Exchange 2000 server with ping, ping -a,
and RPC Ping. Any ideas?

I also get the error message after adding those registry keys. Can
this possibly be related to the recent rpc hotfixes? Just a thought.

- Chris

 

[Jurgen]

Thank you too. It solved also my similar problem an one
machine!!

THANK YOU!

-----Original Message-----
Wow. Thanks so much for the reg import suggestion! I was ready to go crazy
over this one!

There must of been an error in my data-entry that I wasn't seeing. How
embarrasing!

Regards,
- Josh

--
Correspondance sent to jmoyer at nodomain dot net is subject to RCW 19.190,
an anti-spam law.

Hello,

We were able to get our users to connect to Exchange by exporting the
registry key [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\ClientProtocols]
from another Windows XP machine (that had no problems or that didn't
have Office 2003 installed) and then importing it to the affected
machine. This seemed to have fixed the problem.



"Joshua Moyer" <See Message Footer> wrote in message

Chris,
That's a good question. One of the other XP SP1

machines that I tested
also subject to RCW
19.190, them if they are
missing:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\ClientProtocols]
"ncacn_np"="rpcrt4.dll"
"ncacn_ip_tcp"="rpcrt4.dll"
"ncadg_ip_udp"="rpcrt4.dll"
"ncacn_http"="rpcrt4.dll"

"Joshua Moyer" <See Message Footer> wrote in message
I was missing 3 of the 4 suggested registry

values on my Windows XP
SP1 still experiencing
the

.

 

[chris]

Hello,

We were able to get our users to connect to Exchange by exporting the
registry key [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\ClientProtocols]
from another Windows XP machine (that had no problems or that didn't
have Office 2003 installed) and then importing it to the affected
machine. This seemed to have fixed the problem.

Success! I was ready to give up on it, too. I wonder why entering
the values manually didn't work, but exporting and importing on the
broken machine did. In my case, I exported from 2k3 server w/o
Office.

Then again, I did install a couple of patches from MS this week..

- C

 

[Matt]

Unfortunatly for me I dont have another machine that is going to be
running Outlook 2003. Which means I can't export the reg keys from
another working computer. I added the 3 missing keys, so I now have a
total of 4 in there as per the microsoft kb article. Im still
receiving the error about RPC though, any suggestions? I went back
through it a few times now, character for character making sure
everything was right, no typos. the "rpcrt4.dll" value thats entered
to the key, correct me if im wrong but it doesnt have to be Capital
Rpcrt4.dll, or does it? Help ... please ... its appreciated