MultiTrends
asked on
Exchange 2007 meltdown, fixed, but now this strange error
We had a major issue with our main exchange DB recently, it caused me to create a new DB and use a recovery storage group to restore the old DB.. Now it seems when email comes in to mailboxes that reside on that mailbox DB they >DO< arrive just fine, but there is also a bounce message to the original sender:
Generating server: internalfqdn.com
anyone@mycompany.com
#< #5.2.0 smtp;550 5.2.0 STOREDRV.Deliver: The Microsoft Exchange Information Store service reported an error. The following information should help identify the cause of this error: "MapiExceptionCallFailed:1 6.18969:E7 1B0000, 17.27161:000000006A0000000 00000001F0 0000000000 000, 255.23226:00000000, 255.27962:7A000000, 255.27962:0A000000, 255.27962:0E000000, 255.17082:B6040000, 0.27745:94000000, 4.21921:B6040000, 255.27962:FA000000, 255.1494:0F010480, 255.26426:0E000000, 255.1750:2F400000, 0.26849:4F000000, 255.21817:B6040000".> #SMTP#
Any idea?
Generating server: internalfqdn.com
anyone@mycompany.com
#< #5.2.0 smtp;550 5.2.0 STOREDRV.Deliver: The Microsoft Exchange Information Store service reported an error. The following information should help identify the cause of this error: "MapiExceptionCallFailed:1
Any idea?
Try re-creating your send and receive connectors.
Do you have journaling enabled? If so, disable it and see if that clears it up.
@https://www.experts-exchange.com/questions/23609530/Cant-send-receive-mail-within-domain-Can-only-receive-mail-from-outside-domain.html
@https://www.experts-exchange.com/questions/23609530/Cant-send-receive-mail-within-domain-Can-only-receive-mail-from-outside-domain.html
ASKER
recreated receive connector, monitoring.
- not sure where to set journaling..I didn't turn it on
- not sure where to set journaling..I didn't turn it on
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
no dice on the receive connector.
ASKER
Journalling not on. thanks for the CMDLET
Check this out...
You receive a 5.2.0 non-delivery report (NDR) message when you send an e-mail message to an Exchange 2007 server that is running the Isinteg.exe tool in a dismounted mailbox store: http://support.microsoft.com/kb/932515/
You receive a 5.2.0 non-delivery report (NDR) message when you send an e-mail message to an Exchange 2007 server that is running the Isinteg.exe tool in a dismounted mailbox store: http://support.microsoft.com/kb/932515/
ASKER
It might be important to note that I still get the emails, the bounce is a false bounce...
and not >ALL< inbound email gets that bounce..when I test from my gmail account it works fine, no bounce. When someone emails from a domino server, bouce message.
and not >ALL< inbound email gets that bounce..when I test from my gmail account it works fine, no bounce. When someone emails from a domino server, bouce message.
ASKER
__________________________ __________ _
RE: Check this out...
You receive a 5.2.0 non-delivery report (NDR) message when you send an e-mail message to an Exchange 2007 server that is running the Isinteg.exe tool in a dismounted mailbox store: http://support.microsoft.com/kb/932515/
__________________________ __________ _
My DB is mounted and functional currently.
I >DID< dismount it and do work on the old DB but nevertheless..
I'm going to move a mailbox to a different infostore and see if it works there..
RE: Check this out...
You receive a 5.2.0 non-delivery report (NDR) message when you send an e-mail message to an Exchange 2007 server that is running the Isinteg.exe tool in a dismounted mailbox store: http://support.microsoft.com/kb/932515/
__________________________
My DB is mounted and functional currently.
I >DID< dismount it and do work on the old DB but nevertheless..
I'm going to move a mailbox to a different infostore and see if it works there..
How are the resources looking on the repaired Exchange server?
Moving the mailbox and or disconnecting and re-connecting the mailboxes to the culprit users is a good idea.
Moving the mailbox and or disconnecting and re-connecting the mailboxes to the culprit users is a good idea.
ASKER
Moving my mailbox to the 3rd storage group/other maildb works.. something appears fubar with the 1st storage group as the DB is brand new..
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.