I created a "Test" project that I want to delete, using the following command:
TfsDeleteProject /server:xyz\sqlserver2008 “Test“
Getting this error:
TF30076: The server name or Uniform Resource Identifier (URI) you typed,
xyz\sqlserver2008, cannot be
resolved to a Team Foundation server.
If you type a server name, it must match the name you typed in the
Add Team Foundation Server dialog. If you type a URI, it must use
the following syntax: http[s]://:
The server instance is valid. (The installation of TFS is app tier and db are on seperate boxes) What might be going on ?
xyz is eht server name, sqlserver2008 is the db instance. For eg. I access the db using sql server management studio client app using xyz\sqlserver2008 as dbname.
Specify the full server URI including the http:// and :port. Also look for these error numbers in the MSDN.
Edit: Follow the first link, Andrew posted that's where I got my info from :)
Related
I use the Process Template Editor from the marketplace (Microsoft DevLabs). I load a Work Item Type from Project and (with or without changing anything) I want to save it. Then I get the error message:
Failed to save the 'xxx' Work Item Type to the server. TF237090: Nicht vorhanden oder Zugriff verweigert. The last sentence means in english something like not available or no permissions.
I access the server from my workstation. Both computers are in the same domain. In the AD I am only a normal user, but at the TFS I am in the group Team Foundation-Administrators. Inside the website I can modify everything normally. Can it be that this is a direct access to the database and the database has to be set to access external requests?
Or has someone another idea where to look?
I get this error when I work with TFS and I want insert an image in the description box.
solve this:
go Team Foundation server Administration Console
in Application Tier
in change URLs => set your server URL with IP(http://i.i.i.i) or Correct Address (http://yourdomain.com)
I am developing test application for displaying claims of authenticated identity in MVC-ASP.net (Visual studio 2013)
I have given authentication from active directory in following way.
1.Add new mvc project in solution .
2.click on Change authentication.
3.select organization account
4.select on premises.
5.given federation url
6.App Id url
After running the application i am getting following error.
WIF10201: No valid key mapping found for securityToken: 'System.IdentityModel.Tokens.X509SecurityToken' and issuer: 'http://websso.avanade.com/adfs/services/trust'
This error is coming only for this federation for other federation i am able to see claims.
After searching on internet i am thinking that it is certificate(thumbprint) issue.
But I am not clear with solutions.
Can anybody explain me why this error throwing and solution for the same.
Thanks in Advance !!!
There could be 2 causes for this error.
Missing thumbprint in web.config: Get the actual thumbprint from ADFS and put in web.config under the thumbprint tag
Mismatch in port number between the site and ADFS configuration: Update ADFS configuration with the url containing the correct port number
The second solution fixed it for me...
I ran into this while trying to update a legacy MVC application to use AAD.
I based the changes on a newly created project with organizational authentication and noticed I did not have a connection string named DefaultConnection, which the DatabaseIssuerNameRegistry assumes you will, nor did I have either of the required tables in the database.
Using Vittorio Bertocci's great post with all the details, I refactored the code to integrate the new database tables, created and applied a migration, and inserted the appropriate key and tenant in the new IssuingAuthorityKey and Tenant tables, respectively. I also had to make sure to change the DatabaseIssueNameRegistry to use the existing DbContext.
For solutions created in VS2013 and later, the solution should contain the logic to roll over keys automatically. No need to put the value in the web.config file.
You might run into this issue when migrating your solution from local to another environment. In that case you will probably try to point your solution to a new application in Azure Active Directory. Check the following:
Make sure all urls in the web.config are pointing to the correct url not the one automatically generated when you set it up locally
Remove all enteries from IssuingAuthorityKeys table. The keys will autopopulate when you re-build the solution and run it. On the server you might need to replace the dlls manually for it to refresh
Last and most important, delete all rows from the Tenants table. On the first run on the new environment, an Admin from the owning Active Directory has to sign up and authorize the application.
If the values in both tables are still not populated automatically after these steps, check this article for steps on how to manually get the values.
Thumbprints and server names are case sensitive in web.config. make sure they are typed correctly and restart IIS.
It fixed my issue.
I'm trying to upgrade from TFS2012.2 to TFS2012.3.
I downloaded the ISO, ran the tfs_server.exe, and after a few reboots, I'm prompted with the Upgrade Wizard.
On step two(2) "Specify a Team Foundation Server configuration database to upgrade", I need to specify a SQL Server Instance. But when I click "List Available Databases", no database shows up in the list.
I tried different combinations of SQL Server Instance (servername, servername.domain, ., (local)) but all of them returns an empty list. Note SQL is not running named instance.
SQL is up and running and I can see the TFS databases (Tfs_Configuration, Tfs_DefaultCollection, Tfs_Warehouse).
Everything is running on this one machine.
Digging deeper, in the Event Logs (Team Foundation Server Build Service Events), I found this:
Exception Message: TF400686: The requested schema property TFS_SCHEMA_VERSION did not match the expected value. The server requires the Microsoft Team Foundation Server 2012 M49 schema but the database currently implements Microsoft Team Foundation Server 2012 M44 (QU2). (type DatabaseSchemaException)
I'm not sure if this is a clue or not.
Last point: If I go to the TFS Admin Console, when I click on Application Tier, the screen shows a "This features has been installed but needs to be configured. Click on Configure Installed Features to begin initial configuration."
Did I miss a step?
I've been experimenting with ASP.Net MVC, and have come across a problem that is probably not specifically MVC related. But I cannot get the authentication in the default MVC application (the one created by the wizard when you create a new MVC project) to work properly under IIS 7 on Windows 7.
If I run under the Visual Studio environment, it works, but if I switch the settings to run under IIS instead, I get the following exception trying to submit the login or registration:
Failed to generate a user instance of
SQL Server due to failure in
retrieving the user's local
application data path. Please make
sure the user has a local user profile
on the computer. The connection will
be closed.
I believe that this is because the website runs under my own account in Visual Studio, but under the IUSR account in IIS. Google searches on the exception message have been unhelpful so far.
So, can one create a local user profile for the IUSR account? If so, how? Is there something else I should be doing to get the SQLExpress engine to work under the anonymous account in IIS 7?
I also tried configuring the IIS website to use my account, but since this is my home machine, my account doesn't have a password, and it appears that IIS won't let a website be configured to use an account without a password. Or, since this is my first experience with IIS 7, and configuration feels very different than IIS 5/6, I am just missing the right setting that will let me configure the account to use for anonymous access.
EDIT: Some additional information. If I empty the App_Data folder and try again from IIS, SQLExpress attempts to create my database and fails, but the exception message has further information with the following suggestions.
SQLExpress database file auto-creation
error:
The connection string specifies a
local Sql Server Express instance
using a database location within the
applications App_Data directory. The
provider attempted to automatically
create the application services
database because the provider
determined that the database does not
exist. The following configuration
requirements are necessary to
successfully check for existence of
the application services database and
automatically create the application
services database:
If the applications App_Data directory does not already exist, the
web server account must have read and
write access to the applications
directory. This is necessary because
the web server account will
automatically create the App_Data
directory if it does not already
exist.
If the applications App_Data directory already exists, the web
server account only requires read and
write access to the applications
App_Data directory. This is necessary
because the web server account will
attempt to verify that the Sql Server
Express database already exists within
the applications App_Data directory.
Revoking read access on the App_Data
directory from the web server account
will prevent the provider from
correctly determining if the Sql
Server Express database already
exists. This will cause an error when
the provider attempts to create a
duplicate of an already existing
database. Write access is required
because the web server accounts
credentials are used when creating the
new database.
Sql Server Express must be installed on the machine.
The process identity for the web server account must have a local user
profile. See the readme document for
details on how to create a local user
profile for both machine and domain
accounts.
I've pretty extensively confirmed that the first three suggestions have been satisfied. The fourth seems to be the cause of my problems, but I can't figure out how to do that. And although the suggestion claims there is a readme document that describes it, I have not been able to find that document.
I got this problem as well running under medium trust. The process that creates the database requires at least High trust. You can check this by looking in your Web.Config for
<trust level="TrustLevel" />
If there is no trust specified in your Web.Config, try adding it and set it to either Full or High. If this doesn't work, there is a machine.config in your IIS which you would need to modify.
That being said, the best route I have found to solve this is to just use aspnet_regsql.exe to create the necessary tables and then change the connection string in your Web.Config to look at it directly.
I solved "The directory 'LocalApplicationData' does not exist." error when running an SSIS package through an SQL Job by ensuring the SQL SSIS service and SQL Server Agent service were running under the same account as the swql job was set to use!
This in my case was a domain account.
Solution: Try UNINSTALLING any updates before you started experiencing the issue. I spent countless hours - wasted hours that I will never get back in my life - reading and following every solution possible without success. I uninstalled all SQL Server updates and now everything works fine.