Re: Outlook client fails to connect to Exchange Server 2000 but OW
- From: Shaf <Shaf@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 7 Sep 2006 02:26:02 -0700
Sorry Sir I cud not respond yesterday, the server did not develop this
problem suddenly, there were errors in the logs even before this. I got the
hardware issue sorted out with the IBM heldesk yesterday. They did not do any
changes with the OS or other software, they asked me to clear the BIOS logs.
The 3rd Intel NIC tht I had mentioned, I have removed it.
As u hav mentioned that ipconfig/all cud tell of any config problems, I
think theres no problem with tht as nslookup works fine and then netdiag also
does not fail the DNS test.
Now I tried to get help from 1 guy workin with MS Exchange, he told me tht
it may b an issue with the MAPI driver.
Thanks
"Lanwench [MVP - Exchange]" wrote:
In news:20A8BE2F-82B8-4481-8F83-F082D375EC99@xxxxxxxxxxxxx,.
Shaf <Shaf@xxxxxxxxxxxxxxxxxxxxxxxxx> typed:
Thanks for your response :) Sir
We have a single MS Exchange Server 2000 which works as a member
server in our domain. Now the problem is that it restarted once due
to some problem
More info there might help...
******** The server is IBM eServer x225 running WIndows 2000 Advanced
Server with 3 NIC's now, onboard Broadcom NIC which is assigned a
static address 192.168.0.230/24, the 2nd NIC Compex make connected to
public network
I would not recommend that. Get a router / firewall and use a single NIC ...
otherwise you have to be using RRAS/NAT, and I really don't see the value
in making your server do that. If you must, then see
http://support.microsoft.com/?kbid=299801 and make sure you've got it
configured properly.
and a 3rd from Intel as backup and is not used coz the
Compext NIC was had problems some time ago but recntly was
functioning smoothly.
So this one is disabled, right? If not, disable it. Or remove it.
The error LED was turned on so I spoke to local
support guys and they asked for some time
Not sure what that means. I guess you mean that they worked on it? What
exactly did they do?
and during this the server
restarted.
All by itself?
and since then Outlook clients are unable to connect to it
What errors? ******there were a lot of errors but I found this one
more relevant
but OWA works. Now I had an error in the log saying MAPI cannot load
emsabp.dll
Which log? ******The error was in the Application log.
so what I did was searched for the file and found
emsabp32.dll so what I did was made a copy of it and renamed it to
emsabp.dll, all the errors have vanished but the problem still
remains, I can access exchange thru OWA but not thru Outlook client.
I will mention a few errors below.
Application Log
Event Id: 1005
Source: MSExchangeSA
Unexpected error <<0xc1050000 - Network problems are preventing
connection to the Microsoft Exchange Server computer. Contact your
system administrator if this condition persists. MAPI was unable to
load the information service emsabp.dll. Be sure the service is
correctly installed and configured. Microsoft Exchange Address Book
ID no: 00040380-0000-00000000>> occurred.
Was this before or after the local support guys did whatever they did?
Event Id: 8197
Source: MSExchangeFBPublish
Error initializing session for virtual machine MAIL. The error number
is 0x80040111. Make sure Microsoft Exchange Store is running.
But it is, right? You can mount the stores, and open mailboxes in OWA...
System Log
Information Event
Event Id: 6006
The description for Event ID ( 9 ) in Source ( b57w2k ) cannot be
found. The local computer may not have the necessary registry
information or message DLL files to display messages from a remote
computer. The following information is part of the event: , Broadcom
NetXtreme Gigabit Ethernet.
I think this is a big part of your problem, and is probably related to your
network config (which again I do not recommend). You might post an unedited
ipconfig /all from the server.
Event Id: 36871
The description for Event ID ( 36871 ) in Source ( Schannel ) cannot
be found. The local computer may not have the necessary registry
information or message DLL files to display messages from a remote
computer. The following information is part of the event: server.
These errors no longer exist but still the connection to Exchange thru
Outlook client fails whereas theres no problem with OWA I can send
emails to anyone over the internet and receive also.
One more thing SIR I have not learnt Exchange yet, I am an MCSA
though, and had to take care of the Exchange server while my
colleague was out for his wedding and this is wht I hav ended up
with. Plz help.
I'm curious as to what happened in the first place. Did the server just
suddenly develop this problem? Outlook clients could connect, OWA worked, no
errors in the event logs, and then .... ? The problem can't be due entirely
to the server restarting; a restart alone shouldn't be causing errors.
Thanks in advance.
"Lanwench [MVP - Exchange]" wrote:
In news:A6B10BCA-83CA-482D-903F-C8E2ED57E1C6@xxxxxxxxxxxxx,
Shaf <Shaf@xxxxxxxxxxxxxxxxxxxxxxxxx> typed:
Hello
We have a single MS Exchange Server 2000 which works as a member
server in our domain. Now the problem is that it restarted once due
to some problem
More info there might help...
and since then Outlook clients are unable to connect
to it
What errors?
but OWA works. Now I had an error in the log saying MAPI cannot
load emsabp.dll
Which log?
so what I did was searched for the file and found
emsabp32.dll so what I did was made a copy of it and renamed it to
emsabp.dll, all the errors have vanished but the problem still
remains, I can access exchange thru OWA but not thru Outlook client.
Thanks in advance.
regards
Shafiuddin A Kazi
- Follow-Ups:
- Re: Outlook client fails to connect to Exchange Server 2000 but OW
- From: Lanwench [MVP - Exchange]
- Re: Outlook client fails to connect to Exchange Server 2000 but OW
- References:
- Re: Outlook client fails to connect to Exchange Server 2000 but OWA wo
- From: Lanwench [MVP - Exchange]
- Re: Outlook client fails to connect to Exchange Server 2000 but OW
- From: Shaf
- Re: Outlook client fails to connect to Exchange Server 2000 but OWA wo
- Prev by Date: TLS/SSL capabilities on Outlook 2003
- Next by Date: Re: TLS/SSL capabilities on Outlook 2003
- Previous by thread: Re: Outlook client fails to connect to Exchange Server 2000 but OW
- Next by thread: Re: Outlook client fails to connect to Exchange Server 2000 but OW
- Index(es):
Relevant Pages
|
Loading