| 27909 | MS07-028: Vulnerability in CAPICOM could allow remote code execution |
| 27910 | The FTP adapter may stop processing messages if the FTP adapter cannot communicate with the FTP server during the initial handshake in BizTalk Server 2004 |
| 27911 | Error message when you try to compile a project in BizTalk Server 2004: The current .NET type name of this root node is a duplicate |
| 27912 | You can cluster a BizTalk Server 2006 Host and the Enterprise Single Sign-On (SSO) service only by using Microsoft Windows Clustering |
| 27913 | How to provide high availability for the MQSAgent COM+ application or for the MQSAgent2 COM+ application in a clustered environment |
| 27914 | An orchestration has a status of Suspended (not resumable) while the send port has a status of Suspended (resumable) in BizTalk Server 2004 |
| 27915 | Event ID: 4099 is logged when a message that is not valid is submitted in a solution that you develop by using BizTalk Server 2004 and BizTalk Accelerator for SWIFT 2.1 |
| 27916 | In BizTalk Server 2004, some elements may not appear as expected when you open a schema in the BizTalk Mapper |
| 27917 | The BizTalk Adapter for MQSeries 2.0 may not send active messages to an MQSeries queue that is on an MQSeries cluster when the active cluster node fails over to passive mode in BizTalk Server 2004 |
| 27918 | A valid message may be incorrectly suspended in BizTalk Server 2004 Service Pack 2 |
| 27919 | How to use the Enterprise Single Sign-On Trace utility for Host Integration Server systems and for BizTalk Server systems |
| 27920 | Side-by-side deployment does not work as expected when convoys are used in orchestrations in BizTalk Server 2004 |
| 27921 | Changes to daylight saving time in 2007 for BizTalk Server 2004 |
| 27922 | Error message in BizTalk Server 2004: The message was not found in the Message Box or the Tracking databases |
| 27923 | Event ID 10034 when an orchestration terminates unexpectedly in BizTalk Server 2004 |
| 27924 | Error message when the BizTalk Server Accelerator for HIPAA 3.0 receives or sends a 997 functional acknowledgement receipt: The schema cannot be found in the HIPAA EDI repository |
| 27925 | Error message when you use the ISSOTicket.IssueTicket method in BizTalk Server 2004: 80070057: Invalid parameter |
| 27926 | The MessageID property in the Health and Activity Tracking (HAT) tool does not match the MessageID property of the corresponding output file when you enable the Message Body Tracking feature in BizTalk Server 2004 |
| 27927 | Summary of operating systems and SQL Server versions supported by different versions of BizTalk Server |
| 27928 | BizTalk Server 2004 documentation that describes persistence and system shutdown information contains some inconsistences |
| 27929 | List of bugs that are fixed in BizTalk Server 2004 Service Pack 2 |
| 27930 | Error message when you test a map in BizTalk Server 2004: XSL transform error |
| 27931 | In BizTalk Server 2004, incoming messages and response messages may be suspended, and you may receive an error message that resembles the following: Activation message was suspended |
| 27932 | Error message when you try to change the ADO.NET connection string of an SQL send port on a server that is running BizTalk Server 2004: HRESULT: 0x80131500 |
| 27933 | Error message when the MessageBox_Message_ManageRefCountLog_BizTalkMsgBoxDb SQL Server job fails in BizTalk Server 2004: Arithmetic overflow error |
| 27934 | In BizTalk Server 2004, a signed MIME message may be marked as falsified when the message is received by an SMTP client |
| 27935 | The receive locations do not accept the newly submitted documents when you deploy a new version of a pipeline assembly in BizTalk Server 2004 |
| 27936 | A SQL Server transaction log may unexpectedly grow very large after you install BizTalk Server 2004 Service Pack 1 |
| 27937 | You cannot configure the BizTalk host instance to use a Windows group name that exceeds 63 characters in BizTalk Server 2006 and in BizTalk Server 2004 |
| 27938 | You may receive an out-of-memory error message when you use the BizTalk Accelerator for HIPAA 3.0 to process large EDI documents |
| 27939 | Error message when a flat file parser parses a message that contains blank spaces in BizTalk Server 2004 Service Pack 1: The element 'MessageUserReference_108' has incomplete content |
| 27940 | Error message when you call a .NET assembly from BizTalk Server 2004 in the .NET Framework 1.1 SP1: Unable to create the transform |
| 27941 | You see event ID 10034 in the Application log when you start an orchestration that uses the Business Rules Engine in BizTalk Server 2006 or BizTalk Server 2004 |
| 27942 | You experience inconsistent behavior when you submit a zero byte file to an FTP send adapter in BizTalk Server 2004 |
| 27943 | The MSMQT adapter may unexpectedly stop processing messages if you experience database failure or intermittent connectivity issues in BizTalk Server 2004 |
| 27944 | Event ID: 5754 when you use the SOAP adapter or the HTTP adapter together with a client certificate in BizTalk Server 2004 |
| 27945 | How to recover a single-node BizTalk Server 2004 configuration after the Configframework.exe /u command is run accidentally |
| 27946 | Event ID: 27 may be logged when you try to validate an EDI document or when you try to send an EDI document in BizTalk Server 2004: Index was outside the bounds of the array |
| 27947 | Error message when you try to build a project in BizTalk Server 2006 or BizTalk Server 2004: Use of Unconstructed Message |
| 27948 | BizTalk Server monitoring does not work as expected after you import the BizTalk Server 2004 Management Pack for MOM and the BizTalk Server 2006 Management Pack for MOM 2005 into the same MOM management group |
| 27949 | Some Business Rule Engine values in the Windows registry are reset to the default values in BizTalk Server 2004 |
| 27950 | How to delete a byte order mark from an outgoing message in BizTalk Server 2006 and in BizTalk Server 2004 |
| 27951 | Availability of the Microsoft BizTalk Server Adapter for MQSeries 2.0 hotfix rollup package |
| 27952 | Description of the SQL Server Agent jobs in BizTalk Server 2004 |
| 27953 | Error message in Visual Studio when you try to generate an instance of a schema in a BizTalk Server 2004 SP1 project: Failed to create instance for schema |
| 27954 | White spaces are removed from promoted fields after map execution in an orchestration after you install BizTalk Server 2004 SP1 |
| 27955 | Error message when you compile a BizTalk Server 2004 solution: Object reference not set to an instance of an object |
| 27956 | Messages that generate a BAD_DST_Q_NACK acknowledgement are not moved to a dead-letter queue in BizTalk Server |
| 27957 | You experience delays in message processing when BizTalk Server 2004 is processing a large flat file message |
| 27958 | You may receive an out-of-memory error message, Event ID 7031 or Event ID 5410 messages, or Event ID 4786 error messages, or you may experience similar symptoms in BizTalk Server |
| 27959 | How to reconfigure the BAM databases in BizTalk Server 2004 |
| 27961 | The flat file output may not contain the flat file delimiters as expected in BizTalk Server 2006 and in BizTalk Server 2004 |
| 27962 | You experience blocking, deadlock conditions, or other SQL Server issues when you try to connect to the BizTalkMsgBoxDb database in BizTalk Server 2006 or in BizTalk Server 2004 |
| 27963 | Changes to tracking options for an orchestration may be lost when you change the sort order for the orchestrations in BizTalk Server 2004 |
| 27964 | Error message when you try to change the Authentication trusted setting in BizTalk Server 2006 and in BizTalk Server 2004: This service account logon is already used by another BizTalk Host instance |
| 27965 | The SMTP adapter does not try to resend a BizTalk Framework document in BizTalk Server 2004 |
| 27966 | The Base EDI adapter reads only the first AK2 segment in the 997 functional acknowledgement in BizTalk Server 2004 |
| 27967 | The policy file may be ignored when you use the BizTalk Adapter for Web Services Enhancements 2.0 in BizTalk Server 2004 |
| 27968 | A runtime error may occur when you receive a message if the target namespace names or root names are not unique in BizTalk Server 2006 or in BizTalk Server 2004 |
| 27969 | You receive an error message when you try to consume a Web service in BizTalk Server 2004 |
| 27970 | You may experience slow performance when you configure the HAT tool to save all tracked messages for an orchestration in BizTalk Server 2004 |
| 27971 | A memory leak may occur in the BizTalk service when a receive location uses the MSMQT adapter in BizTalk Server 2004 |
| 27972 | The memory may not be released as expected when you compile a BizTalk Server 2004 project |
| 27973 | Event ID: 5724 or Event ID: 5719 occurs when you use the Base EDI Adapter in BizTalk Server 2004 |
| 27974 | You receive a Completed with discarded message message in the HAT tool when you use a sequential convoy in BizTalk Server 2004 |
| 27975 | Running the Base EDI Adapter on multiple BizTalk Server 2004 servers in a BizTalk Server 2004 group at the same time is not supported |
| 27976 | Microsoft SQL Server 2005 is not currently supported for Microsoft BizTalk Server 2004 databases |
| 27977 | After a failover of the SQL Server cluster resource, response messages are suspended in BizTalk Server 2004 |
| 27978 | Error message when you run the sp_GetRemoteServerName stored procedure in BizTalk Server 2004 Service Pack 1: Msg 7403, Level 16, State 1 |
| 27979 | Performance may decrease over time when you use a long-running orchestration in BizTalk Server 2004 |
| 27980 | You may experience intermittent lock conditions when you have multiple BizTalkMsgBoxDb databases configured in BizTalk Server 2004 |
| 27981 | The BizTalk service restarts unexpectedly when you map large messages in BizTalk Server 2004 |
| 27982 | Error message when you use the BizTalk Adapter 2.0 for mySAP Business Suite to manage a connection to an SAP system: The adapter failed to transmit message going to send port 'sap://ipaddress' |
| 27983 | You cannot enlist a dynamic send port in BizTalk Server 2004 |
| 27984 | The BizTalk Adapter for WSE Schema Generation Wizard may not generate a schema or an orchestration as expected in a BizTalk Server 2004 project |
| 27985 | A newer version of an assembly may unexpectedly stop working when you undeploy an older version of the assembly in BizTalk Server 2004 |
| 27986 | Event ID 4101, event ID 5720, and event ID 5680 may be logged when you use BizTalk Accelerator for HIPAA 3.0 in a BizTalk Server 2004 configuration |
| 27987 | An HWS task may be reassigned to two distinct TaskID identifiers at the same time in BizTalk Server 2004 |
| 27988 | Error message when you run the Configuration Wizard in BizTalk Server 2004: Failed to enable the Single Sign-On (SSO) service |
| 27989 | An HTTP success code is returned when an incoming HTTP message is suspended, and an HTTP 500 error code is returned when an incoming HTTP message is not suspended in BizTalk Server 2004 |
| 27990 | The bts_fnFindConvoySet function in BizTalk Server 2004 uses lots of SQL Server CPU resources |
| 27991 | Error message when you try to save message bodies that are tracked by a PassThrough pipeline in BizTalk Server 2004: Internal failure |
| 27992 | The generated file contains two message body parts when you create a custom pipeline that contains only a MIME Decoder in BizTalk Server 2004 |
| 27993 | You cannot deploy a BizTalk assembly, and you may receive an error message in BizTalk Server 2004 |
| 27994 | The Add Generated Items Wizard may not generate an XSD schema and you may receive an error message when you try to convert a DTD schema or an XDR schema to an XSD schema in a BizTalk Server 2004 project |
| 27995 | Only use the Microsoft.BizTalk.Bam.EventObservation.dll file to query server-side BAM-related events on a computer that is running BizTalk Server 2004 |
| 27996 | Assemblies may be removed from the global assembly cache when you deploy BizTalk Server assemblies by using Application Center 2000 on a server that is not running BizTalk Server 2004 |
| 27997 | You cannot call an orchestration that is exposed as a Web service on a server that is running BizTalk Server 2004 |
| 27998 | How to implement a receipt URL for reliable messaging that requires a user name and a password in BizTalk Server 2004 |
| 27999 | Message assignments that have inconsistent values in BizTalk Server 2004 |
| 28000 | The auto update statistics option, the auto create statistics option, and the Parallelism setting are turned off in the SQL Server 2000 instance that hosts the BizTalk Server 2004 BizTalkMsgBoxDB database or the BizTalk Server 2006 BizTalkMsgBoxDB databas |
| 28001 | The BizTalk Service may appear to stop responding and you may receive out-of-memory error messages in BizTalk Server 2004 |
| 28002 | The Business Rule Engine may not process rules that have different priorities when a server is under a heavy load in BizTalk Server 2004 |
| 28003 | Per-instance pipeline configuration does not work as expected in BizTalk Server 2004 |
| 28004 | Fixes a problem that occurs if you submit an EDI document that has more than 999,999 segments to the Base EDI Adapter in BizTalk Server 2004. A hotfix is available to resolve this problem. |
| 28005 | Fixes a problem that occurs when you call the GetCommonValue against an empty element from a Scripting functoid or from the Get Common Value functoid in BizTalk Server 2004. To resolve this problem, you must install a hotfix. |
| 28006 | Describes a problem where an orchestration is suspended and is marked not resumable when the SQL Server-based cluster fails over. A hotfix is provided. |
| 28007 | Explains that using NAT together with Message Queue Server 1.0, Message Queuing 2.0, Message Queuing 3.0, and BizTalk Message Queuing (MSMQT) is not supported. |
| 28008 | Fixes a problem that occurs in a serial convoy orchestration in BizTalk Server 2004 when the orchestration is enlisted and then stopped. When the orchestration is started, it finishes with discarded messages. |
| 28009 | You may receive a The operation completed successfully message before the configuration process has completed when you run the Configuration Wizard in BizTalk Server 2004 |
| 28010 | You notice many dehydrated service instances when you run a query in BizTalk Server 2004 Health and Activity Tracking |
| 28011 | You receive out-of-memory exception error messages when an orchestration contains Delay shapes in BizTalk Server 2004 |
| 28012 | You may receive a Failed to create project error message when you try to publish an orchestration as a Web service in BizTalk Server 2004 |
| 28013 | Information about handling incoming data streams in pipeline components in BizTalk Server 2004 |
| 28014 | You must run the Configuration Wizard when you move an installation of BizTalk Server 2004 from one domain to another domain |
| 28015 | Event ID 5719 may occur when you use a custom receive pipeline to validate a document structure in BizTalk Server 2004 |
| 28016 | An Enterprise Single Sign-On is offline error message may be logged in the Configuration log when you try to use the Configframework /s command to silently reconfigure BizTalk Server 2004 |
| 28017 | The Tracking_Spool1 or Tracking_Spool2 tables in the BiztalkMsgBoxDb database become very large in BizTalk Server 2004 |
| 28018 | You may receive a The following platform components failed to install and will need to be manually installed before setup can proceed Enterprise Single Sign-On Server error message when you try to install BizTalk Server 2004 |
| 28019 | The Business Activity Services Messaging Adapter does not work as expected in BizTalk Server 2004 after you install Windows SharePoint Services Service Pack 2 |
| 28020 | The rule engine may return incorrect values in BizTalk Server 2004 |
| 28021 | You may receive a Repository was locked on host error message when you try to validate an EDI schema in BizTalk Server 2004 |
| 28022 | The XLANG engine may not report a failed DTC transaction and may not end the transaction in BizTalk Server 2004 |
| 28023 | Applications that use Enterprise Single Sign-On cannot log on to remote applications if the ENTSSO service cannot communicate with the SSO credential database for 5 or more minutes |
| 28024 | The performance of a singleton orchestration that contains a Call Orchestration shape may decrease over time in BizTalk Server 2004 |
| 28025 | You receive a SQL Server does not exist or access denied error message when you try to view tracked policy execution events in the Health and Activity Tracking tool |
| 28026 | You receive an error message when you try to map a document or series of documents in BizTalk Server 2004 |
| 28027 | A suspended message is sent through a destination send port even if the send port is not started in BizTalk Server 2004 |
| 28028 | An Index was outside the bounds of the array error message is logged and existing messages do not correctly correlate after you install BizTalk Server 2004 Service Pack 1 |
| 28029 | You receive an error message when you try to use the BizTalk Adapter for MSMQ version 2.0 in BizTalk Server 2004 to send an XML message to a BizTalk Server MSMQ receive function |
| 28030 | Description of a documentation error in the Restoring the BizTalk Configuration Database topic in the BizTalk Server 2004 online documentation |
| 28031 | Support for high availability in the BizTalk Adapter for MSMQ when you use Message Queuing transactional messages in BizTalk Server 2004 |
| 28032 | The exception block variable is not visible in the Call Orchestration shape or in the Start Orchestration shape in a BizTalk Server 2004 orchestration |
| 28033 | You receive a Could not connect EDI Subsystem (StartDatabase returned -2) to Database error message, and the BizTalk Base EDI service does not start in BizTalk Server 2004 |
| 28034 | The BizTalk Server 2004 FTP send adapter may send duplicate messages when you configure two FTP send ports to use the same BTS.ReceivePortName filter |
| 28035 | The tracking event stream is not exposed in BizTalk Server 2004 orchestrations |
| 28036 | Message processing may stop, you may receive an event ID error message, and the MSDTC service may stop committing transactions when you map a large document in BizTalk Server 2004 |
| 28037 | You may receive an Index was outside the bounds of the array error message when you have specified multiple schemas in the Document schemas collection of a receive pipeline in BizTalk Server 2004 |
| 28038 | Describes a problem that occurs when you compile a flat file schema that contains positional records of different lengths in BizTalk Server 2004. |
| 28039 | You may receive a btm1050: XSL transform error error message when you test a map in BizTalk Server 2004 |
| 28040 | The BizTalk service may stop responding and you may receive an Event ID 25 error message when messages are processed in BizTalk Server 2004 |
| 28041 | Fixes a problem in the BizTalk Server 2004 Orchestration Compiler where you receive build error messages because code generation is incorrect for certain orchestration configurations. |
| 28042 | Describes a problem that occurs when performance may decrease if you use the BizTalk Adapter for FTP when delivery notification is enabled. |
| 28043 | Describes a problem that occurs when you try to use the EDI Adapter to send a message in BizTalk Server 2004, the message is not sent, and you receive an error message. Includes a hotfix that you can apply to resolve the problem. |
| 28044 | You experience deadlocks on the BizTalkMsgBox database after you install BizTalk Server 2004 SP1 |
| 28045 | The Value Extractor functoid may return a value that is not correct when BizTalk Server 2004 is under a heavy load |
| 28046 | The number of running orchestrations increases and remains constant after you reach the thread pool limit, and orchestration execution time may also increase in BizTalk Server 2004 |
| 28047 | You may experience suboptimal performance when you use Value Mapping functoids in BizTalk Server 2004 |
| 28048 | Some messages that are picked up by using a File receive adapter location may be lost in BizTalk Server 2004 |
| 28049 | Message processing may slow or stop after you install BizTalk Server 2004 Service Pack 1 |
| 28050 | The BizTalk Server 2004 online documentation contains an error in the BufferedEventStream Class topic |
| 28051 | BizTalk Server 2004 incorrectly generates repeated NACK messages for a BizTalk Framework message that remains in the suspended queue |
| 28052 | You cannot use a Call Orchestration shape or a Start Orchestration shape to pass a derived type that has the base type as the parameter to a BizTalk Server 2004 orchestration |
| 28053 | You receive a Type http://www.w3.org/2001/XMLSchema:char is not declared or not a simple type error message when you try to generate a schema by using the SQL Transport Schema Generation Wizard in BizTalk Server 2004 |
| 28054 | A BizTalk Server Host instance fails and a General Network error is written to the Application log when the BizTalk Server-based server processes a high volume of documents |
| 28055 | Describes a problem in BizTalk Server 2004 where you receive an exception error message when you try to call the GetActivityFlowInfo method immediately after you add an activation block to an activity flow. |
| 28056 | A message is not suspended in the suspended queue if validation is unsuccessful when you send a message to a MSMQT receive location in BizTalk Server 2004 |
| 28057 | You may receive a System.Runtime.InteropServices.COMException exception error when you try to send a large message by using the Large Message to MSMQT sample application in BizTalk Server 2004 |
| 28058 | The value in the database is not successfully updated when an orchestration runs in BizTalk Server 2004 |
| 28059 | Fixes a problem that occurs when you import a BizTalk assembly binding file that has multiple child Alias elements specified in the PartyAlias element. |
| 28060 | Fixes a problem in BizTalk Server 2004 that occurs when you try to export an orchestration that contains a System.Xml.XmlDocument variable to BPEL. You receive an error message. |
| 28061 | Describes an issue in the BizTalk Server tutorials where you receive an error message. This issue occurs when the Logon property of the BizTalkServerIsolatedHost host is incorrectly set. |
| 28062 | Describes an issue that occurs when an XML message is translated into an EDI message in BizTalk Server 2004. A time-out occurs that causes no output to be generated. |
| 28063 | Describes a problem that occurs when you publish a schema that contains nested nodes that have the maxOccurs attribute set to the unbounded value. Provides a workaround for the problem. |
| 28064 | Explains that BizTalk Server 2004 is not supported in Windows NT 4.0 domains or in Windows 2000 domains in legacy mode. |
| 28065 | Contains information about how to install the BizTalk Adapter for MSMQ. Corrects the incorrect instructions in the BizTalk Adapter for MSMQ Installation Guide. |
| 28066 | Fixes a problem that occurs when a high volume of messages are passed to the SOAP adapter in BizTalk Server 2004. The startup thread pool is not large enough to handle the number of SOAP requests |
| 28067 | Fixes a problem in BizTalk Server 2004 that occurs when you try to use an MSMQT send port to process a message. You receive a The root element is missing error message. |
| 28068 | Describes a problem that occurs if the if an Error event is logged that indicates that a document is suspended in BizTalk Server. An exception handler is not triggered, and your trading partner may resend the original document. |
| 28069 | Describes a problem that occurs when a custom exception occurs in a published BizTalk Web service. Provides a resolution to the problem. |
| 28070 | Fixes a problem that occurs after you apply BizTalk Server 2004 SP1. You receive an exception when you try to validate a map in an Orchestration when the source documents have no target namespace. |
| 28072 | Fixes a problem that occurs when the Backup BizTalk Server SQL job is run and SQL Server is not listening on the default TCP port of 1433. The job is unsuccessful and errors are logged in the SQL Server error log. |
| 28073 | Fixes a problem in BizTalk Server 2004 where you receive a SQL Server does not exist error message when you connect to a BizTalk Server Management database from BizTalk Explorer. |
| 28074 | Fixes a problem that occurs when you try to persist messages to the database when the scope specifies an atomic transaction in BizTalk Server 2004 Service Pack 1. To resolve this problem, you must install a hotfix. |
| 28075 | Describes an error message that you may receive when you try to install a BizTalk Server 2004 service pack or other product update. To resolve this problem, contact Microsoft Product Support Services. |
| 28076 | Fixes a problem in BizTalk Server 2004 where you receive an error message when you configure the Logical address property for the EDI Adapter send handler. |
| 28077 | Describes a problem that occurs when you specify the Attribute FormDefault property of the source schema as Qualified, and the result of the Index functoid is an empty string. Includes a hotfix to resolve this problem. |
| 28078 | Describes a scenario where you may receive a Document Locked error message when you use the BizTalk SharePoint Messaging Adapter if you save an Office InfoPath document directly to a Windows SharePoint Services site. |
| 28079 | Fixes a problem that may occur if threads become deadlocked in SQL Server 2000 because a race condition occurs during the message dequeuing process in BizTalk Server 2004. |
| 28080 | 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. |
| 28081 | Fixes a problem that occurs when you set the EDI Datatype property to String in an XML Schema. The EDI Schema Editor Extension incorrectly sets the edi_datatype property to A when it should be AN. |
| 28082 | Fixes a problem that may occur when a heavily-loaded BizTalk Server 2004-based computer is configured to track whole message bodies. |
| 28083 | Fixes a problem in BizTalk Server 2004 where the EDI database repository is locked when it is accessed by multiple users by using different Terminal Sessions. |
| 28084 | Discusses a problem that occurs when you build data cubes with BizTalk Server 2004 data. When activity increases in the Business Activity Monitoring databases, you may experience periodic failures of Data Transformation Services in SQL Server 2000. |
| 28085 | Explains that if you modify and then assign the XML representation of a message in a BizTalk Server 2004 orchestration, this may appear to succeed. However, unless this was completed in a Construct Message shape, the actual message will not change. |
| 28086 | Describes a problem that occurs if BizTalk Server 2004 momentarily loses connectivity with a computer that is running SQL Server 2000. |
| 28087 | Describes the problem that occurs when a System.OutOfMemory exception occurs when you compile a solution map that has a complex source schema or a complex destination schema. Includes a hotfix to resolve the problem. |
| 28088 | Fixes a problem in BizTalk Server 2004 where a CDATA section and formatting is lost when you use a custom XSLT file to translate data. |
| 28089 | Describes a problem that occurs in Human Workflow Services Administration in BizTalk Server 2004. When you register actions or activity models, you may receive error messages. |
| 28090 | Fixes errors that occur when you try to validate an electronic data interchange (EDI) instance in BizTalk Server 2004. |
| 28091 | Describes a problem that occurs when you install BizTalk Server 2004 after you change the default settings for the Collation designator option and the sort order in SQL Server 2000. |
| 28092 | 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. |
| 28093 | 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. |
| 28094 | Discusses a problem where messages that are delivered to a Send port may not be sent by the BizTalk Server 2004 Adapter for SQL Server. To resolve this problem, you must install an earlier hotfix. |
| 28095 | Describes a problem that may occur in BizTalk Server 2004. BizTalk Message Queuing Adapter (MSMQT) may not start. |
| 28096 | Discusses a problem that may occur when you compile a BizTalk Server 2004 project that has a promoted property. If the property has a name that is the same as the Namespace property of the PropertySchema.xsd file, you may receive a compile error. |
| 28097 | Discusses a problem in BizTalk Server 2004 where you receive an error message when you try to send a message to the Inbox or Sent Items folder, you try to send a message from the Outbox to BizTalk Server, or you try to register a server. |
| 28098 | Fixes a problem that occurs when you generate a schema for a send port by using the SQL Transport Schema Generation Wizard in BizTalk Server 2004. The schema contains only a Success node. |
| 28099 | Describes a situation where BizTalk Server 2004 still lists Departments that are no longer registered with Business Active Services (BAS). |
| 28100 | Fixes a problem in BizTalk Server 2004 where the tracking data of a transaction is truncated because the data is larger than the space that is allocated in SQL Server to store the data. |
| 28101 | Fixes a problem that occurs when there is an unexpected increase in memory usage by the Windows Management Instrumentation provider process that hosts the Microsoft.Biztalk.ExplorerOM.dll file. |
| 28102 | Describes a problem that may occur when you run a BizTalk orchestration that is bound to a receive port that uses the BizTalk File adapter. |
| 28103 | Fixes a problem in BizTalk Server 2004 where SQL Server blocking occurs when a receive port has the Message Body Tracking feature enabled and a failure occurs. |
| 28104 | Describes why you may receive an Event ID: 6913 error message in the event log when you run a query in the Health and Activity Tracking tool in BizTalk Server 2004. Provides two resolutions to this problem. |
| 28106 | Describes why you may receive a Message has not been initialized error message in Visual Studio when you build a Microsoft BizTalk 2004 solution. |
| 28107 | Fixes the problem in BizTalk Server 2004 where a routing failure prevents a message from being published, but the corresponding pipeline-initiated transaction is not aborted. |
| 28108 | Fixes the problem where the segment terminator value of a functional acknowledgement is ignored when you configure the send port to use a specific character for the segment terminator in the Base EDI adapter send port of BizTalk Server 2004. |
| 28109 | Describes a problem that occurs when you post a document to a one-way HTTP receive port in BizTalk Server 2004, and you receive different HTTP status codes. |
| 28110 | Describes how to use GB18030 characters in BizTalk Server 2004 Service Pack 1. |
| 28111 | Describes a problem where BizTalk Server 2004 generates incorrect XML code for the loop structures for some schemas. |
| 28112 | Describes a fix for a problem where the signed message that is received from the BizTalk SharePoint Messaging Adapter cannot be verified. |
| 28113 | Describes why there is no option to disassemble result sets in the SQL adaptor that is provided in Microsoft BizTalk Server 2004. |
| 28114 | Discusses a problem where you may receive errors in the Application log on a BizTalk Server 2004 host because not all servers that are associated to the host can access the receive location. |
| 28115 | Describes a problem that occurs when you set a value for the retry count or the retry interval of the MSMQT adapter in Microsoft BizTalk Server 2004. |
| 28116 | Discusses an issue where you receive a Com_could not send BTS error message when you send messages through a send port that uses the EDI transport in BizTalk Server 2004. |
| 28117 | Describes a problem that may occur when you receive an invalid character error message after you save a rule in BizTalk Server 2004 Business Rule Composer. |
| 28118 | Describes how the data may become corrupted when you try to modify a database with updategrams. The data may become corrupted when the updategrams contain an XML prefix that is the same as text strings in the data. |
| 28119 | Describes how to obtain the latest BizTalk Server 2004 service pack. Additionally, it provides a link to the list of bugs that are fixed in the service pack. |
| 28120 | Describes the list of bugs that are fixed in BizTalk Server 2004 Service Pack 1. |
| 28121 | Fixes a problem that occurs if BizTalk Server enters a continuous loop when it processes an orchestration. A hotfix is available to resolve this problem. |
| 28122 | Fixes a problem that occurs when the subscription table in the BizTalk Server 2004 BizTalkMsgBoxDb database continues to fill up with ACK and NACK subscriptions. Provides a hotfix to resolve the problem. |
| 28123 | Fixes a problem with the BizTalk Server 2004 File Adapter may cause a NonPagedPool memory leak by issuing too many input/output request packets (IRPs). |
| 28124 | Fixes the problem of Minimal Lower Layer Protocol (MLLP) transport type not being available. This problem occurs when you configure a solicit-response send port for BizTalk Server Accelerator for HL7 1.0 (BTAHL7). |
| 28125 | Fixes the problem of performance degradation that is caused by delivery notification in Microsoft BizTalk Server 2004. |
| 28126 | Explains a problem that occurs when BizTalk Server 2004 loses an SQL connection during the time when the client is sending data through a published BizTalk one-way Web service. There may be a data loss. |
| 28127 | Describes a problem that occurs in BizTalk Server 2004 when you generate an instance of an EDIFACT schema. You receive a Failed to create instance for schema error message. |
| 28128 | Describes a problem that may occur when you send many large messages to IBM WebSphere MQ Workflow (formerly known as MQSeries Workflow). |
| 28129 | Fixes a problem in BizTalk Server 2004 where the BizTalk Business Rule Engine may incorrectly use the incorrect value when it evaluates a rule where different elements or attributes that are in an input XML document are retrieved with the same type. |
| 28130 | Fixes a problem where the effect of the Constraint.IsPositive property is reversed in Human Workflow Services (HWS) if you test with the ActivityModel\Design sample in the BizTalk Server 2004 SDK. |
| 28131 | Discusses an error message that you may receive in the BizTalk Server 2004 Configuration Wizard when you install BizTalk Server 2004 on a single computer. |
| 28132 | Discusses an issue that occurs where you receive an Invalid column name error message when you use SQLXML mapping schemas in BizTalk Server 2004. |
| 28133 | Describes an issue that occurs with query data in the Microsoft BizTalk Server 2004 Health and Activity Tracking tool. The data is not updated when you change your preferences from archived data to live data |
| 28134 | Discusses the problem of “Error 7105†being generated when Microsoft BizTalk Server 2004 accesses data in BizTalk Messaging Management or BizTalk MessageBox database on Microsoft SQL Server |
| 28135 | Describes a fix for a problem with BizTalk Server 2004. BizTalk Server 2004 may slow down when you use MSMQT. |
| 28136 | Fixes a problem where your BizTalk Server 2004-based computer slows and you receive deadlock errors in your SQL Server 2000 error log when BizTalk Server runs the bts_PurgeSubscriptions stored procedure. |
| 28137 | Describes a problem that occurs when the icon and the string resources for a custom functoid are not displayed in BizTalk Server 2004. |
| 28138 | Describes a behavior that is related to permissions. The behavior occurs when a BizTalk Server 2004 receive location is configured to use the File transport type. To resolve the behavior, you must grant the correct permissions. |
| 28139 | Fixes a problem that occurs when you have an increased load of messages that are being processed, and you are using ordered delivery ports. Microsoft BizTalk Server 2004 seems to stop responding. |
| 28140 | Fixes a problem where the Wrap segments property of the EDI Adapter send port is ignored in BizTalk Server 2004. You must install a hotfix to resolve this problem. |
| 28142 | Describes support for signing certificates on outgoing messages in BizTalk Server 2004. |
| 28143 | Describes a problem that may occur where you receive the “Build failed error message. The compiler for file type *.xsd and for file type *.btp failed in Microsoft BizTalk Server 2004. |
| 28144 | Describes a fix for a problem that occurs when you use the file adapter to receive messages that are larger than 100 KB in an orchestration. BizTalk Server 2004 stops responding. |
| 28145 | Describes a problem that may occur when you configure Message Queuing and MSMQT in a side-by-side installation, and messages may not be transmitted correctly. |
| 28146 | Explains that you cannot select the PartContextPropertyBase option as a configuration option for a property schema in BizTalk Server 2004. |
| 28147 | Describes a problem that occurs when you may receive a failure executing the receive pipeline event log error message when you deploy a schema assembly in BizTalk Server 2004. |
| 28148 | Describes a problem that occurs when you want to back up an instance of BizTalk Server 2004, and you must back up all the BizTalk Server 2004-related databases. Includes a hotfix that permits BizTalk Server 2004 to create a warm standby environment. |
| 28149 | Describes a problem that occurs when you receive a “NullPartException†error message when you use nested orchestrations in BizTalk Server 2004. Includes a hotfix to resolve the problem. |
| 28150 | Discusses the Error 8198 the job failed†error message in Microsoft BizTalk Server 2004. |
| 28151 | Fixes a problem in BizTalk Server 2004 where activity model observers cannot retrieve activity flow information if they are not participating in the activity flow. This behavior contradicts BizTalk Server 2004 documentation. |
| 28152 | Describes a problem that may occur when you send a document in BizTalk Server 2004, and you receive a Microsoft.BizTalk.DefaultPipelines.XMLTransmit error message. |
| 28153 | 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. |
| 28154 | Describes a problem that may occur when long delays occur before the server sends acknowledgements to client Message Queuing messages in BizTalk Server 2004. Includes a hotfix that you can apply to resolve the problem. |
| 28155 | Describes a problem that occurs when you try to run the Base EDI tutorial in BizTalk Server 2004, and you may receive an error message. |
| 28156 | Explains an issue that may occur when you create a custom pipeline component for handling large messages in BizTalk Server 2004. |
| 28157 | Describes why you cannot enable an SQL Receive Location in the BizTalk Server 2004 Administrator snap-in after you install the hotfix that is provided in Microsoft Knowledge Base article 843543. |
| 28158 | Describes a problem that occurs when you are running an orchestration that has a Dynamic HTTP Solicit-response port, and you receive an error message. Includes a hotfix that you can apply to resolve the problem. |
| 28159 | Describes why a BizTalk Server 2004 master secret may not always restore correctly after the NetBIOS name of the master secret server has been changed. |
| 28160 | Describes a problem where you receive a Schema is not deployed error message when you run the ArbitraryXPathSample sample that is in the BizTalk Server 2004 SDK. To resolve the problem, you must modify a line of code. |
| 28161 | Fixes a problem in BizTalk Server 2004 where increased memory usage occurs in the XLangHost process and then you receive a COMException exception from Microsoft.XLANGs.BizTalk.Engine in BizTalk Server 2004. |
| 28162 | Fixes a problem where BizTalk Server 2004 does not process documents correctly that contain certain character in the UNOC character set and certain Swedish characters. |
| 28163 | Describes a problem that occurs when you use the BizTalk Deployment Wizard to deploy an assembly that contains one or more EDI schemas, and the EDI database on the destination computer is not updated to include the deployed EDI schemas. |
| 28164 | Describes data duplication or loss that may occur if use the BizTalk Server 2004 FTP adapter. Discusses the configuration changes that we recommend that you make to avoid this behavior. |
| 28165 | Discusses an issue in BizTalk Server 2004 where a promoted property that has a default value set does not show up as a context property when the document is received. |
| 28166 | Explains that you may not be able to add more than one inbound connection to a script functoid in BizTalk Mapper. |
| 28167 | Describes steps that are missing from the Enterprise Application Integration tutorial in the BizTalk Server 2004 Documentation. |
| 28168 | Describes an error message that you receive in the BizTalk Server 2004 Explorer when you create a send port that uses the Electronic Data Interchange (EDI) Transport type. |
| 28169 | Lists the variant type (VT) attributes and corresponding VT values in a BizTalk Server 2004 binding file. |
| 28170 | Explains why the BizTalk Explorer for BizTalk Server 2004 may not be available in Visual Studio. |
| 28171 | Fixes a problem where error message details are not entered in the event log when pipeline failures for a Receive Location occur in BizTalk Server 2004. |
| 28172 | Fixes a problem where context properties of messages are not saved in the Message Box database and are lost in BizTalk Server 2004. |
| 28173 | Discusses a problem where creating a map that accepts multiple input message schemas that belong to the same namespace does not work in BizTalk Server 2004. |
| 28174 | This article discusses how to remove a non-functional computer from a BizTalk Server 2004 group. |
| 28175 | Describes an error message that you may receive when you configure the Business Activity Messaging and SharePoint Portal Server site in the BizTalk Server 2004 Configuration Wizard. |
| 28176 | Fixes a problem where an exception handler captures one exception two times when an exception occurs in a BizTalk Server 2004 orchestration. |
| 28177 | Explains how to cluster the Enterprise Single Sign-On (SSO) master secret server for use with a BizTalk Server 2004 group. |
| 28178 | Describes a problem that can occur when the TrackedMessages_Copy_BizTalkMsgBoxDb SQL Server Agent job runs in BizTalk Server 2004. Explains how to fix the problem. |
| 28179 | Discusses a problem where more than one OutResendT message may exist in the BizTalk Server 2004 Health and Activity Tracking (HAT) tool for each instance of the Message Queuing Adapter (MSMQT). |
| 28180 | Describes a bug in BizTalk Server 2004 where the ActivityModelDesigner API-provided default step parameters are not validated when you call the SaveActivityModelToSystem method. |
| 28181 | Fixes a problem in BizTalk Server 2004 where the orchestration stops responding and you must restart the BizTalk Server Host because an exception was not handled. |
| 28182 | Fixes a problem where you receive an HRESULT 0x80131500 error message in BizTalk Server 2004 Explorer or a Failed to execute SQL Statement error message in Visual Studio .NET 2003 if execution of the SQL statement takes too long. |
| 28183 | Fixes a problem in BizTalk Server 2004 where you receive a schemaLocation could not be resolved compiler error message when you import schemas from assemblies that have redundant imports. |
| 28184 | Discusses a documentation error for the Before Put FTP command and the After PUT FTP command in the online documentation for BizTalk Server Adapter for FTP. |
| 28185 | Discusses group inheritance for agreements in BizTalk Server 2004. |
| 28186 | Discusses a problem in BizTalk Server 2004 where you cannot open a list of saved queries in Health and Activity Tracking (HAT). |
| 28187 | Explains that the BizTalk Framework (BTF) document type is not supported with the BizTalk Message Queuing Adapter (MSMQT) in BizTalk Server 2004. |
| 28188 | Describes why the BizTalk Rules database is not created when you install BizTalk Server 2004 Administration Tools. |
| 28189 | Explains that the Hub Side SEED Wizard deployment tool does not package custom pipeline components in BizTalk Server 2004. |
| 28190 | Provides information about integrating large security systems to improve operational efficiencies and reduce deployment cost in new LOB computing solutions. Tells how to offer single sign-on to existing programs and how to synchronize user passwords. |
| 28191 | Fixes a problem in BizTalk Server 2004 where you may not pick up files when you use the Electronic Data Interchange (EDI) Adapter and you specify the Uniform Naming Convention (UNC) path for the receive handler location. |
| 28192 | Fixes the disabled receive locations that occur during the BizTalkMsgBoxDb database failover. |
| 28193 | Fixes a problem where the BizTalk Server 2004 XML Mapper Database Lookup functoid/Value Extractor functoid produces inconsistent results when it tests a map with many Database functoids. |
| 28194 | Fixes a memory leak in Visual Studio .NET that occurs when you deploy a project that contains a schema with a number of roots and then you try to edit or create Send or Receive ports. |
| 28195 | Explains that if your installation of BizTalk Server 2004 requires more than one computer, you must specify domain groups and user accounts in the BizTalk Server Configuration Wizard. |
| 28196 | Fixes a problem in BizTalk Server 2004 where the SQL Adapter generates a System.OutOfMemory exception when it polls a large-sized message (about 205 MB). |
| 28197 | Explains why the BizTalk Server Message Queuing Adapter (MSMQT) fails with no error message when you send a message to @DIRECT=OS:NoSuchMachine\private$\NoSuchQueue1. |
| 28198 | Fixes a problem in BizTalk Server 2004 where you may receive an error message when you use the BizTalk 2004 Mapper to test a map. |
| 28199 | Explains why you cannot resume messages from BizTalk Server 2004 Health and Activity Tracking after Internet Information Services (IIS) is stopped and then is restarted. |
| 28200 | Fixes the BizTalk Server EDI Adapter so that it can work with any EDI document types. |
| 28201 | Describes a problem that occurs because the appID column of the xref_IDXRefData table is limited to 50 characters. Includes a hotfix that you can apply to extend the appID column from 50 characters to 255 characters. |
| 28202 | Fixes a problem in BizTalk Server 2004 where the whole Electronic Data Interchange (EDI) interchange is suspended if any subdocuments fail validation. |
| 28203 | Adds a new property that is named Openness to the global property schema in BizTalk Server 2004. |
| 28204 | Fixes a problem in BizTalk Server 2004 where any change to an Electronic Data Interchange (EDI) schema does not take effect. |
| 28205 | Fixes a Health and Activity Tracking (HAT) problem where HAT does not reflect the completed status of a business process. |
| 28206 | Fixes BizTalk Server 2004 to improve performance by optimizing the internal processing of XPaths. |
| 28207 | Fixes a bug where outbound maps are not applied in a request-response receive port. |
| 28208 | Updates BizTalk Server 2004 so that the user can add custom HTTP headers and modify standard HTTP headers in HTTP request and response. |
| 28209 | Discusses how the Document Target Namespace and Response Root Element Name parameters are used in a BizTalk Server 2004 static one-way port that uses a transport type of SQL. |
| 28210 | Explains how a functoid that has been renamed from the Toolbox in the BizTalk Mapper will not retain its new name when it is placed on the BizTalk Mapper grid. |
| 28211 | Discusses how deploying an orchestration can cause documents that are in the location that is monitored by the orchestration's Receive location to be suspended. |
| 28212 | Explains why you cannot receive a file in an orchestration by using a pass-through pipeline in Microsoft BizTalk Server 2004. |
| 28213 | Fixes a problem in BizTalk Server 2004 when you try to match a character set name to its WebName property. |
| 28214 | Explains that you may have various unexpected problems when you try to use BizTalk Server 2004 on a virtual machine. Microsoft does not support this configuration. |
| 28215 | Describes a problem that occurs when the SQL Adapter repeatedly tries to process a bad message. Includes a hotfix that you can install to resolve this problem. |
| 28216 | Describes a problem that occurs when you try to process an XML document that is larger than 4 GB. BizTalk Server 2004 creates an integer overflow exception in the application log of the BizTalk Server computer. |
| 28217 | Describes a problem that occurs after you deploy a BizTalk Server 2004 project to additional Web servers. Includes a resolution that you can use to resolve the problem. |
| 28218 | Describes a problem that occurs when you receive a schema validation error when you have all optional children under a positional tagged element. Includes a hotfix that you can use to resolve the problem. |
| 28219 | Describes the operating systems that are supported by the FTP Adapter for BizTalk Server 2004. |
| 28220 | Discusses an error message that you receive in BizTalk Server 2004 Setup that occurs because BizTalk Server 2004 does not permit multiple components to share the same database. |
| 28221 | Fixes a problem where BizTalk Server 2004 rejects old-format reliable messaging receipts from BizTalk Server 2000 and from BizTalk Server 2002. |
| 28222 | Fixes a memory leak that occurs when you open and you close maps in Visual Studio. |
| 28223 | Fixes an problem in BizTalk Server 2004 where you cannot override the HTTP Adapter properties within a send port. |
| 28224 | 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. |
| 28225 | Fixes a problem in BizTalk Server 2004 so that you can disable chunked encoding in HTTP transport. |
| 28226 | Fixes a problem where BizTalk Server throws a PersistenceException exception when it tries to persist the state of an orchestration instance to the database. |
| 28227 | Fixes a problem where the BizTalk Server 2004 MIME/SMIME Decoder in a receive pipeline does not decrypt an incoming message. |
| 28228 | Discusses a problem that occurs when you delete the BizTalk 2004 Server database before you run the configFramework.exe /u command (unconfigure mode). Describes a workaround for this problem. |
| 28229 | Fixes an issue where the HAT UI becomes unresponsive if BizTalk Server is processing a lot of data. |
| 28230 | Fixes a compilation error that may occur while you are compiling large maps. |
| 28231 | Fixes a problem where BizTalk Server rejects the response when you use content-based routing with a request-response port. |
| 28232 | Fixes a problem where element reference resolution fails due to multiple imports with a same namespace. |
| 28233 | Discusses the SOAP port and the authentication types that are available in BizTalk Server 2004. |
| 28234 | Fixes an issue with high CPU utilization when a timed scope is not throwing the timeout exception in BizTalk Server 2004. |
| 28235 | Describes the problems that are fixed in BizTalk Server 2004 Rollup Package 2004. |
| 28236 | Explains the steps to remove the BizTalk Server 2004 Rollup Package 1 that is mentioned in Knowledge Base article 837168. |
| 28237 | Explains that the BizTalk Server 2004 Configuration Wizard can fail if you specify the user account or the group to be used for the SSO Administrator with a nomenclature that specifies the domain name as the fully qualified domain name. |
| 28238 | Fixes the problem of slow performance by adding optimizations to maps that use logical functoids. |
| 28239 | In Microsoft BizTalk Server 2004, when you use the Microsoft Windows Management Instrumentation (WMI) classes MSBTS_DeploymentService API to deploy large assemblies in BizTalk Server 2004, you may receive an error message that is similar to the... |
| 28240 | Fixes an unhandled exception that may occur in the flat file parser when BizTalk Server 2004 is under heavy stress. |
| 28241 | Fixes a problem that occurs when you use the same condition two times in a rule set, one time with the NOT operator and one time without the NOT operator. |
| 28242 | Fixes a bug that causes the HTTP adapter to fail to send messages larger than 48 KB if there is a proxy. |
| 28243 | Provides a hotfix to correct the expression error A service or property can only be accessed on the current service. |
| 28244 | Microsoft BizTalk Server 2004 includes a new component named the Business Rules Engine (BRE). You can use BRE to dynamically add, edit, and delete business rules that are being applied to the business processes. |
| 28245 | 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. |
| 28246 | Explains that profiles created with the Tracking Profile Editor (TPE) cannot be configured to track string messages. Tracking profiles depend on information in XML schemas for tracking messages. String messages do not use schemas. |
| 28247 | Explains why this error occurs and provides links to many language versions of the rollup packages that you can install to fix this problem. |
| 28248 | Explains that the BizTalk Server Application Service must be stopped and then restarted after a modified schema is redeployed. |
| 28249 | Explains how to install the BizTalk Adapter Trace Utility and enable tracing in BizTalk Server 2004. Trace files can be useful tools for debugging problems in BizTalk Server 2004. |
| 28250 | Explains that if you try to run a BizTalk Server 2004 Orchestration that contains rules, you may receive an error message if you installed the Rules Engine separately from the BizTalk Engine. |
| 28251 | This article applies to the release candidate of Microsoft BizTalk Server 2004. This article discusses known issues that you may experience when you use Microsoft BizTalk Server 2004. |
| 28252 | A File Receive function fails and becomes disabled and an error message similar to the following appears in the BizTalk Server application log: Event Type: Error Event Source: BizTalk Server Event Category: Document Processing Event ID: 324 Computer:... |