BizTalk blog posts 02/2013 - 05/2013

The past time I haven't posted a lot on this blog, especially not much blog posts on BizTalk subjects. This doesn't mean that I haven't done any BizTalk related blog posts, I just haven't done it on my personal blog for a while... I've mostly posted on my companies blog, where I am the sole contributor and administrator.

But for all of you loyal readers of my personal blog, I thought it would be nice to give an overview of all of my latest posts. I'm thinking of doing this every once in a while to keep all of you updated on ALL of my posts.

So here goes for the period till May 2013...

• BizTalk error: ‘The message found multiple request response subscriptions’: solution to sending messages to multiple request-response send ports
• BizTalk file mask difference for windows 7 and windows server 2008 r2: A difference in file mask usage between windows 7 and windows server 2008 r2
• BizTalk360 v6.0: new features explained: a quick view on some of the improvements introduced in the new BizTalk360 version 6.0
• BizTalk Server 2013 is now RTM!: the announcement of the new BizTalk version release on MSDN, with the new features listed
• BTS2013 features explained: XslCompiledTransform: I started a new series on viewing some of the new features of BizTalk 2013 in more detail, the first one was about the XslCompiledTransform
• BTS2013 features explained: Improvements in dynamic send ports: follow up post on a new BizTalk 2013 feature on the Improvements in dynamic send ports
• BTS2013 features explained: Dependency tracking: an in depth view of the new dependency tracking feature of BizTalk 2013
• First Cumulative Update for BizTalk 2013… available through Microsoft Update!: the announcement that the very first cumulative update was released for BizTalk 2013, and that it even was available through Microsoft Update
• BAM error: Failed to list permissions for BAM view – System.Data.SqlTypes.SqlNullValueException: Data is Null: a solution to a BAM issue I encountered

Hope you enjoy these blog posts!

Error on Calendar/Contacts sharing in Outlook

I 've encountered a problem sharing Contacts from within Outlook. We were trying to share a contactgroup where both parties are from the same company, so on the same Office365 license.
However, on trying to send out a share request we stumbled upon following error:

"Problem: Your organization's policy does not allow you to share with this recipient."

At first it seemed that there should be anything wrong with the organizations settings made in office365. But nothing strange was configured there... Setting the permissions to the other mail addres did seem to work. What got me questioning there would be anyhting wrong in the configurational settings.

It turned out there was a difference when trying to share the contact or setting the permission. And after realising this, even sharing the contact worked just fine... without changing any of the configuration settings!

Solution

What turned out to be the problem than?

when the user started typing the recipient name in the "To" box of the "Share invitation" dialog, the recipient was picked up by autocompletion. However, the autocompletion picked up the recipient from the Contacts instead of from the Global Address List. So the name of the recipient appeared as "User Name <user@company.com>", where it had to be "User Name" when you choose from the Global Adress list.

So on sending the email invitation to share the contact list, Microsoft Exchange considered the recipient to be outside the organization. Which resulted in the above error message of course.

key file authentication with the BizTalk SFTP adapter

Authentication on an SFTP location can be done with simple username/password credentials… However another way to authenticate the sender is by using a Key Authentication file. But how can this last authentication method be used inside the BizTalk SFTP adapter?

the BizTalk SFTP adapter we used to achieve this is the  freely available SFTP adapter on Codeplex. Just download the adapter and install it. And don’t forget to add the adapter in the BizTalk admin console of course.

Now then let’s set up the port in BizTalk. In my example I ‘ve configured a receive location, but obviously the same goes for the send port configuration.

First of all choose the created adapter in the biztalk admin console, as shown below.



To set up the proper configuration for the SFTP port, just press the ‘Configure’-button.



These parameters need to be set:

• Schedule: define a timely schedule how often you want to poll the SFTP location (receive location only)
• File Mask: set the correct file mask
• SSH Host: the host address of the SFTP location
• SSH Identyfile: Select the Key authentication file on disk
• SSH Identyfile Passphrase: the password of the selected key authentication file
• SSH Remote Path: the path on on the SFTP location
• SSH User: the user name to authenticate on the SFTP location

Seems pretty straight forward, doesn’t it?
Well there are some things you ‘ll need to take into account to make sure the connection can be made…

Make sure the identyfile type is supported

You’ll need to make sure the identyfile type is supported by the library. The supported versions can be found here. As this is the library which is used by the bizTalk SFTP adapter.

Make sure the identyfile can be recognized

In my case for example, I got an *.ppk file as authentication file. But as it turned out, this wasn’t recognized.
The error message you git is this:

invalid privatekey: D:\tempkey.ppk

Which in the end seemed a bit misleading, as the problem wasn’t the private key for the authentication file. It was just the *.ppk file that wasn’t supported.
To make the key authentication file working, I had to convert the file to an OpenSSH key file. This can be done by using PuttyGen for example, and exporting the authentication file as an OpenSSH key file.

Don’t use both password parameters

Also make sure you only use the intended parameter SSH Identyfile Passphrase, and leave the SSH password blank.
In case both password fields are filled, the SFTP adapter will try to authenticate by the username/password credentials stated. So it won’t offer the specified identyfile to authenticate.




I orignally posted this on my companies blog: http://blog.cnext.eu/2013/02/19/using-key-file-authentication-with-the-biztalk-sftp-adapter/

Error: The self-extracting zip file is part of a multidisk zip file

I tried to install the Cumulative update package 14 for SQL Server 2008 R2.

After requesting the update on http://support.microsoft.com/kb/2703280, I got an email containing a link to download the file 449383_intl_x64_zip.exe. After downloading the file an trying to run the self extracting zip file, I got following error:

This self-extracting zip file is part of a multidisk zip file. Please insert the last disk of the set.

There is no other option than pressing the OK-button.And after pressing the OK-button 3 times, I got following error message:


An error occured while unzipping. One or more files were not succesfully unzipped. The error code is 110.

The solution for this seemed to be to just download the file from the given link in my email again.
After this I could succesfully run the self-extracting zip file an install my cumulative update package.

SQL Server Configuration Manager - Error 0x80041010

When opening the SQL Server Configuration manager (for SQL Server 2008 R2 in my case), I kept getting following error:

Cannot connect to WMI provider. You do not have permission or the server is unreachable. Note that you can only manage SQL Server 2005 and later servers with SQL Server Configuration Manager. Invalid class [0x80041010]

The solution to resolve this turned out to be quite simple. Just open a command prompt and execute following command:

C:\Program Files\Microsoft SQL Server\100\Shared>mofcomp "C:\Program Files\Microsoft SQL Server\100\Shared\sqlmgmproviderxpsp2up.mof"

Depending on the SQL version installed the path to the file could also be something like C:\Program Files\Microsoft SQL Server\90\Shared\sqlmgmproviderxpsp2up.mof

Error on attaching DB

When trying to reattach a database I kept getting following error:

In the SQL log I could find below error. The same error was given when trying to attach the DB with a T-SQL statement.

Msg 5120, Level 16, State 101, Line 3 Unable to open the physical file "E:\Program Files\Microsoft SQL Server\MSSQL10_50.BTSISDEV1\MSSQL\DATA\BizTalkMsgBoxDb.mdf". Operating system error 5: "5(failed to retrieve text for this error. Reason: 15105)".

After several attempts on how to solve this I finally found the solution.
Turned out, all I needed to do was run the SQL Server Management Studio as an Administrator.
How can it be that simple, yet has me looking for a solution for over an hour :).

Promote using Correlation initialisation inside a loop

I assume you already know how to promote properties when sending a message from an orchestration to the messagebox.
This can of course be achieved by initializing a correlation set with containing all context properties you like to promote. But that 's not why I'm posting this blog. If you need more info on how to promote properties from an orchestration I'll refer you to this blog.

Problem

The problem is when you try to do this from a send shape inside a loop, you'll get an error when building the project in visual studio.
The received error is "Correlation set may be initialized only once".

Solution

The solution to this issue is actually real easy. All you have to do is create a scope inside the loop. And place the send shape (and even other shapes if needed) in the created orchestration. The benefit of the orchestration is that you can define the correlation set on the scope itself (instead of as a global correlation set).
Now can initialize your correlation set on your send shape inside the scope.

