SSO and BizTalk Server 2004 Services Fail Post-XPSP2 (KB841893)

If you’re running Biztalk Server 2004 on Windows XP (I recommend running in a VPC or Virtual Server on 2003), you will likely encounter errors after applying XPSP2 and/or enabling XP security services.

ConfigFramework may generate this error:

Failed to generate the master secret (error code 0x800706BF)

Upon starting the SSO service, the event log will report this error:

Event Type: Error
Event Source: ENTSSO
Event Category: Enterprise Single Sign-On
Event ID: 10555
Description: Secret server access denied. Client User: Domain\UserName

Note: Any component that tries to access the ENTSSO or BizTalk Server runtime services will get an "Access denied" error message, but no error written to the BizTalk Server event log.

This happens because the Remote Procedure Call (RPC) protocol is different post-SP2.

Microsoft issued a KB article “The Enterprise Single Sign-On Service and associated BizTalk Server 2004 services fail after you install Windows XP Service Pack 2 (SP2)” that addresses and resolves this issue.

About Michael Coates
I am a pragmatic evangelist. The products, services and solutions I write about fulfill real-world expectations and use cases. I stay up-to-date on real products I use and review, and share my thoughts here. I apply the same lens when designing an architecture, product or when writing papers. I am always looking for ways that technology can create or enhance a business opportunity .. not just technology for technology's sake. My CV says: Seasoned technology executive, leveraging years of experience with enterprise and integration architectural patterns, executed with healthy doses of business acumen and pragmatism. That's me. My web site says: Technology innovations provide a myriad of opportunities for businesses. That said, having the "latest and greatest" for its own sake isn't always a recipe for success. Business successes gained through exploiting innovation relies on analysis of how the new features will enhance your business followed by effective implementation. Goals vary far and wide: streamlining operations, improving customer experience, extending brand, and many more. In all cases, you must identify and collect the metrics you can apply to measure your success. Analysis must be holistic and balanced: business and operational needs must be considered when capitalizing on a new technology asset or opportunity.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: