This fix need to be applied ASAP (before next week) as we will be hitting the leap year date 2/29/2012 in just about a week

This fix should be applied in:

• Microsoft BizTalk Server 2006 R2
• Microsoft BizTalk Server 2009 without CU installed (The fix has been available for quite some time and also included as part of the CU for BizTalk 2009 since CU1).

If you are not using X12 in your EDI transactions, this issue is not applicable to you and hence you don’t have to worry about taking this fix at this time.  The fix is only on the x12 code path and does not affect EDIFACT processing.

Problem

When you use the Electronic Data Interchange (EDI) pipeline to receive EDI interchanges in Microsoft BizTalk Server 2006 R2 or Microsoft BizTalk Server 2009, you may receive the following error message in the Application log:

Error encountered during parsing. The X12 transaction set with id ‘<n>’ contained in functional group with id ‘<n>’, in interchange with id ‘<n>’, with sender id ‘<sender id> ‘, receiver id ‘<receiver id>’ is being suspended with following errors:
Error: 1 (Field level error)
SegmentID: DTM
Position in TS: 42
Data Element ID: DTM02
Position in Segment: 2
Data Value: leapdate
8: Invalid Date

Cause

This issue occurs because the EDI interchange cannot validate a data element that contains a leap date value. For example, this issue occurs if the EDI interchange contains the "20120229" date value.

Hotfix

• EDI Leap Year hotfix: BizTalk 2009 and BizTalk 2006 R2:
• http://support.microsoft.com/kb/2435900
• BizTalkServer 2009:
• Option1: Install any BizTalk 2009 Cumulative Update. KB 2555976 lists the available cumulative updates
• Option 2: Install thestand-alone fix by clicking View and request hotfix downloads at the top of KB article 2435900.

Original post by Guru Venkataraman (BizTalk Customer Response Team) here and here.

Problem encountered during the install of the BizTalk EDI Leap Year Hotfix

• “The patch 861c5534-6cfa-4dcf-ba70-cbf01129b646 in the package Microsoft BizTalk Server 2006 R2 Hotfix [See KB article 2435900 for detail] cannot be applied. The minimum installed version of Microsoft BizTalk Server 2006 must be 3.6.2222.12. The installed version on this computer is 3.6.1404.0.” By Bart D’hoore here.

Note: you need to install this hotfix with a user with administrative privileges on the machine.

Tags: BizTalk | Hotfix

sc.exe config "Service Name" obj= "DOMAIN\User" password= "password"

However if we do this, we will obtain configuration inconsistencies between the services and settings in BizTalk administration console, as you can see in the picture:

What might cause unforeseen errors.

To change user credentials of BizTalk Host Instances we need to follow a different approach.

Change user credentials of a BizTalk Host Instance

//Getting the list of BizTalk Host Instances objects
$hosts = Get-WmiObject MSBTS_HostInstance -namespace ‘root/MicrosoftBizTalkServer’

//Listing existing BizTalk Host Instances names
$hosts | ft HostName

//Getting/Filter the desired instance
$MyHost = $hosts | ?{$_.HostName -eq "BizTalkDemoApplication"}

//Change BizTalk Host Instance user credentials
$MyHost.Install("DOMAIN\User", "password", "true")

Or simply

$hostApp = gwmi -n ‘root/MicrosoftBizTalkServer’ -q ‘select * from MSBTS_HostInstance where HostName="BiztalkDemoApplication"’

$hostApp..Install("DOMAIN\User", "password", "true")

Tags: BizTalk | PowerShell | Hosts

Uncaught exception (see the ‘inner exception’ below) has suspended an instance of service ‘MyService(4dfd3eeb-5cb2-9ca5-2e15-59dd321e72ed)’.
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: b8b6c570-516c-4e40-a07a-96632f7e8506
Shape name:
ShapeId:
Exception thrown from: segment -1, progress -1
Inner exception: Could not load type ‘type name’ from assembly ‘assembly name, Version=1.0.0.0, Culture=neutral, PublicKeyToken=…’.
Exception type: TypeLoadException
Source: …
Target Site: Microsoft.XLANGs.Core.StopConditions segment1(Microsoft.XLANGs.Core.StopConditions)

This error occurs after invoke the service or after dropping a file to the receive location.

CAUSE

• You didn’t install the assembly specified in the error.
• Your DLL depend on other DLL’s to get its job done and if you didn’t copy or install those too, you’d indeed get this error message.
• Or you have installed an older version of the assembly.

