I am in the middle of running VSSConverter to migrate our source (~2GB) from VSS to TFS.
It has been hanging for an hour or so with error # TF60047. The error message says there could be a problem with the network connection or TFS connection.
I am running in a single server setup so TFS and SQL Server are all on the same machine, and all are running, incl. all SQL Server service - I checked in Configuration Mgr.
One problem earlier was that there was huge (~800K) memory usage by w3wp.exe which was being run by the TFSService account. So I shut down IIS. Now, even though memory usage is down to acceptable levels, the migration is still not moving forward.
Any ideas on how I can proceed here? Or if I were to start afresh, how do I do that?
Btw, I remember getting this exact error the last time I did a migration (on another TFS server). Only at that time I was lucky that the problem resolved itself in 30 minutes or so.
Any ideas here??
| | DQM | You may want to check with this thread, where another user was getting the same error.
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=537882&SiteID=1
Team Foundation Server - http://blogs.msdn.com/jmanning/ | | James Manning - MSFT | I did look at that post earlier. I tried the suggestions mentioned there, but no luck.
I aborted the migration. Ran dbcc checkdb on ALL TFS dbs. All are fine.
Deleted all temporary workspaces that were created.
Running migration again. VSSConverter detects that it is an incremental migration. Then same problems start again. Huge memory usage and the same error - TF60047.
The VSSConverter log shows these errors/warnings (last part of log):
[VersionControl, Warning, 15, 2006/09/26 15:11:33.673] Repository is down. Retrying...
[VersionControl, Warning, 15, 2006/09/26 15:12:43.360] Repository is back
[VersionControl, Error, 15, 2006/09/26 15:16:32.138] Exception: System.Net.WebException
Message: The underlying connection was closed: An unexpected error occurred on a receive.
Stack Trace: at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request)
at System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRequest request)
at Microsoft.TeamFoundation.Client.TeamFoundationSoapProxy.GetWebResponse(WebRequest request)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at Microsoft.TeamFoundation.VersionControl.Proxy.Repository.QueryItems(String workspaceName, String workspaceOwner, ItemSpec[] items, VersionSpec version, DeletedState deletedState, ItemType itemType, Boolean generateDownloadUrls)
at Microsoft.TeamFoundation.Converters.VersionControl.Common.HatterasWrapper.QueryItemsInternal(Workspace workspace, ItemSpec[] itemSpecs, VersionSpec version, DeletedState deletedState)
Help Link:
BaseExceptionMessage: An existing connection was forcibly closed by the remote host
InnerException: System.Net.WebException
InnerException Message: The underlying connection was closed: An unexpected error occurred on a receive.
InnerException Stack Trace: at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request)
at System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRequest request)
at Microsoft.TeamFoundation.Client.TeamFoundationSoapProxy.GetWebResponse(WebRequest request)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at Microsoft.TeamFoundation.VersionControl.Proxy.Repository.QueryItems(String workspaceName, String workspaceOwner, ItemSpec[] items, VersionSpec version, DeletedState deletedState, ItemType itemType, Boolean generateDownloadUrls)
at Microsoft.TeamFoundation.Converters.VersionControl.Common.HatterasWrapper.QueryItemsInternal(Workspace workspace, ItemSpec[] itemSpecs, VersionSpec version, DeletedState deletedState)
InnerException Help Link:
InnerExceptionBaseExceptionMessage: An existing connection was forcibly closed by the remote host
[VersionControl, Warning, 15, 2006/09/26 15:16:36.747] Repository is down. Retrying...
[VersionControl, Warning, 15, 2006/09/26 15:17:42.700] Repository is back
| | DQM | As I understand it w3wp is the process that controls the IIS app pools. The converter can really put a beating on the server so i wouldnt be surprised to find out that IIS is using alot of memory in the process.
Stopping IIS essentialy takes down the TFS server which could be why your unable to continue. If you havent already; restart IIS.
Some other things you can do if that doesnt work.
Check the computers event long around the time of the errors; look for any errors that might indicate that the server went down. And why it went down.
It might be helpfull to know what the actions were happening right before the error. Can I see a few lines before the error?
Check that you can access the team project with Team Explorer.
Please let me know weather or not this unblocks you.
Curtis Pettit | | Curtis Pettit - MSFT | Yes, after my previous post I figured that IIS was required for the migration. So I restarted it. But it didn't go anywhere.
I can connect to TFS from Team Explorer.
I ran a couple more incremental migrations without any luck either.
So I backed up the VSSConverter logs, deleted the folders in TFS that were already created and started from scratch.
Now again it is hanging, and at exactly the same action. I know this because I made a note of the action description and number the previous time.
While the migration as moving smoothly the w3wp process memory usage was around 260-310K. Now it is back to over 800K. 
| | DQM | I backed up my VSS data again and ran against the new backup, just to try and rule out any problems. Same problem.
What's really wierd is that it is hanging at the same action # as it did with the previous VSS backup, although the action itself is different - i.e. operating on a different file.
In the event log, I see that the TfsVersionControl db is periodically restarting. There is no fixed time to this. The error number is TF10181.
| | DQM | It sounds like that might be a particularly large change. Can you confirm this?
How long did you let it hang before killing the process?
I want you to turn on verbose tracing. And see if it is really hanging or just doing alot of things in the backround.
In the in the same folder you found VSSConverter there should be a VssConverter.exe.config file. When you open it you will see 4 lines like this
| | Curtis Pettit - MSFT | Hi Curtis,
Thanks for getting back.
I have tried most of the steps you have suggested above. I did set trace levels to verbose in the config file- I saw this in a previous posting from Robert Horvick.
The error is what I posted in a previous post. Nothing more to add than that.
About the version control db - it appears in the App event log as an informational message. There is no error/warning symbol attached to it. I have another test server with TFS running as well. I looked at the event logs there, and I saw the same message being posted. On that (test) server I was able to do a migration last month. On both severs, the db does restart.
The VSS db is not particularly large. It is ~2GB total. I am trying to migrate one folder in it, which will be 10-20% of the total source. As I mentioned, the migration last month ran successfully. But I do remember it hanging for quite some time at the point too - but it did complete. Looking at that conversion's log I see it took 51 minutes.
I left this migration effort running overnight. No luck - the ConverterErrors.txt just gives TF60047 error message over and over again.
| | DQM | Hello.
I'm sorry to hear that you are continuing to have problems with the converter.
Since you have already enabled verbose logging could you please send me the entire log file via email at robert.horvick AT microsoft.com. That might provide some additional context about the error which will assist in debugging the issue.
Robert.
Robert Horvick - SDE - TFS Version Control | | Robert Horvick MSFT | Hi Robert,
I mailed you the log file some time back.
Thanks for taking the time to look into this!
| | DQM | I am giving up on this issue.  We don't have the time to pursue this any longer.
From my investigation, it seems as though SQL Server SP1 is causing the problems, including timeouts. Hope this helps someone else who encounters this problem.
| | DQM | Problems with SQL server could certinaly cause the converter to fail. However, since you have said that your running it on the same machine as your TFS, which is operating normaly, I would tend to think that you SQL is operating nomaly. If that is the problem then you can use the setting files to tell the converter to use the SQL instance on another machine. Find the instructions here http://msdn2.microsoft.com/en-us/library/ms253161.aspx
Also, ive had some time to look at your log file. There are a large numnber of exceptions that indicate that the converter is unable to get files from VSS. If you ever decide to pick this up again I would start by checking your connection to VSS . I couldnt hurt to run the vss analyze tool either (analyze -F)
Better luck in the future.
Curtis Pettit | | Curtis Pettit - MSFT | I did run the VSS analyze tool with -F -V options to look at what problems were encountered. I saw that there were around 30 files not found. However, this is the SAME list of files that was generated when I did a test run a month or so ago - when the migration succeeded.
I don't think it could be a VSS connection problem because the files were also on the local machine and nobody was accessing them at the time I was running the migration.
| | DQM |
|
index > Team Foundation Server - Version Control > VSS Migration hanging TF60047 - how to move forward?