Jonathan Wu's .NET and BizTalk Blog

MCTS in BizTalk 2006

2006-11-21T18:14:00.000-08:00

I passed the MCTS certification exam in BizTalk 2006 today. There were 50 questions and I finished them in 60-70 minutes. I have been programming in BizTalk 2004 and 2006 extensively for a couple years now, as it turned out that I over-prepared for the exam; I should have (probably) passed it just based on my experience. I would have to say the exam questions are relatively easy and not well balanced. Like most of the bloggers pointed out that there are too many BAM and BRE related questions. Moreover, there are too many questions about distinguished/promoted properties.
There is a lack of the core architecture questions on the messaging engine, publishing-subscribing model, orchestrations etc.

I almost felt that those exam authors might be programming heavily in BAM/BRE; they were probably not extremely familiar (or concerned) with the more popular/well-known features in BizTalk like orchestrations, maps, pipelines etc. There're 0 questions about the custom components development which I consider it's a big weakness of the exam. Programming custom components like adapters, pipeline components, functoids, fact retrievers, and BAM interceptors are essential part of the BizTalk framework. The exam didn't cover these areas well.

Another big complaint from me is that MCTS in BizTalk 2006 is not a constituent part of the MCPD certification. From my perspective, it most definitely should be. BizTalk developers must have equally strong .NET programming skills as web / winform developer. Anyway, I hope MSFT would consider this seriously and revise the certification path.

System.Web.Services.Protocols.SoapException: Server was unable to process request. --> Cannot create ActiveX component. EnvDTE

2006-05-20T09:36:00.000-07:00

I got this exception thrown at me when I tried to do the following in the web service:

DTE ideObject = (DTE) Microsoft.VisualBasic.Interaction.CreateObject
(
"VisualStudio.DTE.7.1", ""
);

You may run into the similar problem if you wanted to access native Microsoft objects such as excel or word. There are two solutions:
1) Make sure your aspnet_wp work process runs under a priviledged account that has the sufficient permission to carry out this task. This is usually done through the impersonation in web.config file. You will find plenty of posts explaining how this is achieved.
2) Grant explicit Launch/Activation and Access permission to "Microsoft Visual Studio Solution Object" in DCOM Config.

The following are the steps for option 2):
a) Go to "Start | Settings | Control Panel | Administrative Tools | Components Services".
b) Drill thru "Components Services -> Computers -> My Computer -> DCOM Config"
c) Select "Microsoft Visual Studio Solution Object"
d) Right click and bring up the "Properties"
e) Click on the "Security" Tab
f) In the groupbox "Launch and Activation Permissions"; select "Customize" radio button and click on "Edit" button; check both "Local Launch" and "Local Activation" to grant these permissions to Machine\ASPNET account.
g) In the groupbox "Access Permissions"; repeat step (f) to grant the "Local Access" to Machine\ASPNET account.
h) Click "Apply" to apply the changes.

Here are some screen shots:

Microsoft Visual Studio Solution Object Properties

Launch and Activation Permissions

Access Permissions

StartCache: Error 0x80070002: failed to get download: 90A40409-6000-11D3-8CFE-0150048383C9

2005-11-13T19:22:00.000-08:00

Ran into a HUGE installation problem when I attempted to install SQL Server 2005 RTM on my personal computer. I had SQL Server 2005 Beta CTP installed before. I kept getting the OWC11 installation failure message. I ended up manually install the OWC11 component with logging turned on... The log file tells me it's the infamous : 1603 problem.


Action ended 21:33:45: ProcessComponents. Return value 1.
Action 21:33:45: StartCache. Starting cache of cabinets to local installation source
Action start 21:33:45: StartCache.
StartCache:  Error 0x80070002: failed to get download: 90A40409-6000-11D3-8CFE-0150048383C9
Action ended 21:33:45: StartCache. Return value 3.
Action ended 21:33:45: INSTALL. Return value 3.
Action ended 21:33:45: ExecuteAction. Return value 3.
Action 21:33:45: TheFatalError.
Action start 21:33:45: TheFatalError.

I ended up cleanning two registry keys which finally made it work:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\11.0\Delivery\90A40409-6000-11D3-8CFE-0150048383C9
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Delivery\SourceEngine\Downloads\90A40409-6000-11D3-8CFE-0150048383C9

Hopefully it will help if you run into the same problem.

A Microsoft Distributed Transaction Coordinator problem prevented connection to the Configuration database again

2005-03-07T19:40:00.000-08:00

When you work with a Microsoft BizTalk Server 2004 project on a Microsoft Windows Server 2003-based computer, and you deploy the assemblies to BizTalk Server 2004, you may receive the following error message from Microsoft Visual Studio .NET:


[DeploymentException] Cannot open database BizTalkMgmtDb on server [server]. 
[DeploymentException] Cannot open database BizTalkMgmtDb on server [server]. 
A Microsoft Distributed Transaction Coordinator problem prevented connection to the Configuration database. 
The transaction has already been implicitly or explicitly committed or aborted

You will also receive a similar error if you run the BizTalk Deployment Wizard. KB839187 provided a solution which is pertinent but not sufficient in some scenarios. Recently, I had a new development set up that took me back to this problem and it cost me approximately 2.5 hours of productivity to figure out exactly why.

I have a mutile server BizTalk setup. BizTalk Databases and the default BizTalk host are on a dedicated Windows 2003 server box. I do my development work on laptop with Windows XP (SP2). When I try to deploy a BizTalk assembly, I ran into the problem described above. I immediately tried the workaround suggested by KB839187 which didn't work. After some research, I belive the following steps are a better overall approach to this problem.

Make sure your development machine and BizTalk server (server runs BizTalk databases) can ping each other

Make sure MS DTC service is up and running on both computers

Modify the following registry key on both computers: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\TurnOffRpcSecurity = 1

