Recently we began seeing an increase in Delay and Failure notices in
relationship to meeting requests with outside persons. Specifically, if we
include someone that resides on an Exchange 2007 server (outside) the meeting
will surely generate a delay then subsequent failure.

If the user on the Exchange 2007 server creates the meeting, we get it just
fine. If we then try to edit the meeting; new time, new people or resources,
the request will not get back to the originator and we will receive a
delay/failure.

Now, if we send a meeting to someone on an Exchange 2003 box, no problems.

Us:

Exchange 2003 SP2
Windows 2003 SP1
Outlook 2007
Outlook 2003 SP1 & SP2

Them:
Exchange 2007
Windows 2003 SP2
Outlook 2007
Outlook 2003 SP2

Tried:
Disable Spam filters
Disable AV
Routine Exchange DB Maintenance

Message in Exchange Queue
"Unable to open message for delivery"

Message in NDR
"Could not deliver in the time specified"

Any Ideas?

Have you posted this to an Exchange group?

--�
Milly Staples [MVP - Outlook]

Post all replies to the group to keep the discussion intact. All
unsolicited mail sent to my personal account will be deleted without
reading.

After furious head scratching, LH - Brett asked:

| Recently we began seeing an increase in Delay and Failure notices in
| relationship to meeting requests with outside persons. Specifically,
| if we include someone that resides on an Exchange 2007 server
| (outside) the meeting will surely generate a delay then subsequent
| failure.
|
| If the user on the Exchange 2007 server creates the meeting, we get
| it just fine. If we then try to edit the meeting; new time, new
| people or resources, the request will not get back to the originator
| and we will receive a delay/failure.
|
| Now, if we send a meeting to someone on an Exchange 2003 box, no
| problems.
|
| Us:
|
| Exchange 2003 SP2
| Windows 2003 SP1
| Outlook 2007
| Outlook 2003 SP1 & SP2
|
| Them:
| Exchange 2007
| Windows 2003 SP2
| Outlook 2007
| Outlook 2003 SP2
|
| Tried:
| Disable Spam filters
| Disable AV
| Routine Exchange DB Maintenance
|
| Message in Exchange Queue
| "Unable to open message for delivery"
|
| Message in NDR
| "Could not deliver in the time specified"
|
| Any Ideas?

Thanks for your response. Yes, I also posted in one of the Exchange groups.

Brett

"Milly Staples [MVP - Outlook]" wrote:

Have you posted this to an Exchange group?

--�
Milly Staples [MVP - Outlook]

Post all replies to the group to keep the discussion intact. All
unsolicited mail sent to my personal account will be deleted without
reading.

After furious head scratching, LH - Brett asked:

| Recently we began seeing an increase in Delay and Failure notices in
| relationship to meeting requests with outside persons. Specifically,
| if we include someone that resides on an Exchange 2007 server
| (outside) the meeting will surely generate a delay then subsequent
| failure.
|
| If the user on the Exchange 2007 server creates the meeting, we get
| it just fine. If we then try to edit the meeting; new time, new
| people or resources, the request will not get back to the originator
| and we will receive a delay/failure.
|
| Now, if we send a meeting to someone on an Exchange 2003 box, no
| problems.
|
| Us:
|
| Exchange 2003 SP2
| Windows 2003 SP1
| Outlook 2007
| Outlook 2003 SP1 & SP2
|
| Them:
| Exchange 2007
| Windows 2003 SP2
| Outlook 2007
| Outlook 2003 SP2
|
| Tried:
| Disable Spam filters
| Disable AV
| Routine Exchange DB Maintenance
|
| Message in Exchange Queue
| "Unable to open message for delivery"
|
| Message in NDR
| "Could not deliver in the time specified"
|
| Any Ideas?

Brett,

Have you resolved this issue? I ask because we are seeing the EXACT
same thing, with one diffference: Sometimes an outgoing meeting request
to the same people it failed with before, now works. In other words, it
doesn't ALWAYS happen to the same outside people.

I get the same "Unable to open message for delivery", and when I search
the outgoing queue directory for the message, the message isn't there
(hence the error), even the the queue in System Manager says it is
there.

Paul Stemper
Magenic


--
PStemper

No resolution yet.

We are finding the same thing you are. Which is that not all requests get
held up. We have also found that the problem seels pretty random. The only
thing we have narrowed down thus is that if you send a meeting to someone at
Microsoft.com or w-link.com you will most likely get this issue.

I will keep you posted if I hear anything.

"PStemper" wrote:


Brett,

Have you resolved this issue? I ask because we are seeing the EXACT
same thing, with one diffference: Sometimes an outgoing meeting request
to the same people it failed with before, now works. In other words, it
doesn't ALWAYS happen to the same outside people.

I get the same "Unable to open message for delivery", and when I search
the outgoing queue directory for the message, the message isn't there
(hence the error), even the the queue in System Manager says it is
there.

Paul Stemper
Magenic


--
PStemper

Thanks for the update!

I am seeing the exact same thing (most requests to microsoft.com fail,
and it is sporadic.)

I am working with an MS tech to try to determine the cause and the fix.
I will let you know what I find.

Thanks again!

Paul

LH - Brett;7699567 Wrote:
No resolution yet.

We are finding the same thing you are. Which is that not all requests
get
held up. We have also found that the problem seels pretty random. The
only
thing we have narrowed down thus is that if you send a meeting to
someone at
Microsoft.com or w-link.com you will most likely get this issue.

I will keep you posted if I hear anything.

"PStemper" wrote:


Brett,

Have you resolved this issue? I ask because we are seeing the EXACT
same thing, with one diffference: Sometimes an outgoing meeting
request
to the same people it failed with before, now works. In other words,
it
doesn't ALWAYS happen to the same outside people.

I get the same "Unable to open message for delivery", and when I
search
the outgoing queue directory for the message, the message isn't
there
(hence the error), even the the queue in System Manager says it is
there.

Paul Stemper
Magenic


--
PStemper



--
PStemper

Paul - Feel free to contact me offline at

info at lhseattle dot com

Brett

"PStemper" wrote:


Thanks for the update!

I am seeing the exact same thing (most requests to microsoft.com fail,
and it is sporadic.)

I am working with an MS tech to try to determine the cause and the fix.
I will let you know what I find.

Thanks again!

Paul

LH - Brett;7699567 Wrote:
No resolution yet.

We are finding the same thing you are. Which is that not all requests
get
held up. We have also found that the problem seels pretty random. The
only
thing we have narrowed down thus is that if you send a meeting to
someone at
Microsoft.com or w-link.com you will most likely get this issue.

I will keep you posted if I hear anything.

"PStemper" wrote:


Brett,

Have you resolved this issue? I ask because we are seeing the EXACT
same thing, with one diffference: Sometimes an outgoing meeting
request
to the same people it failed with before, now works. In other words,
it
doesn't ALWAYS happen to the same outside people.

I get the same "Unable to open message for delivery", and when I
search
the outgoing queue directory for the message, the message isn't
there
(hence the error), even the the queue in System Manager says it is
there.

Paul Stemper
Magenic


--
PStemper



--
PStemper

Was a solution ever found? I'm having the exact same issue.

Thanks.
- dave

Solutions are found all the time, BUT the question for you to answer is,
what was the problem? You didn't identify it! Sort of like walking up to
a stranger and saying "Will this road lead to my destination?"

Dave wrote:

Was a solution ever found? I'm having the exact same issue.

Thanks.
- dave