I have installed and configured TFS 2013.
The TFS Administration Console shows in the Reporting section the following urls:
Reporting Server: http://COMPUTERNAME:80/ReportServer_STANDARD2014
Reporting Manager: http://COMPUTERNAME:80/Report_STANDARD2014
but in the IIS Manager, I do not have a web with the name "COMPUTERNAME". The URL ist inaccessible. But I cannot change it to the Machines IP Address, I get an error message, with not found and so on.
Why tfs uses such inaccessible URLS. How I can access the Reports?
I have also set up a Build configuration. In the tfs event viewer, I can read, that the build service http://COMPUTERNAME:9191/Build/v5.0/Services successfully registered.
But this url seems also not correct. But the buildservice is running.
And I have another problem with accessing the tfs web-interface.
From machines outside in the internet, I am able to access the tfs webinterface with the dns name of the machine like http://www.ourdomain.net:8080/tfs
But on the TFS server itself, I cannot. I can only access by the machines ip-address like http://11.12.13.14:8080/tfs
Using the dns name, I cannot log on, the provided credential is not accepted.
TFS queries reporting services and uses the URL's that it reports.
You can find the correct URL's if you open the Reporting Services Configuration console on the box it runs on. RS no longer uses IIS so you will not find anything in there.
It sounds like someone has changed the reporting services url since tfs was configured.
Update your hosts file with the correct IP address for computer names.
Related
I'm new to Jenkins and am trying to set up the team project collection. My servername is:
http://<server-name>/tfs/Development%20and%20CFS%20UK/
I've left the last bit in so you can see it has spaces.
I'm adding the Jenkins credentials as:
Domain: Global credentials (it won't let me choose anything else)
Kind: Username with Password
Username: my windows domain\username used to access TFS
Password: my windows password used to access TFS
ID/Description, not sure whether these are important - assume not!
The error I receive is as follows:
javax.servlet.ServletException: com.microsoft.tfs.core.exceptions.TECoreException: The SOAP endpoint http://<server-name>/tfs/Development%20and%20CFS%20UK/Services/v1.0/Registration.asmx could not be contacted. HTTP status: 502
If I cut and paste the url above into a browser it appears fine, with the following message:
Team Foundation Registration web service
The following operations are supported. For a formal definition, please review the Service Description.
GetRegistrationEntries
The login name is important which must contain the name of domain and user.
For [on-premises] Team Foundation Server, the User name can be
specified in two ways:
EXAMPLE-DOMAIN\user
user#domain.example.com
Suggest you to use the latest Team Foundation Server Plugin in Jenkins, more details of the job configuration, you can check the release note.
To narrow down if the space of your team project collection cause the issue, you could give a try with another collection url without space.
Update
If you copy the collection url in browser, it should link to a TFS web portal.
I already have a website running and want to install JIRA Server on it. So how do I add a sub directory to my main website, example www.mywebsite.com is my actual website so want www.mywebsite.com/Jira how do I achieve this?
I had downloaded the windows JIRA Installer and ran it locally connecting to the database hosted on my server and it worked using localhost(http://localhost:8080/secure/Dashboard.jspa) however now I want to access it through the web link i.e base URL.
I am new to this so any help would be really appreciated.
Well I understand you do have a domain and you want to run your JIRA with context path /jira un that domain. If that's the case, you may need to consider running your JIRA behind proxy. Take a look at Atlassian documentation since it contains all the information that you need for this:
https://confluence.atlassian.com/kb/proxying-atlassian-server-applications-with-apache-http-server-mod_proxy_http-806032611.html
My server running TFS express crashed. I managed to mount the disk and extract mdf/ldf file for my TFS collection. Here is what I did next:
Built a new machine (with the same name/IP address) and installed SQL Express/TFS server express.
From SQL Server Management Studio, attached the mdf/ldf files. I can now see TFS_MyCollection as a new database.
From TFS Administrative console, clicked on "Attach Collection."
However, the new database is not being listed.
I went through a bunch of links on the Internet. https://social.msdn.microsoft.com/Forums/en-US/d949edf3-1795-448a-a1cc-39555ce87b50/tfs-2010-installation-error had a similar situation. Based on the suggestion, I had attached the database. I also looked at https://msdn.microsoft.com/en-us/library/ms404869(VS.80).aspx. However, this one talks about using backup/restore, which is not my case.
I must be missing some configuration step. Please advice. Regards.
You cant just attach a collection that was never detached.
You need to unconfigure your TFS instance (tfconfig.exe setup /uninstall:all) and then restore all of the databases.
You will need to restore each collection and the configuration DB. They are currently a set. Once you have all of the databses attached/restored you need to run the setup and "configure application tier only".
https://msdn.microsoft.com/en-us/library/ms404869.aspx
You need to follow the documentation for moving hardware. Make sure that you follow each step.
Note: You should take backups!
I have a prod domain and a test domain, unfortunately in the only part I can install TFS ins a virtual machine in the test domain.
The question is, as developers, can we still access the tfs for source control? As far as I know it will use the windows credentials when connecting and those credentials wont exist in the test environment.
What can you suggest?
Yes, Team Explorer clients will try to authenticate with the default Windows credentials to the TFS server. If you're on different domains (and there's no trust relationship between them) then this authentication will fail and you'll be prompted to enter your username/password for the TFS server.
If you don't wish to be prompted each time, you can set up credentials for the server in the Windows Credential Manager in your Control Panel.
I am currently in the middle of a TFS 2010 multi-server installation and have the following questions:
should i go with the default installation of having tfs sit on http://server:8080/tfs as i would probably prefer http://server/ or http://server:8080
I can't seem to find the best practice for which user i should use to remotely connect to the reporting services - should this be a domain user, or a local machine account on the database server?
If i install sharepoint and i want the database stored on another server, am i ok to install sharepoint as a single server or do i need to install "application only" and create a "farm"
that is all :)
•should i go with the default
installation of having tfs sit on
http://server:8080/tfs as i would
probably prefer http://server/ or
http://server:8080
We have our hosted externaly so we go with a FQDN, but if not you should use the default as Visual Studio also uses this default. By all means setup a FQDN or other URL on port 80 to give people the choice, and to make the web access more accessable.
•I can't seem to find the best
practice for which user i should use
to remotely connect to the reporting
services - should this be a domain
user, or a local machine account on
the database server?
Network Service is fine and TFS will set everything up during the install. You can create a "domain\TfsReports" if it makes you feel better and I would recommend this if you are going to setup Kerberos or are runnign in a security consious enviroment.
•If i install sharepoint and i want
the database stored on another server,
am i ok to install sharepoint as a
single server or do i need to install
"application only" and create a "farm"
You can put the Sharepoint databases anywher you like during the insatll. if you are doing what you sugest, remember not to lose them. A better option would be to integrate with your existing Sharepoint 2007/2010 corporate deployment.
Integrate SharePoint 2010 with Team Foundation Server 2010