This issue is mostly likely caused by a conflict in user names being provided to the VCS client running on the Integration Server. If the VCS client is not running at the time of a VCS transaction in Designer, the VCS Integration feature starts the VCS client and passes it the appropriate command string, which includes the VCS user account name associated with the current Designer user account. When the transaction is complete, the VCS client terminates. This mode of operation causes no problems. However, it is possible that the VCS client may already be running and connected to the VCS server with a VCS user account that is different from the VCS user account that is associated with the current Designer user. In this case, when a VCS transaction occurs, the VCS Integration feature will pass the VCS client a VCS user name that is different than the VCS client’s connected user name. This causes unexpected results in the VCS transaction.

Patrick starts the VCS client on Integration Server and connects to the VCS server as user Patrick_VCS. He completes his VCS tasks but leaves the VCS client running. Patrick then logs on to Designer as user Administrator. This account is associated with the VCS user account Admin_VCS. Patrick attempts to check out some elements from the VCS. The VCS Integration feature submits the transaction to the VCS client with the VCS user name of Admin_VCS, but the VCS client is connected to the server as Patrick_VCS. Unexpected results occur.

Either shut down the VCS client on the Integration Server, or restart the VCS client and connect to the VCS server using the same VCS user name as the one associated with the current Designer user.