Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Wednesday, December 8, 2010 9:21 PM
A message with the Internal Message ID 614908 was rejected by the remote server. This message will be deferred and retried because it was marked for retry if rejected. Other messages may also have encountered this error.
-and-
400 4.4.7 The server responded with: 554 5.2.0 STOREDRV.Deliver.Exception:PropertyErrorException; Failed to process message due to a permanent exception with message Property: [0x67480014] FID, PropertyErrorCode: AccessDenied, PropertyErrorDescription: . PropertyErrorException: Property: [0x67480014] FID, PropertyErrorCode: AccessDenied, PropertyErrorDescription: .. The failure was replaced by a retry response because the message was marked for retry if rejected.
All replies (9)
Wednesday, December 8, 2010 10:52 PM
And your question is?
Simply posting an error message on its own doesn't really help anyone to answer any question, if there is indeed a question there.
Simon.
Simon Butler, Exchange MVP
Blog | Exchange Resources
Thursday, December 9, 2010 2:57 AM
i am running exchange 2010 sp1 in a DAG 2 servers 2 sites and i am experiencing this error message when messages are being journaled. not sure if anyone has come across this issue or not.
Tuesday, January 4, 2011 3:18 PM
Hi,
i have the same error messages.
Many messages are in the queue from the mailbox database local delivery. Destination is the mailbox for the journal. The from adresse is empty.
The messages seems to be the one who users download via POP3 from ohter accounts and store into their Mailbox.
Server:
Exchange 2010 SP1 Rollup 1
Full Error Message from Queue:
400 4.4.7 The server responded with: 554 5.2.0 STOREDRV.Deliver.Exception:PropertyErrorException; Failed to process message due to a permanent exception with message Eigenschaft: [0x67480014] FID, PropertyErrorCode: AccessDenied, PropertyErrorDescription: ''. PropertyErrorException: Eigenschaft: [0x67480014] FID, PropertyErrorCode: AccessDenied, PropertyErrorDescription: ''.. The failure was replaced by a retry response because the message was marked for retry if rejected.
Any ideas?
Greetings
Florian
Friday, March 25, 2011 9:10 PM
Hi Guys,
I am having the same problem but only from one outside sender. 10 people in my organization receive this email from the sender everyday but only 4 users email is getting journaled. The rest 6 is getting stuck in the queue with same same error message as der_schaefer. Below is the error message again. Its weird that it is only happening to the emails send by this one outside email address.
Server:Exchange 2010 SP1
Last Error: 400 4.4.7 The server responded with: 554 5.2.0 STOREDRV.Deliver.Exception:PropertyErrorException; Failed to process message due to a permanent exception with message Property: [0x67480014] FID, PropertyErrorCode: AccessDenied, PropertyErrorDescription: . PropertyErrorException: Property: [0x67480014] FID, PropertyErrorCode: AccessDenied, PropertyErrorDescription: .. The failure was replaced by a retry response because the message was marked for retry if rejected.
Did anybody get this resolved? Any help would be appreciated.
Thanks,
Hitul
Friday, December 30, 2011 4:53 PM
this is a bug.
fixed in http://support.microsoft.com/kb/2536702
rgds
Caio Ribeiro Cesar
Wednesday, April 25, 2012 11:25 PM
Hello,
I don't think it is that same bug. I have this same issue and this past weekend we upgraded to SP2 with update rollup 1. The problem continues. In our case, it's a user who has a 3rd party IMAP account as well as an Exchange account. Exchange is her default storage, even though IMAP delivers to its own mailbox... she uses SMTP to deliver through the 3rd party as well. But, when Outlook 2010 puts the message in the Outbox on Exchange for a split second, somehow our internal server name and an email message ID are being stamped in the properties/header of the message. Then if she's sending to one of our Exchange users (goes out through the 3rd party and gets delivered via SMTP into our mail server), I get the same above errors and the message stuck in the queue for Journaling. We had messages stuck for 2 months!
If anyone has further thoughts to try, I'd appreciate hearing about them.
Thanks,
H
Thursday, July 5, 2012 8:06 PM
Anybody yet has an idea? I have the same issue, so far noticed it happening only on journaling mailbox and we have sp2 and and all the rollups up to the now. So far did not see much info regarding this on the internet and my solution is just to delete this garbage time to time - not a solution, obviously. Would hate to open call to MS - for the last couple of years their support got really bad, takes days and repetitions of stupids steps to resolve a simple problem if at all. Besides, with incredible number of bugs and loopholes in E2010 calling MS for each one would deplete us financially so fast that email would become the least of my problems.
I will try to investigate a little deeper the issue and post whatever I find. But any help would be appreciated.
Thursday, July 5, 2012 9:50 PM
Hi Vadim2,
Just an FYI, If it turns out that the problem that you are experiencing is a bug, Microsoft Support won't charge you.
Rajith Enchiparambil | http://www.howexchangeworks.com |
Saturday, August 25, 2012 8:27 PM
Here is a reference that sounds more specific to your issue: http://support.microsoft.com/kb/2686540