C
charftong
I just started seeing this issue come up and I am not sure what is
causing it, but it has been happening more and more frequently with
different users around the company.
Currently we have a purchase order request(custom form item) that is
published to our global form library that creates an item in a public
folder. Certain users are unable to get their item into the public
folder upon submission when in Cached Exchange Mode. The get the
following error:
"Your message did not reach some or all of the intended recipients.
Subject: PO Request 6103065
Sent: 11/28/2006 10:42 AM
The following recipient(s) could not be reached:
Company Wide Purchase Orders on 11/28/2006 10:42 AM
This message could not be sent. Try sending the message
again later, or contact your network administrator. Error is
[0x8004011b-00000000-00000000]."
They have never had this problem before until very recently. Nothing
has changed in their instance of Outlook(2003). Nothing has changed on
the custom form itself in regards to where the item is being sent.
Has anyone run into this issue before?
causing it, but it has been happening more and more frequently with
different users around the company.
Currently we have a purchase order request(custom form item) that is
published to our global form library that creates an item in a public
folder. Certain users are unable to get their item into the public
folder upon submission when in Cached Exchange Mode. The get the
following error:
"Your message did not reach some or all of the intended recipients.
Subject: PO Request 6103065
Sent: 11/28/2006 10:42 AM
The following recipient(s) could not be reached:
Company Wide Purchase Orders on 11/28/2006 10:42 AM
This message could not be sent. Try sending the message
again later, or contact your network administrator. Error is
[0x8004011b-00000000-00000000]."
They have never had this problem before until very recently. Nothing
has changed in their instance of Outlook(2003). Nothing has changed on
the custom form itself in regards to where the item is being sent.
Has anyone run into this issue before?