And that's all you'll have to do!! It really is that easy! :)

SAP calling RFC hosted in BizTalk

 I've configured a SAP receive port in BizTalk. However when trying to enable the receive location I got some errors in the error log saying ' 'saprfc.ini' failed: 'No such file or directory' '.  Here is the full error message:

The Messaging Engine failed to add a receive location "RECEIVE MIXED ERIKS SAP" with URL "sap://CLIENT=900;LANG=EN;@a/SAPSERVER/00?GWSERV=sapgw00&ListenerDest=TRADCOMSAPDEST&ListenerGwServ=sapgw00&ListenerGwHost=194.178.122.5&ListenerProgramId=TRADCOMSAPPROG&RfcSdkTrace=False&AbapDebug=False" to the adapter "WCF-SAP". Reason: "Microsoft.Adapters.SAP.RFCException: Details: ErrorCode=RFC_OK. ErrorGroup=RFC_ERROR_SYSTEM_FAILURE. SapErrorMessage=Open file 'saprfc.ini' failed: 'No such file or directory'.  AdapterErrorMessage=Error accepting incoming connection. RfcAccept returned RFC_HANDLE_NULL..

Apparently this file is used in the RFC library of SAP:
“The RFC library will read the saprfc.ini file to find out the connection type and all RFC-specific parameters needed to connect to an SAP system, or to register an RFC server program at an SAP gateway and wait for RFC calls from any SAP system.”

How to solve this issue?

First of all you'll need to create a System Variable called RFC_INI. To manage the Environment Variables you'll need to open the system properties and select 'Environment Variables...', as shown below.

Then create the new system variable RFC_INI with a filepath as value, for example C:\SAPINI\saprfc.ini.

 

Next we need to add the contents to our saprfc.ini file.  The values that I needed to provide include: 

Field	Value	description
DEST	TRADCOMSAPDEST	In this case, this is the name of the RFC Destination that our BASIS team created for us from SM59.  More details here.
TYPE	R	Type R is for RFC server programs or for a client program working with another external program as RFC server program which is already registered at an SAP gateway.
GWHOST	SAP_HOST_NAME	In my case, this is the name of the physical server that his hosting the SAP Gateway.
GWSERVER	SAP_GATEWAY_NAME	The name of the SAP Gateway.  A standard naming convention is: SAPGW## where ## is the system number for the SAP instance that you are working on.
PROGID	TRADCOMSAPPROG	This is the name of the Program ID that has also been provided by BASIS.

When you compare the data between the Receive Location and the saprfc.ini file, you'll see a certain symmetry between the two.  However, the values in the ini file take precedence.<br />

 
You'll need a restart of the BizTalk host instance, the one defined on the SAP adapter, for the changes to take effect.
This should be all to resolve the issue.

Source: Kent Weare's BizTalk Blog: SAP calling RFC hosted in BizTalk

Task Scheduler failed to start: Error Value: 2147943645

We have a script scheduled using the Task Scheduler. Now we realised however that the script hadn't run for a while.

when analyzing the scheduled task, we couldn't find any issue... the task was currently running.
However, when we reveiwed the history of the task we noticed there was an error each time it tried to run the task.
The error just said : 'Task Scheduler failed to start "YourScript" task for user "yourUser". Additional Data: Error Value: 2147943645.'

The error message doesn't say much useful. But what does it mean?
Turned out the solution was quite simple: it just means you are trying to run a job with the “Run only when user is logged on” flag set.

This also explains why the job was running succesfully when we checked the task, since we were logged in as the configured user. A real simple solution for a meaningless error message.

List of Biztalk Errors and warnings: causes and solutions

On the techNet wiki there is a new post on BizTalk errors and warnings.
The article is yet to be expanded.

The point is to get a complete list of possible BizTalk errors and warinings with their causes and solutions for all stages/components.
For now the list is still rather limited, but with the contribution of all of you this list can become complete.

List on TechNet Wiki: BizTalk: List of Errors and Warnings, Causes and Solutions

Error 0xC0002A1F in BizTalk installation

During the BizTalk installation I got the error code '0xC0002A1F' when configuring the installation using the Microsoft BizTalk Server Configuration Wizard. There wasn't any error description given, only the code 0xC0002A1F which of course didn't was of much help.

