Exchange 2003, Outlook 2007 issue. I've already tried kb938650 to no avail.

I've notice the problem only occurs with meeting updates, not the initial requests. it may have something to do with Outlook 2007, because all the failures seem to come from stations that have that version installed.

I also have a couple of offsite people that connect in via IMAP, and their connections generate event ID 1023 in IMAP4SVC with the description: "Error 0x7da occurred while rendering message [MessageID] for download for user [EmailAddress]." when downloading the meeting request updates in question.

In addtion, we use GFI Mail Archiver to archive all our mail. It connects to the exchange server via IMAP and it chokes when trying to download the same meeting updates.

This appears to be some kind of formatting problem with the way Outlook 2007 sends meeting request updates in Exchange 2003, but that is just an educated guess.

I've also confirmed what Kfi and laur said about the SMTP service not even making an outbound connection to deliver the items. It chokes while trying to render the message for delivery and doesn't even get far enough to attempt an outbound connection to send the message. it just sits in the queue until expiration failure.

If anyone has any solutions, thanks in advance!



Mel Kerner wrote:

You are required to be a member to post replies.
21-Aug-09

You are required to be a member to post replies. After logging in or becoming a member, you will be redirected back to this page.

Previous Posts In This Thread:

On Friday, April 25, 2008 10:41 AM
laur wrote:

Updates to meetings coming back undeliverable
Users in our organization are reporting an issue when sending meeting
updates. The first time they send the meeting request to internal employees
or outside customers, everything is fine and the meeting schedules without a
problem. If the organizer needs to make a modification to the meeting, say
the time, an undeliverable report will be sent to them that it did not reach
all recipients, but only for outside email addresses. The undeliverable does
not come back right away. The email appears to sit in the queue until it
times out. The undeliverable received is "could not deliver the message in
the time limit specified. 4.4.7". So to the organizer, they think everything
has been sent out and updated without any problems because they don't receive
any undeliverable right away. We are running Exchange 2003 and all users
have Office 2007. Any help would be appreciated.

Thanks!
Laura

On Saturday, April 26, 2008 12:29 PM
Diane Poremsky {MVP} wrote:

Updates to meetings coming back undeliverable
From http://support.microsoft.com/kb/284204
Numeric Code: 4.4.7

Possible Cause: The message in the queue has expired. The sending server
tried to relay or deliver the message, but the action was not completed
before the message expiration time occurred. This NDR may also indicate that
a message header limit has been reached on a remote server or that some
other protocol timeout occurred during communication with the remote server.
Troubleshooting: This code typically indicates an issue on the receiving
server. Verify the validity of the recipient address, and verify that the
receiving server is configured to receive messages correctly. You may have
to reduce the number of recipients in the header of the message for the host
that you are receiving this NDR from. If you resend the message, it is
placed in the queue again. If the receiving server is on line, the message
is delivered.

Obviously, if its an update, the address and # of recipients should be ok.
Does the NDR give any clues as to why its not getting sent or accepted by
the outside server?

--
Diane Poremsky [MVP - Outlook]
Author, Teach Yourself Outlook 2003 in 24 Hours
Need Help with Common Tasks? http://www.outlook-tips.net/beginner/
Outlook 2007: http://www.slipstick.com/outlook/ol2007/

Outlook Tips by email:


Outlook Tips: http://www.outlook-tips.net/
Outlook & Exchange Solutions Center: http://www.slipstick.com
Subscribe to Exchange Messaging Outlook newsletter:




"laura" wrote in message
...

On Tuesday, April 29, 2008 10:47 AM
laur wrote:

there doesn't seem to any indication why the email would just sit in the
there doesn't seem to any indication why the email would just sit in the
message queue until it timed out. that's what is so confusing, they're
correct email addresses! i don't know what to look for next....


"Diane Poremsky {MVP}" wrote:

On Wednesday, June 25, 2008 1:51 PM
sher wrote:

Updates to meetings coming back undeliverable
Did you figure this out? We are having the same problem.

"laura" wrote:

On Friday, June 27, 2008 7:29 AM
Kfi wrote:

Did anyone find what is the cause and how to fix?
Did anyone find what is the cause and how to fix?

We have the same problem as well. The one thing I think we have in common
and might be a clue is that the server is Exchange 2003 (SP2) and the meeting
update requests are coming from Outlook 2007. From outlook 2003 We do not
have that problem. This happens randomly.

I checked the logs of our firewall and when it happens the Exchanges server
doesn't even try to connect outside to send the message. It just sit in queue
until it bounces as non delivery.

Kfir

"sheri" wrote:

