CODEWITHSUNDEEP
team-explorer-everywhere
Setsu
Setsu

Reputation: 1228

Team Explorer Everywhere command line can't checkin

When I try to do a checkin command I get an error saying No changes were matched by any arguments, but the file has in fact been changed! The culprit seems to be that TEE didn't automatically checkout the file upon edit, even though MSDN seems to suggest that it should have (source).

OK big deal, so I tried to checkout the file instead knowing I'd have to make the changes again. But this time I'm getting a new error saying: 

An error occurred: TF400032: The operation could not be completed because the workspace 
WORKSPACE_NAME is a local workspace.

Things get more bizarre when I try to do other things, like a simple add; it gives the same error! It seems that the only thing I could get working was using tf get to update everything to the latest version.

I'm at a loss to what's causing this after several attempts: (right now I'm not able to push any changes to the server)

  1. Modified file using vim. tf status doesn't report changes
  2. Tried tf checkin file.m and tf checkin file.m -force, both of which reported no changes
  3. Tried tf get file.m, but it reports that the file is up to date. Tried tf get file.m -force and this time it properly replaced the file with the server version
  4. Tried tf checkout file.m, but it reports the error message about the local workspace
  5. Tried tf add file.m, but it reports the same error message about the local workspace

Here's some details on my setup:

Upvotes: 3

Views: 1508

Answers (1)

evenro
evenro

Reputation: 2646

I'm not sure if it is relevant in your case, but for me that was the issue:

If you are connected to a cluster, with multiple computers/servers, the workspace is created for the specific server you were logged in to (although the storage is probably shared).

This results in the workspace having a computer name that mismatches the computer name from which you'd might later check in your file.

The only solution I found so far is to connect to the specific node which I was running the creation of the workspace and work from that node. (or to upload the edited file using the web interface). Same issue will rise if you work locally, but changed your computer name or any related configuration (domain for example).

Hope it helps...

Upvotes: 2

Related Questions