Forum Replies Created
-
AuthorPosts
-
October 13, 2008 at 9:41 PM in reply to: Biztalk Server 2006 R2 Compatibility with Developer Edition with Visual studio 2005 and 2008 Professional editions #20969
Hi Nick,
Thanks for your help.
Regards,
V-DAK,
Anon,
Unfortunately, its quite hard to calculate the size of the BizTalk tracking database (the BizTalkDTADb database) without some historical data.
The size of the tracked data will depend on the size of the messages your environment will process and the ‘amount’ of tracking you have enabled (i.e. on both the send ports or receive ports, or both). I would recommend running for a week with you tracking options and using this size as an average for the coming weeks and months.
Don’t forget that you can manage the tracking database using the DTA Archive and Purge SQL Agent job (see http://www.microsoft.com/technet/prodtechnol/biztalk/biztalk2004/planning/archiving.mspx – BizTalk 2004 SP1 orientated, but gives an excellent overview of the process); I also have a write up on using the purge only job on my blog at: http://www.modhul.com/2008/04/13/why-archive-and-purge-when-you-can-just-purge/ and truncating the database if it becomes too big: http://www.modhul.com/2008/04/10/truncating-the-biztalk-2006-tracking-database/)
Hope this helps,
Rgds, Nick.
Razi,
There is a good overview of the installation process at http://sujant.spaces.live.com/blog/cns!61B9CE11DC9962C3!258.entry, along with links to the various installers for the Oracle WCF Adapter.
Rgds, Nick.
October 13, 2008 at 8:13 AM in reply to: Biztalk Server 2006 R2 Compatibility with Developer Edition with Visual studio 2005 and 2008 Professional editions #20964V-DAK,
BizTalk 2006 R2 is compatible with all editions of Visual Studio 2005 (with the exception of Express Edition I believe).
It is not compatible with Visual Studio 2008 – this is coming with BizTalk 2009.
Rgds, Nick.
October 13, 2008 at 1:42 AM in reply to: Could not access the SSO database when configure Biztalk Runtime #20961“I think that’s because OS were coloned on these 2 servers.”
That probably would be the problem, yes…!
Nick.
I would personally go with XPath in an orchestration, as loading an external assembly will incur additional overhead and I personally don’t like to manage additional assemblies if I can help it. This approach however is technically valid.
Nick.
Seems like a good approach to me.
October 12, 2008 at 5:29 AM in reply to: Could not access the SSO database when configure Biztalk Runtime #20958Thanks for your reply, Nickh!
I tried almost all the modification on MSDTC(Actually a lot of others) and DTCPing shows fine. But error still.
So I have to reinstall MSDTC on both servers. Worked!
I think that’s because OS were coloned on these 2 servers.
In addition, we’d better reinstall MSDTC strictly per http://support.microsoft.com/kb/279786
Before ripping out MSMQ and trying to replace it with something else; have you actually dug in and check to see that the delay is indeed happening in MSMQ and/or the MSMQ Adapter?
There are a lot of reasons that response time could be happening:
It might be that the adapter is not polling the queues as often.
It might be that you have network problems that are delaying message delivery (in which case fixing the network is the right option)
It might be that your biztalk hosts are too busy to give the adapter the right number of threads or processing time it needs; in which case sometimes just moving the locations/ports to separate hosts might do the trick or maybe it’s time to get a new server.
Might be that BizTalk isn’t processing the messages (orchestrations or whatever) fast enough. It might just be that the Host/Engine message polling frequency might need to be adjusted. It might be messages getting stuck on the message box before getting sent out because of other issues.
In other words, it’s important to determine the root cause of the delay before just ripping MSMQ out 🙂
October 10, 2008 at 12:49 PM in reply to: Error : The message found multiple request response subscriptions. A message can only be routed to a single request response subscription #20955In your Biztalk 2006 Administration console do you have Biztalk Application1, can you check if you have the same schema there also. It happened to me few times.If yes, delete from there.. and you should be good to go
I receieved such kind of messages almost 50 times from the time I started with Biztalk. But each a different solution worked..
Here are the options:
1) In your send ports .. Under Filters try BTS.ReceivePortName = [YourReceivePortName]
2) Terminate all the running and suspended instances
3) Restart the host instance.
4) Check the Queue name.That helped me lot of times
5) Try to delete evreything and try redoing it.. may you are doing something wrong if you are a beginner.. That helped me as I am a beginner myself.
MQAdapter Problem…
I am passing a message to MQseries by setting up MQSeries.Msg-ID and MQSeries.Coor_id. The message is placed on queue and i am trying to consume same message within the same orchestration using diffrent receive port i could able to consume the message but the message is not moved to my out folder.
I get an error…
Event Type: Error
Event Source: BizTalk Server 2006
Event Category: BizTalk Server 2006
Event ID: 5778
Date: 10/10/2008
Time: 10:44:30 AM
User: N/A
Computer: XXXXXXX
Description:
The Messaging engine failed to process a message submitted by adapter:MQSeries Source xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx. Details:The published message could not be routed because no subscribers were found. This error occurs if the subscribing orchestration or send port has not been enlisted, or if some of the message properties necessary for subscription evaluation have not been promoted. Please use the Biztalk Administration console to troubleshoot this failure.Please help me as i need to meet the dead line…..
HI I am also facing the same can you please help me here…
I am passing a message to MQseries by setting up MQSeries.Msg-ID and MQSeries.Coor_id. The message is placed on queue and i am trying to consume same message within the same orchestration using diffrent receive port i could able to consume the message but the message is not moved to my out folder.
I get an error…
Event Type: Error
Event Source: BizTalk Server 2006
Event Category: BizTalk Server 2006
Event ID: 5778
Date: 10/10/2008
Time: 10:44:30 AM
User: N/A
Computer: XXXXXXX
Description:
The Messaging engine failed to process a message submitted by adapter:MQSeries Source URL:MQS://198.238.39.12/TQM/OFM.TQM.GCLM.PORTAL.TESTING. Details:The published message could not be routed because no subscribers were found. This error occurs if the subscribing orchestration or send port has not been enlisted, or if some of the message properties necessary for subscription evaluation have not been promoted. Please use the Biztalk Administration console to troubleshoot this failure.Please help me as i need to meet the dead line…..
October 10, 2008 at 11:01 AM in reply to: Using wright correlation in asynchronous mode in BizTalk + MQSeries. #20949HI I am also facing the same can you please help me here…
I am passing a message to MQseries by setting up MQSeries.Msg-ID and MQSeries.Coor_id. The message is placed on queue and i am trying to consume same message within the same orchestration using diffrent receive port i could able to consume the message but the message is not moved to my out folder.
I get an error…
Event Type: Error
Event Source: BizTalk Server 2006
Event Category: BizTalk Server 2006
Event ID: 5778
Date: 10/10/2008
Time: 10:44:30 AM
User: N/A
Computer: XXXXXXX
Description:
The Messaging engine failed to process a message submitted by adapter:MQSeries Source URL:MQS://198.238.39.12/TQM/OFM.TQM.GCLM.PORTAL.TESTING. Details:The published message could not be routed because no subscribers were found. This error occurs if the subscribing orchestration or send port has not been enlisted, or if some of the message properties necessary for subscription evaluation have not been promoted. Please use the Biztalk Administration console to troubleshoot this failure.Please help me as i need to meet the dead line…..
Thanks for the reply, both of you.
According to one my collegue’s suggestion, I created a C# library and in that library I get the Header and Body as it is a SoapMessage. Deserialized the Header. Body is available with GetBodyObject of the SoapEnvelope and then.. called the library from Orchestration.
What do you guys think about this approach.. Please let me know if you see any negatives.
Thanks,
-
AuthorPosts