On Monday, June 30, 2008 9:01 AM
laur wrote:

Still haven't found a resolution to this issue.
Still haven't found a resolution to this issue. I would suspect it has
something to do with the combo of Exchange 2003 and Outlook 2007.
Frustrating because, like you said, the message just sits in the queue until
it expires. It never attempts to contact the other mail server.

"Kfir" wrote:

On Thursday, July 24, 2008 6:41 PM
rya wrote:

I too am having this problem... nothing found on Google...
I too am having this problem... nothing found on Google... any help would be
greatly appreciated.

-- Ryan

"laura" wrote:

On Friday, July 25, 2008 1:29 PM
Ryan Carnel wrote:

Updates to meetings coming back undeliverable
http://support.microsoft.com/kb/938650/en-us

"laura" wrote:

On Friday, August 21, 2009 12:57 PM
Mel Kerner wrote:

You are required to be a member to post replies.
You are required to be a member to post replies. After logging in or becoming a member, you will be redirected back to this page.

EggHeadCafe - Software Developer Portal of Choice
License ASP.NET Applications - Desaware vs Microsoft SLP
http://www.eggheadcafe.com/tutorials/aspnet/d7bad06f-dc88-4254-98ef-45699c35efd9/license-aspnet-applicati.aspx

Do you have Office 2007 SP2 installed? Any client side hotfixes installed?

--
Diane Poremsky [MVP - Outlook]
Outlook Tips: http://www.outlook-tips.net/
Outlook & Exchange Solutions Center: http://www.slipstick.com/

Outlook Tips by email:


EMO - a weekly newsletter about Outlook and Exchange:




"David Laughlin" wrote in message
...
Exchange 2003, Outlook 2007 issue. I've already tried kb938650 to no
avail.

I've notice the problem only occurs with meeting updates, not the initial
requests. it may have something to do with Outlook 2007, because all the
failures seem to come from stations that have that version installed.

I also have a couple of offsite people that connect in via IMAP, and their
connections generate event ID 1023 in IMAP4SVC with the description:
"Error 0x7da occurred while rendering message [MessageID] for download for
user [EmailAddress]." when downloading the meeting request updates in
question.

In addtion, we use GFI Mail Archiver to archive all our mail. It connects
to the exchange server via IMAP and it chokes when trying to download the
same meeting updates.

This appears to be some kind of formatting problem with the way Outlook
2007 sends meeting request updates in Exchange 2003, but that is just an
educated guess.

I've also confirmed what Kfi and laur said about the SMTP service not even
making an outbound connection to deliver the items. It chokes while
trying to render the message for delivery and doesn't even get far enough
to attempt an outbound connection to send the message. it just sits in
the queue until expiration failure.

If anyone has any solutions, thanks in advance!



Mel Kerner wrote:

You are required to be a member to post replies.
21-Aug-09

You are required to be a member to post replies. After logging in or
becoming a member, you will be redirected back to this page.

Previous Posts In This Thread:

On Friday, April 25, 2008 10:41 AM
laur wrote:

Updates to meetings coming back undeliverable
Users in our organization are reporting an issue when sending meeting
updates. The first time they send the meeting request to internal
employees
or outside customers, everything is fine and the meeting schedules without
a
problem. If the organizer needs to make a modification to the meeting,
say
the time, an undeliverable report will be sent to them that it did not
reach
all recipients, but only for outside email addresses. The undeliverable
does
not come back right away. The email appears to sit in the queue until it
times out. The undeliverable received is "could not deliver the message
in
the time limit specified. 4.4.7". So to the organizer, they think
everything
has been sent out and updated without any problems because they don't
receive
any undeliverable right away. We are running Exchange 2003 and all users
have Office 2007. Any help would be appreciated.

Thanks!
Laura

On Saturday, April 26, 2008 12:29 PM
Diane Poremsky {MVP} wrote:

Updates to meetings coming back undeliverable
From http://support.microsoft.com/kb/284204
Numeric Code: 4.4.7

Possible Cause: The message in the queue has expired. The sending server
tried to relay or deliver the message, but the action was not completed
before the message expiration time occurred. This NDR may also indicate
that
a message header limit has been reached on a remote server or that some
other protocol timeout occurred during communication with the remote
server.
Troubleshooting: This code typically indicates an issue on the receiving
server. Verify the validity of the recipient address, and verify that the
receiving server is configured to receive messages correctly. You may have
to reduce the number of recipients in the header of the message for the
host
that you are receiving this NDR from. If you resend the message, it is
placed in the queue again. If the receiving server is on line, the message
is delivered.

Obviously, if its an update, the address and # of recipients should be ok.
Does the NDR give any clues as to why its not getting sent or accepted by
the outside server?

--
Diane Poremsky [MVP - Outlook]
Author, Teach Yourself Outlook 2003 in 24 Hours
Need Help with Common Tasks? http://www.outlook-tips.net/beginner/
Outlook 2007: http://www.slipstick.com/outlook/ol2007/

Outlook Tips by email:


Outlook Tips: http://www.outlook-tips.net/
Outlook & Exchange Solutions Center: http://www.slipstick.com
Subscribe to Exchange Messaging Outlook newsletter:




"laura" wrote in message
...

On Tuesday, April 29, 2008 10:47 AM
laur wrote:

there doesn't seem to any indication why the email would just sit in the
there doesn't seem to any indication why the email would just sit in the
message queue until it timed out. that's what is so confusing, they're
correct email addresses! i don't know what to look for next....


"Diane Poremsky {MVP}" wrote:

On Wednesday, June 25, 2008 1:51 PM
sher wrote:

Updates to meetings coming back undeliverable
Did you figure this out? We are having the same problem.

"laura" wrote:

On Friday, June 27, 2008 7:29 AM
Kfi wrote:

Did anyone find what is the cause and how to fix?
Did anyone find what is the cause and how to fix?

We have the same problem as well. The one thing I think we have in common
and might be a clue is that the server is Exchange 2003 (SP2) and the
meeting
update requests are coming from Outlook 2007. From outlook 2003 We do not
have that problem. This happens randomly.

I checked the logs of our firewall and when it happens the Exchanges
server
doesn't even try to connect outside to send the message. It just sit in
queue
until it bounces as non delivery.

Kfir

"sheri" wrote:

On Monday, June 30, 2008 9:01 AM
laur wrote:

Still haven't found a resolution to this issue.
Still haven't found a resolution to this issue. I would suspect it has
something to do with the combo of Exchange 2003 and Outlook 2007.
Frustrating because, like you said, the message just sits in the queue
until
it expires. It never attempts to contact the other mail server.

"Kfir" wrote:

On Thursday, July 24, 2008 6:41 PM
rya wrote:

I too am having this problem... nothing found on Google...
I too am having this problem... nothing found on Google... any help would
be
greatly appreciated.

-- Ryan

"laura" wrote:

On Friday, July 25, 2008 1:29 PM
Ryan Carnel wrote:

Updates to meetings coming back undeliverable
http://support.microsoft.com/kb/938650/en-us

"laura" wrote:

On Friday, August 21, 2009 12:57 PM
Mel Kerner wrote:

You are required to be a member to post replies.
You are required to be a member to post replies. After logging in or
becoming a member, you will be redirected back to this page.

EggHeadCafe - Software Developer Portal of Choice
License ASP.NET Applications - Desaware vs Microsoft SLP
http://www.eggheadcafe.com/tutorials/aspnet/d7bad06f-dc88-4254-98ef-45699c35efd9/license-aspnet-applicati.aspx

I'm still having the calendar issue as described in kb938650 after applying
the described fix in http://support.microsoft.com/default.aspx/kb/938650. I
beleive all Office 2007 updates have been applied, I will verify tomorrow.

"David Laughlin" wrote:

Exchange 2003, Outlook 2007 issue. I've already tried kb938650 to no avail.

I've notice the problem only occurs with meeting updates, not the initial requests. it may have something to do with Outlook 2007, because all the failures seem to come from stations that have that version installed.

I also have a couple of offsite people that connect in via IMAP, and their connections generate event ID 1023 in IMAP4SVC with the description: "Error 0x7da occurred while rendering message [MessageID] for download for user [EmailAddress]." when downloading the meeting request updates in question.

In addtion, we use GFI Mail Archiver to archive all our mail. It connects to the exchange server via IMAP and it chokes when trying to download the same meeting updates.

This appears to be some kind of formatting problem with the way Outlook 2007 sends meeting request updates in Exchange 2003, but that is just an educated guess.

I've also confirmed what Kfi and laur said about the SMTP service not even making an outbound connection to deliver the items. It chokes while trying to render the message for delivery and doesn't even get far enough to attempt an outbound connection to send the message. it just sits in the queue until expiration failure.

If anyone has any solutions, thanks in advance!



Mel Kerner wrote:

You are required to be a member to post replies.
21-Aug-09

You are required to be a member to post replies. After logging in or becoming a member, you will be redirected back to this page.

Previous Posts In This Thread:

On Friday, April 25, 2008 10:41 AM
laur wrote:

