Kantse
asked on
how to resolve this issue event id 3005.
Our exchange servers 2003 are clustered, the problem we are experiencing are mail is not delivered to some users on other virtual servers and on the bridgehead server it give us this error: event id 3005 , NDR . users are receiving mail from one virtual server. Please assist .
ASKER
Hi, users are not receiving mail internaly from this virtual server but they receive from d75fers002 and d75fers001 but they cannot send to users on d75fers003 but this users on d75fers002 can send to them.
3005.txt
3005.txt
1. For the Event ID 3005, check the below link:
https://www.experts-exchange.com/questions/21439432/Small-Business-server-2003-Exchange-error.html
2. For the event ID: 5007, are you able to failover your cluster resources? If yes, ,move the resources
to the other node and check for the message tracking. If it works, then reboot the first node and
move the resources back to this node and check.
3. Download ExTRA from Microsoft site and check for your message routing issues.
>>>> Veera.
https://www.experts-exchange.com/questions/21439432/Small-Business-server-2003-Exchange-error.html
2. For the event ID: 5007, are you able to failover your cluster resources? If yes, ,move the resources
to the other node and check for the message tracking. If it works, then reboot the first node and
move the resources back to this node and check.
3. Download ExTRA from Microsoft site and check for your message routing issues.
>>>> Veera.
ASKER
Maybe this can give you the light: When I use telnet to send to users on server d75fers003 they receive the mail, but when using outlook client they do not receive that mail and it does not give any error , except those I send to you. problem still persist.
1. If you have more than one recipient policy in exchange, check the primary SMTP for these users.
2. To verify the SMTP issues, use ADSIEDIT (available with Windows 2003 support tools) to compare it
with working ID.
3. When you do Send/Recieve in outlook, do you see any error message?
4. Check for possible OAB issues. Enable the Diagnostics logging for OAB on problematic server and
check the event log.
Did you try ExTRA?
>>>> Veera.
2. To verify the SMTP issues, use ADSIEDIT (available with Windows 2003 support tools) to compare it
with working ID.
3. When you do Send/Recieve in outlook, do you see any error message?
4. Check for possible OAB issues. Enable the Diagnostics logging for OAB on problematic server and
check the event log.
Did you try ExTRA?
>>>> Veera.
ASKER
3.When i click send/receive i dont get anny errors. I will try ADSIEDIT today , How to use ExTRA.
Go to the download page of this tool. You can see the details there itself.
OR just follow the on screen instructions.
>>>> Veera.
OR just follow the on screen instructions.
>>>> Veera.
ASKER
Today this is where we are:
Mail are delivered as follows
1. EVS001 - EVS001 >> Delivered OK
2. EVS001 - EVS002 >> Delivered OK
3. EVS001 - EVS003 >> Delivered OK
4. EVS002 - EVS001 >> Delivered OK
5. EVS002 - EVS002 >> Delivered OK
6. EVS002 - EVS003 >> Non-Delivery
7. EVS003 - EVS001 >> Delivered OK
8. EVS003 - EVS002 >> Delivered OK
9. EVS003 - EVS003 >> Delivered OK
So there seem to be a problem in sending mail from D75FEVS002 TO D75FEVS003, however, EVS003 can successfully send mail to EVS002
Mail are delivered as follows
1. EVS001 - EVS001 >> Delivered OK
2. EVS001 - EVS002 >> Delivered OK
3. EVS001 - EVS003 >> Delivered OK
4. EVS002 - EVS001 >> Delivered OK
5. EVS002 - EVS002 >> Delivered OK
6. EVS002 - EVS003 >> Non-Delivery
7. EVS003 - EVS001 >> Delivered OK
8. EVS003 - EVS002 >> Delivered OK
9. EVS003 - EVS003 >> Delivered OK
So there seem to be a problem in sending mail from D75FEVS002 TO D75FEVS003, however, EVS003 can successfully send mail to EVS002
Good statistics.
So, Enable SMTP logging on both servers and also enable diagnostics logging for all under MSExchangeTransport. make sure to increase the application log size to 32 MB or 64 MB.
If you don't get any useful hint, then enable the diagnostics logging under MSExchangeIS/Mailbox --> Transport General, Transport Delivering and Transport Sending.
Note: You can get the solutions if you use ExTRA.
>>>> Veera.
So, Enable SMTP logging on both servers and also enable diagnostics logging for all under MSExchangeTransport. make sure to increase the application log size to 32 MB or 64 MB.
If you don't get any useful hint, then enable the diagnostics logging under MSExchangeIS/Mailbox --> Transport General, Transport Delivering and Transport Sending.
Note: You can get the solutions if you use ExTRA.
>>>> Veera.
ASKER
ExTRA , is it a .exe or just Extra because i dont get any file from MS side.
ASKER
I have downloaded the EXTRA thank you. I checked my routings,DNS and tested SMTP they are fine , when i send using telnet the user does receive mail. with outlook client no delivery.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
We have one node you cannot do fail over to so we restarted both node at the same time and failed to the other node and its working thank you.
ASKER
What could have caused the hanging of mail, after we rebooted both nodes at the same time we swapped virtual servers took 003 where 002 was.
ASKER
We have one node that the system attendant fails and you cannot do fail over to this node
If the failover does not happen and the SA fails, there could have been a failure in the past which was not rectified.
1. Do a online backup of exchange and cluster.
2. Dismount the stores.
3. Delete the System Attendant resource from cluster admin. And also delete all the SA dependant
resources.
4. Recreate System Attendant, it should recreate all the other resources with you old configuration
details.
>>>> Veera.
1. Do a online backup of exchange and cluster.
2. Dismount the stores.
3. Delete the System Attendant resource from cluster admin. And also delete all the SA dependant
resources.
4. Recreate System Attendant, it should recreate all the other resources with you old configuration
details.
>>>> Veera.
And need more details about your setup.
>>>> Veera.