Import hangs

frans · Post by **frans** » Wed Apr 28, 2004 6:29 am

Hello, I am currently evaluating Vault 2.0.2. As a part of the evaluation, I am trying to import a part of our VSS database. I have tried to import several times, but the process always stops at the same moment. The import window is still visible, but does not change for a long time (over an hour). the last message in the log file is an "Importing Label" message.

I think I have done everything right, I am using two different machines, VSS 6.0c + hotfix, I have retored the VSS archive in a fresh database and had analyze.exe check the data, etc. What could be the matter?

Post by **jeremy_sg** » Wed Apr 28, 2004 11:11 am

Is the import process running out of memory? Often, the import will hang when its memory usage reaches 1 Gig. This is due to a limitation in the .Net Framework. Is the processor being utilized? Could you post the end of you log file here or email it to me?

Don Thimsen · Post by **Don Thimsen** » Wed Apr 28, 2004 5:27 pm

Did you setup any shadow folders before the import? I had problems with this a few months ago. Search for:

Vault 2.0.1 locks during sourcesafe import

Don

frans · Post by **frans** » Thu Apr 29, 2004 3:11 am

Thank you kindly for your replies.

No, I have not created any shadow folders before importing. The only thing I do before importing is create a new Vault repository, nothing else.

I believe I have looked at memory and CPU usage, and I can't recall noticing a heavy load on either of them when I noticed the import had stopped. But it might have occured before that.

I have just started the import again, and I will watch CPU and memory load more closely now. Also, I have checked all the labels for import except the one the import tool happened to stumble over in the first runs.

Jeremy, I will send the tail of the import log by e-mail.

Greetings,

Frans

frans · Post by **frans** » Thu Apr 29, 2004 8:48 am

Well, this time my test import has reached the end. Unchecking the one label that caused the import process to hang was the solution. If it is only one label, I think we can live with that. Chances are that there was something wrong with the label in VSS to start with. We have had some very strange label problems with VSS in the past, problems that were not identifies or solved by the analyze.exe utility.

At the end of the import run, the import tool reported several other problems but these do not seem to be serious for us and did not cause the import to hang. Now I can continue evaluating Vault..

Bye,

Frans