VSS Migration Error
This popped up twice and prevented my migration from going through. You'll notice the link goes no where. So, any clues/suggestions on what to do next?
Thanks,
Drew
This popped up twice and prevented my migration from going through. You'll notice the link goes no where. So, any clues/suggestions on what to do next?
Thanks,
Drew
Umm, little help here? Tryin' to migrate over by this weekend and this is currently the only show stopper. Here's more detail from VSSConverter.log:
[VSS, Perf, 3, 2006/04/21 23:56:46.617] Time taken to Read Metadata::00:42:40.8095031 [VSS, Perf, 3, 2006/04/21 23:56:46.617] Processing Metadata [VSS, Perf, 3, 2006/04/21 23:56:46.648] Start Rename [VSS, Perf, 3, 2006/04/21 23:57:09.461] Start Update [VSS, Perf, 3, 2006/04/21 23:57:09.461] Time taken to process DB: 00:00:22.8279789 [VSS, Perf, 3, 2006/04/21 23:57:09.461] Processing Metadata complete. Adding to Version Control [VSS, Error, 3, 2006/04/21 23:57:09.726] Exception: Microsoft.TeamFoundation.Converters.Utility.ConverterException Message: Unable to write to SQL Server: .\SQLEXPRESS due to Error: The size (4969) given to the parameter 'Mappings' exceeds the maximum allowed (4000). Stack Trace: at Microsoft.TeamFoundation.Converters.VersionControl.Vss.DBConnect.WriteMappings() at Microsoft.TeamFoundation.Converters.VersionControl.Vss.VssConverter.AddToHatteras(UserMapper usermap) Help Link: BaseExceptionMessage: The size (4969) given to the parameter 'Mappings' exceeds the maximum allowed (4000). InnerException: Microsoft.TeamFoundation.Converters.Utility.ConverterException InnerException Message: Unable to write to SQL Server: .\SQLEXPRESS due to Error: The size (4969) given to the parameter 'Mappings' exceeds the maximum allowed (4000). InnerException Stack Trace: at Microsoft.TeamFoundation.Converters.VersionControl.Vss.DBConnect.WriteMappings() at Microsoft.TeamFoundation.Converters.VersionControl.Vss.VssConverter.AddToHatteras(UserMapper usermap) InnerException Help Link: InnerExceptionBaseExceptionMessage: The size (4969) given to the parameter 'Mappings' exceeds the maximum allowed (4000). [VSS, Perf, 3, 2006/04/21 23:57:09.726] Migration Complete
TFS is not installed on SQL Express it uses SQL Server.
VSSConverter by default uses SQL Express to to store VSS history in an intermediate DB. This default can be overridden this blog will help you understand your settings file more.
I can help you more if you could provide me the settings file you used for running converter.
-ankur
I didn't use a custom SQL server, I just let it use SQLExpress. There are no other "settings" really. All I did was setup my user mapping file and my project mapping file and ran the thing. For the most part it's successful, but it reports this error a couple times for a couple diff. places a couple projects.
I can send you the results and my mappings files if you'd like to analyze the situation, but I'd rather not post them here on the internet.
Thanks for your help,
Drew
Well, here's an interesting twist. My project mapping file has 55 mappings in it. If I break the file down into chunks, the conversion succeeds for all projects without error. For example, I initially commented everthing out to 11 logically related projects, ran it and had no errors. Ran the next set of related projects... again no errors. I've now finished with all 55 using this chunked approach and no errors running this way. *shrug*
So I'm happily migrated at this point, but if you'd still like more information about what I was doing I'll happily share my data with you privately as I mentioned before.
Thanks,
Drew
Sorry for not replying for so long i was on leave. you can mail data to ankurs[at]microsoft.com .
My understanding is that length of your mappings exceeded length supported by SQL express for "nvarchar" field which is 4000.