Enable the "Network Clients" for MS DTC for both computers. To do this:
- Click through: Start | Settings | Control Panel | Administrative Tools | Component Services
- Expand "Computers" under "Component Services" node
- Right click on "My Computer" and click on "MSDTC" tab on "My Computer Properties" dialog
- Click on "Security Configuration" button
- For Windows Server 2003, check "Network Clients" checkbox as indicated in the following picture.
  
  For Windows XP (SP2), configure the "Security Settings" as indicated by the following picture.
Restart the MS DTC services on both computers if they have not been automatically restarted.

Themize Windows Application

2005-02-18T10:13:00.000-08:00

I am thinking about writing an article about how to themize the windows forms by using a cascading style sheet. I have a subset of functionality implemented. Here's a form that applied a nice theme called "VRust".

How to use updategram to update multiple rows in BizTalk orchestration

2005-02-17T16:50:00.000-08:00

Using the updategram to insert and delete are very straightforward. It's also easy to update one row of data using the updategram in BizTalk. BizTalk SQL adapter seems to be problematic when dealing with updating multiple rows of data using updategram. SQL XML states that you need to use the attribute "updg:id" to associate the records enclosed in the <updg:before> and those enclosed in <updg:after>(article here). I am pretty sure if you are reading this blog, you have tried the default schema generated by BizTalk and realized it didn't work. I have tried the following two approaches and they didn't work:

Use multiple <sync> nodes to describe the updategram. It didn't work.


<?xml version="1.0" encoding="utf-8" ?> 
<ns0:updateStatsPendingRequest xmlns:ns0="http://www.bankofamerica.com/">
 <ns0:sync>
  <ns0:before>
   <ns0:StatsPending APPLICATIONID="100010.032970" /> 
  </ns0:before>
  <ns0:after>
   <ns0:StatsPending APPLICATIONID="100010.032970" 
     SITEID="24" ASSIGNPROCESSED="true" /> 
  </ns0:after>
 </ns0:sync>
 <ns0:sync>
  <ns0:before>
   <ns0:StatsPending APPLICATIONID="100010.032971" /> 
  </ns0:before>
  <ns0:after>
   <ns0:StatsPending APPLICATIONID="100010.032971" 
     SITEID="25" ASSIGNPROCESSED="true" /> 
  </ns0:after>
 </ns0:sync>
</ns0:updateStatsPendingRequest>

Conclusion: SQL Adapter has difficulty handling multiple <sync> elements.

Use the <id> attributed as suggested by SQL XML. I added the extra id attribute into the schema like this:


<xs:attribute name="id" type="xs:string" updategram:Prefix="updg" />

This solution fails since the generated xml document instance doesn't have the correct xml schema prefix. As described by SQL XML, the prefix for the "id", "sync", "before" and "after" should really be "updg". However, the xml instance generated by BizTalk will look like:


<?xml version="1.0" encoding="utf-8" ?> 
<ns0:updateStatsPendingReq xmlns:ns0="http://www.bankofamerica.com/">
 <ns0:sync>
  <ns0:before>
   <ns0:StatsPending ns0:id="100010.040649" /> 
   <ns0:StatsPending ns0:id="100010.042313" /> 
  </ns0:before>
  <ns0:after>
   <ns0:StatsPending ns0:id="100010.040649" 
                     ns0:APPLICATIONID="100010.040649" 
                     ns0:SITEID="24" 
                     ns0:ASSIGNPROCESSED="1" /> 
   <ns0:StatsPending ns0:id="100010.042313" 
                     ns0:APPLICATIONID="100010.042313" 
                     ns0:SITEID="24" 
                     ns0:ASSIGNPROCESSED="1" /> 
  </ns0:after>
 </ns0:sync>
</ns0:updateStatsPendingReq>

As you can see from the above xml instance, all of the elements and attributes are qualified with "ns0" prefix which is not what we wanted. After some research, I figured out that SQL XML need to use the "updg" prefix in order to correctly associate the records in <before> and <after> blocks. Therefore, we need to make the BizTalk to generate the document instance looks like this:


<?xml version="1.0" encoding="utf-8" ?> 
<ns0:updateStatsPendingReq 
  xmlns:updg="urn:schemas-microsoft-com:xml-updategram" 
  xmlns:ns0="http://www.bankofamerica.com/">
 <ns0:sync>
  <ns0:before>
   <ns0:StatsPending updg:id="100010.040649" /> 
   <ns0:StatsPending updg:id="100010.042313" /> 
  </ns0:before>
  <ns0:after>
   <ns0:StatsPending updg:id="100010.040649" 
                     ns0:APPLICATIONID="100010.040649" 
                     ns0:SITEID="24" 
                     ns0:ASSIGNPROCESSED="1" /> 
   <ns0:StatsPending updg:id="100010.042313" 
                     ns0:APPLICATIONID="100010.042313" 
                     ns0:SITEID="24" 
                     ns0:ASSIGNPROCESSED="1" /> 
  </ns0:after>
 </ns0:sync>
</ns0:updateStatsPendingReq>

After I tweak the schemas to generate the xml instance like above, it worked!!
If you run the SQL profiler, you will see the following TSQL statements are generated:


SET XACT_ABORT ON
BEGIN TRAN
DECLARE @eip INT, @r__ int, @e__ int
SET @eip = 0

UPDATE StatsPending SET SITEID=N'24', ASSIGNPROCESSED=N'1' 
WHERE (APPLICATIONID=N'100010.042313');  
SELECT @e__ = @@ERROR, @r__ = @@ROWCOUNT
 IF (@e__ != 0 OR @r__ != 1) SET @eip = 1
 IF (@r__ > 1) RAISERROR ( N'Ambiguous update, unique identifier required', 16, 1)
 ELSE IF (@r__ < 1) RAISERROR ( N'Empty update, no updatable rows found', 16, 1)

