The object could not be found.

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
Tom.Wells
Posts: 65
Joined: Tue Sep 21, 2004 10:35 am

The object could not be found.

Post by Tom.Wells » Wed Nov 10, 2004 9:25 am

I cannot delete or rename a folder in a repository. I get the message

The object could not be found. It may have been deleted, moved or renamed.

The first time I tried to rename it I accidentially tried to rename it to an existing folder. Now I can't do anything to it. How do I delete this folder?

Vault 2.0.6
Win XP SP2 on the client
Windows Server 2003 on the server

Tom

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Post by lbauer » Wed Nov 10, 2004 9:48 am

Are you saying you can't rename any folder or just a particular folder?

What name does the folder currently have? Is there a trailing space after the name?
Linda Bauer
SourceGear
Technical Support Manager

Tom.Wells
Posts: 65
Joined: Tue Sep 21, 2004 10:35 am

Post by Tom.Wells » Wed Nov 10, 2004 9:53 am

I can't rename a particular folder. It's name is "Equipment Management 322 ". I wasn't aware of it but yes, it does accidentally have a space on the end.

Tom

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Post by lbauer » Wed Nov 10, 2004 1:16 pm

The server runs each request path through a cleaner which removes things like $///the//folder/path and changes it into $/the/folder/path. The space at the end of your new folder name got trimmed, so Vault is looking for "foldername<space>" but this doesn't exist anymore, only "foldername."

This has been fixed for Vault 3.0, but for now, we can change the foldername in the database.

First, run this query and let me know the results.
USE sgvault
GO


SELECT vernameid, name FROM tblfsobjectversionnames WHERE REPLACE(name, N' ', N'\') LIKE N'%\'
GO
Please note that there is a space between the apostrophes in (name, N'(sp)', N'\')
Linda Bauer
SourceGear
Technical Support Manager

Tom.Wells
Posts: 65
Joined: Tue Sep 21, 2004 10:35 am

Post by Tom.Wells » Wed Nov 10, 2004 2:17 pm

Here's the results:


vernameid name
-------------------- ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
25 Equipment Management 322

(1 row(s) affected)

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Post by lbauer » Wed Nov 10, 2004 4:10 pm

Now try these steps:

1) Stop Vault server

2) Have all users clear their client side tree cache for this repository.
(C:\Documents and Settings\username\Application Data\SourceGear\Vault_1\Client). If they don't clear their caches they'll still see the old name.

3) Run the following query: (note that you are adding an underscore to the name of the folder.)

USE sgvault
GO
UPDATE tblfsobjectversionnames SET name = N'Equipment Management 322_' WHERE vernameid = 25

GO

4) Restart Vault server

5) Users should now see the folder as "Equipment Management 322_", and they can delete it or rename it.
Linda Bauer
SourceGear
Technical Support Manager

Tom.Wells
Posts: 65
Joined: Tue Sep 21, 2004 10:35 am

Post by Tom.Wells » Fri Nov 12, 2004 7:47 am

I tried a test on my local machine first. Couldn't make it work. I had to use a different vernameid value of course. I wasn't sure how to stop the vault service so I stopped IIS. Deleted all the local cache folders in the path you gave, then ran the SQL then restarted IIS. Though the SQL shows the row being changed it still appears the same in the client. Renames and deletes fail. What did I miss?

Tom

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Post by lbauer » Fri Nov 12, 2004 9:02 am

Run this again to see if the results are the same as before:

USE sgvault
GO


SELECT vernameid, name FROM tblfsobjectversionnames WHERE REPLACE(name, N' ', N'\') LIKE N'%\'
GO
Linda Bauer
SourceGear
Technical Support Manager

Tom.Wells
Posts: 65
Joined: Tue Sep 21, 2004 10:35 am

Post by Tom.Wells » Fri Nov 12, 2004 9:04 am

No the results are not the same. The SQL returns nothing.

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Post by lbauer » Fri Nov 12, 2004 9:33 am

Then most likely the client side cache files still have the old file information. Try this again:

Close the Vault Client. Stop IIS. Delete the client cache for the repository in %appdata% \SourceGear\Vault_1\Client. Restart IIS, then open the Vault Client. This should force the client to get a fresh view of the tree.
Linda Bauer
SourceGear
Technical Support Manager

Tom.Wells
Posts: 65
Joined: Tue Sep 21, 2004 10:35 am

Post by Tom.Wells » Fri Nov 12, 2004 10:03 am

Nope. No difference. I am doing this all on the same machine. The vault service is on the local machine. I'm running the client on the same machine. I closed the client, then stopped IIS for the "Default Web Site" then located the cache files which in my case were here

C:\Documents and Settings\twells\Application Data\SourceGear\Vault_1\Client\007310D6-F8D3-4A52-92E4-5E0FD4BB5C33

I deleted that whole folder. Then restarted ISS then restarted the client. no joy.

Tom

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Post by lbauer » Fri Nov 12, 2004 10:28 am

Email your phone number to linda at Sourcegear.com and I'll give you a call.
Linda Bauer
SourceGear
Technical Support Manager

Tom.Wells
Posts: 65
Joined: Tue Sep 21, 2004 10:35 am

Post by Tom.Wells » Tue Nov 16, 2004 8:02 am

I figured it out. I rebooted my machine. Now I can see the changes.

Will a fix for this be made available for version 2?

jclausius
Posts: 3706
Joined: Tue Dec 16, 2003 1:17 pm
Location: SourceGear
Contact:

Post by jclausius » Tue Nov 16, 2004 8:16 am

Tom:

This has been fixed in Vault 3
Jeff Clausius
SourceGear

Post Reply