|
Home > Archive > BizTalk Server General > November 2004 > MSMQT side-by-side send port problem
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
MSMQT side-by-side send port problem
|
|
| Kuba Gregorski 2004-11-16, 2:47 am |
| Hi!
I was wondering if anyone had the same problem I'm experiencing.
I have BizTalk 2004 with MSMQT adapter installed in a side-by-side mode,
configured everything according to the documentation - i.e. separate IPs,
separate entries in dns, and modified
HKLM\Software\Microsoft\MSMQ\Parameters BindInterfaceIP to IP on which old
MSMQ should listen.
I created send port with MSMQT adapter sending messages to queue on a remote
machine using
'DIRECT=OS:machine\private$\queue' format.
When I send messages to the remote machine all or most of them never reach
the destination.
Checking in HAT reveals that MSMQT is not getting acknowledge, hence all
messages stay in BizTalk in status 'Consumed'.
With each new message 'Unacknowledged messages' counter increases and the
message does not get sent.
I've managed to figure out that the problem is in standard MSMQ 'disturbing'
BizTalk's MSMQT -
when I disable standard MSMQ service everything works fine - i.e. BizTalk
sends messages successfuly and gets acknowledges back.
However this is not a solution I would hope for, since this puts the whole
idea of side-by-side installation in question.
Has anyone experienced this problem? Any ideas how I might solve this?
Thank you in advance for your help.
Kuba
| |
| Danny Buysse 2004-11-16, 7:46 am |
| Kuba,
We had similar problems with a side by side installation.
All went wel when you do the setup and try 1 message. But when we had some
load it always blocked. Messages from MSMQ stayed in the outgoing queues and
messages from MSMQT where consumed but never arrived in MSMQ.
Restarting the services solved the problem, but this wasn't an option.
So we have placed one extra box with just MSMQ running on it for when we
need it.
"Kuba Gregorski" wrote:
> Hi!
> I was wondering if anyone had the same problem I'm experiencing.
>
> I have BizTalk 2004 with MSMQT adapter installed in a side-by-side mode,
> configured everything according to the documentation - i.e. separate IPs,
> separate entries in dns, and modified
> HKLM\Software\Microsoft\MSMQ\Parameters BindInterfaceIP to IP on which old
> MSMQ should listen.
>
> I created send port with MSMQT adapter sending messages to queue on a remote
> machine using
> 'DIRECT=OS:machine\private$\queue' format.
> When I send messages to the remote machine all or most of them never reach
> the destination.
> Checking in HAT reveals that MSMQT is not getting acknowledge, hence all
> messages stay in BizTalk in status 'Consumed'.
> With each new message 'Unacknowledged messages' counter increases and the
> message does not get sent.
>
> I've managed to figure out that the problem is in standard MSMQ 'disturbing'
> BizTalk's MSMQT -
> when I disable standard MSMQ service everything works fine - i.e. BizTalk
> sends messages successfuly and gets acknowledges back.
> However this is not a solution I would hope for, since this puts the whole
> idea of side-by-side installation in question.
>
> Has anyone experienced this problem? Any ideas how I might solve this?
>
> Thank you in advance for your help.
>
> Kuba
>
>
>
>
| |
| Kuba Gregorski 2004-11-16, 7:46 am |
| Thank you for your answer!
This is exactly the same problem I'm experiencing.
So it seems there is no way to get around this other than have a separate
machine...
Brrr... :-)
Thank you!
Kuba
"Danny Buysse" <DannyBuysse@discussions.microsoft.com> wrote in message
news:A8EEE4CC-3D38-438F-B1E8-8772F8DAEA8A@microsoft.com...[vbcol=seagreen]
> Kuba,
>
> We had similar problems with a side by side installation.
> All went wel when you do the setup and try 1 message. But when we had some
> load it always blocked. Messages from MSMQ stayed in the outgoing queues
> and
> messages from MSMQT where consumed but never arrived in MSMQ.
> Restarting the services solved the problem, but this wasn't an option.
>
> So we have placed one extra box with just MSMQ running on it for when we
> need it.
>
>
> "Kuba Gregorski" wrote:
>
| |
| Nikhil Rajwade 2004-11-16, 7:46 am |
| Gents,
We are running Biztalk 2004 in a similar config and it works fine. I think
its a problem with the MSMQT ip binding. Did you install MSMQ before or after
you configured Biztalk? In the config framework wizard did you bind Biztalk
Message Queing to a particular IP. The default is all assigned IP addresses.
Try reconfiguring Biztalk using the ConfigFramework.exe (you will need to
run ConfigFramework.exe /u to wipe the configuration. Manually delete the
Biztalk databases including the SSODB and the BAM databases on the analysis
server.) and selecting 'Bind to this IP only' in the Biztalk Messaging
(MSMQT) configuration screen.
Hope this helps!
Nikhil
Biztalk Consultant - Sysrepublic.
"Kuba Gregorski" wrote:
> Thank you for your answer!
>
> This is exactly the same problem I'm experiencing.
>
> So it seems there is no way to get around this other than have a separate
> machine...
>
> Brrr... :-)
>
> Thank you!
>
> Kuba
>
> "Danny Buysse" <DannyBuysse@discussions.microsoft.com> wrote in message
> news:A8EEE4CC-3D38-438F-B1E8-8772F8DAEA8A@microsoft.com...
>
>
>
| |
| Kuba Gregorski 2004-11-16, 2:28 pm |
| See inline comments.
"Nikhil Rajwade" <Nikhil Rajwade@discussions.microsoft.com> wrote in message
news:D778FACB-EFC4-4AA5-A102-A0AB3C64B870@microsoft.com...
> Gents,
>
> We are running Biztalk 2004 in a similar config and it works fine. I think
> its a problem with the MSMQT ip binding. Did you install MSMQ before or
> after
> you configured Biztalk?
MSMQ had been installed on the machine before I installed Biztalk.
During biztalk configuration I chose 'Bind to this IP only' and set it to IP
A.
After installing Biztalk I added HKLM\Software\Microsoft\MSMQ\Parameters
BindInterfaceIP
with IP B. Needless to say machine reboot followed.
> In the config framework wizard did you bind Biztalk
> Message Queing to a particular IP. The default is all assigned IP
> addresses.
Yes. As described above.
> Try reconfiguring Biztalk using the ConfigFramework.exe (you will need to
> run ConfigFramework.exe /u to wipe the configuration. Manually delete the
> Biztalk databases including the SSODB and the BAM databases on the
> analysis
> server.) and selecting 'Bind to this IP only' in the Biztalk Messaging
> (MSMQT) configuration screen.
Done that :-)
>
> Hope this helps!
> Nikhil
> Biztalk Consultant - Sysrepublic.
Thank you very much for your answer, unfortunately it seems that this didn't
solve my problem.
Do you think reinstalling MSMQ (not MSMQT/Biztalk - done it a couple of
times) could help? I think I haven't tried this one yet.
Thanks again for help!
Kuba
[vbcol=seagreen]
> "Kuba Gregorski" wrote:
>
| |
| Nikhil Rajwade 2004-11-16, 2:28 pm |
| Kuba,
Try using
DIRECT=TCP:<MSMQT/MSMQ configured IP Addess>\Private$\<QueueName
instead of DIRECT=OS . We are using Direct=tcp.
I dont think its an MSMQ problem (it either completely works or it dead
doesnt! you seem to have a problem half way down the line).
"Kuba Gregorski" wrote:
> See inline comments.
>
> "Nikhil Rajwade" <Nikhil Rajwade@discussions.microsoft.com> wrote in message
> news:D778FACB-EFC4-4AA5-A102-A0AB3C64B870@microsoft.com...
>
> MSMQ had been installed on the machine before I installed Biztalk.
> During biztalk configuration I chose 'Bind to this IP only' and set it to IP
> A.
> After installing Biztalk I added HKLM\Software\Microsoft\MSMQ\Parameters
> BindInterfaceIP
> with IP B. Needless to say machine reboot followed.
>
>
> Yes. As described above.
>
>
> Done that :-)
>
>
> Thank you very much for your answer, unfortunately it seems that this didn't
> solve my problem.
> Do you think reinstalling MSMQ (not MSMQT/Biztalk - done it a couple of
> times) could help? I think I haven't tried this one yet.
>
> Thanks again for help!
>
> Kuba
>
>
>
>
| |
| Nikhil Rajwade 2004-11-16, 2:28 pm |
| I was able to reproduce the problem if I use Direct=OS. I think thats because
in a side by side installation a machine name is ambigious since the MSMQ(T)
services are bound to IP addresses. Using Direct=TCP the problem seems to be
solved as a specific (IP bound) MSMQ(T) implementation is being addressed.
Hope this solves it for you as well.
Regards
"Nikhil Rajwade" wrote:
[vbcol=seagreen]
> Kuba,
> Try using
> DIRECT=TCP:<MSMQT/MSMQ configured IP Addess>\Private$\<QueueName
> instead of DIRECT=OS . We are using Direct=tcp.
>
> I dont think its an MSMQ problem (it either completely works or it dead
> doesnt! you seem to have a problem half way down the line).
>
>
> "Kuba Gregorski" wrote:
>
| |
| Kuba Gregorski 2004-11-17, 2:46 am |
| Hi!
Thank you very much for your help!
Unfortunately changing to DIRECT=TCP: didn't solve it. The first 7 messages
went through like a breeze;
however, all the following stayed in Biztalk with status 'Delivered' - which
is the same problem I had with DIRECT=OS:.
I think there is some intereference with MSMQ and MSMQT since, as I
mentioned in my previous post, when I turn off MSMQ
MSMQT works fine.
Do you think the fact that I had MSMQ installed before Biztalk installation
could cause this error?
Did you on your machine install MSMQ before or after Biztalk?
Once again thank you for your help!
Kuba
"Nikhil Rajwade" <NikhilRajwade@discussions.microsoft.com> wrote in message
news:64DF7679-3C7D-43EE-8789-6EDCAFF665FD@microsoft.com...[vbcol=seagreen]
>I was able to reproduce the problem if I use Direct=OS. I think thats
>because
> in a side by side installation a machine name is ambigious since the
> MSMQ(T)
> services are bound to IP addresses. Using Direct=TCP the problem seems to
> be
> solved as a specific (IP bound) MSMQ(T) implementation is being addressed.
>
> Hope this solves it for you as well.
> Regards
>
> "Nikhil Rajwade" wrote:
>
| |
| Nikhil Rajwade 2004-11-17, 7:47 am |
| Kuba,
Sorry to hear that the solution didnt work. Thats funny coz if I use
Direct=OS I can reproduce your problem! And it seems to go away with the TCP
formatName.
We installed MSMQ after we installed Biztalk. Our deployment team does
standard builds only (the buggers) and on biztalk 2004 systems MSMQ is not
part of our standard build.
Have you opened an incident with Microsoft PSS?
Regards,
Nikhil
"Kuba Gregorski" wrote:
> Hi!
> Thank you very much for your help!
> Unfortunately changing to DIRECT=TCP: didn't solve it. The first 7 messages
> went through like a breeze;
> however, all the following stayed in Biztalk with status 'Delivered' - which
> is the same problem I had with DIRECT=OS:.
>
> I think there is some intereference with MSMQ and MSMQT since, as I
> mentioned in my previous post, when I turn off MSMQ
> MSMQT works fine.
>
> Do you think the fact that I had MSMQ installed before Biztalk installation
> could cause this error?
> Did you on your machine install MSMQ before or after Biztalk?
>
> Once again thank you for your help!
>
> Kuba
>
>
> "Nikhil Rajwade" <NikhilRajwade@discussions.microsoft.com> wrote in message
> news:64DF7679-3C7D-43EE-8789-6EDCAFF665FD@microsoft.com...
>
>
>
| |
| Kuba Gregorski 2004-11-17, 7:47 am |
| Nikhil,
Not yet. I decided to search for the answers first on the newsgroup.
I'll try to uninstall MSMQ, reinstall biztalk and put MSMQ back on. If this
doesn't help I will open a case.
Thank you for your help!
LP,
Kuba
"Nikhil Rajwade" <NikhilRajwade@discussions.microsoft.com> wrote in message
news:522AE174-3CE8-4D77-A6CB-FD2C263EA74E@microsoft.com...[vbcol=seagreen]
> Kuba,
> Sorry to hear that the solution didnt work. Thats funny coz if I use
> Direct=OS I can reproduce your problem! And it seems to go away with the
> TCP
> formatName.
>
> We installed MSMQ after we installed Biztalk. Our deployment team does
> standard builds only (the buggers) and on biztalk 2004 systems MSMQ is not
> part of our standard build.
>
> Have you opened an incident with Microsoft PSS?
>
> Regards,
> Nikhil
>
> "Kuba Gregorski" wrote:
>
| |
| Yoel Arnon 2004-11-24, 2:47 am |
| There was a posting from March 15 at microsoft.public.biztalk.admin, By
Kevin Tusler. It seems to contain everything you need for side by side
configuration.
Reading this post, I assume that your problem is not having a complete
separation between MSMQ and MSMQT. They need to have different network names
and different IP addresses, and you must make sure that no DNS query on one
name returns the other IP address.
---- Copy of the March 15 posting ----
It is now in the BTS 2004 help file. Included below.
MSMQT and Microsoft Message Queuing (also known as MSMQ) can be installed
side-by-side. Use the following guidelines to ensure a successful
side-by-side installation:
Note Side-by-side is not a mainline mode for BizTalk Server, it is a
feature for niche cases. For server consolidation purposes, it is strongly
recommended that you use virtualization software instead of installing
side-by-side.
To install Microsoft Message Queuing and BizTalk Message Queuing
side-by-side
Ensure that your operating system supports side-by-side installation. Only
Windows 2003 Server™, Windows 2000 Service Pack 4, and Windows XP Service
Pack 2 support side-by-side installation.
You will need two IP addresses on every computer that will run BizTalk
Message Queuing and Microsoft Message Queuing side-by-side. You can install
two network adapters on these computers or add two static IPs on the same
network interface card. If you choose the second option, both addresses
must be in the same subnet. Microsoft Message Queuing will use the first IP
and BizTalk Message Queuing will use the second IP.
You will need a new, unused computer name. BizTalk Server will use the
computer name "BizTalk" to store the BizTalk Message Queuing configuration.
You can append "MSMQT" to your computer name to get an unused computer
name.
For practical purposes, assume that your computer name is MyServer and
BizTalk Server will use MyServerMSMQT.
Ask your network administrator to configure the DNS so that any query for
MyServer will always return IP1 and a query for MyServerMSMQT will always
return IP2. You can achieve this by disabling DNS registration on your
computers and manually adding entries in the DNS tables.
Important If a query for MyServer returns both IP1 and IP2, messages sent
to Microsoft Message Queuing might end up in BizTalk/MSMQT queues.
Test the DNS configuration. At the Command Prompt, type nslookup, and press
Enter.
At the Command Prompt, type MyServer and verify that the system only
returns IP1.
At the Command Prompt, type MyServerMSMQT, and verify that the system only
returns IP2.
Install Microsoft Message Queuing.
Configure Microsoft Message Queuing for side-by-side use. Using the
Registry Editor, browse to
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MS
MQ\Parameters. Add a new string
value called BindInterfaceIP, set its value to IP1, and then restart the
Microsoft Message Queuing service.
Install BizTalk Server. In the Configuration Framework MSMQT screen, set
the IP field to IP2. Set the Computer name to MyServerMSMQT. If you plan to
use PUBLIC or PRIVATE format names, select the Active Directory box. Do not
check the Register in dns box unless advised so by the network
administrator.
Side-by-side limitations
Communication between MyServer and MyServerMSMQT is only possible with the
PRIVATE/PUBLIC format names. BizTalk Server does not support DIRECT format
names. There are no restrictions when a third party communicates with
Microsoft Message Queuing or MSMQT.
Note BizTalk Server 2004 does not support the Microsoft Message Queuing
API. To run applications written with the Microsoft Message Queuing API,
you must have Microsoft Message Queuing and BizTalk Server 2004 installed
on the same computer.----------- Copy Ended ----------Hope that helps,Yoel
Arnonyoel@msmq.biz"Kuba Gregorski" <gregorsk_REMOVE---ME_@poczta.fm> wrote
in message news:%237CfEJJzEHA.2752@TK2MSFTNGP11.phx.gbl...
> Nikhil,
> Not yet. I decided to search for the answers first on the newsgroup.
> I'll try to uninstall MSMQ, reinstall biztalk and put MSMQ back on. If
> this doesn't help I will open a case.
>
> Thank you for your help!
>
> LP,
> Kuba
>
>
> "Nikhil Rajwade" <NikhilRajwade@discussions.microsoft.com> wrote in
> message news:522AE174-3CE8-4D77-A6CB-FD2C263EA74E@microsoft.com...
>
>
|
|
|
|
|