While trying to open source control explorer in VS 2008 (when you are connected to TFS 2017 or above) you get the following error:
The user name [ID] is not a fully-qualified user name. Pareter name: workspaceOwner
How do we fix it?
After a bit of googling, I found the solution. Here is the link:
https://developercommunity.visualstudio.com/content/problem/16924/vs2008-and-tfs-2017-the-user-name-id-is-not-a-full.html
and here is the summary, please download and install the following GDR's for VS 2008 and VS2010 respectively:
VS2008 GDR
VS2010 GDR
Related
I am trying to setup SSDT so that I am able to run reports locally and edit them in Visual Studio. I have a previous report that I know works. I have installed the Oracle Developer Tools for Visual Studio 2015. I can configure the dataset and have tested the connection my Oracle Database,It works. When I preview the report I can input my parameter but when I click view report I get the following error.
An error occurred during local report processing.
An error has occurred during report processing
An attempt has been made to use a data extension 'ORACLE' that is either not registered for this report serve or is not supported in this edition of Reporting Services.
We are running SQL Server 2012
I have Visual Studio 2008,2012,2015. I'd prefer to do everything in Visual Studio 2015. I've already setup all the TNS information as well. What settings or installs am i missing.
I've recently bumped into this issue and it was very tricky to resolve. It looks like there was an undocumented change to the drivers used in the SQL 2016 RTM release, as I didn't strike these issues on the same machine when it had the RC3 build.
Anyway in case it helps, here are the setup steps I'm using (with thanks to Dan English for some tips):
Install Oracle drivers: Oracle Client 12c (32-bit) plus ODAC.
a. Download and unzip the following files from http://www.oracle.com/technetwork/database/enterprise-edition/downloads/database12c-win64-download-2297732.html and http://www.oracle.com/technetwork/database/windows/downloads/utilsoft-087491.html ):
i. winnt_12102_client32.zip
ii. ODAC112040Xcopy_32bit.zip
b. Run winnt_12102_client32\client32\setup.exe. For the Installation Type, choose Admin. For the installation location enter C:\Oracle\Oracle12. Accept other defaults.
c. Start a Command Prompt “As Administrator” and change directory (cd) to your ODAC112040Xcopy_32bit folder.
d. Enter the command: install.bat all C:\Oracle\Oracle12 odac
e. Copy the tnsnames.ora file from another machine to these folders:
i. C:\Oracle\Oracle12\network\admin
ii. C:\Oracle\Oracle12\product\12.1.0\client_1\network\admin
Install Oracle drivers: Oracle Client 12c (64-bit) plus ODAC.
a. Download and unzip the following files from http://www.oracle.com/technetwork/database/enterprise-edition/downloads/database12c-win64-download-2297732.html and http://www.oracle.com/technetwork/database/windows/downloads/index-090165.html ):
i. winx64_12102_client.zip
ii. ODAC121024Xcopy_x64.zip
b. Run winx64_12102_client\client\setup.exe. For the Installation Type, choose Admin. For the installation location enter C:\Oracle\Oracle12_x64. Accept other defaults.
c. Start a Command Prompt “As Administrator” and change directory (cd) to the C:\Software\Oracle Client\ODAC121024Xcopy_x64 folder.
d. Enter the command: install.bat all C:\Oracle\Oracle12_x64 odac
e. Copy the tnsnames.ora file from the K drive folder (see 4.a. above) to these folders:
i. C:\Oracle\Oracle12_x64\network\admin
ii. C:\Oracle\Oracle12_x64\product\12.1.0\client_1\network\admin
After all that, most SSRS components worked OK. The exception was the SSRS Portal where Data Source setup and Test worked OK, but (bizarely) running reports gives an error:
ORA-12154: TNS:could not resolve the connect identifier specified
Eventually I gave up on this and went with an EZCONNECT connection string: host:port/sid. I never liked TNSNAMES files anyway, so this was my excuse to kill them for good.
I had this exact problem until I also installed Oracle Data Access Components. This link is for ODAC with ODT for Visual Studio - like you, I'd already installed ODT for VS 2015 but this didn't seem to be a problem.
I have migrated a MVC4 web application version controlled in VSS 2005 to TFS 2015 and that migration is successful.
Then I tried to open the project in VS 2010 (Since VS2015 does not support)
It gives me following error. How do I connect to TFS successfully
Error message:
The solution appears to be under source control, but its binding
information cannot be found. It is possible that the MSSCCPRJ.SCC file
or another item that holds the source control settings for the
solution, has been deleted. Because it is not possible to recover this
missing information automatically, the projects whose bindings are
missing will be treated as not under source control.
Using:
Windows server 2012 + Updates
SQL 2014
TFS 2015 (Version 14.0.24712.0)
Open file - Source Control - Change Source Control... Select all projects and click the Bind... button. That should re-create the binding, if the files are in a valid TFS workspace.
Since you're mixing and matching VS2010 and VS2015, you may first need to set your workspace to "Server" instead of the default for 2015's "Local". VS2010 doesn't support local workspaces. You can change this setting from Visual Studio 2015 only.
Error
TF30170: The plugin Microsoft.ProjectCreationWizard.TestManagement failed during task TestResolutionState from group TestManagement.
Explanation
Plugin error text: “System.MissingFieldException: Field not found:
'Microsoft.TeamFoundation.TestManagement.Common.WitCategoryRefName.SharedDataSet'.
at
Microsoft.TeamFoundation.TestManagement.Client.TestManagementTeamProject.get_SharedParameterDataSetWorkItemTypeName()
at
Microsoft.TeamFoundation.TestManagement.Client.TestManagementTeamProject.get_HasSupportForSharedParameterDataSets()
at
Microsoft.TeamFoundation.TestManagement.Client.TestManagementTeamProject..ctor(TestManagementService
manager, String projectName) at
Microsoft.TeamFoundation.TestManagement.Client.TestManagementService.b__0(String
name) at
Microsoft.TeamFoundation.TestManagement.Client.ObjectCache`2.Get(Key
key, Creator creator) at
Microsoft.TeamFoundation.TestManagement.Client.TestManagementService.GetTeamProject(String
projectName) at
Microsoft.TeamFoundation.TestManagement.PcwPlugin.ContextWrapper.get_Project()
at
Microsoft.TeamFoundation.TestManagement.PcwPlugin.PcwPluginComponentCreator.SetPermissionsIfNeeded(ContextWrapper
wrapper) at
Microsoft.TeamFoundation.TestManagement.PcwPlugin.PcwPluginComponentCreator.Parse(ContextWrapper
wrapper, XmlNode taskXml, Boolean fExecute)”
User Action
Contact your Team Foundation Server administrator.
I just saw this exact problem (TFS 2013 Update 4 and Visual Studio 2013 Update 4). I found the solution posted here on the Microsoft Connect site solved the problem. In short, uninstalling some assemblies that were mistakenly installed got everything working again.
1. Close all instances on Visual Studio and Microsoft Test Manager
2. Open Visual Studio command prompt in admin mode.
3. Perform the following steps:
ngen uninstall Microsoft.TeamFoundation.TestManagement.Client
ngen uninstall Microsoft.TeamFoundation.TestManagement.Common
I have seen this issue when the version of Visual Studio is not upgraded to Update 4 and an attempt is made to create a new team project. I would suggest that you first make sure that the version of visual studio (that you use to create the new team project) is on the same version as TFS (in this case Update 4).
I found a workaroud on msdn forum
There is a bug in the V1.0 version of the product that impacts Team
Project creation when the Team Foundation Administrators group has a
TFS project level group in its hierarchy. One way that this might
occur is if you try to open the system up by adding the Team
Foundation Valid Users group to the Team Foundation Administrators
group, though any TFS project level group will trigger the condition
(e.g., [project A]\Project Administrators). This issue only impacts
Team Project creation and it can be worked around by temporarily
removing the TFS project level group from the Team Foundation
Administrators group. There is a variation on this Team Project
creation bug that will appear if the sync process runs across a user
that does not have a valid security identifier. I am not quite sure
if your case of deleted domain users triggers this condition, but I
will follow up to find out. In the meantime, please take a look at
the membership of your Team Foundation Administrators group to see if
there are any TFS project level groups in the hierarchy.
I don't know if Microsoft had realeased a patch for this bug but for now I choosed to return to TFS 2012 which works like a charm
Download the Visual Studio 2013 Ultimate package from Microsoft Volume Licensing site; extracted the ISO to a local folder and ran the EXE.
All goes well for a while, until it fails and says "Setup Failed!"
Then it displays the error message...
Microsoft Visual Studio 2013 VsGraphics Helper
Not a cryptographic message or the cryptographic message is not formatted correctly.
See screenshot # http://i.stack.imgur.com/stdYB.png
The fix for my issue was to browse the image and locate the installer package for the vsgraphics_helperbits.msi.
Location relative to ISO:
\Install\packages\vsgraphics_helper\amd64\vsgraphics_helperbits.msi
Just on internet on your pc and go to the below path then rename the amd64 to amd64888s
packages\vsgraphics_helper\amd64
Now run the setup and after getting package error just click on the download from internet option and continue the setup.
Have a happy coding
I encountered the same problem with the Visual Studio 2013 Ultimate With Update 5 ISO after extracting it even if the SHA-1 was correct.
Solution if your machine has access to internet : Simply delete the corrupted packages folders in packages\. The installer will prompt you to download them.
You can find the packages in error in the log given by the installer when the setup is complete (fail or success).
On my Windows 7, I had to delete these packages to avoid errors and warnings :
netfx_451mtpack
netfx_451mtpackcor
PerfTools_CORE
PortableLibrary
professionalcore
sptoolsDependencie
TFSObjectModel
TFSStoryboarding
VCDesigntime
vcRedistD11
vc_libraryDesktop
vsgraphics_helper
In bold the critical ones.
I just had this issue. Someone at another site suggested that it the ISO image file of the install was corrupt. We redownloaded it, and it installed correctly the second time.
Just make sure you have updated your windows. (Restart windows after update)
If you have the ISO then mount it to virtual drive and then run the installer. (Don't extract and run)
Hope above instructions will help.
Note: Follow same process for VS 2015 installation.
I installed Office 2013 and VS2013 on Windows 8.1 - when I now open old Projects which reference the version 12 PIAs (for Office 2007) these are missing in the references since VS2013 does only install Version 14 and 15 of the PIAs.
Since I want to Keep using PIA 12 I do not want to change the references. Instead I'd like to Register the Version 12 PIA's with VS2013. How can I achieve this?
I already tried using the PIA redistributable, but it does not want to work unless I install Office 2007, too (which I don't want). I can get a copy of the dlls from some other system, but how do I register These with Visual Studio 2013 (I don't need them in the GAC, I think, just in VS2013).
As far as I know for the PIA some COM class ID's should be recorded, I just don't know how/which.
Edit:
Right now the PIA dlls are referenced just by Name and Fingerprint/public key (no hint path). When I open the reference Panel in VS2013 they will Show up, can be selected and work. They seem to be registered somewhere so VS2013 can find them. I just want to replicate this on other Computers.
I've got the exact same setup, a machine with Windows 8.1 and only Office 2013 installed. No trouble at all getting the Office 2007 PIAs installed. Do beware that this is a two-step process. After you downloaded PrimaryInteropAssembly.exe from the Microsoft server and started it, you prompts you to give a directory to store intermediate files. Navigate to that directory, right-click the o2007pia.msi file and select Install to get them actually registered.
It isn't the only way to get them onto your machine. If you have another machine with the PIAs installed then create a dummy project and add the references to the Microsoft.Interop assemblies you need. Select them and ensure that the "Embed Interop Types" property is set to False and the "Copy Local" property is set to True. Build the project, you'll get the interop assemblies in the bin\Debug directory. Copy them to your machine and use the Browse button to add a reference to them. You always want the "Embed Interop Types" property set to True in your real project so you don't have to deploy the PIA on your user's machine anymore. Check them in with your project so you don't lose them again.
UPDATE: PIAs are obsolete since .NET 4.0 and VS2010. Check this post for the details.