UPDATE StatsPending SET SITEID=N'24', ASSIGNPROCESSED=N'1' 
WHERE (APPLICATIONID=N'100010.040649');  
SELECT @e__ = @@ERROR, @r__ = @@ROWCOUNT
 IF (@e__ != 0 OR @r__ != 1) SET @eip = 1
 IF (@r__ > 1) RAISERROR ( N'Ambiguous update, unique identifier required', 16, 1)
 ELSE IF (@r__ < 1) RAISERROR ( N'Empty update, no updatable rows found', 16, 1)

IF (@eip != 0) ROLLBACK ELSE COMMIT
SET XACT_ABORT OFF

The following are list of things you need to do in order to ask BizTalk to generate the "updg" prefix.

Define Updategram.xsd like this:

In your updategram schema's <xs:schema> element, add this line:
```
xmlns:updg="urn:schemas-microsoft-com:xml-updategram"
```

Add an <xs:import> element in your updategram schema:


<xs:import
  schemaLocation="Updategram.xsd"
  namespace="urn:schemas-microsoft-com:xml-updategram" />

Add <updg:id> attribute in <before> and <after> elements by using the following line:


<xs:attribute ref="updg:id" />

Your schema will look like this:


<?xml version="1.0"?>
<xs:schema
 xmlns:xs="http://www.w3.org/2001/XMLSchema"
 xmlns="http://www.bankofamerica.com/commercialprocesstechnology/sbui"
 xmlns:updg="urn:schemas-microsoft-com:xml-updategram"
 targetNamespace="http://www.bankofamerica.com/commercialprocesstechnology/sbui"
 attributeFormDefault="unqualified"
 elementFormDefault="qualified"
>
 <xs:import
  schemaLocation="Updategram.xsd"
  namespace="urn:schemas-microsoft-com:xml-updategram" />
 <xs:element name="updateStatsPendingReq">
  <xs:complexType>
   <xs:sequence>
     <xs:element
      xmlns:updategram="urn:schemas-microsoft-com:xml-updategram"
      updategram:Prefix="updg" minOccurs="1" maxOccurs="unbounded" name="sync">
      <xs:complexType>
       <xs:sequence>
        <xs:element updategram:Prefix="updg" minOccurs="0" maxOccurs="unbounded" name="before">
         <xs:complexType>
          <xs:sequence>
           <xs:element minOccurs="0" maxOccurs="unbounded" name="StatsPending">
            <xs:complexType>
             <xs:attribute ref="updg:id" />
             <xs:attribute name="APPLICATIONID" type="xs:decimal" />
            </xs:complexType>
           </xs:element>
          </xs:sequence>
         </xs:complexType>
        </xs:element>
        <xs:element updategram:Prefix="updg" minOccurs="0" maxOccurs="unbounded" name="after">
         <xs:complexType>
          <xs:sequence>
           <xs:element minOccurs="0" maxOccurs="unbounded" name="StatsPending">
            <xs:complexType>
             <xs:attribute ref="updg:id" />
             <xs:attribute name="APPLICATIONID" type="xs:decimal" />
             <xs:attribute name="SITEID" type="xs:string" />
             <xs:attribute name="ASSIGNPROCESSED" type="xs:boolean" />
            </xs:complexType>
           </xs:element>
          </xs:sequence>
         </xs:complexType>
        </xs:element>
       </xs:sequence>
      </xs:complexType>
     </xs:element>
    </xs:sequence>
  </xs:complexType>
 </xs:element>
  <xs:element name="updateStatsPendingRep">
    <xs:complexType>
      <xs:sequence>
        <xs:element name="Success" />
      </xs:sequence>
    </xs:complexType>
  </xs:element>
</xs:schema>

In the message transformation shape when you construct the updategram, use a map similar to this:

Then just fire off the orchestration and watch the updategram does its work. The particular orchestration I ran was able to update approximately 1800 records in a few seconds without any problem. Email me if you need a sample project.

Inline XSLT Call Template

2005-01-19T20:04:00.000-08:00

Google's Biztalk group posted this interesting problem about how to use the Inline XSLT Call Template and cumulative functoid in the map. I am quoting Jeremy's question here:

"In the following sample, I have a multiple invoice file that has 1 header record and a repeating detail record for each invoice. Can someone help me using inline xslt to sum the detail records of each invoice so that I can get the total for each invoice. I have seen how to do this just using xslt instead of the mapper, but I would like to do this within the mapper as I have other functoids that I am using. It appears I cannot get the cumulative sum functoid to sum each invoice with the scope parameter; instead it always seems to sum the entire file or nothing at all."


inbound: 

<Invoices xmlns="http://www.google.com">

 <Invoice>

  <Header>

   <Credit>-20</Credit>

  </Header>

  <Detail>

   <Debit>10</Debit>

  </Detail>

  <Detail>

   <Debit>9</Debit>

  </Detail>

  <Detail>

   <Debit>1</Debit>

  </Detail>

 </Invoice>

 <Invoice>

  <Header>

   <Credit>-10</Credit>

  </Header>

  <Detail>

   <Debit>7</Debit>

  </Detail>

  <Detail>

   <Debit>3</Debit>

  </Detail>

 </Invoice>

</Invoices>



outbound: 

<ns0:Invoices xmlns:ns0="http://www.google.com">

 <ns0:TotalFileCredit>-30</ns0:TotalFileCredit>

 <ns0:TotalFileDebit>30</ns0:TotalFileDebit>

 <ns0:Invoice>

  <ns0:TotalInvoiceCredit>-20</ns0:TotalInvoiceCredit>

  <ns0:TotalInvoiceDebit>20</ns0:TotalInvoiceDebit>

  <ns0:Header>

   <ns0:Credit>-20</ns0:Credit>

  </ns0:Header>

  <ns0:Detail>

   <ns0:Debit>10</ns0:Debit>

  </ns0:Detail>

  <ns0:Detail>

   <ns0:Debit>9</ns0:Debit>

  </ns0:Detail>

  <ns0:Detail>

   <ns0:Debit>1</ns0:Debit>

  </ns0:Detail>

 </ns0:Invoice>

 <ns0:Invoice>

  <ns0:TotalInvoiceCredit>-10</ns0:TotalInvoiceCredit>

  <ns0:TotalInvoiceDebit>10</ns0:TotalInvoiceDebit>

  <ns0:Header>

   <ns0:Credit>-10</ns0:Credit>

  </ns0:Header>

  <ns0:Detail>

   <ns0:Debit>7</ns0:Debit>

  </ns0:Detail>

  <ns0:Detail>

   <ns0:Debit>3</ns0:Debit>

  </ns0:Detail>

 </ns0:Invoice>

