The Curious Engineer

All blogs / Windows internals

Chris Forster

learn.microsoft.com/en-us/archive/blogs/chrisforster

The Online Home of Chris Forster

Windows internalsDistributed systems / cloudMicrosoft blogsMSDN archive

’10’15’20’25
Posts
21 from 10 Dec 2007 to 7 Feb 2011
Posting
archived, read-only
Kind
personal blog
Feed
https://learn.microsoft.com/en-us/archive/blogs/chrisforster/feed.xml

2011 1

  1. Windows Phone 7 (WP7) and Facebook

2010 3

  1. When using thread impersonation “DTCGetTransactionManagerEx”is failing from the MSDTC groups passive cluster node
  2. Reinstalling / Rebuilding COM+ on Windows 2008
  3. MSDTC communication is not working on a Windows 2008 Cluster when Incoming Caller Authentication or Mutual Authentication is required

2009 7

  1. Unable to view or change the properties (Tracing, Logging or Security settings) in Component Services for a clustered instance of MSDTC which resides in a SQL Server cluster resource group
  2. SubInACL Installation
  3. Knowing the limits (MSDTC participant / enlistment limits)
  4. MSDTC transaction statistics show a large number of aggregated “Unknown” and “Total” transactions when viewed from a remote machine
  5. Windows 2008 SQL Server Cluster (with MSDTC) when using the Windows Firewall with Advanced Security
  6. You cannot use or configure MSDTC on a Windows 2003 Cluster without a shared disk
  7. You cannot start transactions in an application running without administrative privileges on a Windows 2003 clustered Server

2008 6

  1. The "COM+ Event System" Service will not enter the "Started" State
  2. Moving a "MSDTC Cluster Resource" from the "Main Cluster Group" to its own "MSDTC Cluster Group"
  3. ACL Problem with the MSDTC service?
  4. WCF Transaction Flows
  5. MSDTC in Windows Vista and Windows Server 2008 - Removal of the "TIP" checkbox
  6. MSDTC in Windows Vista and Windows Server 2008

2007 4

  1. MSDTC Changes Since Windows 2003 SP1
  2. Embedding a Manifest File Using Visual Studio
  3. A solution and workaround to the change in manifest preference behaviour in Windows 2003 SP1 and Windows Vista
  4. A solution and workaround to the change in manifest preference behaviour in Windows 2003 SP1 and Windows Vista