http://www.dpawson.co.uk/xsl/sect2/padding.html

<xsl:template name=”prepend-pad”>
<!– recursive template to right justify and prepend–>
<!– the value with whatever padChar is passed in   –>
<xsl:param name=”padChar”/>
<xsl:param name=”padVar”/>
<xsl:param name=”length”/>
<xsl:choose>
<xsl:when test=”string-length($padVar) &lt; $length”>
<xsl:call-template name=”prepend-pad”>
<xsl:with-param name=”padChar” select=”$padChar”/>
<xsl:with-param name=”padVar” select=”concat($padChar,$padVar)”/>
<xsl:with-param name=”length” select=”$length”/>
</xsl:call-template>
</xsl:when>
<xsl:otherwise>
<xsl:value-of select=”substring($padVar,string-length($padVar) -
$length + 1)”/>
</xsl:otherwise>
</xsl:choose>
</xsl:template>

<xsl:template name=”append-pad”>
<!– recursive template to left justify and append  –>
<!– the value with whatever padChar is passed in   –>
<xsl:param name=”padChar”/>
<xsl:param name=”padVar”/>
<xsl:param name=”length”/>
<xsl:choose>
<xsl:when test=”string-length($padVar) &lt; $length”>
<xsl:call-template name=”append-pad”>
<xsl:with-param name=”padChar” select=”$padChar”/>
<xsl:with-param name=”padVar” select=”concat($padVar,$padChar)”/>
<xsl:with-param name=”length” select=”$length”/>
</xsl:call-template>
</xsl:when>
<xsl:otherwise>
<xsl:value-of select=”substring($padVar,1,$length)”/>
</xsl:otherwise>
</xsl:choose>
</xsl:template>

ItinerarySelectReceiveXml – Verify the schema for this document specification is deployed and is in the Global Assembly Cache.

I thought I was going to have to reinstall the ESB Toolkit. It turns out all I needed to do was change the IIS Application Pool the WCF website was running on from .NET 2.0 to .NET 4.0. Apparently it was looking for the assembly in the 2.0 GAC rather than the 4.0 GAC.

Thanks to this forum thread for the solution!

This is a situation I was having and was resolved using this technique…

When parsing a flat-file, then applying a transform (map) to it in an itinerary, I was consistently getting an error message:

Description: There was a failure executing the receive pipeline

Reason: Cannot access a disposed object.

Object name: ‘DataReader’.

Updating the FF Disassembler Pipeline Component in my custom Pipeline fixed the issue. I had to set the “Recoverable interchange processing” property to true.

This article describes the function of this property in the disassemble stage.

http://social.msdn.microsoft.com/Forums/en-US/biztalkediandas2/thread/17e16112-209b-40ed-926b-8d2627954b9a/

I have a situation at a client because we were keeping the Party/Agreement nodes in the Bindings file when we promoted new bindings from QA to Production. This was causing the Party Agreements to get dropped and re-created, which reset the control numbers back to 1. The result was 997 rejects for duplicate control numbers.

Moving forward, I will have to be careful to remove the Trading Partners from the Bindings file which we do not want to be dropped and re-created, that way the EDI Control Numbers will be maintained.

This is the answer to my question about the issue from the MSDN Forum link above:

To get the current ISA Control number, you can find it in the BizTalkMsgBoxDb database EdiControlNumbers table. Control numbers are maintained based on the Agreement set up between trading partners. Agreement details can be found in BizTalkMgmtDb – tpm.OnewayAgreement table.

When you import binding file with a party information, which already exists, existing agreement id will be removed and new agreement id will be created with new control numbers(1 as starting value).

Here are the queries I used to help track down the Party to get the OneWayAgreement.Id to use when querying the EdiControlNumbers table.

 USE BizTalkMgmtDb

select * from tpm.OnewayAgreement o

inner join tpm.BusinessIdentity bi on bi.Id = o.ReceiverId

inner join tpm.BusinessProfile bp on bp.ProfileId = bi.ProfileId

where bp.Name like ‘%[name]%’

USE BizTalkMsgBoxDb

select * from EdiControlNumbers

where OnewayAgreementId = [id]

1. Get a backup of the database on the other end of the linked server call.
2. Restore the backup on your local SQL Server instance
3. Run the code below to create the loopback linked server

EXEC sp_addlinkedserver @server = N’name_for_linked_server’,

@srvproduct = N’ ‘,

@provider = N’SQLNCLI’,

@datasrc = N’name_of_my_sqlserver_instance’,

@catalog = N’name_of_database’

http://www.businessprocessintegration.net/2009/03/espportal-and-a-network-related-or-instance-specific-error-occurred-while-establishing-a-connection-to-sql-server/

I was seeing this error when I would attempt to navigate to the Registry tab of the ESB Portal.

Exception information:

Exception type: SqlException

Exception message: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 – No connection could be made because the target machine actively refused it.)

Request information:

Request URL: http://localhost/ESB.Portal/Lists/RegistrySummaryContainer.aspx

Request path: /ESB.Portal/Lists/RegistrySummaryContainer.aspx

The solution was to enabled TCPIP in the SQL Server Configuration Manager under SQL Server Network Configuration–>Protocols for MSSQLSERVER.

The same issue is addressed at this blog post and has an interesting comment.

I solved the problem the opposite way: I altered the connection string to remove “Network Library=dbmssocn”, thus eliminating the requirement to use TCP/IP.Richard

I did not try that solution, but it sounds plausible as well.

http://btsplcw.codeplex.com/releases/view/46419

It took me a little while to find it on Google, so I thought I’d give something to add to the search community!

I looked through the XSLT file and discovered a couple of tweaks that got it all working.

Basically, everywhere in the XSLT where it references ”@Type = ‘Link’” or ”@Type = ‘Constant’” had to be changed to ”@Type = ‘link’” and ”@Type = ‘constant’”.

XLST is a case-sensitive language. Apparently in BizTalk 2010 the Type for Links and Constants in the map-generated code has all lower-case “link” and “constant”.

Anyway, I am glad to have found an easy solution. It sure beats having to put all that documentation together by hand! There will be lots of maps by the end of this project, so I am happy to have an automated tool to create useful docs.

http://www.tipandtrick.net/2008/fix-virtual-pc-2007-shared-networking-nat-internet-not-working-in-windows-server-2003-2008-and-vista-guest-os/

It appears that Ping was working, but url browsing was not.

I followed these steps and was able to get the Orchestration to open properly in the IDE:

1. Close Visual Studio
2. Launch the services console with the command: Services.msc. Restart the “Protected Storage” Service (make sure it is in the automatic mode and started).
3. Restart IIS with the command : iisreset
4. Reset the Visual Studio loaded packages (in a Visual Studio Command Prompt) with the command: devenv.exe /setup /resetskippkgs

After these steps, I right-clicked on the Orchestration in the IDE Solution Explorer, chose “Open With” and then Orchestration Designer just to make sure it would open as expected.

I found this solution here: http://geekswithblogs.net/synBoogaloo/archive/2007/04/17/111745.aspx#423642