FIX: You receive an "unhandled exception" error message in the event log when you use the flat file parser in BizTalk Server 2004

This article has been archived. It is offered "as is" and will no longer be updated.
Symptoms
If you use the flat file parser that is included with Microsoft BizTalk Server 2004 while your system is running under high stress conditions, one of the following error messages may be logged in the event log:

Message 1

Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.BizTalk.ParsingEngine.LLState.ComputeClosure(ConstLLStateItemSet kernel, LLStateMapper mapper, Grammar grammar, Int32 depth, Int32 maxDepth)
at Microsoft.BizTalk.ParsingEngine.LLState.Construct(ConstLLStateItemSet kernel, LLStateMapper mapper, Grammar grammar, Int32 depth, Int32 maxDepth)
at Microsoft.BizTalk.ParsingEngine.LLStateMapper.GetState(ConstLLStateItemSet kernel, Grammar grammar, Int32 depth, Int32 maxDepth)
at Microsoft.BizTalk.ParsingEngine.LLState.ComputeClosure(ConstLLStateItemSet kernel, LLStateMapper mapper, Grammar grammar, Int32 depth, Int32 maxDepth)
at Microsoft.BizTalk.ParsingEngine.LLState.Construct(ConstLLStateItemSet kernel, LLStateMapper mapper, Grammar grammar, Int32 depth, Int32 maxDepth)
at Microsoft.BizTalk.ParsingEngine.LLStateMapper.GetState(ConstLLStateItemSet kernel, Grammar grammar, Int32 depth, Int32 maxDepth)
at Microsoft.BizTalk.ParsingEngine.Grammar.FactorStatesList(ConstProductionVector productions, NonTerminalSymbol follow, Int32 depth)
at Microsoft.BizTalk.ParsingEngine.Grammar.Factor(Int32 depth, ErrorCollection errors)
at Microsoft.BizTalk.ParsingEngine.LLParseInfo..ctor(Grammar grammar, Int32 lookAheadDepth, ErrorCollection errors)
at Microsoft.BizTalk.ParsingEngine.DocumentSchema.get_ParseInfo()
at Microsoft.BizTalk.ParsingEngine.FFParser..ctor(DocumentSchema schema, IDataReader dataReader)
at Microsoft.BizTalk.ParsingEngine.FFReader..ctor(DocumentSchema schema, IDataReader dataReader)

Message 2

Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object. at System.Collections.Hashtable.get_Item(Object key)
at Microsoft.BizTalk.ParsingEngine.Grammar.ComputeTransitiveClosure(Hashtable channels, Hashtable sets)
at Microsoft.BizTalk.ParsingEngine.Grammar.ComputeFollowSets(Boolean incremental)
at Microsoft.BizTalk.ParsingEngine.Grammar..ctor(ConstProductionVector productions, NonTerminalSymbol start, ErrorCollection errors, Boolean forSpeed)
at Microsoft.BizTalk.ParsingEngine.SchemaTranslator.Translate(DocumentSchema schema, ErrorCollection errors)
at Microsoft.BizTalk.ParsingEngine.DocumentSchema.get_ParseInfo()
at Microsoft.BizTalk.ParsingEngine.FFParser..ctor(DocumentSchema schema, IDataReader dataReader)
at Microsoft.BizTalk.ParsingEngine.FFReader..ctor(DocumentSchema schema, IDataReader dataReader)
at GrammarBuilderStress.GrammarBuilderStress.ThreadProc() in c:\sd\myprojects\grammarbuilderstress\grammarbuilderstress.cs:line 101 System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.BizTalk.ParsingEngine.LLState.ComputeClosure(ConstLLStateItemSet kernel, LLStateMapper mapper, Grammar grammar, Int32 depth, Int32 maxDepth)
at Microsoft.BizTalk.ParsingEngine.LLState.Construct(ConstLLStateItemSet kernel, LLStateMapper mapper, Grammar grammar, Int32 depth, Int32 maxDepth)
at Microsoft.BizTalk.ParsingEngine.LLStateMapper.GetState(ConstLLStateItemSet kernel, Grammar grammar, Int32 depth, Int32 maxDepth)
at Microsoft.BizTalk.ParsingEngine.LLState.ComputeClosure(ConstLLStateItemSet kernel, LLStateMapper mapper, Grammar grammar, Int32 depth, Int32 maxDepth)
at Microsoft.BizTalk.ParsingEngine.LLState.Construct(ConstLLStateItemSet kernel, LLStateMapper mapper, Grammar grammar, Int32 depth, Int32 maxDepth)
at Microsoft.BizTalk.ParsingEngine.LLStateMapper.GetState(ConstLLStateItemSet kernel, Grammar grammar, Int32 depth, Int32 maxDepth)
at Microsoft.BizTalk.ParsingEngine.Grammar.FactorStatesList(ConstProductionVector productions, NonTerminalSymbol follow, Int32 depth)
at Microsoft.BizTalk.ParsingEngine.Grammar.Factor(Int32 depth, ErrorCollection errors)
at Microsoft.BizTalk.ParsingEngine.LLParseInfo..ctor(Grammar grammar, Int32 lookAheadDepth, ErrorCollection errors)
at Microsoft.BizTalk.ParsingEngine.DocumentSchema.get_ParseInfo()
at Microsoft.BizTalk.ParsingEngine.FFParser..ctor(DocumentSchema schema, IDataReader dataReader)
at Microsoft.BizTalk.ParsingEngine.FFReader..ctor(DocumentSchema schema, IDataReader dataReader)

Resolution

Service pack information

To resolve this problem, obtain the latest service pack for Microsoft BizTalk Server 2004. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
888751 How to obtain the latest BizTalk Server 2004 service pack

Hotfix information

A 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. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

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, contact 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: 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.

File information

The English version of this hotfix has the file attributes (or later) 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 tool in Control Panel.
   Date         Time   Version     Size    File name   --------------------------------------------------------------------------------   08-Mar-2004  18:06  3.0.5252.0   11,776  Dsdump.exe   08-Mar-2004  18:06  3.0.5252.0  221,184  Microsoft.biztalk.flatfileextension.dll   08-Mar-2004  18:06  3.0.5252.0  212,992  Microsoft.biztalk.pipeline.dll
Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.This problem was corrected in BizTalk Server 2004 Service Pack 1.
More information
For additional information about the terminology that is used to describe Microsoft product updates, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Properties

Article ID: 838221 - Last Review: 01/17/2015 07:23:30 - Revision: 3.0

  • Microsoft BizTalk Server 2004 Enterprise Edition
  • Microsoft BizTalk Server 2004 Developer Edition
  • Microsoft BizTalk Server 2004 Partner Edition
  • Microsoft BizTalk Server 2004 Standard Edition
  • kbnosurvey kbarchive kbautohotfix kbbiztalk2004-2006swept kbhotfixserver kbbiztalk2004sp1fix kbqfe kbfix kbbug KB838221
Feedback