One of my client report me that the EDI
batch stop to generate the EDI batch file in our BizTalk production server
today, it seems serious.
When I login to the BizTalk server, everything
looks fine, BizTalk received the LOB message, transformed it to EDI format and
send it to the EDI batch orchestration. But, the “Start”, “Override”, “Stop”
button in the batch all are disabled, I can only Refresh it.
Then I tried to restart the host instance
and the application, I thought it will be OK, but, all the button are the same--disabled.
I try to check the suspended message and
found that, there are some EDI batch messages suspended over there. The suspended
services name is :
Microsoft.BizTalk.Edi.BatchingOrchestration.BatchingService,
Microsoft.BizTalk.Edi.BatchingOrchestration, Version=3.0.1.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35
Then I terminated all these type of service
and all of the button enabled again after restart the host instance. I can
Start, Override, Stop the instance now.
I don’t know why Microsoft design the Edi Batch
at this way----one EDI message failed, then all of the batch failed. But I
really don’t like it, it make me have to check the EDI status always, maybe I
have to develop a tool to monitor it.
没有评论:
发表评论