</ns0:Invoices>

Obviously the inbound and outbound xml document instances could share a same schema. Here's the schema code:


<xs:schema

 xmlns:xs="http://www.w3.org/2001/XMLSchema"

 xmlns="http://www.google.com"

 targetNamespace="http://www.google.com"

 elementFormDefault="qualified"

 attributeFormDefault="unqualified"

>

<xs:complexType name="Detail">

 <xs:sequence>

  <xs:element name="Debit" type="xs:int" />

 </xs:sequence>

</xs:complexType>

<xs:complexType name="Header">

 <xs:sequence>

  <xs:element name="Credit" type="xs:int" />

 </xs:sequence>

</xs:complexType>

<xs:complexType name="Invoice">

 <xs:sequence>

  <xs:element minOccurs="0" name="TotalInvoiceCredit" type="xs:int" />

  <xs:element minOccurs="0" name="TotalInvoiceDebit" type="xs:int" />

  <xs:element name="Header" type="Header" />

  <xs:element maxOccurs="unbounded" name="Detail" type="Detail" />

 </xs:sequence>

</xs:complexType>

<xs:complexType name="Invoices">

 <xs:sequence>

  <xs:element minOccurs="0" name="TotalFileCredit" type="xs:int" />

  <xs:element minOccurs="0" name="TotalFileDebit" type="xs:int" />

  <xs:element maxOccurs="unbounded" name="Invoice" type="Invoice" />

 </xs:sequence>

</xs:complexType>

<xs:element name="Invoices" type="Invoices" />

</xs:schema>

Here's the map I have used:

In the scripting functoid, I used the XSLT Call Template below:


<xsl:template name="MyXsltConcatTemplate">

 <xsl:param name="param1" />

 <xsl:element name="ns0:TotalInvoiceDebit" 

  namespace="http://www.google.com">

  <xsl:value-of 

   select="sum(*[local-name()='Detail']/*[local-name()='Debit'])" />

 </xsl:element>

</xsl:template>

We couldn't use the inline xslt here since we need to pass in a local node "Invoice" that occurs multiple times in the inbound document. You can't pass in any parameter using the inline xslt script. The inline xslt call template, however, allows you to pass in a local node and you can apply your xslt transformation within the scope of passed parameter. In this case it is "param1" and it refers to one of the "Invoice" element of the xml document.

Web service project name cannot exceed 61 characters!

2004-12-31T13:09:00.000-08:00

I think I just figured out the problem I posted below. It turns out that the web service project name can't be longer than 61 characters. Therefore, the assembly's friendly name couldn't exceeds 61 characters for web servie dll. I took the default name


BancOfMercury.CurrencyLaunderingTechnology.DUI.Orchestrations_Proxy

for the web service when I published it from the ws publishing wizard. It's 67 characters and it exceeds this arbitrary limit. I tried to create a dummy web service on my computer with the name


BancOfMercury_CurrencyLaunderingTechnology_DUI_GrabTheMoneySer

which failed to allow me to access it as well. The error reported by the fusion.exe is very deceiving. It pointed me to other directions when I troubleshoot the problem. I thought error is in the assembly probing process. FUSLOGVW says this:
LOG: Post-policy reference:


BancOfMercury.CurrencyLaunderingTechnology.DUI.Orchestrations_Proxy, 
Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
ERR: Setup failed with hr = 0x80131047.
ERR: Failed to complete setup of assembly (hr = 0x80131047). 
Probing terminated.

Anyway, I tried another dummy project with name


BancOfMercury_CurrencyLaunderingTechnology_DUI_GrabTheMoneySe
BancOfMercury_CurrencyLaunderingTechnology_DUI_GrabTheMoney

and it worked. There's no documentation states that we couldn't name web service project with a name more than 61 chars. It still perplexes me since microsoft uses a cut off to be 61 instead of 64 which is exactly 8 bytes.

0x80131047

2004-12-30T14:48:00.000-08:00

I was able to publish the web service from the biztalk and the the web service project was generated successfully. I was able to compile the program okay as well. However, when I browse to the asmx page, I got this configuration error. So far I was not able to figure out why. I also enclosed the fusion output.

Server Error in '/BancOfMercury.CurrencyLaunderingTechnology.DUI.Orchestrations_Proxy' Application.

Configuration Error

Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: The given assembly name or codebase, 'BancOfMercury.CurrencyLaunderingTechnology.DUI.Orchestrations_Proxy', was invalid.

Source Error:




Line 196:				<add assembly="System.EnterpriseServices, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>

Line 197:				<add assembly="System.Web.Mobile, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>

Line 198:				<add assembly="*"/>

Line 199:			</assemblies>

Line 200:		</compilation>

Source File: c:\winnt\microsoft.net\framework\v1.1.4322\Config\machine.config Line: 198

Assembly Load Trace: The following information can be helpful to determine why the assembly 'BancOfMercury.CurrencyLaunderingTechnology.DUI.Orchestrations_Proxy' could not be loaded.




=== Pre-bind state information ===

LOG: DisplayName = BancOfMercury.CurrencyLaunderingTechnology.DUI.Orchestrations_Proxy

 (Partial)

LOG: Appbase = file:///c:/inetpub/wwwroot/BancOfMercury.CurrencyLaunderingTechnology.DUI.Orchestrations_Proxy

