Comments (5)
  1. Hari says:

    Awesome post.  It worked like a charm.  I would request you to put the example as well.

  2. Bernhard says:

    Export of metadata worked for me, but if i try to import the file on testserver, i get following error:

    PS C:Windowssystem32> Import-SPMetadataWebServicePartitionData -Identity "ee9c

    f807-5cbd-484a-a11d-77ebbf2ef071" -ServiceProxy "680fdccd-fc67-498c-8fc4-587fae4

    54b6b" -Path \testserverbackupSPF01_Metadata.bak -OverwriteExisting

    Import-SPMetadataWebServicePartitionData : Bei der Konvertierung eines nvarchar

    -Datentyps in einen datetime-Datentyp liegt der Wert außerhalb des gültigen Ber


    Die Anweisung wurde beendet.

    At line:1 char:41

    + Import-SPMetadataWebServicePartitionData <<<<  -Identity "ee9cf807-5cbd-484a-

    a11d-77ebbf2ef070" -ServiceProxy "680fdccd-fc67-498c-8fc4-587fae454b6b" -Path

    grazsp99backupSPF01_Metadata.bak -OverwriteExisting

       + CategoryInfo          : InvalidData: (Microsoft.Share…cePartitionData:

      SPCmdletImportM…cePartitionData) [Import-SPMetadataWebServicePartitionDa

     ta], FaultException`1

       + FullyQualifiedErrorId : Microsoft.SharePoint.Taxonomy.Cmdlet.SPCmdletImp


  3. BernHard- I don't understand the language used in the error message. Also, I have never faced an exception with this mechanism.

  4. Hi !

    It seems that we have the same error on our French platforms (French OS, French version of SQL and French version of SPS). The error message indicates : "Unable to cast nvarchar to datetime".

    We don't reproduce the error on another platform with English OS and English version of SQL.  We are going to deploy SP1 (and CU June 2011 if necessary) on our French platforms.

    Do you think that the error comes from the language of the platform (OS and/or SQL) ?



  5. JB says:


    I found the problem and a workaround:

    Problem is the CmdLet calls exec proc_ECM_GetChanges @SinceTime='2012-02-27 15:30:22.530' with an English format date.

    If your SQL Server is not in EN, it tries to parse this date, but fails.

    Workaround is to set temporarly the default language for the involved DB user (farm account) to English (from SQL Management Studio, Security, Properties for the user, then change his default language).

    Will MS fix this??

Comments are closed.

Skip to main content