Check Names = "Exchange Server computer is busy..."

[Guest]

Here's what I got:

Active Directory on Server 2003
1 Domain Controller also running DNS and WINS
No other DNS or WINS servers (I know, I know)
Static IP Addresses...NO DHCP
Exchange Server 2003 on a member server
Client running W2K SP4
Outlook 2000 SP3
Exchange has 4 mailboxes set, but nobody is using it. I'm still testing
things out.

When I try to connect to Exchange via my Outlook 2000, I get the following
message:
"The function cannot be performed because the Microsoft Exchange Server
computer is busy. Try again later"

I've tried it from 3 different client computers where the only difference
between them is that they have different IP addresses. Otherwise, they are
configured the same, accessing the same servers, etc.

Event logs on the clients and Exchange server don't indicate any sort of
problems. The Exchange server can't be busy because nobody is using
Exchange. Utilization on the server is pegged a 1% (that's a one).

Here's are the kickers: From these same client computers I can access
Exchange via Outlook Web Access. Also, if I install Outlook 2003 on the same
client computers, Check Name resolves perfectly and they can send/receive
Exchange email like a champ.

I do have one diclosure - I did install Outlook 2003 on the Exchange Server,
but it has since been removed. For the record, Outlook 2003 connected to
Exchange when they were on the same computer/server.

If anybody has any help or guidance, I'd really appreciate it.

Thanks in advance.

 

[Milly Staples [MVP - Outlook]]

Installing Outlook on an Exchange server could have messed with MAPI. You
might want to try (as a last resort) reinstalling Exchange.

However, to the present problem. If you try to ping the Exchange server by
name, or IP, what happens? Have you tried a hosts file?


--
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 furious head-scratching, ITTrout asked this group:

| Here's what I got:
|
| Active Directory on Server 2003
| 1 Domain Controller also running DNS and WINS
| No other DNS or WINS servers (I know, I know)
| Static IP Addresses...NO DHCP
| Exchange Server 2003 on a member server
| Client running W2K SP4
| Outlook 2000 SP3
| Exchange has 4 mailboxes set, but nobody is using it. I'm still
| testing things out.
|
| When I try to connect to Exchange via my Outlook 2000, I get the
| following message:
| "The function cannot be performed because the Microsoft Exchange
| Server computer is busy. Try again later"
|
| I've tried it from 3 different client computers where the only
| difference between them is that they have different IP addresses.
| Otherwise, they are configured the same, accessing the same servers,
| etc.
|
| Event logs on the clients and Exchange server don't indicate any sort
| of problems. The Exchange server can't be busy because nobody is
| using Exchange. Utilization on the server is pegged a 1% (that's a
| one).
|
| Here's are the kickers: From these same client computers I can access
| Exchange via Outlook Web Access. Also, if I install Outlook 2003 on
| the same client computers, Check Name resolves perfectly and they can
| send/receive Exchange email like a champ.
|
| I do have one diclosure - I did install Outlook 2003 on the Exchange
| Server, but it has since been removed. For the record, Outlook 2003
| connected to Exchange when they were on the same computer/server.
|
| If anybody has any help or guidance, I'd really appreciate it.
|
| Thanks in advance.

 

[Guest]

I've read about how installing Outlook on the server could screw things up,
but as to the present problem of not being unable to connect to Exchange 2003
via Outlook 2000, I don't think it was a factor because I installed Outlook
on the server to verify connectivity because I couldn't get connected via the
client.

DNS and WINS are working fine. Everything resolves forwards and backwards.
Just for grins I did make specific entries in the local HOSTS file.

What perplexes me is that the error message I get doesn't reference
connectivity isssues. Rather it tells me the Exchange server is busy. The
Exchange server can't be busy because nobody can get connected to it.

Thanks for your reply!

Installing Outlook on an Exchange server could have messed with MAPI. You
might want to try (as a last resort) reinstalling Exchange.

However, to the present problem. If you try to ping the Exchange server by
name, or IP, what happens? Have you tried a hosts file?


--
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 furious head-scratching, ITTrout asked this group:

| Here's what I got:
|
| Active Directory on Server 2003
| 1 Domain Controller also running DNS and WINS
| No other DNS or WINS servers (I know, I know)
| Static IP Addresses...NO DHCP
| Exchange Server 2003 on a member server
| Client running W2K SP4
| Outlook 2000 SP3
| Exchange has 4 mailboxes set, but nobody is using it. I'm still
| testing things out.
|
| When I try to connect to Exchange via my Outlook 2000, I get the
| following message:
| "The function cannot be performed because the Microsoft Exchange
| Server computer is busy. Try again later"
|
| I've tried it from 3 different client computers where the only
| difference between them is that they have different IP addresses.
| Otherwise, they are configured the same, accessing the same servers,
| etc.
|
| Event logs on the clients and Exchange server don't indicate any sort
| of problems. The Exchange server can't be busy because nobody is
| using Exchange. Utilization on the server is pegged a 1% (that's a
| one).
|
| Here's are the kickers: From these same client computers I can access
| Exchange via Outlook Web Access. Also, if I install Outlook 2003 on
| the same client computers, Check Name resolves perfectly and they can
| send/receive Exchange email like a champ.
|
| I do have one diclosure - I did install Outlook 2003 on the Exchange
| Server, but it has since been removed. For the record, Outlook 2003
| connected to Exchange when they were on the same computer/server.
|
| If anybody has any help or guidance, I'd really appreciate it.
|
| Thanks in advance.