Add Scrip Map error in IIS 7

Error:

The specified module required by this handler is not in the modules list. If you are adding a script map handler mapping, the IsapiModule or the CgiModule must be in the modules list.

Background:

I had this error message when configuring BTSHTTPReceive.dll into Handler Mappings  of IIS 7 in my development machine.

Solution:

Windows 7 64 bit:

1. Go to the “Control Pannel” –> “Programs and Features”
2. Click on “Turn Windows features on or off”
3. Make sure “Application Development Features” are enabled.

Enterprise Single Sign-On Service Error:0x80131700

ESSO service cannot start and giving  error message,

Windows could not start the Enterprise Single Sign-On Service service on 
Local Computer.
Error 0x80131700: 0x80131700 

This is happens after installing .net 4.0 framework. This is known known issue and there is a hotfix to install.

The URL* is, Update for Microsoft Enterprise Single Sign-On v4 (KB2252691)

---

* last access: 2011-10-31 11:45AM

For more details
http://support.microsoft.com/kb/2252691

BizTalk 2010 EDI : Parties/Party Migration

Parities cannot be directly migrated from order version to BizTalk 2010. Because,  Trading Partner Management (TPM) has been re-engineered in BizTalk 2010. You have to use BizTalk Server Party Migration Tool.

Party Creation in 2010 is more logical & practical than 2006 R2.

New changes are:

1. We have to create a party (Trading Partner) along with a business profile. Business Profile is analogue to the business divisions in an organization where can have multiple. Each business profiles define parameters for B2B messaging like identifiers, Encoding formats, Protocol  settings.
    
   Figure 1
2. In order to do B2B messaging, we have to define agreement(s) between trading partners. This is very easy to use and understand. 
   
   Figure 2
   
   As of Figure 2, once you select the second party (number 3 in the picture)  two more tabs on the dialog (number 6) where you defines the interchange and transaction set settings based on the protocol selected. 
   
   If you have created protocol settings when creating party, you can select them or leave      –None- to override them. (number 5)

BizTalk 2010 Error: Schema referenced by Map ‘<map name>’ has been deleted.

When my BizTalk 2006 R2 applications going to be migrated to BizTalk 2010, I did test run on my test server( BizTalk 2010 on Windows 2008R2 64bit).

Then I choose one of simple live-running application to test with, and I got following error in BizTalk administration console.

TITLE: BizTalk Server Administration
------------------------------ 
Schema referenced by Map 'Map name goes here' has been deleted. The 
local, cached version of the BizTalk Server group configuration is out of date. 
You must refresh the BizTalk Server group configuration before making further 
changes. (Microsoft.BizTalk.Administration.SnapIn) 
For help, click: http://go.microsoft.com/fwlink/?LinkId=47400&ProdName=Microsoft+BizTalk+Server+2010&ProdVer=3.9.469.0&EvtSrc=Microsoft.BizTalk.ExplorerOM.Resources&EvtID=IDS_ERR_FIND_SCHEMA 

This is yet another message from BizTalk with no help at all.  I could not be able to refresh whole BizTalk Group\Applications Node in the BizTalk Administration console. I spent couple of hours ,while scratching my head, to find a solution.

Solutions like, restarting BizTalk service, Administration console, etc did not work. But I found solution (not my own) which is really works though it is not recommended.

The solution is SQL,

   1:  

   2: -- Run bellow queries against BizTalkMgmtDb database.

   3: -- You can find the related item here

   4: SELECT * FROM bt_mapspec

   5: -- Replace with correct itemid value

   6: DELETE FROM bt_mapspec WHERE itemid =165 

Reason:

One of blog post suggests, it could be the reason when the Map and references Schemas are in separate assemblies. I can agree with it, i believe , in this application the map and its source schema in two separate assemblies.

PowerShell Error: the execution of scripts is disabled on this system

When you run powershell scripts (.pl1), in Windows PowerShell console you may received following error.

 

 

File C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management 
Portal\Install\Scripts\Management_Install.ps1 cannot
be loaded because the 
execution of scripts is disabled on this system. Please see "get-help 
about_signing" for more de
tails.
At line:1 char:25
+ 
.\Management_Install.ps1 <;;;<<< 1
 + 
CategoryInfo : 
NotSpecified: (:) [], PSSecurityException
 + 
FullyQualifiedErrorId : RuntimeException 

To fix this, run following command, in the console

set-executionpolicy unrestricted

On 64bit version of Windows 2008R2, also make sure to set this command for 64bit  PowertShell, which can be found in C:\Windows\SysWOW64\WindowsPowerShell\v1.0 

After you done, it is recommended to revert the setting by using

set-executionpolicy restricted

        OR

set-executionpolicy default

Windows Could Not Start Enterprise Single Sign-On Service

In Windows 7 development machine, suddenly I got following error  when starting the ESSO service.

Windows could not start the Enterprise Single Sign-On Service service on Local Computer Error 0x80131700: 0x80131700

