Nikolais Rant

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

On a course I saw this very cool SysInternals tool being used on the class desktops that display the systems configuration information. Very nifty, new and cool, very geeky. Check it out.

http://www.sysinternals.com/ntw2k/freeware/bginfo.shtml

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

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 =)