none
Outbound 997 is created in outbox but not copied to destination folder RRS feed

  • Question

  • BizTalk 2006 with base EDI subsystem.

    I have outbound 997 using a local folder as target. It worked fine for several weeks. Last week the server ran out of disk space, which was quickly fixed (It is a VM) . Since then the ACK files were not sent out to the target folder. I can see that ACK files were created in the EDI System\External\Outbox folder. But that's it. The files are not send to the configured folder.

    I am not sure the 997 issue related to the disk issue or not.

    I checked the ACK configuration, no changes; Checked security, no changes (the EDI subsystem/BizTalk service account is a member of local admin group)

    Any one experieced this before? What else (configurations, logs, traces) should I check?

    Thanks

     

     

    Wednesday, October 20, 2010 1:14 PM

Answers

  • The issue was resolved.

    Before the ACK issue, we had an incident that the disk for the BizTalk was full and was resolved quickly.  During the disk full period, an empty ACK file was written to disk. In the audout  table in EDI database, the log entry had the right length for the ACK file and it didnot match the file on the disk.

    The EDI subsystem could not send the empty file from the outgoing box, it could neither update the log entry status. The EDI subsystem stuck there even we restart the service/reboot the machine.

    After we deleted the empty file from the outgoing box and removed the log entry in audout table, everything went back to normal. All pending ACK files were sent out immediately.

     

     

    • Marked as answer by phe Monday, October 25, 2010 7:49 PM
    Monday, October 25, 2010 7:49 PM

