MQSAgent Configuration on Windows 2000 Errors

I have a Server running win2k and WebSphere MQ 5.3 Server that I need to integrate with. I have installed all the lastest fix packs, fix pack 12 for WebSphere MQ. I need to integrate to it using the BizTalk 2006 MQSeries Adapter. I have run the BizTalk Server 2006 MQSeries Agent configuration wizard to deploy the MQSAgent COM+ object on my server with BizTalk and that has successful. The other application that I'm trying to integrate to is running on Windows 2000 and has WebSphere MQ Server installed on it. When I ran theMQSeries Agent configuration Wizard I'm getting the following error: "The installation if the COM+ component failed". I have checked in the event viewer there is no indication to what is causing the error.

I then tried to deploy the MQSeries COM+ object manually by copying the MQSAgent.dll from the BizTalk folder and copied it to the machine with WebShpere MQ Server ran the command "Regsvr32 MQSAgent.dll ". When I tried to send the messages to it using the BizTalk MQSeries Adapter. I'm getting an error that the remote MQSAgent is not configured properley. I checked the security setting in the DCOM configuration and the MQSAgent2 COM+ object was successful deployed. I don't know what I should do next to resolve this error. Depolying and configuring the MQSAgent using the wizard has failed and trying to do it manually has also not worked. Can anyone please help ? Thanx in advance.

[1566 byte] By [Panashe] at [2008-1-10]
# 1

Hi,


Actually, your scenario is not clear in my mind. But the first think that drop into my mind is Group Policy limitations.

Are these machine involved in a domain which has some strict COM+ policies? Did you ever think about it?


Also, second probable think is. Is this machine a 64bit machine? 'Cause as far as I know, MQSAgent COM+ application
is not supported in 64bit platforms.

OR is this Biztalk an upgrade from BizTalk Server 2004 to BizTalk Server 2006. After upgrading to BizTalk Server 2006
from BizTalk Server 2004 re-run setup, select the Modify option, and select the MQSeries Agent under the Additional
Software to install these components.

You can take a look at the following SDK doc

Using the MQSAgent COM+ Configuration Wizard - http://msdn2.microsoft.com/en-us/library/aa561858.aspx


If none of them works for your case, can you give some more info about your case?

- Ibrahim DURMUS
http://www.ibrahimdurmus.com
http://blogs.msdn.com/ibrahim

# 2
Ibrahim,

Thanx for the response. The Windows 2000 is not 64 bit, I'm running BizTalk Server 2006. I haven't upgraded. I'm simply trying to communicate with a gateway on the network that is running windows 2000 and has MQ V5.3 Server installed. What I'm not sure is about is whether the MQSAgent can run on windows 2000 Pro. At the moment I have got a work around by installing WebSphere MQ sever on my machine with BizTalk and the two websphere MQ's talk to each other using remote queuing. So all I have to do is use the BizTalk MQSeries Adapter to put a message on a local WebSphere transmit queue and that passes my message to the remote queue. This works fine but I didn't want to do it this way . This is probably a better solution than trying to use the MQSAgent send message to remote WebSphere MQ.

Panashe at 2007-10-3 > top of Msdn Tech,BizTalk Server,BizTalk R2 General...
# 3

Hi Panashe,

What you basically say is:

MQSeries <> MQSeries can talk
Biztalk Adapter <> MQSeries can not talk.


I bet this is an DTC problem. MQSeries is not blocked but biztalk is blocked with a DTC config.

Can you ensure your MSDTC setting,

Here I point you two documents:

Please give them a credit and try.

Troubleshooting Problems with MSDTC - http://msdn2.microsoft.com/en-us/library/aa561924.aspx
Transactions - http://blogs.msdn.com/florinlazar/archive/2004/06/18/159127.aspx


If these don't work, can you let me know?

Thanks


- Ibrahim DURMUS
http://www.ibrahimdurmus.com
http://blogs.msdn.com/ibrahim

NOTE: Second article can seem to you as related with XP. Don't let it mislead you. It still applies to downlevel OS.