Details | |
Product: | BizTalk Server |
Event ID: | 6912 |
Source: | BizTalk Server 3.0 |
Version: | 3.0.4604.0 |
Message: | The following stored procedure call failed: “%1”. SQL Server returned error string: “%2”. |
Explanation | |
This is an unexpected error. Contact Product Support Services and provide a trace dump. |
|
User Action | |
The stored procedure call was unsuccessful. If this problem persists, enable trace and contact Product Support along with the trace dumps. |
Category: BizTalk Server
There was a failure executing the receive pipeline: “%1” Source: “%2” Receive Location: “%3″ Reason:”%4”.
Details | |
Product: | BizTalk Server |
Event ID: | 5719 |
Source: | BizTalk Server 3.0 |
Version: | 3.0.4604.0 |
Message: | There was a failure executing the receive pipeline: “%1” Source: “%2” Receive Location: “%3″ Reason:”%4”. |
Explanation | |
There was a failure executing the receive pipeline. |
Related:
- The MSMQT subservice failed to actually send the outgoing message to ‘%2’, error code “%1” .
- The message has been delivered to the destination queue.
- MSMQT.DLL and MSMQTN.DLL have different versions.
- The buffer is too small to return result.
- BizTalk Message Queuing was handed over a message for processing without a required property.
The Messaging Engine failed to add a receive URL “%1” to the adapter “%2”. Reason: “%3”.
Details | |
Product: | BizTalk Server |
Event ID: | 5644 |
Source: | BizTalk Server 3.0 |
Version: | 3.0.4604.0 |
Message: | The Messaging Engine failed to add a receive URL “%1” to the adapter “%2”. Reason: “%3”. |
Explanation | |
The Receive Manager failed to add a receive URL to the adapter. |
Related:
- The Messaging Engine failed to create the transport adapter “%1”. Check the configuration.
- The Messaging Engine received an error from a transport adapter while notifying it with the BatchComplete event. Reason “%1”.
- The Messaging Engine failed while notifying an adapter of its configuration.
- The Messaging Engine failed to create the receive adapter “%1”. Reason: “%2”.
- The Messaging Engine failed to update the configuration for the receive location “%1” for adapter “%2”. Reason: “%3”.
The MSMQT subservice encountered an error executing initialization of the networking component. The binding IP address may be invalid, or another application may be holding the IP port.
Details | |
Product: | BizTalk Server |
Event ID: | 7451 |
Source: | BizTalk Server 3.0 |
Version: | 3.0.4604.0 |
Message: | The MSMQT subservice encountered an error executing initialization of the networking component. The binding IP address may be invalid, or another application may be holding the IP port. |
Explanation | |
MSMQT failed to initialize the networking component. This may occur when another process is using port 1801 or port 3527. | |
User Action | |
From the command line prompt, type “netstat -ao” to check if another process is using port 1801 for the BizTalk Server 2004’s IP address. Ensure that the correct versions of msmqt.dll and msmqtn.dll are installed. |
Related:
- The FILE receive location %1 has an invalid format. It must include path and file mask.
- The file %1 is either read-only or a system file. The file receive adapter cannot process files with these attributes.
- The FILE receive adapter cannot delete file %1. This file is processed successfully. Please delete this file from the disk.
- Encoder could not find the encryption certificate in the “Local Machine\\Other People” certificate store. Unable to encrypt outbound message.
- The property sheet field named “From” has not been configured for the BizTalk.SendSMTP transport component.
MSMQT dll has failed to initialize.
Details | |
Product: | BizTalk Server |
Event ID: | 7456 |
Source: | BizTalk Server 3.0 |
Version: | 3.0.4604.0 |
Message: | MSMQT dll has failed to initialize. |
Explanation | |
A MSMQT networking component failed to initialize. | |
User Action | |
Ensure that MSMQ ports 1801 and 3627 are available for BizTalk Server 2004. |
Related:
The Messaging Engine encountered an error moving the message to the SuspendQ.
Details | |
Product: | BizTalk Server |
Event ID: | 5664 |
Source: | BizTalk Server 3.0 |
Version: | 3.0.4604.0 |
Message: | The Messaging Engine encountered an error moving the message to the SuspendQ. |
Explanation | |
The Messaging Engine encountered an error moving the message to the SuspendQ. |
Related:
The property ‘%1’ has a value with length greater than 256 characters.
Details | |
Product: | BizTalk Server |
Event ID: | 6958 |
Source: | BizTalk Server 3.0 |
Version: | 3.0.4604.0 |
Message: | The property ‘%1’ has a value with length greater than 256 characters. |
Explanation | |
The promoted property must be less than 256 characters. |
|
User Action | |
Provide an acceptable input value in your input document. |
Related:
- Invalid data, type or array element size in variant.
- MSMQT static data in the database is written by an incompatible version.
- MSMQT identity: machine %1 GUID %2
- MSMQT failed to get current networking parameters
- The MSMQT subservice failed to start because Windows MSMQ service is running on the computer.
The adapter “%1” raised an error message. Details “%2”.
Details | |
Product: | BizTalk Server |
Event ID: | 5740 |
Source: | BizTalk Server 3.0 |
Version: | 3.0.4604.0 |
Message: | The adapter “%1” raised an error message. Details “%2”. |
Explanation | |
The adapter raised an error message. |
Related:
- The FILE send adapter for URL %1 cannot create completion event.
- The Messaging Engine failed to create the transport Adapter “%1”. The adapter does not impelement one of the mandatory interface(s) “%2”.
- The Messaging Engine failed to create the transport adapter “%1”. Check the configuration.
- The Messaging Engine failed to create the transport adapter “%1″, Reason:”%2”.
- The Messaging Engine failed while notifying an adapter of its configuration.