This error occurs often when we use C# HelperClass to support the orchestrations, but can occur in other situations.

SOLUTION

Make sure that you have the last version of the assembly installed.

• Rebuild the solution.
• Deploy the correct solution.

Tags: BizTalk | Errors and Warnings, Causes and Solutions

To accomplish that you need to start Windows PowerShell from the Start menu, click Start, click All Programs, click Accessories, click the Windows PowerShell folder, and then click the Windows PowerShell item and type:

get-service BTSSvc* | foreach-object -process { SC.EXE config $_.Name start= delayed-auto}

Result:

Tags: BizTalk | PowerShell | Hosts

You can find his questions and my answers here. Where I talk a little about myself, about TeckNet Wiki and give some suggestions for other community members who hope to eventually become MVPs. This was the first time I was interviewed J, hope you like it!

Thanks Steef-Jan for inviting me to this interview, and congratulations for the great job that you have been doing for the BizTalk community.

Tags: TechNet | BizTalk Community

if (!System.Diagnostics.EventLog.SourceExists(sourceName))
{
System.Diagnostics.EventLog.CreateEventSource(sourceName, logName);
}
System.Diagnostics.EventLog.WriteEntry(sourceName, genericString.ToString(), logType);

However when I installed one BizTalk Application in a brand new environment I caught this error:

xlang/s engine event log entry: Uncaught exception (see the ‘inner exception’ below) has suspended an instance of service ‘My.Orchestrations.Orch(f0b8a3ff-15cd-03db-2c20-4530bda13468)’.
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: a69409e2-094c-4f5b-9dd6-f448eec3bd3c
Shape name: Response Error Construct Msg
ShapeId: 95ffeaaa-dd23-4c09-8e3e-7fcd07342a11
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.

Another typical error is: You receive the “Requested registry access is not allowed” error message when you try to create a custom event log

CAUSE

This problem occurs because the user account that you used to log on does not have sufficient permissions.
The first time that you call the EventLog.CreateEventSource() method to create a custom event log, the custom event log entry is created under the following registry subkey:

• HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog

To create this subkey entry, you must have permission to write. However, the regular user account does not have permission to write.

So, the user that runs the application must have administrative rights to create a new event log source or a new custom log.

SOLUTION

You need to grant permission to create a custom event log:

• Log on to the computer as an administrator.
• Click Start, click Run, type regedit in the Open box, and then click OK. The Registry Editor window appears.
• Locate the following registry subkey:
  • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog
• Right-click Eventlog, and then click Permissions. The Permissions for Eventlog dialog box appears.

• Click Add, add the user account or group that you want and set the following permissions: “Full Control”

Tags: BizTalk | Orchestration | Errors and Warnings, Causes and Solutions

• Check the correctly installation (in BizTalk Management Console and in the Global Assembly Cache (GAC))
• Correctly Application Binding
• Restart Host instances

I keep getting this error:

“There was a failure executing the receive pipeline: "Microsoft.BizTalk.DefaultPipelines.XMLReceive, Microsoft.BizTalk.DefaultPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Source: "XML disassembler" Receive Port: "IN_PORT" URI: "/MyService.WS/WebService_Provisioning.asmx" Reason: The document specification <Project.Schemas.MyRequest> from assembly <Project, Version=1.0.0.0, Culture=neutral, PublicKeyToken=776eb620b83c3d30> failed to load. Verify the schema for this document specification is deployed and is in the Global Assembly Cache.”

CAUSE

This error can happen for several reasons!!

• Your DLL was not correctly installed (not installed or missing from GAC).
• Misunderstanding in framework version that you used.
• Forgetting to restart services so that it reflects the new changes

SOLUTION

Because this error can happen for several reasons you may have many solutions to this problem. These are some steps that you should take to resolve the issue:

• Verify if the Assembly is correctly deployed (check if your DLL is in the BizTalk Management Console and in the Global Assembly Cache (GAC)). If the assembly was not found, you need to redeploy correctly the BizTalk Project or run gacutil to install the DLL in GAC.
• Verify if the Application Pool (in case of Service) is running and correctly configured.
• Verify the .NET Framework version of the Application Pool. If the application pool is running .NET Framework 2.0 and BizTalk solution is using other version of .NET Framework, at runtime it will not find the Assembly in GAC (.NET Framework version needs to be consistent.). In this case you need to change the .NET Framework version used in the BizTalk projects or change the Framework used in the App Pool.
• Restart host instances

