Select the product you need help with
FIX: Error message when you receive EDI interchanges by using the EDI receive pipeline in BizTalk Server 2009: "Fatal error encountered in EDI Disassembler, error information is GetTempFileName Failed"Article ID: 973387 - View products that this article applies to. On This PageSYMPTOMSYou use the Microsoft BizTalk 2009 EDI pipeline to receive batched EDI interchanges. In the Temp folder of the BizTalk Server service account, VST files are created. Note The Temp folder is usually located in the following path: C:\Users\<Account>\AppData\Local\Temp (For Windows Vista and Windows Server 2008) C:\Documents and Settings\<Account>\Local Settings\Temp (For Windows XP and Windows Server 2003) However, these VST files do not get deleted as expected. Therefore, the incoming EDI interchanges are suspended in queue. When this problem occurs, you find events in the Application Event log that resemble the following: Event ID: 4097 Description: Fatal error encountered in EDI Disassembler, error information is GetTempFileName Failed. Event ID: 5719 Description: There was a failure executing the receive pipeline: "Microsoft.BizTalk.Edi.DefaultPipelines.EdiReceive, Microsoft.BizTalk.Edi.EdiPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Source: "EDI disassembler" Receive Port: "<Receive Port>" URI: "<URI>" Reason: GetTempFileName Failed. Event ID: 5753
Description:
A message received by adapter "FILE" on receive location "<Receive Location>" with URI "<URI>" is suspended.
Error details: There was a failure executing the receive pipeline: "Microsoft.BizTalk.Edi.DefaultPipelines.EdiReceive, Microsoft.BizTalk.Edi.EdiPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Source: "EDI disassembler" Receive Port: "<Receive Port>" URI: "<URI>" Reason: GetTempFileName Failed.
MessageId: {<message GUID>}
InstanceID: {<instance GUID>}
Note You can restart the BizTalk host instance to remove all VST files removed from the Temp folder. However, this may cause data loss VST file duplication issues if the BizTalk host instances are restarted frequently. CAUSEThis problem occurs because of an error in the EDI components of BizTalk Server 2009.
RESOLUTIONCumulative updated informationFor BizTalk Server 2009, the hotfix that resolves this issue is included in Cumulative Update 1 for BizTalk Server 2009. For more information about how to obtain the cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base: 2429050
(http://support.microsoft.com/kb/2429050/
)
Cumulative update package 1 for BizTalk Server 2009 For BizTalk Server 2009 Hotfix informationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support Note The "Hotfix download available" form displays the languages for
which the hotfix is available. If you do not see your language, it is because a
hotfix is not available for that language.
(http://support.microsoft.com/contactus/?ws=support)
PrerequisitesYou must have Microsoft BizTalk Server 2009 installed to apply this hotfix.Restart requirementYou do not have to restart the computer after you apply this hotfix.Hotfix replacement informationThis hotfix does not replace a previously released hotfix.File informationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.Collapse this table
Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files. For BizTalk Server 2006 R2 SP1The hotfix that resolves this problem is included in cumulative update package 1 for BizTalk Server 2006 R2 SP1. For more information about how to obtain the cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base: 982061
(http://support.microsoft.com/kb/982061/
)
Cumulative update package 1 for BizTalk Server 2006 R2 Service Pack 1 For more information about BizTalk Server 2006 R2 SP1 hotfixes, click the following article number to view the article in the Microsoft Knowledge Base: 974563
(http://support.microsoft.com/kb/974563/
)
List of Microsoft BizTalk Server hot fixes that are included in BizTalk Server 2006 R2 Service Pack 1STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
in the "Applies to" section. MORE INFORMATIONFor a walkthrough of receiving batched EDI interchanges, visit the following Microsoft Developer Network (MSDN) Web site: http://msdn.microsoft.com/en-us/library/dd770108%28BTS.10%29.aspx
(http://msdn.microsoft.com/en-us/library/dd770108%28BTS.10%29.aspx)
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: 824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updatesPropertiesArticle ID: 973387 - Last Review: December 8, 2010 - Revision: 3.0 APPLIES TO
|
Back to the top
