BizTalk Related Issues

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 trying to use ChilkatDotNet4 from a BizTalk solution we get the following errror. We are trying to use the 64 bit version. System.IO.FileNotFoundException: Could not load file or assembly 'ChilkatDotNet4.dll' or one of its dependencies. The specified module could not be found. File name: 'ChilkatDotNet4.dll' I am using BizTalk 2010 on Win Server 2008. I found simular problem but not in BizTalk  with solution here.  http://stackoverflow.com/questions/3104988/trouble-registering-chilkatdotnet4-dll-to-the-gac . The solution is however the same: I changed the host from 64 to 32 bit.

I was trying to use the built in HTTPReceive from BizTalk today, byt the IIS server was not configured to hadle the request. I got an access denied error when calling the BTSHTTPReceive.dll. NOTE: You must be logged on as a member of the BizTalk Server Administrator goup I had to configure the IIS server to be able to utillize this functionality. There is a good explenation on how to do this at microsoft . The way to to it is to add this under Handler Mappings Choose Add Script Map,and set: Request Path = BtsHttpReceive.dll Executable = C:\Program Files\Microsoft BizTalk Server 2010\HttpReceive\BTSHTTPReceive.dll Name = BizTalk HTTP Recevie Under Request Restrictions set under the Verbs tag set POST and under the Access tab set Script Then you haver to Create a new roule under ISAPI and CGI Restrictions: Add an new and set ISAPI or CGI path = C:\Program Files\Microsoft BizTalk Server 2010\HttpReceive\BTSHTTPReceive.dll Description = BizTalk HTTP...

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...

From time to time I get the 'HTTP Error 503 - The Service is nnavailable' when I try to access my BAM portal Usually I spend a few minutes before I remember how to get past this. It is the account configured to run bam that needs to have its password updated. Most of you should change yor password on a regular basis, and its easy to forget to reconfigure BAM with the new passord. So.. here is the solution: Open Microsoft BizTalk ServerConfiguratiuon tool and update the password for the user running BAM portal Apply configuration, restart ISS to be sure (iisreset) and voia : BAM portal up and runnign again

I am creating a orch that has filter on the initial receive shape. When building I got these error: Error 1 : identifier 'MySolutionname' does not exist in 'MyOrchName'; are you missing an assembly reference? Error 2: cannot find symbol 'MySolutionname' Error 3: an 'activate' predicate rvalue must be a string, character, boolean or numeric literal Error 4 : illegal 'activate' predicate The solution to this is to put the filter expression in sting literals (i.e. “double quotes”)

I prefer the WebServiceWizard when creating a webSerivce to use with BizTalk. The orchestration is already created so I just choose the orch dll in the wisard. When this is done I add the web service as a existing webService project to the Solution. After some tweeking on namespaces, portnames, SOAPAction, etc. I now have a fully functional WebService that may receive xml files and deliver them to an orchestration. And now the new stuff begins... First of all you have to install wse 3.0. Then you have to add the reference to Microsoft.Web.Service3 to the project. After this I had to restart VS in order to get the new item on the project property --> WSE 3. 0 properties. When this is enabled just rebuild and publish you new WebService, and a section is added in the WSDL describing the mtom attachment.