vssconverter : The language of Team Explorer (en-US) does not match

Question

Hi,

im trying to run the vss converter tool on vs2008 sp with vss2005.

when calling the vss converter exe i get the foolowing error message

Error: The language of Team Explorer (en-US) does not match with the language of installed Visual SourceSafe 2005 (). Please ensure the language of Team Explorer and Visual SourceSafe 2005 is same.

now i assume that the vss2005 is set to british, and understand that the problem is down to the way vss2005 stores dates but how do i get around this problem.

as far as i know my local machine is set to english british, and the tfs server is the same.

how do i check each part and change them to the correct versions

thanks

James

Answer 1

Hi James,

Thanks for reporting this issue.

It seems that VSS Converter tool cannot detect the lanaguage of VSS 2005.

What's your operating system?
What's the language of VSS 2005? Is it ENU?

Please try changing the Visual Studio language to English instead of same as windows.

---

Please remember to mark the replies as answers if they help and unmark them if they provide no help.
Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.
Send us any feedback you have about the help from MSFT at [e-mail].

Answer 2

os is 2003 where vss2005 is installed, running on a network share. ENU as far as i can tell.

os where im running vssconverter from is xp pro sp2, vs2008 team suite sp1 with latest data dude version.

visual studio language is set to english, not same as windows. from the drop down list in tool options

thanks

James

Answer 3

In Visual Studio, menu [Tools] -> [Options] -> [Environment] -> [International Settings], change language to English.

VSS client and TFS Explorer must be in same language so that VSS Converter can work.

I would suggest you to change all your windows language and reinstall VSS with same language as Team explorer.

---

Please remember to mark the replies as answers if they help and unmark them if they provide no help.
Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.
Send us any feedback you have about the help from MSFT at [e-mail].

Answer 4

Hi i have got past this problem now.

i needed to have the VSS tools installed on my machine where i was running the vss converter from.

this may have been an oversight on my behalf, but i can't honestly remember seeing it in the prerequisits.

James

Answer 5

Hi i have got past this problem now.

i needed to have the VSS tools installed on my machine where i was running the vss converter from.

this may have been an oversight on my behalf, but i can't honestly remember seeing it in the prerequisits.

James

"VSS Tools" Means "Administrative tools" feature in the installer.

Adding the feature does not solve the problem for me.

Olivier.

Answer 6

Had the same problem.

Seems vssconverter.exe doesn't detect the VSS language properly on 64-bit systems (looks at the wrong registry key). Changing it to run 32-bit worked for me ("CorFlags.exe VSSConverter.exe /32bit+ /force")

/vriff

Answer 7

Had the same problem.

Seems vssconverter.exe doesn't detect the VSS language properly on 64-bit systems (looks at the wrong registry key). Changing it to run 32-bit worked for me ("CorFlags.exe VSSConverter.exe /32bit+ /force")

/vriff

You suggestion works for me.

From the Visual Studio 2010 x64 Cross Tools command Prompt, the following command :

CorFlags.exe "C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\VSSConverter.exe" /32bit+ /force

Produce the following Warning :

Microsoft (R) .NET Framework CorFlags Conversion Tool.  Version  4.0.21006.1
Copyright (c) Microsoft Corporation.  All rights reserved.

corflags : warning CF011 : The specified file is strong name signed.  Using /For
ce will invalidate the signature of this image and will require the assembly to
be resigned.

This is not a big deal, because this module comes from a beta release.
I suggest you ask for a fix on the connect web site.


Olivier.