If your trying to get the WSE 2.0 samples setup then you will find these links most helpful. I have been using these to get the “AsymmetricEncryption“ sample up and running on Windows 2000 Professional.

http://pluralsight.com/blogs/aaron/archive/2004/07/13/1623.aspx

http://hyperthink.net/blog/PermaLink,guid,d453be63-5389-450b-8bae-81113fa188f4.aspx

I also found that on Windows 2000 Professional that there is no "Other People Store" and the advice to use IE to import the Public Portion of the Server key does not work. To get around this I simply added the “Server Public.cer“ to “Current User\Personal“ and the samples work as is with no code changes.

If you attempt to import the public portion cert “Server Public.cer“ to another location i.e. “Current User\Trusted People“ you will get policy errors such as “WSE405: A satisfactory subset of policy assertions that could be enforced for the outgoing message could not be found.“. This is basically caused due to the fact that the certificate specified in your policyCache.config can not be found.

Another handy tip is to ensure you have diagnostics policy tracing set to on, this will generate a “SendPolicy.webinfo“ file in your client bin directory with details of any errors. It will provide you with handy information such as:

<wset:message action="http://stockservice.contoso.com/wse/samples/2003/06/StockQuoteRequest" messageId="uuid:e8c0df94-bc61-4430-bcc6-a97fd4018192" appDomain="AsymEncryptPolicyClient.exe" time="2005-08-18T11:21:53.1093750+12:00">
<wset:compile qname="wsp:Policy" wsu:Id="#Encrypt-X.509" usage="Required" canEnforce="false">
<wset:compile qname="wssp:Confidentiality" usage="Required" canEnforce="false">
<wset:annotation>ISecurityTokenManager.PermitsPolicyEnforcementTokenCaching is set to true in the token manager registered for this token type. A token will be loaded from the token manager and cached for subsequent message enforcement.</wset:annotation>
<wset:annotation>Invoking ISecurityTokenManager.LoadTokenFromSecurityTokenAssertion from the token manager registered for this token type.</wset:annotation>
<wset:annotation>Could not find a security token.</wset:annotation>
<wset:annotation>Looking for a satisfactory token in the current message's token collection...</wset:annotation>
<wset:annotation>Looking for a satisfactory token in policy enforcement token cache...</wset:annotation>
<wset:annotation>ISecurityTokenManager.PermitsPolicyEnforcementTokenCaching is set to true in the token manager registered for this token type. Attempting to use the previously cached token...</wset:annotation>
<wset:annotation>Invoking ISecurityTokenManager.LoadTokenFromSecurityTokenAssertion from the token manager registered for this token type.</wset:annotation>
<wset:annotation>Could not find a security token.</wset:annotation>
</wset:compile>
</wset:compile>
</wset:message>

Well I am one of the lucky first one hundred people to attend the Quick Learn BizTalk 2004 Deep Dive training. John Callaway runs the course and has done a fantastic job putting the content together. If you can get on a course that isn't sold out I totally recommend it.

Go check out Scotts Woodgates blog for feedback from partners that have attended to date http://blogs.msdn.com/scottwoo/archive/2005/04/28/413101.aspx

http://www.quicklearn.com/deepdive.htm

Ok, I fixed the first issue with P&P installation, then I had to deal with this next one.....

• Failed to create instances of performance counter '# of Connections Opened/Sec' - Couldn't get process information from remote machine..
• Failed to create instances of performance counter 'Total Command Executions' - Couldn't get process information from remote machine..
• Failed to create instances of performance counter 'Average Command Execution Time' - Couldn't get process information from remote machine..

Well it seems this is a permissions related error and it will cause the DAAB (Data Access Block) to fail when attempting to log instrumentation information. I found this helpful FAQ via MSDN on adding your process user to the correct security groups.

http://msdn.microsoft.com/netframework/programming/bcl/faq/SystemDiagnosticsProcessFAQ.aspx#Question8

How do I use the Process class under a non-admin account?
From Windows Server 2003, you will get an exception if you try to get process performance information under a non-admin account. The workaround is to add that account into the Performance Counter Users Group.

Here is a tip for anyone out there searching to deal with errors associated with Patterns & Practices Enterprise Library installservices.bat failures. If you are getting tonnes of errors like the following in you event log after attempting to deploy to your test or production server:

Enterprise Library Instrumentation
Failed to fire the WMI event 'DataConnectionOpenedEvent'. Exception: System.Exception: This schema for this assembly has not been registered with WMI.

Basically this caused by the annoying script installservices.bat requiring VS.NET installed on your production machine, it doesn't take much to notice what is wrong with that statement does it. Anyway, after reading on Tom Hollanders P&P evangalist blog you really only need access too installutil to register the common classes with WMI. The bat script below should solve your problems, for this to work you need to copy all the compiled assemblies from you development “C:\Program Files\Microsoft Enterprise Library\bin“ to your production\test servers.

http://blogs.msdn.com/tomholl/archive/2005/02/18/376187.aspx

Also check out some good pointers on Jans blog http://weblogs.asp.net/jan/archive/2005/02/23/379089.aspx

Finally someone has actually found something useful on my blog =) But have also pointed out some issues, in this batch file you will need to update the base directory to C:\Windows for XP and C:\WINNT for Win2K3. Cheers Hilton Giesenow

cd C:\WINNT\Microsoft.NET\Framework\v1.1.4322

installutil "C:\Program Files\Microsoft Enterprise Library\bin\Microsoft.Practices.EnterpriseLibrary.Common.dll"
installutil "C:\Program Files\Microsoft Enterprise Library\bin\Microsoft.Practices.EnterpriseLibrary.Caching.dll"
installutil "C:\Program Files\Microsoft Enterprise Library\bin\Microsoft.Practices.EnterpriseLibrary.Configuration.dll"
installutil "C:\Program Files\Microsoft Enterprise Library\bin\Microsoft.Practices.EnterpriseLibrary.Security.Cryptography.dll"
installutil "C:\Program Files\Microsoft Enterprise Library\bin\Microsoft.Practices.EnterpriseLibrary.Data.dll"
installutil "C:\Program Files\Microsoft Enterprise Library\bin\Microsoft.Practices.EnterpriseLibrary.ExceptionHandling.dll"
installutil "C:\Program Files\Microsoft Enterprise Library\bin\Microsoft.Practices.EnterpriseLibrary.Logging.dll"
installutil "C:\Program Files\Microsoft Enterprise Library\bin\Microsoft.Practices.EnterpriseLibrary.Security.dll"

PAUSE

This is an oldie but a goodie. .Net connection strings for accessing SQL server databases and the like are a pain in the ass to remember, this solid site takes away the need to remember this crap =)