However, there is another step which usually is not referenced!

If you are using a Request-Response Port, normally using WCF or SOAP adapter, making restart only to Host Instances is not enough. This type of port is running over BizTalkServerIsolatedHost so you need to also restart App Pool associated with your services.

Tags: BizTalk | Pipeline | Errors and Warnings, Causes and Solutions

When I was analyzing my BizTalk environment with BizTalk Server Best Practice Analyser tool, has appeared a warning that caught my attention:

Privilege Attribute Certificate (PAC) Signature Validation is Enabled on Server BTS2010LAB01.
On server BTS2010LAB01, Privilege Attribute Certificate (PAC) signature is enabled, which may cause some user-authentication delay

And led me to go deeper in trying to see what was causing this strange issue and I found a number of TCP settings that needs to be done (or is recommended) which can also prevent from occurring general network errors on BizTalk Server Environments.

In the scenario described in this series of articles we should apply the following TCP/IP settings:

• Disable the Scalable Networking Pack (SNP) features
• This needs to be done on the BizTalk Server and the SQL Server
• Disable Privilege Attribute Certificate (PAC)
• This needs to be done on the BizTalk Server and the SQL Server
• Check and if necessary increase the ephemeral ports and reduce the TCP re-use timeout setting
• This needs to be done only on the BizTalk Server

How to Disable the Scalable Networking Pack (SNP) features

Scalable Networking Pack (SNP) be used, under specific circumstances, to improve network performance, however, most environments do not have SNP capable network adapters/drivers. This can result in unexpected network problem which is why it is recommended to disable SNP unless a server can benefit from it.

To disable SNP features we need to:

• Disable TCP Chimney Offload in the operating system
• Use administrative credentials to open a command prompt.
• At the command prompt, type the following command, and then press ENTER:
• netsh int tcp set global chimney=disabled
• Disable RSS in the operating system
• Use administrative credentials to open a command prompt.
• At the command prompt, type the following command, and then press ENTER:
• netsh int tcp set global rss=disabled
• Disable NetDMA in the operating system
• Click Start, click Run, type regedit, and then click OK.
• Locate the following registry subkey, and then click it:
  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
• Double-click the EnableTCPA registry entry.
• Note: If this registry entry does not exist, right-click Parameters, point to New, click DWORD Value, type EnableTCPA, and then press ENTER.
• To disable NetDMA, type 0 in the Value data box, and then click OK.

To determine the current status of SNP features, follow these steps:

• Use administrative credentials to open a command prompt.
• At the command prompt, type the following command, and then press ENTER:
• netsh int tcp show global

Note: you need to restart the computer first.

How to Disable Privilege Attribute Certificate (PAC)

The Privilege Attribute Certificate (PAC) is a function invoked within the Windows security system when you log on to a system utilizing Kerberos. It is a network authentication protocol.

The Kerberos Privilege Attribute Certificate (PAC) contains all of the group memberships for the security principal requesting access to a resource. PAC validation means a more secure environment so why should be disabled?

When you run a high-volume server program on a domain member that uses Kerberos to authenticate users, you experience a delay in the user-authentication process. Additionally, you notice an increase in the remote procedure call (RPC) traffic between the domain controller that uses the Net Logon RPC interface and the server. This problem occurs because the Kerberos client verifies the Privilege Attribute Certificate (PAC) signature in the Kerberos ticket by using the domain controller. The Kerberos client performs this verification to prevent PAC spoofing. The increased network traffic is generated by the RPC requests that are part of this verification process.

To disable PAC we need to:

• Click Start, click Run, type regedit, and then click OK.
• Locate the following registry subkey, and then click it:
  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Kerberos\Parameters
• Add the following registry entry
• Right-click Parameters, point to New, click DWORD Value, type ValidateKdcPacSignature, and then press ENTER.
• To disable PAC, double-click the ValidateKdcPacSignature registry entry and type 0 in the Value data box, and then click OK

How to Check and if necessary increase the ephemeral ports and reduce the TCP re-use timeout setting

When a client initiates a TCP/IP socket connection to a server, the client typically connects to a specific port on the server and requests that the server responds to the client over an ephemeral, or short lived, TCP or UDP port.

Under certain conditions it is possible that the available ports in the default range will be exhausted. If this occurs the following symptoms may be observed:

