Software

Ask something
Discussion Locked

Need urgent HELP with QUEUE in Exhcnage

0 helpful
6 replies

by vigo98 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have exchange 2000 SP2 on Win2k Adv. Server SP2.
This box is not an Active Directory controller.
Everything seems to work fine for about 10 mins after each reboot of Exchnage server, but after that, no messages are being delivered. All users logon using POP or IMAP, they can logon and send emails even after the 10 mins. But they wont be delivered untill the server is rebooted. Afetr the reboot all messages are delivered instantly.
I have reapplied SP2 on Exchnage last night. Don't think it helped.

Also, anybody seen an error like this when starting Exchange System Manager:

Facility: WIn32
ID no: 8007203a
Exchange System Manager

It's a message box that comes up after I click on system manager. And system manager starts but doesn't show anything(empty screen). This happens if I leave Exchnage running without rebooting for over 4 or 5 hours. Mind you, all users can still logon and send email even in this state. Exchange services are running too.
Exchange server is usingitself as a primary DNS server and Active Directory controller as secondary. There are no delivery restrictions set. Server doesn't perform reversed DNS lookup on messages.
Please ask if need any more info. Any help is trully appreciated.
Victor

6 replies

by coopachi

don't know if this will help or if you have alreay tried. buy try this document on the microsoft site. Q282186

hope it helps.
coopachi

by maxwell edison

Take a look at Microsoft article Q252331 titled, "XADM: Error Message: Failed to Get ADSI Object: 8007203A".

It states the following:

This problem can occur for either of the following reasons:

You need to hard-code the name of the Exchange Server computer in the script on which this script is running.

By default, the Active Directory Service Interface (ADSI) component communicates with the Exchange Server computer by using port 389. If the Lightweight Directory Access Protocol (LDAP) port number has been changed in Exchange Server, you must specify the correct port number in the script.

See the article for more information and the proposed resolutions.

http://support.microsoft.com/default.aspx?scid=kb;EN-US;q252331(REMOVE SPACES from the pasted URL.)

Maxwell

This discussion is closed to new replies.