If you get the following message in variations logs (Site Actions –> Site Settings –> Site Collection Administration –> Variation Logs)  when the “Variations Create Hierarchies Job Definition” executed, it could be due to missing language packs.

“The Variations Create Hierarchies job failed with the following error message: File or arguments not valid for site template ‘CMSPUBLISHING#0′. Parameter name: WebTemplate.”

When installing a language pack in SharePoint 2010 Server make sure the following is followed.

Lets say for “Spanish” language pack

1. Download SPF 2010 Spanish language pack from http://www.microsoft.com/downloads/en/details.aspx?displaylang=en&FamilyID=646e311a-aaf3-4d30-b03c-2f3c70d19a22
2. Install the Spanish language pack.
3. Run the SP configuration wizard.
4. Download MOSS 2010 Server Spanish language pack from http://www.microsoft.com/downloads/en/details.aspx?displaylang=en&FamilyID=046f16a9-4bce-4149-8679-223755560d54
5. Repeat step 2 & 3

Run the following PowerShell command to view the GUID of the service

Get-SPServiceApplicationProxy

Copy the Id of the SSA “WSS_UsageApplication”

Execute the following by replacing the GUID copied from above output.

$UP = Get-SPServiceApplicationProxy | where {$_.ID -eq "<GUID of the WSS_UsageApplication>"}

$UP.Provision()

Now check the service status from central admin site.

“The specified user DOMAIN\SPFASTContentAdmAppPool could not be found. Some or all identity references could not be translated.”

But the user exists in the active directory. When I investigate further I found out that SharePoint does not accept user names which are more than 20 characters in length.

So new rule to the pre-installation documentation. “Manage account ids should be less than 20 characters”.

class Program
    {
        static void Main(string[] args)
        {
            Console.WriteLine("Please enter site url");

            using (SPSite site = new SPSite(Console.ReadLine()))
            {
                using (SPWeb web = site.OpenWeb())
                {
                    PublishingPageCollection publishingPages                    = PublishingWeb.GetPublishingWeb(web).GetPublishingPages();

                    foreach (PublishingPage page in publishingPages)
                    {
                        SPFile file = page.ListItem.File;
                        if (file.CheckedOutByUser != null)
                        {
                            Console.WriteLine("The page {0} is check out by                               user {1}. Check-in in to take control.",                               file.Title, file.CheckedOutByUser);

                            file.CheckIn("checked in by script",                                      SPCheckinType.MajorCheckIn);
                            SPModerationInformation moderationInformation                                          = page.ListItem.ModerationInformation;
                            if (moderationInformation.Status                                        == SPModerationStatusType.Pending)
                            {
                                file.Approve("Approved by script");
                            }
                            if (moderationInformation.Status                                              == SPModerationStatusType.Draft)
                            {
                                file.Publish("Published using script");
                                file.Approve("Approved by script");
                            }
                        }
                    }
                }
            }
        }
    }

$claimsUserID = read-host -prompt ‘Enter windows user name in format DOMAIN\UserName :’

#convert the user name to claims id
$claimsUserID = New-SPClaimsPrincipal -Identity $claimsUserID -IdentityType WindowsSamAccountName

$claimsUserID = $claimsUserID.ToEncodedString()

#display the claims id
write-host ‘Claims user ID is ‘ $claimsUserID

The below workflow supports extract single attachment or multiple attachments from the same InfoPath form. I am using Title field value to create the folder name. This can change based on the requirement.

Following are the detail configurations of the workflow activities. I think the above flow is self explaining and I don’t need to detail it J

Steps:

1. Read title value from InfoPath form:

   

    

2. Check whether there is a folder exists in a give document library with a name equal to title

   

    

3. If the folder does not exists create the folder in the document library
4. Get the path to the destination folder. In other words path the folder created in the above step.
5. Extract and copy attachments from InfoPath form into folder inside document library

   

    

6. This step I am writing some debug info into workflow history list.

This is just a quick post, so my explanations are very minimal. If you all have any questions or ideas please leave a comment.

First you need to write a converter to convert the byte[] stream to a BitmapImage.

public
object Convert(object value, Type targetType, object parameter, CultureInfo culture)

{

Byte[] bytes = value as
Byte[];

MemoryStream mem = new
MemoryStream(bytes);

mem.Write(bytes, 0, bytes.Length);

mem.Seek(0, SeekOrigin.Begin);

BitmapImage image = new
BitmapImage();

image.BeginInit();

image.DecodePixelWidth = 60;

image.CacheOption = BitmapCacheOption.OnLoad;

image.StreamSource = mem;

image.EndInit();

return image;

}

public
object ConvertBack(object value, Type targetType, object parameter, CultureInfo culture)

{

     return
null;

}

#endregion

}

Then do the xaml…….. That’s it. I hope I don’t have to show the code behind how to to the databind J

<Window x:Class=”Brandix.Employees”

xmlns=”http://schemas.microsoft.com/winfx/2006/xaml/presentation”

xmlns:x=”http://schemas.microsoft.com/winfx/2006/xaml”

xmlns:converters=”clr-namespace:Brandix”

Title=”Employees” Height=”600″ Width=”800″ xmlns:xcdg=”http://schemas.xceed.com/wpf/xaml/datagrid” Loaded=”Window_Loaded”>

<Window.Resources>

<converters:ImageConverter x:Key=”imageConverter” />

</Window.Resources>

<Grid>

<xcdg:DataGridControl Height=”160″ HorizontalAlignment=”Left” Name=”dgEmployees” VerticalAlignment=”Top” Width=”Auto” AutoCreateColumns=”False”>

<xcdg:DataGridControl.View>

<xcdg:CardflowView3D />

</xcdg:DataGridControl.View>

<xcdg:DataGridControl.Columns>

<xcdg:Column FieldName=”epic_picture” ReadOnly=”True” Title=”Picture” IsMainColumn=”True”>

<xcdg:Column.CellContentTemplate>

<DataTemplate>

<Image Source=”{xcdg:CellEditorBinding Converter={StaticResource imageConverter}}” />

</DataTemplate>

</xcdg:Column.CellContentTemplate>

</xcdg:Column>

</xcdg:DataGridControl.Columns>

</xcdg:DataGridControl>

</Grid>

</Window>

1. Develop the InfoPath web form.
2. Publish it to a SharePoint list.
3. Rename a copy of the above form as a “.cab”.
4. Open the “cab” file using WinZip of winrar and copy the “view1.xsl”

   

5. Upload the file to a list in the same SharePoint site.
6. Add a XML web part to a page and set the properties as below.

   

    

   XML Link is the path to the InfoPath form results saved in the document library.

   XSL Link is the path to the XSL file we save in step 5.

    

   And the result is……..

    

    

   

    

   If you want further customization to the form, you can write your own XSL and set the path in the web part.

    

    

   Form with a custom XSL……

    

   

http://www.microsoft.com/casestudies/casestudy.aspx?casestudyid=4000001206