BizTalk Server 2004 Solution Center

Download details - BizTalk Server 2004

• FIX: The HTTP adapter fails when you try to send large messages in BizTalk Server 2004
  Fixes a bug that causes the HTTP adapter to fail to send messages larger than 48 KB if there is a proxy.
• FIX: A BizTalk Server project may stop responding when you add schemas and the schemas are opened in Visual Studio .NET
  Fixes a resource usage problem that occurs when you add a large schema in BizTalk Server 2004. The schema is automatically opened in Visual Studio .NET and this may cause BizTalk Server to stop responding for a while.
• FIX: The xsl:for-each statement is put at the parent field of the child field of the destination schema in BizTalk Server 2004
  Provides a hotfix that permits you to set where you want the xsl:for-each statement.
• FIX: The BizTalk Server EDI Adapter only supports a limited set of document types in BizTalk Server 2004
  Fixes the BizTalk Server EDI Adapter so that it can work with any EDI document types.
• FIX: "A service or property can only be accessed on the current service" error message when one orchestration references another orchestration in the same project in BizTalk Server 2004
  Provides a hotfix to correct the expression error "A service or property can only be accessed on the current service."
• FIX: Some nodes are not expandable in Tracking Profile Editor in BizTalk Server 2004
  Fixes a problem in the BizTalk Server 2004 Tracking Profile Editor where with certain node types are not expandable. Provides a hotfix to resolve the problem.
• FIX: A BizTalk 2004 project may stop responding when you add a schema or pipeline to the project and then you open the project
  Describes a problem that occurs when you open a new BizTalk project after you try to add a new schema or a new pipeline to the project. The project may seem to stop responding.
• BUG: BizTalk Server 2004 Health and Activity Tracking shows a completed business process as incomplete
  Fixes a Health and Activity Tracking (HAT) problem where HAT does not reflect the completed status of a business process.
• FIX: Changes in an EDI schema in BizTalk Server do not take effect
  Fixes a problem in BizTalk Server 2004 where any change to an Electronic Data Interchange (EDI) schema does not take effect.
• FIX: Many Csc.exe processes may be running on a computer that is running BizTalk Server 2004
  Fixes a problem that occurs if an orchestration calls a Web Service Method that uses the SoapRpcMethod attribute. A hotfix is available to resolve this problem.
• FIX: The scoping parameter of the Cumulative Sum functoid does not generate the results that you expect in BizTalk Server 2004
  Describes that the Cumulative Sum functoid returns incorrect results no matter what minimum or maximum occurrence value you configure for a document node. A hotfix is available to resolve this problem.
• FIX: The BPEL Import Wizard quits unexpectedly at the last step in BizTalk Server 2004
  Fixes a problem in the BPEL Import Wizard that causes it to quit unexpectedly when it reaches the last step.
• FIX: You cannot access the headers and the body of an HTTP failure response in a SOAPException exception
  Describes a problem that occurs when you catch a System.Web.Services.Protocols.SOAPException exception and you cannot see the headers or the body in the HTTP failure response. Includes a hotfix that you can use to resolve the problem.
• FIX: BizTalk Server 2004 rejects BTF receipts in Coordinated Universal Time (Greenwich Mean Time) + X time zones
  Fixes a problem where BizTalk Server 2004 cannot accept BizTalk Framework (BTF) receipts that BizTalk Server 2004 generates itself in Coordinated Universal Time (Greenwich Mean Time) + X time zones.
• FIX: You cannot use content-based routing with a solicit-response port in BizTalk Server
  Fixes a problem where BizTalk Server rejects the response when you use content-based routing with a solicit-response port.
• "Specified cast is not valid" error message when you deploy an Orchestration that was created in BizTalk Server 2004
  Explains why this error occurs and provides links to many language versions of the rollup packages that you can install to fix this problem.
• BizTalk Server may fail persisting state to the database and may end the orchestration instance
  Fixes a problem where BizTalk Server throws a PersistenceException exception when it tries to persist the state of an orchestration instance to the database.
• FIX: You experience high CPU utilization and no timeout exception when using a timed scope in orchestration
  Fixes an issue with high CPU utilization when a timed scope is not throwing the timeout exception in BizTalk Server 2004.
• BizTalk Server 2004 rejects reliable receipts from BizTalk Server 2000 and from BizTalk Server 2002
  Fixes a problem where BizTalk Server 2004 rejects old-format reliable messaging receipts from BizTalk Server 2000 and from BizTalk Server 2002.
• FIX: You experience slow performance when large maps contain many logical functoids in BizTalk Server 2004
  Fixes the problem of slow performance by adding optimizations to maps that use logical functoids.
• FIX: You experience slow performance when you use the CrossReference APIs in BizTalk Server 2004
  Fixes slow performance issue when you use CrossReference APIs by adding performance optimizations.
• FIX: The BizTalk Server 2004 HTTP Adapter does not support setting HTTP headers on response from the server
  Fixes a problem in the BizTalk Server 2004 HTTP Adapter where you cannot set HTTP headers on the response from a HTTP receive request from an Orchestration.
• You must install the SQL Server 2000 update that KB article 831950 describes to run BizTalk Server 2004
  Explains that the SQL Server 2000 update 831950 must be installed on the computer or computers where SQL Server 2000 is installed and where the BizTalk Server databases are housed.
• FIX: You receive an "unhandled exception" error message in the event log when you use the flat file parser in BizTalk Server 2004
  Fixes an unhandled exception that may occur in the flat file parser when BizTalk Server 2004 is under heavy stress.
• FIX: You cannot remove an application ID after you create it by using a database functoid in BizTalk Server 2004
  This hotfix adds a new functoid that allows for deletion of an ID that was created with the CrossReferencing APIs.