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.
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.