Home Page › Forums › BizTalk 2004 – BizTalk 2010 › The Messaging Engine encountered an error while suspending one or more messages – PRODUCTION
- This topic has 5 replies, 1 voice, and was last updated 9 years, 1 month ago by
community-content.
-
AuthorPosts
-
-
December 10, 2008 at 7:15 AM #21338
BizTalk Gurus,
I need help on fixing this problem. Here is the error I’m getting in our production server:
“The Messaging Engine encountered an error while suspending one or more messages.”
Using BizTalk Server 2006 and I have about 1000 invoices coming thru our SAP system to BizTalk Server via HTTP adapter. We are using orchestration to pickup these messages, archive the orginal message using Dynamic send port and transform the message to EDI 810 using very complicated map (in ODX itself), send the the translated XML EDI message to Covast Batcher and send it out in the morning 6:00 to the VAN.
My feeling is that this error is coming when we try to archive to a file folder on the BTS server using dynamic send port. We are using Dynamic send because we want to archive the message to a specific folder that is related the partner. So the path is being formed in the ODX. Nothing has stopped and looks like all are going out well but it is creating around 300 errors entries in the event log and we have a process in place to trigger pager from the errors in the event log.
Any help will be appreciated.
-
December 10, 2008 at 7:31 AM #21342
I’m also getting several of “The Messaging Engine encountered an error while deleting one or more messages.” errors.
-
December 10, 2008 at 9:05 AM #21347
Don’t you get some more messages in the error message? Some stacktrace perhaps ?
-
December 10, 2008 at 10:59 AM #21348
BaldurKn,
Not much available after that. All I have is “For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.”
But I did get some errors on my send port but it finally send the messages out to file folder.
There was a failure executing the send pipeline: “Microsoft.BizTalk.DefaultPipelines.XMLTransmit, Microsoft.BizTalk.DefaultPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35” Source: “XML assembler” Send Port: “EDI_Bills_810_4010_Out_1.0.0.0_EDI_Bills_810_4010_Out.ZBOBL_EDIBILLS_810_4010_OUT_Dynamic_Archive_4d2aeeb85dde6a59” URI: “file://E:\EDI\BACKUP_IDocs\EDI_Bills_810\945414530ECP_09_945414530ECP\%MessageID%.xml” Reason: This Assembler cannot retrieve a document specification using this type: “ZBOBL_EDIBILLS”.
I’m thinking this may be related to the performance of the server but I have no idea where to relate. We are using Windows Server 2003 Standard SP1 with 4 gig memory and Intel Xeon 3.2 Gig processor.
-
December 11, 2008 at 6:13 AM #21354
Humm… Are the files large ? Could it be that BizTalk is splitting up the files ?
-
December 11, 2008 at 10:42 AM #21356
Baldur,
Messages are not that big, they are about 30 KB each and we get around 1000 message at the same time from SAP. As I mentioned we are using standard edition 32 bit Windows Server 2003 so were limited to use only 4 gig RAM. We have about 7 hosts (instances) running on this server.
Another thing is, we did not get any errors yesterday night. We got the errors 3 days in a row.
-
-
-
-
-
-
AuthorPosts
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.