robclarke41
asked on
Exchange 2003 Queue on VMWare filling up
Hi All,
I've setup an Exchange 2003 server that is a replica of our production Exchange server in a VMWare workstation environment. It all works fine and I can connect other VM machines to it via Outlook and send mail between them (Internally). The only problem is that the queue in C:\Program Files\Exchsrvr\Mailroot\vs i 1 keeps filling up with mail. Does anyone know how I can stop this happening? Al I want is to be able to send and receive internally without this folder filling up the VM machines hardrive!
Any help appreciated, thanks.
I've setup an Exchange 2003 server that is a replica of our production Exchange server in a VMWare workstation environment. It all works fine and I can connect other VM machines to it via Outlook and send mail between them (Internally). The only problem is that the queue in C:\Program Files\Exchsrvr\Mailroot\vs
Any help appreciated, thanks.
ASKER
Well its a virtual machine in an isolated test environment so there shouldn't be any mails being sent?
How would I setup diagnosis logging for MSExchangeTransport?
How would I setup diagnosis logging for MSExchangeTransport?
If you feel messages are not important, you can stop SMTP service and delete mails from the "C:\Program Files\Exchsrvr\Mailroot\vs i 1".
You should first check for the queues as suggested by shabarinath and then take necessary action.
You should first check for the queues as suggested by shabarinath and then take necessary action.
ASKER
Ok I can see that the queues are filling up and I have already had to delete items from the vsi 1 location just to get the server functioning again as the C:\ drive was completely full. How do I stop this filling up again though?
as smartsid and shabarinath said you'll have to increase diagnostic logging. In 2003 this is done in the ESM by righ clicking the server object and then going to the tab "diagnostic logging" Here you can set the logging for MSExchangeTransport to maximum
If no mails are send through this server, then you need to see what is getting stuck.
Did you get a change to look on the Exchange System Manager queue?
Good luck
Shaba
Did you get a change to look on the Exchange System Manager queue?
Good luck
Shaba
ASKER
Ok thanks guys I'll try the above suggestions and get back to you soon.
ASKER
Hi guys,
I've enabled the logging and am getting thousands of these! Is this the cause?
Event Type: Warning
Event Source: MSExchangeTransport
Event Category: NDR
Event ID: 3006
Date: 27/09/2010
Time: 14:43:18
User: N/A
Computer: Exchange
Description:
A non-delivery report with a status code of 4.4.7 was generated for recipient rfc822;message_journal@myd omain (Message-ID <Exchange13pL32ctFfj800002 450@exchan ge.mydomai n>).
Cause: Message in queue has expired. The sending server tried to relay or deliver the message but the action could not be completed before the message expired.
Solution: This message usually indicates a problem on the receiving server. Check the validity of recipients address and verify that the receiving server is configured to receive messages correctly. Resending the message will place it again in the queue, if the receiving server is up, message delivery will succeed.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: d1 02 04 c0 Ñ..À
I've enabled the logging and am getting thousands of these! Is this the cause?
Event Type: Warning
Event Source: MSExchangeTransport
Event Category: NDR
Event ID: 3006
Date: 27/09/2010
Time: 14:43:18
User: N/A
Computer: Exchange
Description:
A non-delivery report with a status code of 4.4.7 was generated for recipient rfc822;message_journal@myd
Cause: Message in queue has expired. The sending server tried to relay or deliver the message but the action could not be completed before the message expired.
Solution: This message usually indicates a problem on the receiving server. Check the validity of recipients address and verify that the receiving server is configured to receive messages correctly. Resending the message will place it again in the queue, if the receiving server is up, message delivery will succeed.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: d1 02 04 c0 Ñ..À
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
If so, search for the mails and subject line.
Also, suggest you to have diagnosis logging for MSExchangeTransport to get a more detailed view.
Thanks
Shaba