This is a working solution. I tested it.

1. Visual Studio 2005, a pre-requisite
2. Visual Studio Team System 2005 Team Explorer, Download from here
3. Visual Studio 2005 Team Suite Service Pack 1, Download from here
4. Visual Studio Team System 2005 SP1 Forward Compatibility update for TFS 2010, Download from here

Catch here is to follow the order of installation.

1. You must have Visual Studio 2008 installed Off course You had it installed, that’s why you can under this situation you reading this blog post.
2. Install Visual Studio Team System Explorer. Download from here
3. Install Visual Studio 2008 Service Pack 1. Download from here
4. Install Visual Studio Team System 2008 Forward Compatbility Update for TFS 2010. Download from here

When we click a document, Manage section on the ribbon has no button for declaring it a records. This can be seen in the screen shot given below. This means in place records management feature is not enabled on this document library. One thing to remember here is that In Place Records Management is site collection level feature.

1. Go to site collection features and look for “In Place Records Management” feature. Before enabling, it will look like this:
   
   
2. After activation, feature will look like this:
   
   
   

   At this stage in place records management feature is enabled, but Declare Record button will not appear on ribbon. We need to do one more setting here.

3. Now go to document library setting page and click link as shown in screen shot below:
   
   
4. Click the radio button as shown in screen shot below and click ok.
   
   
5. After these settings document library will show Declare Record button. Declare Record button is disabled because we have not selected any document. This implies, in place records management can be applied to single document at a time.
   
   
6. Select a document in document library, declare record button will be enabled.
   
   

Click Declare Record button on the ribbon and you are done with declaring a record.

Enjoy SharePoint 2010.

Here is a code snippet to achieve this.

$siteUrl = “http://somesharepointweb”;
$fieldName = “Region”;
$fieldGroup = “Custom”;
$allowMultipleValues = “false”;
$isRequired = “true”;
$termStoreName = “Managed Metadata Service”;
$termGroupName = “Intranet”;
$termSetName = “North America”

#Get sp web
$site = New-Object -TypeName “Microsoft.SharePoint.SPSite” -ArgumentList $siteUrl;

$fieldType = “”;
$bAllowMulitpleValues = “”;
$bIsRequired = “”;

if ($allowMultipleValues.ToLower() -eq “true”)
{
$fieldType = “TaxonomyFieldTypeMulti”
}
else
{
$fieldType = “TaxonomyFieldType”
}
if ($allowMultipleValues.ToLower() -eq “true”)
{
$bAllowMulitpleValues = $true;
}
else
{
$bAllowMulitpleValues = $false;
}

if ($isRequired.ToLower() -eq “true”)
{
$bIsRequired = $true;
}
else
{
$bIsRequired = $false;
}

#Create a taxonomy field
$field = [Microsoft.SharePoint.Taxonomy.TaxonomyField]$site.RootWeb.Fields.CreateNewField($fieldType, $fieldName);

#Get a taxonomy session
$session = new-object Microsoft.SharePoint.Taxonomy.TaxonomySession($site)

#Get Term Store
$termstore = $session.TermStores[$termStoreName]

#Get Term Group
$group = $termstore.Groups[$termGroupName]

#Get Term Set
$termSet= $group.TermSets[$termSetName]

#populate newly created field
$field.Sspid = $termSet.TermStore.Id
$field.TermSetId = $termSet.Id
$field.AllowMultipleValues = $bAllowMulitpleValues
$field.Group = $fieldGroup
$field.Required = $bIsRequired
$site.RootWeb.Fields.Add($field)

#Update sp web
$site.RootWeb.Update()

OLE DB error: OLE DB or ODBC error: The SELECT permission was denied on the object ‘bam_OrderProcess_PivotTable1_RTATable’, database ‘BAMPrimaryImport’, schema ‘dbo’.; 42000.

Solution:
What ever the user is accessing BAMPrimaryImport database, assing it as role of db_owner.

Happy BAMing.

I came to know that order of BizTalk installation does matter to resolve this issue. Just verify whether you installed VS 2005 before BTS installation. In my case I installed BizTalk Server 2006 R2 prior to installing Visual Studio 2005. Fix is very simple. Just Modify BizTalk Installation and check Developer Tools and SDK check box during installation. After Installation you will be able to locate MicrosoftEdiXSDTemplates.exe in %programfiles%\Microsoft BizTalk Server 2006\XSD_Schema\EDI directory.

Happy BizTalking..

You may get the above error in Windows Event log, while exporting Access 2007 datasheet to Microsoft Office Sharepoint 2007. Solution was very simple and I came to know this after two days of fruitless efforts.

Resolution:
Install Microsoft Office 2007 Service Pack 1 KB936982

Cheers

Resolution:

stsadm -o backup -url http://PORTAL-URL -filename “c:\Backups\BACKUP-FILE.dat”
stsadm -o restore -url http://PORTAL-URL -filename “c:\Backups\BACKUP-FILE.dat” -overwrite

stsadm Command Reference

Cheers

You don’t have permission to save in this location. Contact the administrator to obtain permission.

Workaround is very simple. Administrated privileges need to be given to notepad.exe program before you open hosts file.

Simple type notepad in Run. Right click it and select Run as Administrator. Now you will be able to save file after modification.

Xml Declaration is of the form:
<?xml version="1.0" encoding="UTF-8"?>

Although I don’t see anything wrong in having xml declaration, but I had a requirement to remove it. After googling for some time I didn’t get any working code. Then I tried the following. Sharing here, it might be useful to some other geek.

StreamReader sr = new StreamReader("File.xml");
XmlDocument inDoc = new XmlDocument();
doc.LoadXml(sr.ReadToEnd());
sr.Close();
StringBuilder sb = new StringBuilder();
XmlWriterSettings settings = new XmlWriterSettings();
settings.OmitXmlDeclaration = true;
XmlWriter xWriter = XmlWriter.Create(sb, settings);
inDoc.Save(xWriter);
xWriter.Close();
XmlDocument outDoc = new XmlDocument();
outDoc.LoadXml(sb.ToString());