While importing from VSS to Source Vault, I saw this in the vault log file.
PromoteLabelItems returned: FailInvalidObjVerID
Does this mean the label failed to import? If so, why doesn't the log tell me which label as my project has many labels.
What can I do to recover the label?
Thanks
Tom
Promote Label Error
Moderator: SourceGear
-
Tom
Promote Label Error
Jeremy:
After the import got done, here were the exceptions.
File C:\DOCUME~1\TOMAT~1.FHL\LOCALS~1\Temp\tmp4534.tmp (112023040 bytes) is larger than the server's configured upload limit of 104857600 bytes.Transaction failed
File C:\DOCUME~1\TOMAT~1.FHL\LOCALS~1\Temp\tmp4534.tmp (112023040 bytes) is larger than the server's configured upload limit of 104857600 bytes.Transaction failed
File C:\DOCUME~1\TOMAT~1.FHL\LOCALS~1\Temp\VSSLABELS\1.0.1.42\Capital Plan 2\source\SQL\configdb (112023040 bytes) is larger than the server's configured upload limit of 104857600 bytes.Transaction failed
Label Import: The label $/Capital Plan 2 (1.0.1.42) could not be verified because an exception occured.File C:\DOCUME~1\DARIAT~1.FHL\LOCALS~1\Temp\VSSLABELS\1.0.0.0\Capital Plan 2\source\SQL\configdb (112023040 bytes) is larger than the server's configured upload limit of 104857600 bytes.Transaction failed
Label Import: The label $/Capital Plan 2 (1.0.0.0) could not be verified because an exception occured.
File C:\DOCUME~1\TOMAT~1.FHL\LOCALS~1\Temp\VSSLABELS\1.0.1.47\Capital Plan 2\source\SQL\configdb (112023040 bytes) is larger than the server's configured upload limit of 104857600 bytes.
Transaction failed
Label Import: The label $/Capital Plan 2 (1.0.1.47) could not be verified because an exception occured.
File C:\DOCUME~1\TOMAT~1.FHL\LOCALS~1\Temp\VSSLABELS\1.0.1.51\Capital Plan 2\source\SQL\configdb (112023040 bytes) is larger than the server's configured upload limit of 104857600 bytes.
Transaction failed
Can you shead some light on what these errors mean?
Also, the VSS labels are somehow being downloaded to my cDoc ~Settings\TOMAT\Local Settings\Temp\VSSLABEL folder.
Is there any way to control this setting within Source Gear?
Any can I go ahead and delete these folders/files from the OS hard drive now that my import is finished?
Thanks
Tom
After the import got done, here were the exceptions.
File C:\DOCUME~1\TOMAT~1.FHL\LOCALS~1\Temp\tmp4534.tmp (112023040 bytes) is larger than the server's configured upload limit of 104857600 bytes.Transaction failed
File C:\DOCUME~1\TOMAT~1.FHL\LOCALS~1\Temp\tmp4534.tmp (112023040 bytes) is larger than the server's configured upload limit of 104857600 bytes.Transaction failed
File C:\DOCUME~1\TOMAT~1.FHL\LOCALS~1\Temp\VSSLABELS\1.0.1.42\Capital Plan 2\source\SQL\configdb (112023040 bytes) is larger than the server's configured upload limit of 104857600 bytes.Transaction failed
Label Import: The label $/Capital Plan 2 (1.0.1.42) could not be verified because an exception occured.File C:\DOCUME~1\DARIAT~1.FHL\LOCALS~1\Temp\VSSLABELS\1.0.0.0\Capital Plan 2\source\SQL\configdb (112023040 bytes) is larger than the server's configured upload limit of 104857600 bytes.Transaction failed
Label Import: The label $/Capital Plan 2 (1.0.0.0) could not be verified because an exception occured.
File C:\DOCUME~1\TOMAT~1.FHL\LOCALS~1\Temp\VSSLABELS\1.0.1.47\Capital Plan 2\source\SQL\configdb (112023040 bytes) is larger than the server's configured upload limit of 104857600 bytes.
Transaction failed
Label Import: The label $/Capital Plan 2 (1.0.1.47) could not be verified because an exception occured.
File C:\DOCUME~1\TOMAT~1.FHL\LOCALS~1\Temp\VSSLABELS\1.0.1.51\Capital Plan 2\source\SQL\configdb (112023040 bytes) is larger than the server's configured upload limit of 104857600 bytes.
Transaction failed
Can you shead some light on what these errors mean?
Also, the VSS labels are somehow being downloaded to my cDoc ~Settings\TOMAT\Local Settings\Temp\VSSLABEL folder.
Is there any way to control this setting within Source Gear?
Any can I go ahead and delete these folders/files from the OS hard drive now that my import is finished?
Thanks
Tom
Tom,
The problem is covered in the Tips For a Successful VSS Import at http://support.sourcegear.com/viewtopic.php?t=8
The files are larger than the upload limit configured in point number 9.
Yes, all files in VSS labels are downloaded to a temp directory, so that they can be compared with the Vault label that is being created. Once the label is imported, all of the temp files should be deleted.
The problem is covered in the Tips For a Successful VSS Import at http://support.sourcegear.com/viewtopic.php?t=8
The files are larger than the upload limit configured in point number 9.
Yes, all files in VSS labels are downloaded to a temp directory, so that they can be compared with the Vault label that is being created. Once the label is imported, all of the temp files should be deleted.
-
Tom
Jeremy:
Thanks for your quick response.
I read the "Tips for a successful Import from VSS" and I I think I see what I have to do but I wanted to check with you first.
It looks as if all of my default web settings are OK.
<httpRuntime executionTimeout="86400" maxRequestLength="102400" useFullyQualifiedRedirectUrl="false" minFreeThreads="8" minLocalRequestFreeThreads="4" appRequestQueueLimit="100" />
As I understand it, my executionTimeout is 28.4 hours! Is that how you read it 102400/3600. So I think I'm OK here.
Then next suggesstion was to increase the SQLCommandTimeout to at least an hour.
I think this is the line the article is referring to.
I believe the SQLConnectionString is in seconds, The setting is 4320 or 72 minues. So should I leave this alone.
<sessionState mode="InProc" stateConnectionString="tcpip=127.0.0.1:42424" sqlConnectionString="data source=127.0.0.1;user id=sa;password=" cookieless="false" timeout="4320" />
But I see where in the Admin tool, my IIS FIle Upload is set at 102400. So is this the setting I should double or triple to fix my error? Will this slow me down.
Finally, one more perplexing question. The article recommends the following One machine should be running the Vault server, including SQL Server and the other should be running VSS import on the same server as VSS is installed. I agree with the second part but we typically don't install web sites on the DB server. Actually, our web server is also our domain controller. Don't ask me why but I was planning on installing the Vault server on that. So I would end up with three servers. One as a DB server only. One where my VSS database is and the other as my web site. Do you see any problems with this setup?
Thanks
Tom
Thanks for your quick response.
I read the "Tips for a successful Import from VSS" and I I think I see what I have to do but I wanted to check with you first.
It looks as if all of my default web settings are OK.
<httpRuntime executionTimeout="86400" maxRequestLength="102400" useFullyQualifiedRedirectUrl="false" minFreeThreads="8" minLocalRequestFreeThreads="4" appRequestQueueLimit="100" />
As I understand it, my executionTimeout is 28.4 hours! Is that how you read it 102400/3600. So I think I'm OK here.
Then next suggesstion was to increase the SQLCommandTimeout to at least an hour.
I think this is the line the article is referring to.
I believe the SQLConnectionString is in seconds, The setting is 4320 or 72 minues. So should I leave this alone.
<sessionState mode="InProc" stateConnectionString="tcpip=127.0.0.1:42424" sqlConnectionString="data source=127.0.0.1;user id=sa;password=" cookieless="false" timeout="4320" />
But I see where in the Admin tool, my IIS FIle Upload is set at 102400. So is this the setting I should double or triple to fix my error? Will this slow me down.
Finally, one more perplexing question. The article recommends the following One machine should be running the Vault server, including SQL Server and the other should be running VSS import on the same server as VSS is installed. I agree with the second part but we typically don't install web sites on the DB server. Actually, our web server is also our domain controller. Don't ask me why but I was planning on installing the Vault server on that. So I would end up with three servers. One as a DB server only. One where my VSS database is and the other as my web site. Do you see any problems with this setup?
Thanks
Tom
Your understanding of SQLCommandTimeout is wrong. The timeout that you show is the one for a specific session state which is not applicable. The real setting is in c:\inetpub\wwwroot\VaultService\Vault.config. After changing any value in this file, you will need to perform and iisreset on the web server.
It's fine to have the web service running on a different machine than the database server. I would not recommend running the Vault web service on the domain controller. People do it, but it's a much trickier setup. The tips article was trying to say that it's best if the web service and VSS are on the same box during the import. This reduces the chance that network problems will hurt your import, and may improve your import speed as well.
The file upload limit is something that you should figure out. What is the size of the biggest file that you need to upload? Set it to a few meg larger than that. Also, think about if you really need to add a file that is bigger than 100 meg.
It's fine to have the web service running on a different machine than the database server. I would not recommend running the Vault web service on the domain controller. People do it, but it's a much trickier setup. The tips article was trying to say that it's best if the web service and VSS are on the same box during the import. This reduces the chance that network problems will hurt your import, and may improve your import speed as well.
The file upload limit is something that you should figure out. What is the size of the biggest file that you need to upload? Set it to a few meg larger than that. Also, think about if you really need to add a file that is bigger than 100 meg.
Jeremy, the import tips say that VSS and VSS Import should be running on one machine, and IIS should be running on another machine (or at least the did the last time I read them). That's how we did it. I assumed that this is so that the vss/import process isn't fighting with the Vault process for CPU and disk usage.
When I did our import, we had SQL Server on one machine, IIS on a second machine, and the VSS database and import tool on a third machine. It all worked just fine.
When I did our import, we had SQL Server on one machine, IIS on a second machine, and the VSS database and import tool on a third machine. It all worked just fine.
The recommendation that everything run on two machines is a bit outdated, since the 3.0 import uses much less memory than the 2.0 import. I've changed the tips to reflect my way of thinking, since I'm the one who has to support it. I debated whether to change the tips, but he who controls present controls the past.