Explanation:

TFS 2012 and VS 2012 featured with new workspace concept called “local” workspaces.The workspace concept which was available from VS/TFS 2005 - 2010 is called as “server” workspaces. “server” workspaces is the default option while creating a new workspace in VS 2012.

When a local workspace is created, the required data structures will be moved from the TFS server onto the TFS Client. The data structures are local to local machine instead of being hosted on the TFS server. Moving the data structures to local machine gives VS 2012 the ability to perform a number of source control operations without TFS web service calls or active connection to TFS server. The following operations continue to work when the local machine is disconnected from the TFS server.

• Opening a source-controlled solution
• Checking out a file for edit
• adding a new file or folder for add
• Delete on an existing file or folder
• Rename on an existing file or folder
• Monitor pending changes in the workspace
• Undoing pending changes
• Diffing your copy of a file with the version of the file your change is pended against
• The local workspace will not carry read only bit during get source.
• “Promoting” the candidate adds and/or deletes
• The local workspace will be invisible to VS 2010 and earlier versions
• No enforcement of PendChange permission or checkout locks
• The local workspace can be converted to Server workspace and reverse the same

Drawback on Local workspaces.

Local workspaces have scalability limitations due to their use of the local workspace scanner which checks for edited items.If the workspace has more than 50,000 items, There may be performance problems or "TF400030 errors as operations exceed 45 seconds in duration." may occur

Steps to create a local workspace.

Exception:

"TF400030: The local data store is currently in use by another operation. Please wait and then try your operation again. If this error persists, restart the application.”

Explanation:

The error occur when using local workspaces in Visual Studio 2012 or later

TFS 2012 and VS 2012 featured with new workspace concept called “local” workspaces.The workspace concept which was available from VS/TFS 2005 - 2010 is called as “server” workspaces 

When a local workspace is created, The required data structures will be moved from the TFS server onto the TFS Client. The data structures are local to local machine instead of being hosted on the TFS server. Moving the data structures to local machine gives VS 2012 the ability to perform a number of source control operations without TFS web service calls. The following operations continue to work when the local machine is disconnected from the TFS server.

• Opening a source-controlled solution
• Checking out a file for edit
• adding a new file or folder for add
• Delete on an existing file or folder
• Rename on an existing file or folder
• Monitor pending changes in the workspace
• Undoing pending changes
• Diffing your copy of a file with the version of the file your change is pended against
• The local workspace will not carry read only bit during get source.
• “Promoting” the candidate adds and/or deletes
• The local workspace will be invisible to VS 2010 and earlier versions
• No enforcement of PendChange permission or checkout locks
• The local workspace can be converted to Server workspace and reverse the same

Local workspaces have scalability limitations due to their use of the local workspace scanner which checks for edited items.If the workspace has more than 50,000 items, There may be performance problems or "TF400030 errors as operations exceed 45 seconds in duration." may occur

Reconciled operation on the server or deadlock between two operations may also trigger the error.

In Local workspace architecture, only a single operation (thread) can use this local data at a time. If two pieces of system want to use the data store simultaneously – perhaps the Solution Explorer and the Source Control Explorer both want to refresh after an Undo operation was performed – then these two components have to take turns to use the local data store. One will wait for the other to finish, and who gets to go first is arbitrary.

The ‘loser’ of the race has to wait before proceeding, but will only wait for about 45 seconds. If he ends up waiting for that full amount of time, but still doesn’t get the chance to use the local data store (because some other component of the system is still using it), then this error will be raised.

Workaround:

• keep the size of the local workspace from growing too large, files and folders less than 50,000 items
• Avoid working with extremely large sets of pending changes (10,000+) for a long time without checking in. This helps to keep ‘reconcile’ costs low
• Install Visual Studio 2012 Update 2 or later to get protected from the deadlock scenarios
• Convert the local workspace to server workspace

Exception:

Explanation:

The error may occur when the following cache folder size increases.

C:\Users\<tfsservice account / Build account>\AppData\Local\Temp

Solution:

Clearing the content of the following cache folder location resolved issue with build and team project creation. 

C:\Users\<tfsservice account / Build account>\AppData\Local\Temp

Explanation:

Build fails with missing file: System.Management.Automation.dll, The InvokePowerShellCommand activity in Community TFS Build Extensions has a dependency on System.Management.Automation.DLL

Solution:

Install Windows Management Framework 3.0 on the build server.