Virtual PC console not showing up

VPC stored it’s configuration in the following file:

%APPDATA%\Microsoft\Virtual PC\Options.xml

Within that XML file, I found the following nodes: “left_position” and “top_position”

Reset “left_position” and “top_position” to 0 fixed the issue.

Directly querying the BizTalk database for suspended messages

SELECT
nvcName as ApplicationName,
DATEADD(hh,-6,dtSuspendTimeStamp) as DateSuspended, — Subtract the appropriate hours for your timezone
nvcAdapter as Adapter,
nvcURI as URI,
nvcErrorDescription as ErrorDescription
FROM InstancesSuspended
LEFT OUTER JOIN [Services]
on InstancesSuspended.uidServiceID = [Services].uidServiceID
LEFT OUTER JOIN Modules
on Modules.nModuleID = [Services].nModuleID
WHERE DtCreated between DATEADD(dd,-7,GETUTCDATE()) and GETUTCDATE()
and nErrorCategory=0
ORDER BY dtCreated desc

article source

http://geekswithblogs.net/bosuch/archive/2010/11/29/directly-querying-the-biztalk-database-for-suspended-messages.aspx

Project Reference Errors in BizTalk

While developing BizTalk projects that referencing several other projects, many errors will be shown while compiling the BizTalk Projects. These errors will go away once the references are removed and added again.

Also, sometimes, updated made in the referenced projects will not be updated automatically.

This is a known issue with BizTalk Server 2009 and after googling I found that Microsoft has given a Hot Fix for this which can be downloaded below link

http://support.microsoft.com/kb/977428

the original post is at

http://masteringbiztalkserver.wordpress.com/2010/12/01/project-reference-errors-in-biztalk/

How to debug Orchestrations from Visual Studio for biztalk 2009 using C# .cs file

An Orchestration *.odx file contains an XML file and code written in a language specific to BizTalk called X#.

You can easily find these, when you right click an orchestration and open it with XML Editor or Notepad.

XML Representation of the Orchestration is used by the Graphical Designer to show the shapes on the screen.

X# code is in turn converted to C# at runtime using XSharp.exe file and this C# assembly will be executed.

This C# file can be found inside \obj\Debug\BizTalk\Xlang\File0.cs once the project is built.

Unlike in earlier versions of BizTalk, only one .cs file will be created irrespective of number of orchestration you have in your project.

This File0.cs file has different sealed internal classes for each of the orchestration in your project.

To debug your orchestration or code written in an expression shape, open this File0.cs and keep a break point. Attach BizTalk Server to the BtsNTSvc Process.

Now you will be able to debug your orchestration using C# Code.

http://masteringbiztalkserver.wordpress.com/2011/02/21/debugging-orchestrations-in-visual-studio-2009-using-c-cs-file/#comment-21

modifying a BizTalk Message using C# or External Dll

http://masteringbiztalkserver.wordpress.com/2010/12/01/how-to-modify-a-biztalk-message-using-c-or-external-dll/

biztalk map documenter as HTML

http://biztalkmapdoc.codeplex.com/documentation

Enterprise SSO service start failure after installing VS2010

BizTalk and SSO was running smooth before the installation of VS2010 on my machine. I have a 64-Bit machine with Windows Server 2008 R2 and BTS 2009 installed. When I installed VS2010 my SSO was stopped and when I tried to start I started getting the error below

—————————
Services
—————————
Windows could not start the Enterprise Single Sign-On Service service on Local Computer.

Error 0×80131700: 0×80131700

To issue started because it unregisterd SSOSQL.dll which is found on C:\Program Files\Common Files\Enterprise Single Sign-On folder. To register it again run regasm on the VS command prompt from your 32-Bit machine.

regasm C:\Program Files\Common Files\Enterprise Single Sign-On\SSOSQL.dll

On my 64-Bit it worked by running the 64-Bit regasm which is found on C:\Windows\Microsoft.NET\Framework64\v2.0.50727.

So go to the framework64 folder from the command prompt and run

regasm C:\Program Files\Common Files\Enterprise Single Sign-On\SSOSQL.dll

How to speed up BizTalk Administration Console & SQL Server Management Studio Console at start up

#1# On internet explorer menu, click on Tools, options and go to the advanced tab
#2#Scroll down until finding security options
#3# Disable the Check for Publisher’s certificate revocation and Check for server certificate revocation options

#4# Open the SQL Server management studio console and enjoy the new world of speed

Warning

While this is a user setting, before applying this tip on production environment be sure there are no applications requiring this two settings to run successfully.

How subscriptions work in Biztalk

http://geekswithblogs.net/cyoung/articles/7007.aspx

how to skip debatching in xmlDisassembler

The XmlDisassembler pipeline component in BizTalk Server basically does three things:

promoting properties (including the message type)
validating incoming documents (if turned on)
disassemble batches into body messages

Sometimes situations can occur where you want to process an envelope message but you don’t want to have it disassembled into separate body messages.

For example when receiving a message that contains a lot of data in the header of the envelope that is needed in the body of a message further on in the process. You then ideally want to use a map to copy over this header data into another message. If the port receiving this message uses the XmlDisassembler component the envelope will be processed and the header information is “gone”.

You can of course promote everything in the header to the context but that leads to a lot of data in the context. Besides that a considerable amount of code (distinguished fields and xpath statements in expression shapes) is needed to get the context properties into the message later on.

Another and, in my view, more elegant way to do this is by setting the value of a special property to true on the context of the envelope message before it is processed by the XmlDisassembler. The property is called ‘PromotePropertiesOnly’ and resides in the ‘http://schemas.microsoft.com/BizTalk/2003/xmlnorm-properties’ namespace.

A very simple pipeline component can be used to do this:
public IBaseMessage Execute(IPipelineContext pContext, IBaseMessage pInMsg)
{
pInMsg.Context.Promote(“PromotePropertiesOnly”,
“http://schemas.microsoft.com/BizTalk/2003/xmlnorm-properties”, true);

return pInMsg;
}

After setting this property will still have the functionality of the XmlDisassembler (like property promotion, setting the message type, etc.) but the debatching is skipped.

The property is available and can be used in all versions of BizTalk Server (2004, 2006 (R2), 2009 and 2010).

Articile Source