Using App.Config Settings in BizTalk 2004

This is an example of how to use app.config settings in a BizTalk 2004 Orchestration.
First, you must setup the configuration section that you want to use. This is an example of what this looks like:

<!--This is an example of setting up your configuration section-->
<configuation>
<configSections>
<section name='MyConfigSection' type='System.Configuration.NameValueSectionHandler' />
</configSections>

<MyConfigSection>
<add key='MyKey' value='MyValue' />
</MyConfigSection>
</configuration>

Then, create an orchestration variable of type System.Collections.Specialized.NameValueCollection (I'll call it varConfigHandler)

This is an example of using the varConfigHandler in an expression shape:

// varConfigHandler has to be instantiated and bound to the config section we are interested in
// Notice that the result of the GetConfig function call is being cast into a NameValueCollection
varConfigHandler = new System.Collections.Specialized.NameValueCollection((
System.Collections.Specialized.NameValueCollection)
System.Configuration.ConfigurationSettings.GetConfig("MyConfigSection"));

// Now, we can access keys in the config section
varConfigHandler.Get("MyKey");

For deployment, copy the configSections/section and MyConfigSection into the config file for the BizTalk Service which is located at:

C:\Program Files\Microsoft BizTalk Server 2004\BTSNTSvc.exe.config

Error 5009.Registration of BAM performance counters failed. Return code -1.

Post from: http://blogs.msdn.com/balachandra/archive/2008/10/20/error-5009-registration-of-bam-performance-counters-failed-return-code-1.aspx

In one of my project I was remote installing BizTalk server on the dev machine and I encountered a strange error. "Error 5009. Registration of BAM performance counters failed. Return code -1." I searched and digged in for a solution and found that the performance counter registry may be damaged and the counters need to rebuilt. One of the forum thread suggested the use of lodctr exe with /r option for rebuilding counters. I tried however din't work for me. Let me tell you that my dev machine was running Windows 2003 server and I was not sure whether /r option was supported in that version of lodctr as the help text(use /?) did not show the option however though it showed the option /R: which restores performance registry strings from the specified filename. I also tried to restore PerfStrinBackup.ini file, din't work either. Then I tried the lodctr exe in Vista OS. This version supported the required option. I copied this version of exe to the dev machine and tried executing "lodctr /R". bingo! It worked!!. However please note I don't say that this is the right solution because there may be licencing issues associated in using Vista components in Windows 2003.

No item exists at . It may have been deleted or renamed by another user.

Remove <SharePoint:FieldDescription tags

Beyond Compare Synchronization Sheduling

Create "Folder Compare" session

Add from and to folders (if sharepoint library unc path not working read this)

Add filter if needed

Save Session

Create text file: (script.txt)

log verbose append:"c:\autosync_log.txt"

load session_name

sync update:lt->rt

Create bat file:

BCompare.exe @"script.txt"

Add bat file to sheduled tasks.

Access document library trough UNC path \\servername\doclib

Start the Web Client Service under services and set it to startmode automatic.

Getting Access Into Windows Internal Database Instance MICROSOFT##SSEE

\\.\pipe\mssql$microsoft##ssee\sql\query

Configuring MOSS 2007 to search pdf documents - install and configure pdf ifilters

http://msmvps.com/blogs/sundar_narasiman/archive/2008/02/06/configuring-moss-2007-to-search-pdf-documents-install-and-configure-pdf-ifilters.aspx