RE: Labelling not working in 2.0.1?

yes.  a colleague suggested to look at this problem - http://support.sourcegear.com/viewtopic.php?t=276&highlight=guid.  if you see the 4th post, it describes something similar to what you're seeing.

on the 10th post, they uninstalled and reinstalled the vault server.  it seems something was not set correctly in vault.config during the upgrade.  i would
	- back up your current database
	- uninstall vault server (making certain you keep the database)
	- verify the vaultservice virtual directory has been removed from iis and the physical directory has been removed ( ex: c:\inetpub\wwwroot\vaultservice )
	- reinstall vault server (making certain you keep the database)

hth
jeff

*********** REPLY SEPARATOR  ***********

On 3/24/2004 at 5:53 PM Kevin Hawkins wrote:

>Ah, we may be getting somewhere now.  The following error showed up in
>the log when I tried diff'ing between the labelled version and the
>latest version in the repository:
>
>----3/24/2004 5:52:07 PM     sgvaultsystem--()--
>	A configuration error occurred reading [GetFileCheckBatchSize]
>from Vault.Config.  ConfigReader reported the following error: Object
>reference not set to an instance of an object.
>
>Any ideas on that one?
>
>Thanks,
>Kevin
> 
>
>-----Original Message-----
>From: jeff clausius [mailto:[email protected]] 
>Sent: Wednesday, March 24, 2004 2:08 PM
>To: Kevin Hawkins
>Cc: [email protected]
>Subject: RE: [vault-list] Labelling not working in 2.0.1?
>
>hmmm.... 
>
>i'm not certain what to think.  is there anything in the server's log
>file (sgvault.log), that indicates some sort of error took place?
>
>jeff
>
>*********** REPLY SEPARATOR  ***********
>
>On 3/24/2004 at 2:01 PM Kevin Hawkins wrote:
>
>>Hi Jeff,
>>
>>When I do that, I get a popup dialog with Notepad that says "Cannot 
>>find the 
>>C:\DOCUME~1\kevin\LOCALS~1\Temp\vault99dba14e-8711-4ab1-a0c8-b6e6443265
>>0 8\MyFile.cs file.  Do you want to create a new file?"  Once again, 
>>the directory is there, but there are no files in there.  I have full 
>>access permissions to that directory, so it should be able to write 
>>stuff in there from that standpoint.
>>
>>Thanks,
>>Kevin