LOG: Initial PrivatePath = bin

Calling assembly : (Unknown).

===



LOG: Policy not being applied to reference at this time (private, custom, partial, or location-based assembly bind).

LOG: Post-policy reference: BancOfMercury.CurrencyLaunderingTechnology.DUI.Orchestrations_Proxy

LOG: Attempting download of new URL file:///C:/WINNT/Microsoft.NET/Framework/v1.1.4322/Temporary ASP.NET Files/bancofmercury.currencylaunderingtechnology.dui.orchestrations_proxy/a47ccba5/38832147/BancOfMercury.CurrencyLaunderingTechnology.DUI.Orchestrations_Proxy.DLL.

LOG: Attempting download of new URL file:///C:/WINNT/Microsoft.NET/Framework/v1.1.4322/Temporary ASP.NET Files/bancofmercury.currencylaunderingtechnology.dui.orchestrations_proxy/a47ccba5/38832147/BancOfMercury.CurrencyLaunderingTechnology.DUI.Orchestrations_Proxy/BancOfMercury.CurrencyLaunderingTechnology.DUI.Orchestrations_Proxy.DLL.

LOG: Attempting download of new URL file:///c:/inetpub/wwwroot/BancOfMercury.CurrencyLaunderingTechnology.DUI.Orchestrations_Proxy/bin/BancOfMercury.CurrencyLaunderingTechnology.DUI.Orchestrations_Proxy.DLL.

LOG: Policy not being applied to reference at this time (private, custom, partial, or location-based assembly bind).

LOG: Post-policy reference: BancOfMercury.CurrencyLaunderingTechnology.DUI.Orchestrations_Proxy, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null

Version Information: Microsoft .NET Framework Version:1.1.4322.985; ASP.NET Version:1.1.4322.968

Here's the fusion output


*** Assembly Binder Log Entry  (12/30/2004 @ 5:40:59 PM) ***



The operation failed.

Bind result: hr = 0x80131047. No description available.



Assembly manager loaded from:  C:\WINNT\Microsoft.NET\Framework\v1.1.4322\fusion.dll

Running under executable  C:\WINNT\Microsoft.NET\Framework\v1.1.4322\aspnet_wp.exe

--- A detailed error log follows. 



=== Pre-bind state information ===

LOG: DisplayName = BancOfMercury.CurrencyLaunderingTechnology.DUI.Orchestrations_Proxy

 (Partial)

LOG: Appbase = file:///c:/inetpub/wwwroot/BancOfMercury.CurrencyLaunderingTechnology.DUI.Orchestrations_Proxy

LOG: Initial PrivatePath = bin

LOG: Dynamic Base = C:\WINNT\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET Files\bancofmercury.currencylaunderingtechnology.dui.orchestrations_proxy\a47ccba5

LOG: Cache Base = C:\WINNT\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET Files\bancofmercury.currencylaunderingtechnology.dui.orchestrations_proxy\a47ccba5

LOG: AppName = 38832147

Calling assembly : (Unknown).

===



LOG: Processing DEVPATH.

LOG: DEVPATH is not set. Falling through to regular bind.

LOG: Policy not being applied to reference at this time (private, custom, partial, or location-based assembly bind).

LOG: Post-policy reference: BancOfMercury.CurrencyLaunderingTechnology.DUI.Orchestrations_Proxy

LOG: Attempting download of new URL file:///C:/WINNT/Microsoft.NET/Framework/v1.1.4322/Temporary ASP.NET Files/bancofmercury.currencylaunderingtechnology.dui.orchestrations_proxy/a47ccba5/38832147/BancOfMercury.CurrencyLaunderingTechnology.DUI.Orchestrations_Proxy.DLL.

LOG: Attempting download of new URL file:///C:/WINNT/Microsoft.NET/Framework/v1.1.4322/Temporary ASP.NET Files/bancofmercury.currencylaunderingtechnology.dui.orchestrations_proxy/a47ccba5/38832147/BancOfMercury.CurrencyLaunderingTechnology.DUI.Orchestrations_Proxy/BancOfMercury.CurrencyLaunderingTechnology.DUI.Orchestrations_Proxy.DLL.

LOG: Attempting download of new URL file:///c:/inetpub/wwwroot/BancOfMercury.CurrencyLaunderingTechnology.DUI.Orchestrations_Proxy/bin/BancOfMercury.CurrencyLaunderingTechnology.DUI.Orchestrations_Proxy.DLL.

LOG: Assembly download was successful. Attempting setup of file: c:\inetpub\wwwroot\BancOfMercury.CurrencyLaunderingTechnology.DUI.Orchestrations_Proxy\bin\BancOfMercury.CurrencyLaunderingTechnology.DUI.Orchestrations_Proxy.DLL

LOG: Entering download cache setup phase.

LOG: A partially-specified assembly bind succeeded from the application directory.

LOG: Policy not being applied to reference at this time (private, custom, partial, or location-based assembly bind).

LOG: Post-policy reference: BancOfMercury.CurrencyLaunderingTechnology.DUI.Orchestrations_Proxy, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null

ERR: Setup failed with hr = 0x80131047.

ERR: Failed to complete setup of assembly (hr = 0x80131047). Probing terminated.

Create a New Message Inside an Orchestration Without using an External Component

2004-12-24T09:31:00.000-08:00

BizTalk documentation states: "You construct a message any time that you introduce a message into your orchestration, either by receiving it or by assigning values to a message variable. ... You can invoke a .NET class to create a message, assign one message to another, or use a transform to map certain values within a message to values within another message. Messages are also constructed by a receive action or when your orchestration accepts a message as a parameter."

It basically says this: To create a new message, you have these options:

Transform from an existing message

Assign the variables of an existing message

Assign an existing message or message part to the new message

Use an external .NET component to construct a new message

