Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

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

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

View products that this article applies to.

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)

↑ Back to the top

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

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.

↑ Back to the top

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.

↑ Back to the top

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

↑ Back to the top

Keywords: KB838221, kbbug, kbfix, kbqfe, kbbiztalk2004sp1fix, kbhotfixserver, kbbiztalk2004-2006swept

↑ Back to the top

Article Info
Article ID : 838221
Revision : 4
Created on : 8/17/2006
Published on : 8/17/2006
Exists online : False
Views : 410