If check the windows event viewer, we can see,

Could not create SSOSQL. To fix the problem, reinstall SSO or try 'regasm SSOSQL.dll' from a Visual Studio command prompt.
Error Code: 0x80131700

I ran “regasm” and it is worked.

Brandix B2B (EDI) Implementation

This project was totally new to me. I knew about EDI, but no experiences in the past. But I took the challenge and did our own researches over 2 months and implemented within 6 months. We used Microsoft BizTalk Server 2006 R2 to implement this.

Abstract of the project

Our(Brandix*) one of leading buyer(Mark And Spencer) wanted to implement Business-to-Business (B2B) application with us.So that they can raise their purchase orders and receive invoices electronically. Within 48 hours we will receive invoices status,E.g. Invoice Processing Successful, automatically. 

Architecture

• Download Purchase Orders

1. Buyer raises the purchase order through a trading partner.
2. Our EDI system subscribes that PO.
3. Process in BizTalk server and immediately send email notification to the relevant merchandiser.
   

• Upload Invoices

1. Invoices been processed from our logistic system and upload them to the EDI system (BizTalk server/SQL server)
2. Make the EDI file based on the given EDI specification inside the BizTalk server.
3. Upload to the trading partner.
   

Props & Cons

1. Implementation cost is bit higher
2. Reduce paper works
3. Minimal data entry, hence time saving 
4. Seamless business process

 

---

* Brandix is the FIRST Sri Lankan company using Ms-BizTalk server for B2B integration in Sri Lanka.

BizTalk Event Log error: The source was not found, but some or all event logs could not be searched.

My BizTalk development machine runs on Windows 7. In an orchestration I've wrote
System.Diagnostics.EventLog.WriteEntry("Payment Automation","Instantiated the Process Engine");

When it runs, i can see following error in the event log. But I wont get this in Windows 2003 R2 server.

Figure 1: Windows Event Log

Event Type: Error
Event Source: XLANG/s
Event Category: None
Event ID: 10034
Date:  8/26/2010
Time:  9:27:29 AM
User:  N/A
Computer: 
Description:
Uncaught exception (see the 'inner exception' below) has suspended an instance of service 'Brandix.EAI.Orchestration.PaymentAutomation.BrandixPaymentAutomation(7e9e7bc9-558e-8988-7478-6552f648a021)'.
The service instance will remain suspended until administratively resumed or terminated. 
If resumed the instance will continue from its last persisted state and may re-throw the same unexpected exception.
InstanceId: b4472198-88f8-458f-aee3-aaa272d327ee
Shape name: Event Log Entry
ShapeId: 33391213-fc37-4d3a-91d7-f5f7bd50b667
Exception thrown from: segment 3, progress 3
Inner exception: The source was not found, but some or all event logs could not be searched.  Inaccessible logs: Security.
        
Exception type: SecurityException
Source: System
Target Site: Microsoft.Win32.RegistryKey FindSourceRegistration(System.String, System.String, Boolean)
The following is a stack trace that identifies the location where the exception occured

To avoid this error we have to do following steps.

1. Run RegEdit.exe
2. Expand hives to the level of following
   Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\EventLog\Application
3. Insert a new key to the Application hive, in this case "Payment Automation"
4. Insert a new String Value called "EventMessageFile" under the "Payment Automation"
5. Double click on "EventMessageFile" set Value Data as "C:\Windows\Microsoft.NET\Framework\v2.0.50727\EventLogMessages.dll"

Final windows registry editor will look like this,

Figure 2: Windows Registry Editor

How to create Biztalk schema from FOR XML EXPLICIT

It's very straightforward to create Biztalk schema for SQL adapter if we use FOR XML AUTO. But we'll come across that FOR XML AUTO is not enough to get data from SQL, so that we use FOR XML EXPLICIT. In this case we have to follow some additional things to get biztalk schema generated properly. I''l go step-by-step with an example. This situation really came to me that's why I motivated to do this post.

1. Assume my SP,BIZTK_GetPPS300Attributes @pono, will generates required XML data set with FOR XML EXPLICIT.


2. Open Visual Studio and switch to Biztalk Explorer.
   Create a Receive Port.
   Create a Receive Location for that port and set following properties
   
   Set Address(URI) property as following
   
   Value of Document Root Element Name will be Root Element of schema.
   Document Target Namespace will be schema's target namespace
   For this example SQL Command will be exe BIZTK_GetPPS300Attributes 12345
   


3. Create a send port and set following properties
   


4. Enable Receive Location and start Send port by right clicking on them.


5. Now receive location will execute SQL command that you set and save the XML file in the location where you set in step 3. At this stage we dont want to validate against schema so that we set send/receive pipe line to PassThru.


6. Go to your biztalk project, select Generated Schemas option from Add Generated Items dialog box, give the XML file just you created.


7. Cool. Biztalk schema is properly generated.