Sometime you want to create a simple empty message to start with. This message doesn't have an instance yet. You don't have an existing message to do the message transformation. You don't want to use the external component since it introduces one more layer of complexity. Now what can you do? Looks like you ran out of the options. AMOF, you could easily construct a new message right inside the orchestration by following these steps:

Add a System.Xml.XmlDocument variable to the documentation. Without losing generality, let's say its name is theXmlDoc

Add a message assignment shape



  theXmlDoc = new System.Xml.XmlDocument(); 

  theXmlDoc.LoadXml("<root xmlns=\"http://www.namespace.org\" />"); 

  newMessage = theXmlDoc;

The signature of the map file has changed, some arguments that you specify may not be valid.

2004-11-17T13:05:00.000-08:00

Problem:
One of our developers run into this problem when using the Biztalk Mapper. We searched on internet and found out there's a guy had exact same problem on http://www.webservertalk.com. So I am saving my keystrokes and quote his message below:

I had mapping scenario in where I am having 3 input xml file and 1 output xml file, which I can easily specify in the mapping component in the orchestration. The problem is when it opens the mapper. It shows that it had 3 input documents but only shows fields of first input xml and the other two as empty. When I go back to the orchestration and try to click on the transform component it says that the signature of the map file has changed, some arguments that you specify may not be valid. I believe it is possible to have multiple input file and one output file, Am I missing something?.
Amit

Possible Solution:
I am pretty sure the problem you encountered is due to the namespace#rootElement collision. If you are using the same namespace for those 3 inbound xml documents and these documents also have the same root element, you will run into this problem exactly as you described. You need to make sure the definition of your xml namespaces will always allow BizTalk to derive a unique type. The simple solution to your problem could be:

use a dinstinct namespace name for each inbound document schema; or

use a distinct root element name in each schema.

One common scenario you will run into this problem is when you use the schemas generated by the SQL Adapters invoking the stored procedures. If you let the stored procedure to return "FOR XML RAW" and you have the same namespaces for these stored procedures generated schemas, then BizTalk mapper will not be able to import the rest of schemas since there's a type collision after importing the first schema. You will have these collisions if you define your namespace to be: http://mynamespace.

InputMessagePart_0: http://mynamespace#row InputMessagePart_1: http://mynamespace#row InputMessagePart_2: http://mynamespace#row

How to fix Project location not fully trusted by .Net runtime problem?

2004-11-16T10:32:00.000-08:00

SOLUTION

Go to Settings | Control Panel | Admin Tools | .NET 1.1 Configuration

Drill to "Runtime Security Policy/Machine/Code Groups/All_Code"

Add a new code group with "_" separated name such as "CC_View_Group"

Click on the "Membership Condition" and choose "URL"

In the URL: text box, type in "file://V:/*"

The "SOAP" adapter is suspending an outbound message going to destination

2004-11-15T13:32:00.000-08:00


Event Type:	Error

Event Source:	BizTalk Server 2004

Event Category:	BizTalk Server 2004 

Event ID:	5754

Date:		15/11/2004

Time:		15:24:02

User:		N/A

Computer:	B000E7F60EAA7

Description:

The "SOAP" adapter is suspending an outbound message going to 

destination URL:"/My.WebService/RetrieveCustomerInfo.asmx". 

Details:"Exception of type System.Runtime.InteropServices.COMException 

was thrown.".

You just published an web service from your beautiful orchestration and you are expecting that your web service will work like a champ. Suddenly, you are stopped by this error and scratched your head several times trying to figure out what the h... is going on. You should reproduce the error and try to get more detailed exception context. Remember your could turn on the ThrowDetailedError in the web.config file to get more information about the exception.


  <appSettings>

   <add key="ThrowDetailedError" value="True" />

  </appSettings>

Once you turned on this switch, the exception you received from your client application should give you enough information to go about this exception. From my experience, the error is likely due to the transformation of the xml document to the objects in the message pipeline. For example, if you have an integer type element count in your outbound xml document instance you intend to map to a field or property of your object.


 <count>6.0</count>

The floating point number 6.0 will cause a conversion exception: System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info). This will eventually bubble up to throw the mysterious System.Web.Services.Protocols.SoapException.

You need also keep an eye on the possible number overflow. For example, if you have an element mapped to xs:integer which has a value that's not in the range of [-2147483648, 2147483647], you will receive this type of exception as well.

Got tired of running Deployment Wizard?

2004-10-27T20:01:00.001-07:00

I found it is very annoying to run the BizTalk deployment wizard to deploy or undeploy the assemblies during development phase. Especially when you have multiple assemblies to deal with. You can actually write a simple batch file to automate the deploy/undeploy process. BizTalk provides a BTSDeploy.exe in the installation directory that can take various arguments to perform these tasks easily. The following code (undeploy.bat) is a very rough sample for the undeployment. The deployment step is just the opposite. In case you don't know how to find out the public key token of your assembly, you could use these commands: sn -T assembly.dll and sn -t keyfile.snk.


@echo off

SETLOCAL



::

:: Set the deploy environmental variables for App

::

SET server=dbserver

SET db=BizTalkMgmtDb

SET btsdir="C:\Program Files\Microsoft BizTalk Server 2004"

SET outdir=..\App\bin\Development

SET log=.\undeployapp.log



::

:: The following section could be repeated if mutiple assemblies

:: to be undeployed...

::

SET name=App

SET version=2.0.0.0

SET pkt=29068414d03ece02

SET culture=neutral



echo Undeploy %name% %version% from GAC and %db% on %server% ...

::

:: Perform undeployment; use BTSDeploy.exe

::

%btsdir%\BTSDeploy 

     REMOVE SERVER=%server% DATABASE=%db% 

     NAME=%name% VERSION=%version% CULTURE=%culture% 

     PUBLICKEYTOKEN=%pkt% UNINSTALL=True LOG=%log%



pause

The node to be inserted is from a different document context

2004-10-27T13:16:00.000-07:00

