See this post at Word Press. https://wp.me/p9KCCP-m

See this post at Word Press. https://wp.me/p9KCCP-2f

Server: Windows Server 2012 IIS: Version 8.0.9200.16384 Issue: Trying to browse a WCF service which is running in Application Pool 4.0 Classic. Resolution: The error occurs if correct version of .net is not mapped with the *.svc extension in the IIS Handler Mappings. Ensure the right version of .net is mapped with the *.svc extension. Click on the Web Site and click on Handler Mappings: Add the following maps if missing Try to restart IIS and then browse the service.  The above steps helped me to resolve the issue.

Verify the following key elements are correctly setup in your BizTalk Server. 1. Open Services window and verify the service named “BizTalk ESB Exception Notification” is “Started”.  In my case even though the service is configured to start Automatic but it never started.  I had to start it manually. 2. If the following error occurred then search for the xslt file in your “C:\Program Files” folder.  It was found under C:\Program Files\Microsoft BizTalk ESB Toolkit 2.0\Exception Notification Service\ then copy it to 'C:\Program Files\Microsoft ESB Guidance Exception Notification Service 1.0 - November 2007\.  Create the folder if not already present. Error: The XSLT file for creating rich HTML email could not be found in the following location, 'C:\Program Files\Microsoft ESB Guidance Exception Notification Service 1.0 - November 2007\EmailTransformation.xslt'. The subscriber should start getting emails now.

The WCF-SQL Adapter allows generating schema using Stored Procedure via 2 different ways. 1. “Add Generated Items”.”Add Adapter Metadata” 2. “Add Generated Items”.”Consume Adapter Service” Both options produce different results and I’ll walkthrough both options and will mention the differences. Generate Schema Using “Add Adapter Metadata” Right click on BizTalk Project and select “Add Generated Items” Select “WCF-SQL” and click Next Click “Next” and it will display the following window “Consume Adapter Service” a. Select binding “sqlBinding” b. Configure the URI: “mssql://<servername>//<databasename> a. For example“mssql://localhost//GlobalBankESB” c. Select a category: Notice, the list contains “Procedures” and “Strongly Typed Procedures” If “Procedures” is chosen then the following artifacts will be generated: 1. BizTalk Orchestration.odx 2. sqlBinding_dbo.xsd 3. sqlBinding_System_x2eData.xsd 4. What each artifact is used for? 1....

http://www.marcusoft.net/2008/04/wcf-wsdl-configurations-explained.html I copied the following information from the above link for quick reference. OK - after an intensive coding session i can now proudly say that I understand 4 attributes of the WCF configurations (of the 1200 + that exists ;)) The attributes that you should set are: ServiceBehavior.Namespace - this get generated as the targetNamepace in the wsdl (instead of http://tempuri.org/ ). Also you should use this namespace in the endpoint, with the bindingNamespace-attribute in the config-file: <endpoint bindingNamespace=" http://www.marcusoft.net/Services/ " /> ServiceBehavior.ConfigurationName - this is the name that you use as service name in the configuration file: <service name="OffertTjanst" > ServiceBehavior.Name - the name property has solely to do with the generated wsdl-file. It is generated as the Name-attribute in the wsdl-file: <wsdl:definiti...

This error usually occurs if you are using a third party BizTalk Demo or BizTalk Application. You need to change the Server name in the BizTalk application configuration: “WIN2K-2005-PC” is a third party server name which you have to change it to  your local PC name or just change it to word LOCAL as you see in the following snapshot. NOTE: Must change it for both Configuration Settings (Development/Deployment)

Error: Deploying Activity... ERROR: The BAM deployment failed. Encountered error while executing command on SQL Server "000-0001-XX". Incorrect syntax near '@@ServiceName'. Must declare the scalar variable "@@ServiceInstanceId". Must declare the scalar variable "@@ServiceInstanceId". Must declare the scalar variable "@@ServiceInstanceId". Microsoft (R) Business Activity Monitoring Utility Version 3.6.1404.0 Copyright (C) 2006 Microsoft Corporation. All rights reserved. Using 'BAMPrimaryImport' BAM Primary Import database on server 000-0001-XX... Resolution: You BAM Observation Model contains reserve words, ServiceName and ServiceInstanceId. Try changing them.

Let’s say in BizTalk Mapper, the source schema has a string field that contains a valid DateTime value and you want it to map to xs:DataTime field. You may use the following code to convert the string DataTime into xs:DateTime format static string ConvertDateTimeToXSDDateTime() { System.DateTime dateTime = System.DateTime.Now; string dateTime = System.Xml.XmlConvert.ToString( dateTime, System.Xml.XmlDateTimeSerializationMode.RoundtripKind); return dateTime; } Valid XML DateTime looks like this: 2025-06-01T00:00:00 Document Reference: http://msdn.microsoft.com/en-us/library/cc500278.aspx

Technorati Tags: BizTalk , SSO , Enterprise Single Sing-On Assume you have a BizTalk server and a Non-BizTalk server. The BizTalk server has an SSO affiliate application where you have stored some configuration values. Now you want to retrieve the SSO values from your non-BizTalk server. Also assuming you will be running the application as a Windows Service. Note: Perform Step 1, 2, 7 and 8 on non-BizTalk server. Step 1. Install ‘SSO Client Utility’ The SSO Client Utility is located at the following location on your BizTalk Server. Copy the file to your non-BizTalk server and then run it. File Location: (BizTalk Server) C:\Program Files\Common Files\Enterprise Single Sign-On\SSOClientInstall.exe Step 2. Register COM Object (SSOConfigStore.dll) 1. Copy SSOConfigStore.dll from BizTalk Server to non-BizTalk server. BizTalk Server Location: C:\Program Files\Common Files\Enterprise Single Sign-On\ Non-BizTalk Server Location: C:\Program Files\Common Files...

Error: The Messaging Engine failed to add a receive location "RP_ReceiveAcks.NetTcp" with URL "net.tcp://localhost:8994/Domain/Ack" to the adapter "WCF-NetTcp". Reason: "System.ServiceModel.AddressAlreadyInUseException: There is already a listener on IP endpoint 0.0.0.0:8994. Make sure that you are not trying to use this endpoint multiple times in your application and that there are no other applications listening on this endpoint.   Resolution: Make sure no application is listening on the same endpoint If you are using same port number across multiple endpoints, make sure they all run under one host instance.

Error: This operation cannot be completed because the activity instance could not be found. It may not have been persisted in the database yet or may have been already removed Resolution: This error occurs when Parent activity is already closed and you are trying to attach a child activity to the parent activity.

I found a good step-by-step demo on how to implement BAM using TPE (Tracking Profile Editor) at the following address: http://aspalliance.com/840_Business_Activity_Monitoring_BAM_with_BizTalk_Server_2006_from_Start_to_Finish.all In this blog I’ll use the same sample to implement BAM using BAM API.  Prerequisites: 1. Download GenerateTypedBamApi from CodePlex ( http://www.codeplex.com/GenerateTypedBamApi ) 2. Download BAMSolution.zip from the above link. Steps to implement BAM using BAM API: 1. Open BAMSolution.sln and create a new C# Class Library Project 2. Run GenerateTypedBamApi.exe POActivityView.xls POActivityView.cs Orchestration BAMSolution.Example a. POActivityView.xls is BAM Observation Model b. POActivityView.cs is a C# representation of the Observation Model c. Select Event Stream (Orchestration) d. Select Namespace (BAMSolution.Example) 3. Add the following references in your C# project a. C:\Program Files\Microsoft BizTalk Server 2006\Tracki...