Forum Replies Created
-
AuthorPosts
-
Hi
I just configured the MQ Agent it worked fine. Also I needed to add users of BizTalk to Distributed COM users.
But problem again, messages are suspended as it is saying messages cannot be recognized by Dissassembler component. I am using XML Pipeline in recieving end from MQ.
Regards
Bhaskar
Hi,
You have to install BizTalk Server on a server box with Windows Server 2008 (assuming that you are referring to version 2009 of BizTalk) running on it. The user account should be an admin domain account.
You would only be installing BizTalk Developer toolkit on a Windows XP workstation for development purpose only (assuming that Visual Studio is already installed on that XP workstation).
Daniel.
Hi Daniel,
Thank you so much for your answer! I have one further question. The operating system of the BizTalk Server is Windows XP SP3 an the system is a member of a domain. Is a standard domain user with local admin privilege enough or is a domain admin user necessary?
Or ist this system not convenient? If your answer is yes, I will install BizTalk on a Windows Server with Active Directory in a Virtual PC.
Thanks for your help in advance.
Thanks for that interesting link Daniel. I marked it in my favorites although I’m not sure it solves my problem.
I’m getting 100’s of Errors in my event viewer. Right now, I’m combing through all Hot Fixes for R2 to see if it’s included in a cumalative Hot Fix.
Thanks!
Hi,
Here’s an explanation from Microsoft about 64-bit support:
http://msdn.microsoft.com/en-us/library/aa560166(BTS.10).aspx
Daniel.
I’m starting to think MS missed this fix for the x64?
February 23, 2010 at 11:30 AM in reply to: BizTalk 2006 compitabilty in MMC with BizTalk 2006 R2 installed on local computer #24278Hi Tord,
See if the following Open Source solution can work for you:
http://biztalkdeployment.codeplex.com/
Daniel.
Hi,
Make sure that the user account you are using to do the configuration process is a domain account with sysadmin privilege on both the (Biztalk) application server and the database server.
Before you do the configuration process, make sure that the following four groups are created on the database server: BizTalk Server Administrators, BizTalk Server Operators, BizTalk Application Users and BizTalk Isolated Host Users. Also, make sure that the domain account you are using is a member of the previously mentioned four groups.
I suggest that you uninstall BizTalk before attempting to do the reinstallation and configuration again.
Daniel.
Oops. Seems it is an exception of type Microsoft.XLANGs.Core.XlangSoapException.
Add this in your ODX, in the catch shape (for some reason it can’t be selected the usual way):
<om:Property Name=”ExceptionType” Value=”Microsoft.XLANGs.Core.XlangSoapException” />
I know this might be a bit too late for you :-). But as a service to others with the same problem:
Add a reference to Microsoft.ServiceModel.Channels and System.ServiceModel in your project.
Now you can catch the Microsoft.ServiceModel.Channels.Common.TargetSystemException and suspend the instance with a nice message.
Hi,
I have not implemented such requirements in a production environment, but you might want to check the following article on guidelines to consume very large messages in BizTalk (it was written for version 2004, but I think it’s still relevant for version 2009):
http://blogs.msdn.com/biztalk_core_engine/archive/2005/02/28/381700.aspx
Also, you might want to look into project “Velocity”, Microsoft’s distributed in-memory application cache for scalability and performance in your scenario.
Daniel.
February 22, 2010 at 1:38 PM in reply to: Is there limitation for using Abstract Classes in BTS Orchestration? #24268Hi Yonathan,
From what I’ve seen and experienced (from BizTalk 2004 through 2006 R2), any custom .NET assembly (invoked from an Orchestration) has been built as standalone classes, not derived classes from an abstract class. I don’t know if this has changed in BizTalk 2009, but I highly doubt it.
Daniel.
Hi
For those who are getting there XML from a stored procedure , they might have used
Select XYZ FROM XYZ FOR XML AUTO, ELEMENTS , XMLDATA
to generate the XML output for the SQL stored procedure to return value
Dont forget to comment XMLDATA in the stored procedure to solve this problem in cause ur using SP
Hi Siva,
It seems to me that this this a scoping definition issue with your variable cfg in your orchestration… Try to define this variable at the orchestration level and see if that fixes your Null Reference Exception errors.
Daniel.
Hi,
BizTalk 2004 already provides a String Concatenate functoid, so I don’t understand why you would want to duplicate that feature creating a custom functoid?!?!?!
Daniel.
-
AuthorPosts