Inside your message assignment shape, if you try to do :


Construct MsgB

{

    theXmlDoc.DocumentElement.AppendChild

    (

         xpath

        (

            MsgA,

            "//*[local-name()='someElement']"

        )

    );

    MsgB = theXmlDoc;

}

You will run into this error:


Event Type:	Error

Event Source:	XLANG/s

Event Category:	None

Event ID:	10034

Date:		10/27/2004

Time:		4:13:29 PM

User:		N/A

Computer:	B00D059B675E2

Description:

Uncaught exception terminated service A, instance B



The node to be inserted is from a different document context.

   

Exception type: ArgumentException

Source: System.Xml

Target Site: System.Xml.XmlNode AppendChild(System.Xml.XmlNode)

Help Link:

Additional error information:

SOLUTION: This is because the node to be copied belongs to another Xml document and is not recognized by the destination xml document. In order to make it work, you will need to import it first. If you read MSDN's documentation for the XmlNode.AppendChild() method, you will notice the following description:

...
If the node being inserted was created from another document, you can use XmlDocument.ImportNode to import the node to the current document. The imported node can then be inserted into the current document. ...

Therefore, all you need to do is to add XmlDocument.ImportNode() method in the message assignment expression editor:


Construct MsgB

{

    theXmlDoc.DocumentElement.AppendChild

    (

       theXmlDoc.ImportNode

       (

           xpath

           (

               MsgA,

               "//*[local-name()='someElement']"

           )

       )

    );

    MsgB = theXmlDoc;

}

Cannot retrieve list of objects due to a WMI provider failure. New transaction cannot enlist in the specified transaction coordinator.

2004-10-27T05:11:00.000-07:00

Cannot retrieve list of objects due to a WMI provider failure. New transaction cannot enlist in the specified transaction coordinator.

This problem occurs when you run the BizTalk Server across the fire wall. Take a look at the following links:

KB 250367

KB 306843

KB 300083

Ports need to be opened

Windows Command Line Tricks

2004-10-24T16:11:00.000-07:00

Command Line Expansion:

I am sure you like the command line expansion capability of csh, tcsh and bash in unix family of operating systems. You can have the same capability in Windows Command Line if you enable it. :-) You can use "tab" to expand the whole command line argument after you give a few starting characters. To enable this capability, set the following registry key value to 9.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Command Processor\PathCompletionChar

Open File Explorer From cmd and Set Address to Current Working Directory:

Developers constantly spend time in command line and sometime it is useful to start up the file explorer from the comand line environment. It will be very cool and save us a little bit time if the file explorer opened will point to the same working directory. You can do this easily with this command:
C:\Program Files\Microsoft BizTalk Server 2004> explorer %cd%
This command will open up a file explorer and take you to directory:
C:\Program Files\Microsoft BizTalk Server 2004

The property 'TargetSite' on type 'System.Exception' cannot be serialized because it is decorated with declarative security permission attributes.

2004-10-21T19:20:00.000-07:00

Detailed error:
The property 'TargetSite' on type 'System.Exception' cannot be serialized because it is decorated with declarative security permission attributes. Consider using imperative asserts or demands in the property accessors.

Solution: System.Exception object can not be serialized to transfer over the HTTP channel. Obviously, we need to provide some mechanism to serialize its state to some transferable medium like string. And on the other end, typically web service, we need to deserialize it back to the exception object.

I have a BaseException class that derives from System.Exception class. It has
a public property called "ExceptionState" that serializes it to Base64String representation. It also has a static method "Reconstruct" that reconstructs it from the Base64String back to the BaseException object.


public class BaseException : Exception, ISerializable

{



//...



string state; 

static BinaryFormatter binaryFormatter = new BinaryFormatter(); 



/// <summary>

/// Persiste BaseException object to the base 64 string. This property returns

/// a string representation of the exception state which could be used to 

/// reconstruct this exception if desired. <see cref="Reconstruct"/> method.

/// This property is introduced to fix the following issue: 

/// The property 'TargetSite' on type 'System.Exception' cannot be serialized 

/// because it is decorated with declarative security permission attributes. 

/// Consider using imperative asserts or demands in the property accessors.

/// </summary>

public string ExceptionState

{

    get

    {

	if (state == null)

	{

	    MemoryStream stream = new MemoryStream();

	    binaryFormatter.Serialize(stream, this); 

	    stream.Seek(0, SeekOrigin.Begin);

	    state = Convert.ToBase64String(stream.ToArray()); 

	}

	return this.state; 

    }

}



/// <summary>

/// Reconstructs a <c>BaseException</c> from the supplied exceptionState 

/// string. <see cref="ExceptionProperty"/> property comments. 

/// </summary>

/// <param name="exceptionState">

/// Base 64 string representation of the xception</param>

/// <returns>

/// A reconstructed <c>BaseException</c> object; null if reconstruction failed. 

/// </returns>

public static BaseException Reconstruct(string exceptionState)

{

   byte [] buffer = Convert.FromBase64String(exceptionState); 

   Stream stream = new MemoryStream(buffer, 0, buffer.Length, false); 

   stream.Seek(0, SeekOrigin.Begin); 

   object obj = binaryFormatter.Deserialize(stream); 

   return obj as BaseException; 

}

}

Scritping Functoid Catch

2004-10-21T06:09:00.000-07:00

I experienced a problem when I was using the Inline XSLT inside the scripting functoid. I entered the XSLT first, then I scrolled the "Script type" dropdown to check out the template of "Inline C#". Then I clicked on the "OK" button without noticing that "Configure Functoid Scripts" dialog actually overwrites the the script type of my choice "Inline XSLT" with "Inline C#", even though your intention is to use XSLT. As a matter of fact, when you scroll the "Script type" dropdown to any other script types in front of the "Inline XSLT" inside the "Script type" dropdown, BizTalk will automatically uses the first available in the list even somtime it only has script in comments. When you compile your project, it will not signal error since all of the commented code, i.e. empty script, is considered valid by compiler. But when you run your orchestration, it will bomb. The solution is you need to rearrange the precedence of the inline scripts. To do this, right click inside of the map area; then go to the property window and bring up the "Script Type Precedence" dialog.