All replies

  • Hi,

    Looks like the permission issue. Could you please verify that BizTalk Host Account which is hosting the send port must have the access to the configured folder. You can also verify the Event Log for any error logs. Also try restarting the host instances. You can also try deleting the folder and recreating it all over again afte taking the back up.


    Best Regards, Vishnu
    Wednesday, October 20, 2010 1:32 PM
  • Permission is not an issue. The account is a member of administrator, and I used the same account log in to the server and access the files in edi doc home and could copy files from there to the folder.

    I found the following error in application log:

     

    Event Type:   Error

    Event Source: Application Error

    Event Category:      (100)

    Event ID:     1000

    Date:         10/18/2010

    Time:         9:12:06 PM

    User:         N/A

    Computer:     xxxxx

    Description:

    Faulting application esp_srv.exe, version 4.1.167.29, faulting module esp_gen.dll, version 4.1.167.79, fault address 0x00012e23.

     

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    Data:

    0000: 41 70 70 6c 69 63 61 74   Applicat

    0008: 69 6f 6e 20 46 61 69 6c   ion Fail

    0010: 75 72 65 20 20 65 73 70   ure  esp

    0018: 5f 73 72 76 2e 65 78 65   _srv.exe

    0020: 20 34 2e 31 2e 31 36 37    4.1.167

    0028: 2e 32 39 20 69 6e 20 65   .29 in e

    0030: 73 70 5f 67 65 6e 2e 64   sp_gen.d

    0038: 6c 6c 20 34 2e 31 2e 31   ll 4.1.1

    0040: 36 37 2e 37 39 20 61 74   67.79 at

    0048: 20 6f 66 66 73 65 74 20    offset

    0050: 30 30 30 31 32 65 32 33   00012e23

     

    Wednesday, October 20, 2010 2:19 PM
  • Hi,

    I am not sure whether you have looked at below KB article or not. Are you dealing with the Large EDI messages ??

    http://support.microsoft.com/kb/924666

     


    Best Regards, Vishnu
    Wednesday, October 20, 2010 2:29 PM
  • Thanks.

    I checked the link but it is for 2004 and HIPPA. I don't use HIPPA.

     

    Wednesday, October 20, 2010 3:44 PM
  • From the EDI Report in HAT, I can see that for those not sent ACKs, the Network Identification became (null); for those sent successfully, the Network Identification is empty string.

     

    Wednesday, October 20, 2010 7:09 PM
  • Some entries in EDI Adaptor trace log:

    You can see the file connector was triggered successfully. The problem is Audit record has no INSERT or UPDATE status: no output files...

    T  1: Thu Oct 21 11:12:11.775 DBIO::[INSERT INTO audout (msgout,icout,dtbdd,tmbdd,dubdd,dtte,tmte,dute,dtcs,tmcs,ducs,pdtcs,ptmcs,bytcnt,mstscd,pc,dc,msrvcd,sid,rid,refpas,ti,mcvr,ref,uname,prog,del_not,ownpc,owndc,icin,msgin,sidcdq,ridcdq,fcvr,msgttk,routad,clientid,resetyn,resetdate,resettime,resetby,hashtot,dttpli,tmtpli,dtfpli,tmfpli,prio,dubddms,dutems,ducsms,seqno,msrvcdout,icr,mrn,grpout,gcr,grpin,sroutad,servername,messagedigest,setname) VALUES (19341,19341,convert(datetime,'2010-10-21 00:00:00',120),CONVERT(DATETIME,'2010-10-21 11:12:11',120),CONVERT(DATETIME,'2010-10-21 00:00:00',120),convert(datetime,'2010-10-21 00:00:00',120),CONVERT(DATETIME,'2010-10-21 11:12:11',120),CONVERT(DATETIME,'2010-10-21 00:00:00',120),NULL,NULL,NULL,NULL,NULL,1121,3,'29','DEFAULT',0,'7043297824','MLFDE','',0,'997   004010DEFAULT          X','','','',2,'3','DEFAULT',0,0,'12','ZZ','5 00401 ','','4166222040','',0,NULL,NULL,'','17/FVEem16yc6awRAIdhRBA==',NULL,NULL,NULL,NULL,2,0,0,0,0,1,'19341','19341',28682,'28682',0,'7043297824','','','ASCII')]
    T  1: Thu Oct 21 11:12:11.775 MEM_ALLOC +412 (id=37403) (#=101*4) tot 1203355 (Realloc DBCommandlist) (mem=03588498)
    T  1: Thu Oct 21 11:12:11.775 MEM_ALLOC +1017 (id=37404) (#=1*1009) tot 1204372 (DBCommand) (mem=0356E878)
    T  1: Thu Oct 21 11:12:11.775 db_Insert() ret=0
    T  1: Thu Oct 21 11:12:11.775 db_CommitTransaction(dbtype=9, dbcon=6, stmt=20871764)
    T  1: Thu Oct 21 11:12:11.838 MEM_FREE -1017 (id=37404) tot 1203355 (EDBC - _ClearCursor - cmd[li]) (mem=0356E878)
    T  1: Thu Oct 21 11:12:11.838 MEM_FREE -412 (id=37403) tot 1202943 (EDBC - _ClearCursor - cmd) (mem=03588498)
    T  1: Thu Oct 21 11:12:11.838 db_CommitTransaction() ret=0
    T  1: Thu Oct 21 11:12:11.838 engine_TriggerConnector(msrvcd=1, direction=1)
    T  1: Thu Oct 21 11:12:11.838 trigger connector (submit) X5 (File system)
    T  1: Thu Oct 21 11:12:11.853 Connector triggered succesfully
    T  1: Thu Oct 21 11:12:11.853 engine_TriggerConnector() ret=0
    T  1: Thu Oct 21 11:12:11.853 au_UpdateMonitorInfo(Direction=[OUTGOING], Action=[INSERT], Status=[], Previous=[-], Number=[1]
    T  1: Thu Oct 21 11:12:11.853 au_UpdateAllMonitorInfo([0][0][0][0][0][0][0][0]  [0][1][0][0][1][1][0][0][0][0]
    T  1: Thu Oct 21 11:12:11.853 MEM_FREE -1130 (id=37394) tot 1201813 (ESP_GEN - buf_Free - p_buf->data) (mem=0202A268)
    T  1: Thu Oct 21 11:12:11.853 MEM_FREE -3132 (id=37391) tot 1198681 (FreeFA - release hardcoded FAs) (mem=0355C010)
    T  1: Thu Oct 21 11:12:11.853    AuditRecord #1: DBAction=[DELETE], Status=[3,], Intnr=[26415], Docnr=[0], next=[034D9B40]
    T  1: Thu Oct 21 11:12:11.853 Start writing output files for current audit record
    T  1: Thu Oct 21 11:12:11.853 Audit record has no INSERT or UPDATE status: no output files...
    T  1: Thu Oct 21 11:12:11.853 Finished writing output files

    Thursday, October 21, 2010 3:32 PM
  • The issue was resolved.

    Before the ACK issue, we had an incident that the disk for the BizTalk was full and was resolved quickly.  During the disk full period, an empty ACK file was written to disk. In the audout  table in EDI database, the log entry had the right length for the ACK file and it didnot match the file on the disk.

    The EDI subsystem could not send the empty file from the outgoing box, it could neither update the log entry status. The EDI subsystem stuck there even we restart the service/reboot the machine.

    After we deleted the empty file from the outgoing box and removed the log entry in audout table, everything went back to normal. All pending ACK files were sent out immediately.

     

     

    • Marked as answer by phe Monday, October 25, 2010 7:49 PM
    Monday, October 25, 2010 7:49 PM