Vault excepting in GETLABELDIFFS after upgrade to SQL SP4
Moderator: SourceGear
-
- Posts: 6
- Joined: Mon Apr 03, 2006 10:53 am
Vault excepting in GETLABELDIFFS after upgrade to SQL SP4
I have a batch file called since.bat that simply gets the change delta from a given lebel. This has been working great. This morning it is not. You can see the command [and the exception in GetLabelTimeStamps I receive now] below. The only thing that has happened is the IT guy applied SP4 to our SQL instance. Any help is very much appreciated!
Thanks,
Tim
C:\Program Files\SourceGear\Vault Client>VAULT GETLABELDIFFS -host ngbuild1 -user timw -password something -repository ngonline $/ngonline_v1 PROD_31MAR06
<vault>
<error>
Invalid label: PROD_31MAR06
</error>
<exception>
System.ArgumentException: Invalid label: PROD_31MAR06
at VaultCmdLineClient.VaultCmdLineClient.GetLabelTimeStamps(String item, String label1, String label2, DateTime& timestamp1, DateTime& timestamp2)
at VaultCmdLineClient.VaultCmdLineClient.ProcessCommandGetLabelDiffs(String strReposPath, String strLabel1, String strLabel2)
at VaultCmdLineClient.VaultCmdLineClient.ProcessCommand(Args curArg)
at VaultCmdLineClient.VaultCmdLineClient.Main(String[] args)
</exception>
<result success="no" />
</vault>
Thanks,
Tim
C:\Program Files\SourceGear\Vault Client>VAULT GETLABELDIFFS -host ngbuild1 -user timw -password something -repository ngonline $/ngonline_v1 PROD_31MAR06
<vault>
<error>
Invalid label: PROD_31MAR06
</error>
<exception>
System.ArgumentException: Invalid label: PROD_31MAR06
at VaultCmdLineClient.VaultCmdLineClient.GetLabelTimeStamps(String item, String label1, String label2, DateTime& timestamp1, DateTime& timestamp2)
at VaultCmdLineClient.VaultCmdLineClient.ProcessCommandGetLabelDiffs(String strReposPath, String strLabel1, String strLabel2)
at VaultCmdLineClient.VaultCmdLineClient.ProcessCommand(Args curArg)
at VaultCmdLineClient.VaultCmdLineClient.Main(String[] args)
</exception>
<result success="no" />
</vault>
-
- Posts: 6
- Joined: Mon Apr 03, 2006 10:53 am
REVault excepting in GETLABELDIFFS after upgrade to SQL SP4
This Vault client is version 3.1.2.3511
[4/10/2006 1:50:04 PM] Version Check: Your Vault server is version 3.1.6.3658
[4/10/2006 1:50:04 PM] Version Check: Your Vault server is version 3.1.6.3658
We've had other reports of this error. In one case a user discovered the -rowlimit argument is ignored in the history item query in the GetLabelTimeStamps function... instead it is hard-coded to 10K. So if your labels don't fall in the first 10K items, the label(s) won't be found. He replaced this with a 0, and got the diffs.
http://support.sourcegear.com/viewtopic.php?p=23178
Does this work for you?
http://support.sourcegear.com/viewtopic.php?p=23178
Does this work for you?
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
-
- Posts: 6
- Joined: Mon Apr 03, 2006 10:53 am
-
- Posts: 6
- Joined: Mon Apr 03, 2006 10:53 am
Maybe it hit a default row limit?I'm curious why it broke suddenly
Getlabeldiffs does have a rowlimit option:
Try setting rowlimit to 0 and see if the labeldiff works then.This is a list of possible options:
-rowlimit limitnumber
Limits the number of rows returned for a history query to
limitnumber
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
-
- Posts: 6
- Joined: Mon Apr 03, 2006 10:53 am
-
- Posts: 6
- Joined: Mon Apr 03, 2006 10:53 am
Hi Linda,
I tried this with a rowlimit of 0 (I actually read it this time! ) and it still fails. Not sure how Rowlimit is hit but this is in a snapshot branch with only a half dozen labels since the branch and, literall, no changes between when it was working and when it wasn't, except for SP4. My concern was that something to do with dates creeped in.
Not a big deal since the history/beginlabel think is working now but it's a little worrisome because the output looks like something is getting stomped. Look at DateTime& in the log, like some kind of url encoding on the request to GetLabelTimeStamps?
Thanks,
Tim
System.ArgumentException: Invalid label: PROD_05APR06a
at VaultCmdLineClient.VaultCmdLineClient.GetLabelTimeStamps(String item, String label1, String label2, DateTime& timestamp1, DateTime& timestamp2)
at VaultCmdLineClient.VaultCmdLineClient.ProcessCommandGetLabelDiffs(String strReposPath, String strLabel1, String strLabel2)
at VaultCmdLineClient.VaultCmdLineClient.ProcessCommand(Args curArg)
at VaultCmdLineClient.VaultCmdLineClient.Main(String[] args)
I tried this with a rowlimit of 0 (I actually read it this time! ) and it still fails. Not sure how Rowlimit is hit but this is in a snapshot branch with only a half dozen labels since the branch and, literall, no changes between when it was working and when it wasn't, except for SP4. My concern was that something to do with dates creeped in.
Not a big deal since the history/beginlabel think is working now but it's a little worrisome because the output looks like something is getting stomped. Look at DateTime& in the log, like some kind of url encoding on the request to GetLabelTimeStamps?
Thanks,
Tim
System.ArgumentException: Invalid label: PROD_05APR06a
at VaultCmdLineClient.VaultCmdLineClient.GetLabelTimeStamps(String item, String label1, String label2, DateTime& timestamp1, DateTime& timestamp2)
at VaultCmdLineClient.VaultCmdLineClient.ProcessCommandGetLabelDiffs(String strReposPath, String strLabel1, String strLabel2)
at VaultCmdLineClient.VaultCmdLineClient.ProcessCommand(Args curArg)
at VaultCmdLineClient.VaultCmdLineClient.Main(String[] args)