RPC Error with Outlook 2003 and Exchange server 2000

  • Thread starter Thread starter Mitch
  • Start date Start date
M

Mitch

If you are getting an error when attempting to connect a newly
installed version of Outlook 2003 to an existing 2000 Exchange server
and are wondering why the following solution doesn't work - make the
registry entries ON THE SERVER and boot the pile of crap and it should
start working. Mickeysoft doesn't bother to tell you that they need
to be in both locations for there crapware to work.

(sorry for the bluntness - but I've spent two days troubleshooting
this stupid thing to narrow it down to a problem that (1) isn't
documented accuratly and (2) a problem that is clearly an issue with
Microsuck, er, ..soft; so I'm a little tired and a little pissed off).

***************************************************************



Dear Miro,

Thank you for your description on this issue, I can understand it
clearly.

This issue can be caused when your client misses the ClientProtocols
registry key which is:

[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"

After you install Outlook 2003, please check it and make sure all
entries
exist in your registry.If you find that all entries all correct, then
please try to install Outlook 2003 on another computer and log on to
the
Exchange 2000 server, does this problem still exist?

I am looking for your response, have a nice weekend!

Best Regards,

John Yan

Microsoft Online Support Engineer

Get Secure! - www.microsoft.com/security

=====================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no
rights.
 
Um, if you had searched this news group , you would have found the answer in
about 5 minutes, provided by Neo-MVP Outlook. Try google groups before you
burn your next incident.

--
Milly Staples [MVP - Outlook]

Post all replies to the group to keep the discussion intact. Due to
the (insert latest virus name here) virus, all mail sent to my personal
account will be deleted without reading.

After searching google.groups.com and finding no answer, Mitch asked:

| If you are getting an error when attempting to connect a newly
| installed version of Outlook 2003 to an existing 2000 Exchange server
| and are wondering why the following solution doesn't work - make the
| registry entries ON THE SERVER and boot the pile of crap and it should
| start working. Mickeysoft doesn't bother to tell you that they need
| to be in both locations for there crapware to work.
|
| (sorry for the bluntness - but I've spent two days troubleshooting
| this stupid thing to narrow it down to a problem that (1) isn't
| documented accuratly and (2) a problem that is clearly an issue with
| Microsuck, er, ..soft; so I'm a little tired and a little pissed off).
|
| ***************************************************************
|
|
|
| Dear Miro,
|
| Thank you for your description on this issue, I can understand it
| clearly.
|
| This issue can be caused when your client misses the ClientProtocols
| registry key which is:
|
| [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"
|
| After you install Outlook 2003, please check it and make sure all
| entries
| exist in your registry.If you find that all entries all correct, then
| please try to install Outlook 2003 on another computer and log on to
| the
| Exchange 2000 server, does this problem still exist?
|
| I am looking for your response, have a nice weekend!
|
| Best Regards,
|
| John Yan
|
| Microsoft Online Support Engineer
|
| Get Secure! - www.microsoft.com/security
|
| =====================================================
| When responding to posts, please "Reply to Group" via
| your newsreader so that others may learn and benefit
| from your issue.
| =====================================================
| This posting is provided "AS IS" with no warranties, and confers no
| rights.
 
Here is one I found in about 4 minutes of searching (and 2 minutes of
sneezing, nose-blowing, sorry, have a cold)'

http://groups.google.com/groups?q=N...#[email protected]&rnum=73


--
Milly Staples [MVP - Outlook]

Post all replies to the group to keep the discussion intact. Due to
the (insert latest virus name here) virus, all mail sent to my personal
account will be deleted without reading.

After searching google.groups.com and finding no answer, Mitch asked:

| If you are getting an error when attempting to connect a newly
| installed version of Outlook 2003 to an existing 2000 Exchange server
| and are wondering why the following solution doesn't work - make the
| registry entries ON THE SERVER and boot the pile of crap and it should
| start working. Mickeysoft doesn't bother to tell you that they need
| to be in both locations for there crapware to work.
|
| (sorry for the bluntness - but I've spent two days troubleshooting
| this stupid thing to narrow it down to a problem that (1) isn't
| documented accuratly and (2) a problem that is clearly an issue with
| Microsuck, er, ..soft; so I'm a little tired and a little pissed off).
|
| ***************************************************************
|
|
|
| Dear Miro,
|
| Thank you for your description on this issue, I can understand it
| clearly.
|
| This issue can be caused when your client misses the ClientProtocols
| registry key which is:
|
| [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"
|
| After you install Outlook 2003, please check it and make sure all
| entries
| exist in your registry.If you find that all entries all correct, then
| please try to install Outlook 2003 on another computer and log on to
| the
| Exchange 2000 server, does this problem still exist?
|
| I am looking for your response, have a nice weekend!
|
| Best Regards,
|
| John Yan
|
| Microsoft Online Support Engineer
|
| Get Secure! - www.microsoft.com/security
|
| =====================================================
| When responding to posts, please "Reply to Group" via
| your newsreader so that others may learn and benefit
| from your issue.
| =====================================================
| This posting is provided "AS IS" with no warranties, and confers no
| rights.
 
My thought is simlply that if I'm going to spend $2000+ on Exchange
and another $500+ on EACH instance of Office then Microsoft could
provide information about potential problems. I found the documents
on thier site and the registry hacks on Google (within about 20
minutes), but nowhere did I find that the entries needed to be made at
the server. An oversight on my part? Maybe... but it's frustrating
when we spend that much money on something that doesn't work right out
of the box.

Hopefully this information will help out somebody else who's having
the same problem! :-)
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Cannot start Outlook. Unable to open the outlook window. The set of folders coul 1
All FAX printers are Inaccessible 8
RPC over HTTP problem 3
Problem installing FAX in XP SP2 4
Error starting Outlook 2003 Beta 2 3
RPC over HTTP setup problem 2
Exchange Server 2000 and Outlook 2003 on Windows 2003 Server. 2
deleted lsass entries in the registry 7

Back
Top