Updates to meetings coming back undeliverable
Users in our organization are reporting an issue when sending meeting
updates. The first time they send the meeting request to internal employees
or outside customers, everything is fine and the meeting schedules without a
problem. If the organizer needs to make a modification to the meeting, say
the time, an undeliverable report will be sent to them that it did not reach
all recipients, but only for outside email addresses. The undeliverable does
not come back right away. The email appears to sit in the queue until it
times out. The undeliverable received is "could not deliver the message in
the time limit specified. 4.4.7". So to the organizer, they think everything
has been sent out and updated without any problems because they don't receive
any undeliverable right away. We are running Exchange 2003 and all users
have Office 2007. Any help would be appreciated.

Thanks!
Laura

On Saturday, April 26, 2008 12:29 PM
Diane Poremsky {MVP} wrote:

Updates to meetings coming back undeliverable
From http://support.microsoft.com/kb/284204
Numeric Code: 4.4.7

Possible Cause: The message in the queue has expired. The sending server
tried to relay or deliver the message, but the action was not completed
before the message expiration time occurred. This NDR may also indicate that
a message header limit has been reached on a remote server or that some
other protocol timeout occurred during communication with the remote server.
Troubleshooting: This code typically indicates an issue on the receiving
server. Verify the validity of the recipient address, and verify that the
receiving server is configured to receive messages correctly. You may have
to reduce the number of recipients in the header of the message for the host
that you are receiving this NDR from. If you resend the message, it is
placed in the queue again. If the receiving server is on line, the message
is delivered.

Obviously, if its an update, the address and # of recipients should be ok.
Does the NDR give any clues as to why its not getting sent or accepted by
the outside server?

--
Diane Poremsky [MVP - Outlook]
Author, Teach Yourself Outlook 2003 in 24 Hours
Need Help with Common Tasks? http://www.outlook-tips.net/beginner/
Outlook 2007: http://www.slipstick.com/outlook/ol2007/

Outlook Tips by email:


Outlook Tips: http://www.outlook-tips.net/
Outlook & Exchange Solutions Center: http://www.slipstick.com
Subscribe to Exchange Messaging Outlook newsletter:




"laura" wrote in message
...

On Tuesday, April 29, 2008 10:47 AM
laur wrote:

there doesn't seem to any indication why the email would just sit in the
there doesn't seem to any indication why the email would just sit in the
message queue until it timed out. that's what is so confusing, they're
correct email addresses! i don't know what to look for next....


"Diane Poremsky {MVP}" wrote:

On Wednesday, June 25, 2008 1:51 PM
sher wrote:

Updates to meetings coming back undeliverable
Did you figure this out? We are having the same problem.

"laura" wrote:

On Friday, June 27, 2008 7:29 AM
Kfi wrote:

Did anyone find what is the cause and how to fix?
Did anyone find what is the cause and how to fix?

We have the same problem as well. The one thing I think we have in common
and might be a clue is that the server is Exchange 2003 (SP2) and the meeting
update requests are coming from Outlook 2007. From outlook 2003 We do not
have that problem. This happens randomly.

I checked the logs of our firewall and when it happens the Exchanges server
doesn't even try to connect outside to send the message. It just sit in queue
until it bounces as non delivery.

Kfir

"sheri" wrote:

On Monday, June 30, 2008 9:01 AM
laur wrote:

Still haven't found a resolution to this issue.
Still haven't found a resolution to this issue. I would suspect it has
something to do with the combo of Exchange 2003 and Outlook 2007.
Frustrating because, like you said, the message just sits in the queue until
it expires. It never attempts to contact the other mail server.

"Kfir" wrote:

On Thursday, July 24, 2008 6:41 PM
rya wrote:

I too am having this problem... nothing found on Google...
I too am having this problem... nothing found on Google... any help would be
greatly appreciated.

-- Ryan

"laura" wrote:

On Friday, July 25, 2008 1:29 PM
Ryan Carnel wrote:

Updates to meetings coming back undeliverable
http://support.microsoft.com/kb/938650/en-us

"laura" wrote:

On Friday, August 21, 2009 12:57 PM
Mel Kerner wrote:

You are required to be a member to post replies.
You are required to be a member to post replies. After logging in or becoming a member, you will be redirected back to this page.

EggHeadCafe - Software Developer Portal of Choice
License ASP.NET Applications - Desaware vs Microsoft SLP
http://www.eggheadcafe.com/tutorials/aspnet/d7bad06f-dc88-4254-98ef-45699c35efd9/license-aspnet-applicati.aspx
.