Error when trying to validate EDI message against the schema: [29] Invalid count specified at interchange, group or message level

Error when trying to validate EDI message against the schema: [29] Invalid count specified at interchange, group or message level

by | Jul 10, 2012 | BizTalk Community Blogs via Syndication

As I mentioned in my last post, when we are in the development phase of a BizTalk project is normal to validate test instances of messages that are provided with respective schemas before we make final tests, the same happens when we are dealing with EDI (EDIFACT) messages. When we perform this validation, we can […]
Blog Post by: Sandro Pereira

Great Post on How SharePoint 2010 Load Balancing Works

by | Jul 10, 2012 | BizTalk Community Blogs via Syndication

Overview
In reviewing our client’s SharePoint 2010 / FAST farm topology, a lot of questions came up about how load balancing works in SharePoint 2010.  I came across blog post entitled: How I Learned To Stop Worrying and Love The SharePoint Topology Service by Josh Gavant. 
It’s an excellent read and goes into some detail about […]
Blog Post by: Michael Gerety

Workaround For Enable-WSManCredSSP:This command cannot be executes because the setting cannot be enabled.

by | Jul 10, 2012 | BizTalk Community Blogs via Syndication

Overview
I came across an infuriating issue today after trying to re-enable WSManCredSSP after disabling it to get screenshots for my last blog post on setting up PSRemoting. (you’re welcome!)
When attempting to execute Enable-WSManCredSSP I got the following error:
Enable-WSManCredSSP : This command cannot be executed because the setting cannot be enabled. This can happen if no […]
Blog Post by: Michael Gerety

Error when trying to validate EDI message against the schema: [71] Transaction Set or Group Control Number Mismatch

Error when trying to validate EDI message against the schema: [71] Transaction Set or Group Control Number Mismatch

by | Jul 9, 2012 | BizTalk Community Blogs via Syndication

When we are in the development phase of a BizTalk project is normal to validate test instances of messages that are provided with respective schemas before we make final tests, the same happens when we are dealing with EDI messages. When we perform this validation, we can detect if some enumerators in the existing EDI […]
Blog Post by: Sandro Pereira

Setting Up PSRemoting to Allow PowerShell Script Execution on SharePoint 2010 Server from FAST Search Server 2010

by | Jul 9, 2012 | BizTalk Community Blogs via Syndication

Overview
This post describes setting up PSRemoting to allow execution of PowerShell commands on your SharePoint 2010 Server instance from your FAST Search server instance.  These instructions should work however between any two machines on the same domain.
Setting Up PSRemoting
Enabling PSRemoting
First, PSRemoting needs to be enabled on both the FAST and SharePoint servers.  Launch a PowerShell […]
Blog Post by: Michael Gerety

Fixing “Cannot find type [Microsoft.SqlServer.Management.Smo.Server]” during FAST Search backup

by | Jul 9, 2012 | BizTalk Community Blogs via Syndication

Overview
While attempting to execute a FAST Server back-up following the directions on TechNet, we ran into the following error:
Cannot find type [Microsoft.SqlServer.Management.Smo.Server]: make sure the assembly containing this type is loaded.

This was an issue we hadn’t experienced in production, and were unsure how to resolve.
Solution
After searching around for a while, I found the following post […]
Blog Post by: Michael Gerety

Five Rules to Simplify Large Scale BizTalk Orchestration Development

by | Jul 9, 2012 | Stephen's BizTalk and Integration Blog

Many times on larger BizTalk projects developers need to share working inside Projects and Orchestrations. This means at some point you will have conflicts. While Visual Studios offers the option to Auto-Merge files, I have not seen this done successfully with BizTalk Orchestrations.

Here are 5 simple rules for simplifying and streamlining large scale BizTalk Orchestration Development.

  • Rule #1 – Do not use the default Operation Name on Orchestration Ports
    • When using Direct Routing Port out of an Orchestration, by default only two properties are routable. Those are MessageType and Operation. If you leave Operation as the default value of Operation_1 all the Ports created will be the same.
    • Operation is one of the most important properties that can be used for routing so make sure it is useful.
  • Rule #2 – Always set up Port Types the right way the first time around
    • If using Direct Routing, always use Direct Routing locally. I see a lot of Specify Now or Specify Later that turns into Direct Routing later on. This causes Binding File changes and could mask errors in routing.
  • Rule #3 – Define all your messages as Multi-Part messages
    • Eventually, the message type of a message used inside the Orchestration will need to change. Ensuring all Messages are setup as Multi-Part messages will make this change trivial as compared to having to change break port connections, change port types, update and message variables.
  • Rule #4 – Ensure each developer has the same folder structure for testing locally
    • This helps simplify changes to binding files. If all the developers use the same structure, a common set of development binding files can be stored in TFS.
  • Rule #5 – Smaller units of work
    • Try to break Orchestrations into small units of work and leverage the Call Orchestration shape. This allows more than one person to work on larger processes and ensures simplified testing. Just ensure the performance hit of using the Call Orchestration is going to be acceptable. While I have not done the testing myself, I think it is a very optimized call and not something I would be worried about in most cases

WikiNinjas – Official Blog of TechNet Wiki

by | Jul 9, 2012 | BizTalk Community Blogs via Syndication

The official blog of TechNet Wiki contains multiple posts on what drives the community collaborating on the TechNet Wiki. This blog is maintained by Wiki Ninja’s. This is a group of authors who celebrate and evangelize the community and social-authoring excellence that is known as TechNet Wiki.There are several categories the Wiki Ninja’s are writing posts for:

  • Monday – Interview with a Wiki Ninja
  • Tuesday – TNWiki Article Spotlight
  • Wednesday – Wiki Life
  • Thursday – Community Wins
  • Friday – International Update
  • Saturday – Top Contributors of the Week
  • Weekend Surprise

Every day there is a new post depending on day of the week. This blog site offers a great access point to explore what is being contributed on the TechNet Wiki and what drives the TechNet Wiki Ninja’s.

Since the end of last year I have written a couple of blog posts in a few categories. Below you will find a list of my blog posts:

Cheers,

– Steef-Jan Wiggers