Turned out this error code meant the following:

Error Code: 0xC0002A1F, Cannot perform encryption or decryption because the secret is not available from the master secret server. See the event log for related errors.

This of course was much clearer. It was clear I needed to restore the Master Secret needed of the SSO (Single Sign-on).

After restoring the master secret, all worked well.

Error when configuring the BizTalk runtime

I was installing BizTalk 2010 at home and ran into an error when configuring my BizTalk Server installation with the Microsoft BizTalk Server Configuration wizard. Configuring the BizTalk Runtime gave me following error:

The Microsoft Distributed Transaction Coordinator (MSDTC) may not be configured correctly. Ensure that the MSDTC service is running and DTC network access is allowed on the BizTalk, SQL and SSO Master servers. For more information, see "MSDTC Configuration settings required for BizTalk Server" in the BizTalk Server Help.

To solve this issue, I did the following:

Go to Component Services (Click Start, click Run, and type dcomcnfg to launch the Component Services Management console).
Next, Click to expand My Computer, click to expand Distributed Transaction Coordinator, right-click Local DTC, and click Properties, as shown below.

Now Click the Security tab of the Local DTC Properties dialog.

If either the Mutual Authentication Required or the Incoming Caller Authentication Required configuration options are enabled then the client(s) computer account must be granted the Access this computer from the network user right. If the computer account for a client computer is not granted the Access this computer from the network user right, or is included in the Deny access to this computer from the network user right, then DTC communication between the client and server computer will fail.

These changes caused to give me following error:

New transaction cannot enlist in the specified transaction coordinator

The solution for this is to change the setting under Transaction Manager Communication to “No Authentication Required".
So the MSDTC Security configuration now looks like this:

Using DocumentSpecName of the pipeline configuration

A schema can be defined in the 'DocumentSpecName' attribute of the pipeline configuration properties (in the dissamble stage).
When no schema is defined and there are multiple schema's with the same combination for 'Target Namespace' (optional) and 'Root Name', you 'll get following error in the receive pipeline:

There was a failure executing the receive pipeline: "<ReceivePipeline>" Source: "XML disassembler" Receive Port: "<ReceivePortName>" URI: "<URI>\*.xml" Reason: Cannot locate document specification because multiple schemas matched the message type "<TargetNameSpace><RootName>".

The use of "DocumentSpecName" attribute in the configuration section of the pipelines is there to direct the pipeline to validate the message against a specific schema in the given assembly. The attibute should be filled with the schema full name ('<schema type>, <schema assembly>') as shown in below figure. This should solve the above error.

The issue becomes more complex when using multi-part schemas. In htis situation you'll get following error:

There was a failure executing the receive pipeline: "<ReceivePipeline>" Source: "XML disassembler" Receive Port: "<ReceivePort>" URI: "<URI>\*.xml" Reason: No Disassemble stage components can recognize the data .

What BizTalk want to tell us is that at this stage, given the specific configuration of DocumentSpecName Attribute, in the well known syntax of "<schema type> ,<schema assembly full name>" is not enough for multipart schemas.

Turns out that there should be an additional value is needed in the DocumentSpecName-attribute to fully define the schema. So the above value syntax is not enough, it will direct the pipeline to the desired schema in the assembly, but it doesn't say which root it should validate against.

The correct syntax in this case is : "<schema type>+<root name> ,<schema assembly full name>"
So by adding the root name after the '+' -sign solves the issue for multipart-schemas (schemas with multiple root nodes).

BTS Project build error on string message

Today Is was making an orchestration that contains a Multi-Part message type, with a message part of type System.String. When building the BizTalk Project it returned the error "'System.String' must be Xml serializable to be a message part type". I've tried several things, but it kept giving this same error no matter what I tried. But I was certain I had used System.String parts in an orchestration before, without any problems. So after some debugging, I tried restarting Visual Studio... and this seemed to do the trick! Apparantly all ik took to succesfully build the biztalk project was restarting Visual Studio.

Visual Studio: VS templates missing

I was unable to add an aspx page to my web site solution.
The error I got from Visual Studio was:

"Could not find file 'c:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\ItemTemplatesCahce\Web\Csharp\1033\WebForm.zip\WebForm_cb.aspx'."

This was the solution:

1. Open "Visual Studio 2008 Command Prompt"
2. Run the command: "devenv /installvstemplates"

And that was all to solve my problem!

Biztalk Error: The system cannot find the file specified (Exception from HRESULT: 0x80070002)

Each time I tried to test my new mapping using BizTalk I got this error: The system cannot find the file specified (Exception from HRESULT: 0x80070002).

So the full error in the event viewer looked like this:

A message received by adapter "FILE" on receive location "RECEIVE ORDERS PCE FILE" with URI "C:\B2B.TRADCOM.COM\ORDERS\INBOUND\PCE\*.xml" is suspended.
Error details: The system cannot find the file specified. (Exception from HRESULT: 0x80070002)
MessageId: {F83F1E4B-3B09-4F9B-A9D5-F6C1BD5C2698}
InstanceID: {E162E5AB-E621-4EA1-B643-FD843D7F8D44}


I was able to map the message using Visual Studio, so I was quite sure my BizTalk mapping was correct.

Now it turned out that I forgot to sign the assembly. So the system was unable to place the assembly in the GAC. Because I used a deploy script I didn't notice the resulting warning.

Dependency service or group failed to start

I got following error when I tried to start the SQL Server service:

My SQL service is running on my domain user account, and this is the reason I got the error. To be able to run any services using a domain account, the Netlogon service must be started.
For some reason (I blame the windows updates that were installed) this services startup type was changed to Disabled. Reconfiguring the Netlogon service to automatic and start the service solved the problem.

info
Netlogon: Maintains a secure channel between this computer and the domain controller for authenticating users

CU 1 voor de BizTalk-Adapter Pack 2010

This cumulative update for Microsoft BizTalk Adapter Pack 2010 contains hotfixes for Microsoft BizTalk Adapter Pack 2010 issues that were resolved after the release of BizTalk Adapter Pack 2010.

It contains following hot fixes:

• FIX: The WCF-SQL adapter from BizTalk Adapter Pack 2.0 or from BizTalk Adapter Pack 2010 does not write enough useful error information
• FIX: A WCF-based SQL adapter may lock SQL Server resources when the PolledDataAvailableStatement binding property returns a positive result but the actual polling does not return any data
• FIX: Statement in the PollStatement property incorrectly runs if a receive location uses WCF-based BizTalk Adapter for SQL Server
• FIX: An update is available that adds the ClearRfcContext binding property to the WCF-based SAP adapter from BizTalk Adapter Pack 2.0 or BizTalk Adapter Pack 2010
• FIX: Multiple grouped IDOCs are processed incorrectly if the WCF-based SAP adapter in BizTalk Adapter Pack 2.0 or BizTalk Adapter Pack 2010 uses the String setting to connect to an SAP system
• Hotfix to add the "ReceivedIdocRelease" binding property for the WCF-SAP adapter to BizTalk Adapter Pack 2.0 and Microsoft BizTalk Adapter Pack 2010

SOURCE: http://support.microsoft.com/kb/2539794/en-us

VS2008: web services enumeration components not available

Recently I got following error when trying to add a Web Reference to VS2008:
The web services enumeration components are not available. You need to reinstall Visual Studio to add web references to your application.

I have no idea why this error suddenly appeared.
However, I did find a solution to this issue.

I executed 'devenv /ResetSkipPkgs' from the command line in a VS2008 command prompt.
This did the trick for me.

Resolving Schema type Name error

I've downloaded the xCBL 3.5 schema from their webiste.

When just including the Order.xsd schema in a BizTalk Project, I got following error when building the solution:

Node "<schema>" - This schema file has a TypeName that collides with the RootNode TypeName of one of its root nodes. Make sure that they are different.

Now, the reason for this is quite simple - when the project is compiled, a .NET class will be generated for each top level element in your schema. If you have two schemas which share the same top level element name a clash will occur.

The solution is to change the generated type name for the schema. To do so, select the schema in the Solution Explorer and press F4 to display the Properties window. Then change the Type Name property so that it is not the same as any of the top level elements.