I would test any BizTalk mapper before I compile my projects. To do so, simply right click on your map file and select "Test map" from the context menu.

BizTalk Xml Links ...

2004-10-18T19:29:00.000-07:00

Import, Include or Redefine

Even though you could use <xs:import> or <xs:include> to reuse existing schemas, I found that BizTalk having some proprietary processing for <xs:include>. It will copy the included schema verbatim whenever you place your <xs:include> node. Moreover, the schemas will also be included whenever they are referenced. Thus, you will have multi-rooted master schema if you use <xs:include>. I prefer to use the <xs:import> because it will maintain the single root in the master schema even you reference multiple existing external schemas.

Assign messages

Xml Namespace and XPATH

Elements vs. Attributes

IBM's When to use elements versus attributes

Yet another BizTalk Naming Guideline Recommendations

2004-10-17T17:03:00.000-07:00

For all BizTalk orchestration shapes, I would recommend to call a shape with its name (or its shorthand) and suffix it with a succint description. This is only a recommendation. You don't have to follow this convention. The recommendation strives to promote a common set of guidelines.


...................................................................

              Shape  Short       Example

...................................................................

 Call Orchestration  CallOdx     CallOdx_AssembleReply

         Call Rules  CallRule    CallRule_LoanDecisioning

         Compensate  Compensate  Compensate_BadTransactions

  Construct Message  Mkmsg       Mkmsg_GetEntityParams

             Decide  Decide      Decide_ProcessBorrower

              Delay  Delay       Delay_OneHour

              Group  Grp         Grp_GetFirstEntity

             Listen  Listen      Listen_IncomingReq

               Loop  Loop        Loop_ProcessAllApplications

 Message Assignment  Assign      Assign_EntityMatchResultToReplyMsg

   Parallel Actions  Para        Para_GetMatchAndMkReply

              Port*  Port        Port_GetEntities

            Receive  Recv        Recv_AppReq

               Send  Send        Send_AppRep

Start Orchestration  Init        Init_PlaceOrder

            Suspend  Susp        Susp_CreditEvaluationOdx

          Terminate  Stop        Stop_CreditEvaluationOdx

    Throw Exception  Throw       Throw_UnknownReqException

          Transform  Xform       Xform_GetEntityParams

* Since orchestration's port name has nothing to do with the transfer protocol, the name should not contain the word like Soap, Http, File, etc.

This Assembler cannot retrieve document specification by using this type: "http://tempuri#request"

2004-10-15T08:04:00.000-07:00


Event Type:	Error

Event Source:	BizTalk Server 2004

Event Category:	BizTalk Server 2004 

Event ID:	5720

Date:		14/10/2004

Time:		18:19:46

User:		N/A

Computer:	yourhost

Description:

There was a failure executing the send pipeline: 

"Microsoft.BizTalk.DefaultPipelines.XMLTransmit" 

Source: "XML assembler" 

Send Port: "SQL://server/db/" Reason: This Assembler cannot retrieve 

document specification by using this type: "http://tempuri#request".

SOLUTIONS: This is noramlly caused by the failure of BizTalk's message engine to derive the unique type from the deployed Xml Schema. Type generated by the schema will have the format of "namespace#typename". For example, if you have defined your xmlns=http://myproject and you have an root element called item. The fully qualified element type derived by the BizTalk will be: http://myproject#item. So your responsibility is to make sure:

Indeed you have this schema and desired root element defined

You don't have two or more elements with the exact same name and same namespace deployed. This includes all schemas previously deployed to the BizTalkMgmtDb. You could find the Xml namespaces are saved in the bt_XmlShare and bt_XmlShareReference tables in the BizTalkMgmtDb

BizTalk: 'ActiveView.ColumnAxis' is null or not an object

2004-10-12T20:41:00.000-07:00

HAT failed to run properly, it complains about the snap in. You need download Office 2000 Web Components:
download from here

A Microsoft Distributed Transaction Coordinator problem prevented connection to the Configuration database. Exception from HRESULT: 0x8004D00E

2004-10-12T20:34:00.000-07:00

Follow these steps:

Make sure host and server can ping each other

Make sure DTC service is up and running

Check out kbid 839187
SET HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\TurnOffRpcSecurity = 1

If your DEV BizTalk server is on a Windows XP box with SP2 installed, take a look at this article by Florin Lazar: XP SP2 and Transactions

BizTalk: Type "http://www.w3.org/2001/XMLSchema:char" is not declared or not a simple type

2004-10-12T20:00:00.000-07:00

If you use the datatype char(1) in the stored procedure, it will bomb when you try to generate XML schema in the "add SQL adapter wizard".

It turns out to be a BizTalk bug. You can still use char(1) and it will just work fine after applying the following fix. By default, the schema returned by SQL XML is XDR (XML data Reduced). You can observe this from the Query Analyzer. This reduced schema is not used by BizTalk; BizTalk uses the xsd. BizTalk relies on the XDRToXSD.xslt to transfrom the xdr generated by SQL Server to the desired xsd format. There's a problem in the XDRToXSD.xslt (this file locates in "C:\Program Files\Microsoft BizTalk Server 2004\"). To fix this problem change the following line:


<xsl:template match="@dt:type[.='char']" mode="convert-datatype">xs:char</xsl:template>

to:

<xsl:template match="@dt:type[.='char']" mode="convert-datatype">xs:string</xsl:template>

Thus, char(1) or char will be mapped to a xs:string. Actually, the default http://www.w3.org/2001/XMLSchema namespace has no xs:char build-in type. If you look at the following picture of the build in XMLSchema type hierachy you will find there's no xs:char.

For details about the XMLSchema build in data type click here.