Details | |
Product: | BizTalk Server |
Event ID: | 7459 |
Source: | BizTalk Server 3.0 |
Version: | 3.0.4604.0 |
Message: | MSMQT failed to register or find %2 in Active Directory with the error code %1. You may use support utility ‘tmq treg’ to fix it. |
Explanation | |
This operation failed. BizTalk Server 2004 attempted to locate or create the MSMQ configuration object in the Active Directory under the name specified for MSMQT during BizTalk Server 2004 setup. | |
User Action | |
Check the Active Directory for issues. Verify that y ou have specified the correct name for the Active Directory registration when you installed BizTalk Server 2004. |
Category: BizTalk Server
The MSMQT subservice failed to actually send the outgoing message to ‘%2’, error code “%1” .
Details | |
Product: | BizTalk Server |
Event ID: | 7454 |
Source: | BizTalk Server 3.0 |
Version: | 3.0.4604.0 |
Message: | The MSMQT subservice failed to actually send the outgoing message to ‘%2’, error code “%1” . |
Explanation | |
A MSMQT networking component failed to send the message to the wire. | |
User Action | |
Use error code to find out the reason for the failure. |
Related:
The MSMQT subservice failed to process outgoing message, error code “%1, Destination: %2, Details: %3, %4” .
Details | |
Product: | BizTalk Server |
Event ID: | 7453 |
Source: | BizTalk Server 3.0 |
Version: | 3.0.4604.0 |
Message: | The MSMQT subservice failed to process outgoing message, error code “%1, Destination: %2, Details: %3, %4” . |
Explanation | |
A problem occurred during the outbound processing of the MSMQT message. | |
User Action | |
Use error code to find out the reason for the failure. |
Related:
- The MSMQT subservice failed to process incoming message, error code “%1” .
- The MSMQT subservice encountered an error executing tracking for outbound message.
- The running instance has encountered an unexpected operation or the instance is in an illegal state.
- The BizTalk HTTP receive adapter could not create “%1″, error:”%2”.
- %1Additional error information:Error code: %2!x!Error source: %3Error description: %4
The MSMQT subservice failed to process incoming message, error code “%1” .
Details | |
Product: | BizTalk Server |
Event ID: | 7452 |
Source: | BizTalk Server 3.0 |
Version: | 3.0.4604.0 |
Message: | The MSMQT subservice failed to process incoming message, error code “%1” . |
Explanation | |
A problem occurred during the inbound processing of the MSMQT message. | |
User Action | |
Use error code to find out the reason for the failure. |
Related:
- The running instance has encountered an unexpected operation or the instance is in an illegal state.
- %1Additional error information:Error code: %2!x!Error source: %3Error description: %4
- MSMQT static data in the database is written by an incompatible version.
- MSMQT failed to get current networking parameters
- The MSMQT subservice failed to process outgoing message, error code “%1, Destination: %2, Details: %3, %4” .
The MSMQT subservice encountered an error executing tracking for outbound message.
Details | |
Product: | BizTalk Server |
Event ID: | 7450 |
Source: | BizTalk Server 3.0 |
Version: | 3.0.4604.0 |
Message: | The MSMQT subservice encountered an error executing tracking for outbound message. |
Explanation | |
The tracking operation failed for the outbound MSMQT message. | |
User Action | |
No user action required. |
Related:
- The MSMQT subservice failed to process outgoing message, error code “%1, Destination: %2, Details: %3, %4” .
- The MSMQT subservice failed to process incoming message, error code “%1” .
- The running instance has encountered an unexpected operation or the instance is in an illegal state.
- The BizTalk HTTP receive adapter could not create “%1″, error:”%2”.
- %1Additional error information:Error code: %2!x!Error source: %3Error description: %4
The MSMQT subservice encountered an error executing an outbound pipeline.
Details | |
Product: | BizTalk Server |
Event ID: | 7449 |
Source: | BizTalk Server 3.0 |
Version: | 3.0.4604.0 |
Message: | The MSMQT subservice encountered an error executing an outbound pipeline. |
Explanation | |
The pipeline failed during the processing for the outbound MSMQT message. | |
User Action | |
Verify that the outbound pipeline is configured for the MSMQT send port. |
Related:
- XML Validator cannot retrieve document specification by using this type: “%1”.
- MSMQT receive location configuration used the invalid private queue format number (it should be over 4).
- MSMQT receive location configuration used a private queue format number that is already in use.
- MSMQT static data in the database is written by an incompatible version.
- MSMQT identity: machine %1 GUID %2
The MSMQT subservice encountered an error executing an inbound pipeline.
Details | |
Product: | BizTalk Server |
Event ID: | 7448 |
Source: | BizTalk Server 3.0 |
Version: | 3.0.4604.0 |
Message: | The MSMQT subservice encountered an error executing an inbound pipeline. |
Explanation | |
The pipeline failed during the processing for the inbound MSMQT message. | |
User Action | |
Verify that the inbound pipeline is configured for the MSMQT receive location. |
Related:
- XML Validator cannot retrieve document specification by using this type: “%1”.
- MSMQT receive location configuration used the invalid private queue format number (it should be over 4).
- MSMQT receive location configuration used a private queue format number that is already in use.
- MSMQT static data in the database is written by an incompatible version.
- MSMQT identity: machine %1 GUID %2
The message has been delivered to the destination queue.
Details | |
Product: | BizTalk Server |
Event ID: | 7447 |
Source: | BizTalk Server 3.0 |
Version: | 3.0.4604.0 |
Message: | The message has been delivered to the destination queue. |
Explanation | |
The message has been delivered to the destination. | |
User Action | |
No user action required. |
Related:
Time to receive has expired while the message was still in its local outgoing queue (generated locally by sender).
Details | |
Product: | BizTalk Server |
Event ID: | 7446 |
Source: | BizTalk Server 3.0 |
Version: | 3.0.4604.0 |
Message: | Time to receive has expired while the message was still in its local outgoing queue (generated locally by sender). |
Explanation | |
The sender’s copy of the sent message has expired before the destination could acknowledge receipt of the message. | |
User Action | |
No user action required. |
Related:
- The sender does not have send access rights to the queue.
- MSMQT receive location configuration used the invalid private queue format number (it should be over 4).
- The message has been delivered to the destination queue.
- Time to receive has expired while the message was still in its destination queue (generated by destination)
- The message was purged at the destination queue.
Time to receive has expired while the message was still in its destination queue (generated by destination)
Details | |
Product: | BizTalk Server |
Event ID: | 7445 |
Source: | BizTalk Server 3.0 |
Version: | 3.0.4604.0 |
Message: | Time to receive has expired while the message was still in its destination queue (generated by destination) |
Explanation | |
The sent message was not received by the application. It expired in the destination queue. | |
User Action | |
No user action required. |