BizTalk Related Issues

One of the easiest ways to update a bam activity from an orchestration is to use the BAM API, Simply add reference to Microsoft.BizTalk.Bam.EventObservartion Microsoft.BizTalk.Bam.XLANGs to your project and you are ready to start. In the basic level you have to start, update and end an activity. Start Activity I reccomend creating variables for activity name and instanceID, To avoid any confutions. The Activity name must match the Activity name created and deployed using bm.exe. (I will create a seperate post for this) The code in start-bam-expression-shape in orchestration PreProcessInvoice will then look something like this: activityName = ("ProcessInvoice"); //this is the activity we are loading data into activityInstance = System.Convert.ToString(System.Guid.NewGuid())+"PreProcessInvoice" ; //if bamming to same activity from different orchestration, we may track where the data is comming from by adding orchestration name. Microsoft.BizTalk.Bam...

I just found an issue in the SQL-Adapter for BizTalk 2006R2. It seems that there are different values for displaying the configuration and for the actual configuration. Here is an image showing how it looks like when you open the SendPort to view the details. Don`t trus this view! Here is the actual configuration for the same SendPort with the actual configuration used runtime. If your bindignfile is not 100% acurate you could end up with different values for displaying the configuration and the actual configuration.  As you can see from the images two different values are in the system, but it is the actual configuration that is used. This may happen if you manually update the bindigfile, but forget to update all the entrys for database/queue information.  I have been told that it is the same for MQ-Adapter and even on the BizTalk 2010, but I have not verifyed this

This is an oldie but goodie. When tryin to deliver data to SQL Server using WCF-SQL on need to be carefull when configuring the sendport. The operation needs to be the same name as used in the orchestration. When adding the action configuration this is how you do it: < BtsActionMapping >              < Operation Name =”THIS NEEDS TO BE THE SAME AS IN THE ORC” Action = “TheAction” \ > < /BtsActionMapping > This is how to do it There is an article at msdn explaining the details here

When opening an existing BizTalk solution from designed and build for BizTalk 2006 in VS 2010 and deploying to BizTalk 2010 I got an odd error.  The solution builds fine but i cannot get it to deploy..  Error 7 Access to the path 'C:\Users\eriei\AppData\Local\Temp\BT\PID13428\BizTalkAssembly\0b2cb3ce88fbfe1e5d4e7cc6158a6fd1\Statoil.BizTalk.Utility.Archive.ContentManager.ControllerTestApplication.dll' is denied. 0 0 When trying to delete the file from this location the error message chagned to  Error 64 Failed to add resource(s). Change requests failed for some resources. BizTalkAssemblyResourceManager failed to complete end type change request. Assembly "C:\Users\AppData\Local\Temp\BT\PID3724\BizTalkAssembly\63870f24efcb5f96ec704df4b0b0e533\KHS.834Membership.BizTalk.Orchestrations.dll" does not appear to be a BizTalk assembly, and cannot be deployed to the Configuration database. If this assembly is referenced by other BizTalk assemblies, it needs to be...