Tips for BizTalk partyresolution demo

When you learn the BizTalk orchestration sample partyresolution @ Microsoft BizTalk Server 2010 \ SDK \ samples \ orchestrations \ partyresolution. there will be some problem prevent you keep on going, I listed some of the issues I met and hope can help my friends.

1. there was a failure executing the send pipeline: "Microsoft. samples. biztalk. projectschema. mimepartyressendpipeline, projectschema, version = 1.0.0.0, culture = neutral, publickeytoken = required "Source:" mime/smime encoder "Send Port:" sp_sendpotosupplier "URI:" C: \ Program Files (x86) \ Microsoft BizTalk Server 2010 \ SDK \ samples \ orchestrations \ partyresolution \ filedrop \ purchaseordertosupplier \ purchaseorder. XML "Reason: cocould not validate the trust chain of the signing Certificate. the certificate issuing authority may not be a trusted Certificate Authority.

Resolution:

You have to import the CA into the Trusted Root Certification of the computer.

2. there was a failure executing the send pipeline: "Microsoft. samples. biztalk. projectschema. mimepartyressendpipeline, projectschema, version = 1.0.0.0, culture = neutral, publickeytoken = required "Source:" mime/smime encoder "Send Port:" sp_sendpotosupplier "URI:" C: \ Program Files (x86) \ Microsoft BizTalk Server 2010 \ SDK \ samples \ orchestrations \ partyresolution \ filedrop \ purchaseordertosupplier \ purchaseorder. XML "reason: the mime encoder failed to sign the message because the certificate has private key protection turned on or the private key does not exist.

Please disable private key protection to allow BizTalk to use a certificate for signing.

Resolution:

As the error information told, you have to disable the private key protection. delete the private certification you have imported to your personal account certificates. re-import. pfx certification with the "enable strong private key protection. "option unselected.

3. there was a failure executing the send pipeline: "Microsoft. samples. biztalk. projectschema. mimepartyressendpipeline, projectschema, version = 1.0.0.0, culture = neutral, publickeytoken = required "Source:" mime/smime encoder "Send Port:" sp_sendpotosupplier "URI:" C: \ Program Files (x86) \ Microsoft BizTalk Server 2010 \ SDK \ samples \ orchestrations \ partyresolution \ filedrop \ purchaseordertosupplier \ purchaseorder. XML "reason: the revocation status is unknown for the certificate used to sign the message. this might be because the Certificate Authority is offline.

Resolution:

This is mainly because BizTalk Server doesn't know the revocation status of the private certificate is unknow. you have to import the latest Delta CRL (Certificate Revocation List) into the Trusted Root Certification of the computer.

4. Destination party not found while attempting to send message 'poackmessage' to (s-1-5-7, organizationname ).

Exception type: destinationpartynotfoundexception Source: Microsoft. xlangs. biztalk. engine target site: void writemessagestate (Microsoft. biztalk. interOP. ibtpepinfolookup, system. guid, Microsoft. xlangs. basetypes. xlangmessage, Microsoft. xlangs. core. segment, system. string, system. string, system. collections. ilist, Boolean, system. collections. ilist)

Cause: the Party resolution Pipeline component resolves the sender certificate or the Security ID (SID) to the correct sourcepartyid. however, the party resolution Pipeline component marks the originatorpid context property of the message as "s-1-5-7 ". this notation corresponds to anonymous or guest.

This problem occurs if the authentication trust mechanic of the Pipeline component's BizTalk Server host does not succeed. The authentication trust mechanic for a BizTalk Server Host cannot succeed if the following conditions is true:
A) The server computer are not installed in a Microsoft Active Directory domain environment that is running in Microsoft Windows 2000 native mode or later.
Resolution:

For the authentication trust mechanic of a BizTalk Server Host to work correctly, the following conditions must be true:
A) The server computer must be installed in a Microsoft Active Directory domain environment that is running in Microsoft Windows 2000 native mode or later.

Note:

If your BTS server is running as some other account in the ad, you have to import the. pfx certification key into two location:

A) The current user you logon to the server to operate the BTS Administrator console (you can then browse the Personal Certification key from the group and the host Property)

B) The account you BizTalk host instance running with (Be Better add the account to the Administrator Group of the server, then you can logon use this user and import. pfx certification into the host instance user's personal folder ).