Can't check-in after machine moved to a different domain

[emmanuelhuna]

My company has deployed a new domain (Active Directory) and we all moved our client machines from the old domain (DOMAIN1) to a new domain (DOMAIN2).

After the move I am unable to check-in any of the files that were previously checked out. The check-in option is unavailable and the file appears as renegade. Let's take one file as an example:

Before the domain move:
username: MYUSERNAME
Computer: MYCOMPUTER\DOMAIN1
File checked-out (exclusively):
C:\Vault\Project1\main\File1.cs
$/Project1/main/File1.cs

After the domain move:
username: MYUSERNAME
Computer: MYCOMPUTER\DOMAIN2
File checked-out (exclusively):
C:\Vault\Project1\main\File1.cs
$/Project1/main/File1.cs

What is the EASIEST way to fix this so I will be able to check-in these files?

I tried updating the table tblcheckoutlisitems in the sgvault database to set the hostname from MYCOMPUTER\DOMAIN1 to MYCOMPUTER\DOMAIN2, but that didn't work. I still don't have the check-in option when I run the client.

[Beth]

Just to make sure we don't go down the wrong path, is everything else functional? You can log in and check out, edit, and check back in other files that weren't checked out before?

IF everything else is clear and functional, then I'd suggest first Clear Client Side Cache, and then reopen Vault and try again.

[emmanuelhuna]

Beth, thanks for the fast reply - yes, everything is working fine.

Here's what I'll try:

1) I'll update the table tblcheckoutlisitems so all records for a specific file (eg C:\Vault\Project1\main\File1.cs) will now have a hostname of 'MYCOMPUTER/DOMAIN2'

2) I'll close the Vault client.

3) I'll delete the cache as intructed.

4) I'll start the Vault client and see if I can check in that specific file, C:\Vault\Project1\main\File1.cs.

If that works, I'll update all problematic records on tblcheckoutlisitems, clear the cache and try again for all files.

I'll let you know how it goes.

[emmanuelhuna]

That worked perfectly, thanks!