How to fix BizTalk Server 2016 SSO Administration Console with PowerShell
Have you ever noticed that your SSO Administration Console tool doesn't open in BizTalk Server 2016 Fortunately for Microsoft BizTalk Server team this
Cannot perform encryption or decryption because the secret is not available from the master secre...
Another treasure from my blog backlog: Cannot perform encryption or decryption because the secret is not available from the master secret server When
Visual Studio error: Unable to find transmitPipeline.vstemplate. Please repair the product to fix...
My blog backlog is full of precious things and I stop counting the number of pages I have on my OneNote to be published Today I randomly selected this Unable
Backup BizTalk Server job failed. Executed as user NT SERVICE\SQLSERVERAGENT. Cannot open backup ...
Another day, another error to report directly retrieved from my backlog to be published Today is about another error that can happen on the Backup BizTalk
BizTalk WCF-ORACLEDB error: This is because either (a) ambient transaction is present and the TNS...
Another day, another error to report – still have plenty of them in my backlog to be published, they are an “easy and quick way” to publish something on
BizTalk Administration Console: An internal failure occurred for unknown reasons (WinMgmt) fixed ...
Last month I wrote a blog post regarding the “An internal failure occurred for unknown reasons (WinMgmt)” error in the BizTalk Server Administration
Demystify Invalid type name error on BizTalk Schemas (Part II)
In the last post, we try to demystify the reason and cause of the error: Invalid type name The root node type has to be a valid C# identifier when you are
Demystify Invalid type name error on BizTalk Schemas (Part I)
A few days ago, while trying to compile a BizTalk Server solution I got the following error: Invalid type name The root node type has to be a valid C#
Visual Studio: Failed to create window handle for pane while trying to open a Schema
There are errors that we are familiar with, but I guess this you may never hear about it I didn't know it until today: Failed to create window handle for pane
BizTalk FILE Adapter Error: File transport does not have read/write privileges for receive location
In the spirit of documenting all possible and imaginary errors, let's address today a classic one: File transport does not have read/write privileges for