• Client applications may fail to connect to the BizTalk Server.
• The BizTalk Application service may fail to connect to a remote SQL Server.
• BizTalk Server adapters may fail to connect to a remote server.

To verify that one or more client applications are not generating excessive TCP/IP socket connections perform the following on the BizTalk servers in the group:

• From a command prompt window execute “netstat -ano -p tcp”.
• Count the number of unique Local Address TCP ports open above 1024 for each IP address.

If less than 3000 ephemeral ports are currently in use then it’s fine. (Original source: Recommended Platform Configuration for BizTalk Server by Abdul Rafay)

You can check or modify these settings at the HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters registry key. The recommended values are:

• Registry name: MaxUserPort
• Value: 0xFFFE (65534)
• Comment: Prevents port exhaustion
• Registry name: TcpTimedWaitDelay
• Value: 0x1E (30)
• Comment: Release unused ports as quickly as possible

Or you can view the dynamic port range by using the following netsh commands:

• netsh int ipv4 show dynamicport tcp
• netsh int ipv4 show dynamicport udp

On all BizTalk servers running on Windows Server 2008, Microsoft recommend not modifying the dynamic port range. However, if you determine that additional dynamic ports are needed you can also use netsh command to modify these settings, as follows:

• netsh int <ipv4|ipv6> set dynamic <tcp|udp> start=number num=range

This command sets the dynamic port range for TCP. The start port is number, and the total number of ports is range. Example:

• netsh int ipv4 set dynamicport tcp start=10000 num=1000

These sample commands set the dynamic port range to start at port 10000 and to end at port 11000 (1000 ports).

Important notes:

• The minimum range of ports that can be set is 255.
• The minimum starting port that can be set is 1025.
• The maximum end port (based on the range being configured) cannot exceed 65535.

See Microsoft Help and Support

At the end you should restart BizTalk and SQL Servers.

Other sources TCP settings that can impact BizTalk Server

Related Links

• Installing BizTalk Server 2010 in a Basic Multi-Computer Environment – Installation scenario (Part 1)
• Installing BizTalk Server 2010 in a Basic Multi-Computer Environment: The need for a Domain Controller – Windows Groups and Service Accounts (Part 2)
• Installing BizTalk Server 2010 in a Basic Multi-Computer Environment: Preparing Computers for Installation – Important considerations before set up the servers (Part 3)
• Installing BizTalk Server 2010 in a Basic Multi-Computer Environment: Preparing and Install SQL Server 2008 R2 machine (Part 4)
• Installing BizTalk Server 2010 in a Basic Multi-Computer Environment: Preparing and install prerequisites on BizTalk Server 2010 machine (Part 5)
• Installing BizTalk Server 2010 in a Basic Multi-Computer Environment: Testing environment connectivity’s (Part 6)
• Installing BizTalk Server 2010 in a Basic Multi-Computer Environment: Install and configure BizTalk Server 2010 machine (Part 7)

Tags: BizTalk 2010 | Installation | Configuration

Já está disponível a 33ª edição da Revista PROGRAMAR, uma publicação digital gratuita com diversos artigos relacionados com desenvolvimento de software.

Esta edição contém um artigo da minha autoria sobre o editor de mapas do BizTalk Server e têm como objectivo explicar como os mapas são processados internamente pelo motor do produto à medida que exploramos o editor de mapas do BizTalk Server.

Espero que gostem! E aproveitem para dar a sua opinião votando nos 3 melhores artigos desta edição aqui.

Outros conteúdos desta edição:

• Tema de capa
  • Kinect Hack
• A programar
  • Geração de Números Aleatórios – Parte 3
  • Programação Orientada aos Objectos em Pascal
  • Herança com JavaScript
  • CORE DUMP – Ambientes Produtivos
  • Enigmas de C#: Disposable Structs
  • SQL Azure Federations na Pratica
• Visual (Not) Basic
  • VISUAL (NOT) BASIC -Iterators
• Comunidades
  • BizTalk Server – Princípios Básicos dos Mapas – Parte 2
  • Desenvolvimento em SharePoint 2010 – Parte 2

Tags: BizTalk | Articles

As soon I find new errors and solutions, I’ll try to keep this list updated. However I challenge you all to add new content to this topic making it always up to date.

I know that there are still many errors and solutions that are not here….

TechNet Articles  >  BizTalk: List of Errors and Warnings, Causes and Solutions

See also BizTalk Server Resources on the TechNet Wiki

Tags: BizTalk | Wiki