Error handling when an MQSeries adapter opens a queue in BizTalk

Biztalk MQSeries Adapter Enable queue error handlingAuthor: Zheng Zuo Date: after installing the MQSeries adapter on the BizTalk Server and mqsagent on the MQ server while configuring the new IBM WebSphere MQ server of the Organization today, the following error occurs when you use BizTalk Server 2006 to access the message queue. Event Type: Warning event Source: Biztalk Server 2006 event type: Biztalk Server 2006 event ID: 5740 Date: Event: 9:31:44 User: N/a computer: NBEPORT-BTS description: the adapter "MQSeries" returns an error message. The detailed information is "An error occurred while opening the queue. The queue name is nbeport_nbccmsend.customs.container.movecommand. The cause code is 2045 .". Event Type: Warning event Source: Biztalk Server 2006 event type: Biztalk Server 2006 event ID: 5743 Date: Event: 10:56:05 User: N/a computer: NBEPORT-BTS description: the adapter cannot transmit the data to the sending port "btstomqs. nbccm. customs. container. movecommand "(the URL is" mqs: // 192.120.10.28/nbeport_nbccm/send. customs. container. movecommand. After the Retry Interval specified for the sending port, the message will be re-transmitted. Details: "An error occurred while opening the queue manager. The Queue Manager name is nbeport_nbccm and the cause code is 2354 .". The platform environment is as follows: Biztalk Server 2006 and IBM WebSphere MQ Server 6.0 are deployed on different servers. The operating system is Windows Server 2003 Enterprise Edition + SP2. There is no Windows Domain environment. When creating an MQSeries adapter through BizTalk Server 2006, you can access the server where the remote MQ server is located through the queue definition, and enumerate the queue manager and the corresponding queue. (To make the remote access to mqs successful, you need to configure it, refer to here) Run mongodcomcnfg.exe "to open the component service console. Access "computer"-> "my computer"-> "COM + application"-> "mqsagent2 ". To solve the problem, follow these steps: 1. right-click "mqsagent2" to access "properties", select the "ID" tab in the mqsagent2 Properties dialog box, and confirm that you are using the user. I am using an independently added user with the username "mqsagentuser ". Confirm that the user belongs to the IBM WebSphere MQ Management Group and the group name is "MQM". Also, confirm that the user in the "role" subnode under "mqsagent2" belongs to the "MQM" group. 2. right-click "my computer" to access "properties", select the "MSDTC" tab in the "properties" dialog box, and click "Security Configuration, in the dialog box, select "do not require verification. Run the application instance corresponding to BizTalk Server 20006 again, and read and write the remote mqs queue successfully.