W
WithSPDev
Guest
I am new to TFS. I have been working with Visual Studio and TFS for several months without problem. I started being kicked out of TFS and having to log in to TFS when I was trying to do anything with source control, i.e. check in files or do file comparisons.
Eventually, it would not allow me to log back in at all. I believe this was around the time I changed my windows password.
I kept seeing a message saying. TF204017: the operation cannot be completed because the user does not have one or more required permissions (use) for workspace: workspacename: Admin
I also see a message saying my workspace was not mapped so when I try to re-map it to my working folder, an error message appears saying my workspace is already mapped to the working folder path and I cannot get beyond this point.
I eventually was able to change this by elevating the viewing level of the workspace to Public via Source Control Explorer. The error message I saw then was: "Object not set to an instance of an object". TFS also says it was not connected to a workspace and when I try to connect to my workspace name it appears to connect but still I cannot get beyond "Object not set to an instance of object"
So I backed up my code, deleted the workspace and tried to create anew one pointing to my backup folder, but I still get the "Object not set" error message.
After searching for answers I see help that suggests using a VB online command tool to (tf.exe) to search for all workspaces on my pc and delete them. there is also information about deleting entries from my appdata\locals cache.
Can anyone help or offer some advice? I don't understand why this has happened and I need to get this fixed as soon as possible
Continue reading...
Eventually, it would not allow me to log back in at all. I believe this was around the time I changed my windows password.
I kept seeing a message saying. TF204017: the operation cannot be completed because the user does not have one or more required permissions (use) for workspace: workspacename: Admin
I also see a message saying my workspace was not mapped so when I try to re-map it to my working folder, an error message appears saying my workspace is already mapped to the working folder path and I cannot get beyond this point.
I eventually was able to change this by elevating the viewing level of the workspace to Public via Source Control Explorer. The error message I saw then was: "Object not set to an instance of an object". TFS also says it was not connected to a workspace and when I try to connect to my workspace name it appears to connect but still I cannot get beyond "Object not set to an instance of object"
So I backed up my code, deleted the workspace and tried to create anew one pointing to my backup folder, but I still get the "Object not set" error message.
After searching for answers I see help that suggests using a VB online command tool to (tf.exe) to search for all workspaces on my pc and delete them. there is also information about deleting entries from my appdata\locals cache.
Can anyone help or offer some advice? I don't understand why this has happened and I need to get this fixed as soon as possible
Continue reading...