TFS 2012: URL not reachable - tfs

after a servercrash we installed TFS on a new server. I used Application Tier only for
restoring the databases, and in the Team Foundation Express Administration Console everything shows up.
When on the server I surf to the URL I get a Windows login screen and after entering credentials it proceeds to the website.
However, if I try this from an PC, the URL is not reachable.
I've checked the firewall (even disabled it for test), put port 8080 is added.
I gues something is wrong with the authentication, hence the Windows login screen, but fail to find.
Anyone ideas?
I use TFS Express 2012.4 on Server 2019

Since you are able to access http://localhost:8080/tfs url and work properly.
This tell you TFS is up and running. So issue should not related to IIS side.
Try to disable loopback by creating registry key under the
location
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\DisableLoopbackCheck
and assigned the value “1”.
Details follow this blog.
If you do not want to disable your firewall during daily usage. Make sure Port 8080 is open in Windows firewall.
Also take a look at this similar issue: TFS url with server name is not working

Related

TFS246017: Team Foundation Server could not connect to the database

While attempting Branch operation from within VS I get the error message TFS246017: Team Foundation Server could not connect to the database. Verify that the instance is specified correctly, that the server that is hosting the database is operational, and that network problems are not blocking communication with the server. (The error message box looks like the one in this question).
I logged on to the TFS virtual machine. In event viewer I see a warnning with with the same message as above + Process Name: w3wp, User: domain\MyUser. The IIS TFS site is started.
I opened the TFS console on the TFS machine using both domain\MyUser and domain\tfssetup (this is the user running the Visual Studio Team Foundation Background Job agent service), the console opens successfully. Both users appear in the Administration Console Users list. I did reapply account for both users. I also did update password for domain\MyUser. It shows a connection string with Datasource and Initial Catalog. I logged in to the DB machine, opened SQLSERVER users: the tfssetup user is there with sysadmin and owner of relevant instances. I also added the domain\MyUser and added admin privileges (but the error persists).
I also installed SSMS on TFS machine & was able to connect to DB server using both domain\MyUser and domain\tfssetup and view tables.
This error did not happen in the past. This error didn't happen when branching a different location in the source control ($/Project1/Main vs $/Project2/Main) beforehand. The Source Control Explorer appears to show OK (so TFS is working). Using Visual Studio 2013. TFS 2017. AFAIK Virtual Machines were not moved, IP address were not changed. Using vSphere it seems there is enough disk space for both TFS and DB machines. The error appears after ~4 seconds.
What else can be tried?
Looking in the TFS SQLSERVER log there was a "SERVER ASSERTION" error and this was the cause for the TFS generic error.
In my case the error was very similiar to the one here. CHECKDB and updating to the latest service pack didn't help. What helped was changing the recovery mode to full as recommended in that thread.

Umbraco cannot start. A connection string is configured but the Umbraco cannot connect to the database

I'm using Umbraco CMS v7.4 with SQL Server 2014, the project was working fine until a few hours ago, when an error started showing up:
Umbraco cannot start. A connection string is configured but the Umbraco cannot connect to the database
The error occurs when I tried to open the website, see the image below:
I tried the following:
Checked to see if SQL Server is running
Checked the connection string credentials in web.config
Any help is appreciated.
After a few tries, even I loaded the backed up DB, I found that it caused by the DB login, the user in the connection string was having a password expiration enabled (the password had expired).
So, this is what I did:
Open the SQL server
Logged in as the user used in the connection string
Created a new password
Updated the web.config connection string "Password"
Hope this will help
So, in my case I tried to get started with the existing project. I got all the files, restored DB backup locally, made sure all permissions are set for IIS AppPool user etc. But I kept getting the error in question. It turns out that I cannot use server=localhost;database=... in connection string. After I replaced it with server=.\;database=..., it started to work right away.
Also note that if you're running it in Azure with an Azure SQL database you'll have to go to the Azure SQL Server settings and under "Firewalls and virtual networks" you'll need to tick "Yes" for "Allow Azure services and resources to access this server".
I was getting this error when running an Umbraco project locally, with the DB pointing to an instance on Azure. In that case, this problem happens if you haven't allowed the IP access within the Server Firewall of the DB in Azure.
You can fix this by finding out your IP and then adding it to the DB:
Click All Resources within your Azure portal, then click on the SQL Database your project points to.
Click Set Server Firewall on the right-side window.
Add in your IP as the start and end points, and call it something memorable.
Click Save and once you get the confirmation message that It has been applied, refresh your site locally.
I experienced the same problem and here is how I fixed it.
Right-click on your localhost in SSMS and select Properties
Got to the Security page and select "Select authentication" as "SQL Server and Windows Authentication mode"
Hit OK.
Go to Services and find your SQL Server service and restart it.
Check your local umbraco website now, you should be able to see it without any issues. If you still have problems, then you might need to check your local setup and permissions.
Further details are below and on this blog post.

Can't change notification url on team foundation server 2010 to domain name

Here is a bit of background on the setup:
I have a server called "File-Serv".
I have an NS entry that redirects clients.mydomain.com to the ip address of the modem which in turns forwards the request to the computer (this is all working perfectly so far)
I have apache running on port 80 and one IIS site running on port 8080
I installed TFS and changed the binding of the TFS site to use port 8081 so that it doesn't clash with the rest.
I installed team explorer on the server and was able to connect to TFS and add a project, etc.
The problem is now that i want to access TFS from all other computers on the network and more importantly still access TFS if i'm not connected to the local network but i can't
What i have tried is to change the notification url to clients.mydomain.com and change the binding on IIS to match. when i go to clients.mydomain.com:8081/tfs/web it asks me for a username and password
I do not have active directory installed and i have created users for all the users needed on the server but when whatever combination i put for username/password, i can never ever log in.
I've tried the following usernames with no success:
Administrator
File-Serv\Administrator
clients.mydomain.com\Administrator
I'm really not sure what i'm missing here.. I have read forums upon forums without any resolution. Help!
P.S. This is my first question on stackoverflow after using the site religiously for 2 years now!

Team Foundation Server 2012 broken web access - Error TF400893

I have installed TFS 2012 Express on my computer but I can't get TFS web access portal to work. If I try to view a page with work items I get error:
TF400893: Team Foundation Server services are not available.
This is most likely caused by a network error.
Please check your connection and try again.
It's weird because other parts of the TFS web portal works (e.g. source) so I don't think it's network error. If I connect to the TFS server from Visual Studio everything is working, so I suppose TFS service is running.
I tried to reinstall TFS, but it didn't help :-(
Any ideas what can be wrong?
Try an other browser. I have used Opera and got the error. Using IE should work.
Try changing the account from Applicaiton Tier on TFS Administration Console to your current domain and user info. The default value is NT AUTHORITY.
You should check for any firewalls or other IPS devices between the browser and the application tier for SQL injection attack rules. WIQL being sent from the browser in the AJAX request looks far too much like regular SQL so gets canned by such rules.
As we were experiencing this issue where I work, I decided to take a network packet capture of the browser traffic on a machine experiencing the problem. This yielded a whole bunch of TCP retransmits on the packet containing the plain-text WIQL. Upon presenting this evidence to the company's network team, they located the offending IPS rule which was triggering on these packets, disabled it for packets targeting the TFS Application tier and the problem was solved.
I just got the same error while adding a comment to a work item which included a SQL Statement to drop some tables.
After changing my language to not include explicit T-SQL "DROP TABLE" syntax, I was able to add the comment. My guess is something trying to prevent SQL injection.

WebService Error Endpoint

I'm working on a project that must connect to a asmx page.
But, it throws an exception 'Endpoint not found', but I configured all my app, set all the endpoints configurations in app.config. I've tried to connect to localhost and it works.
I've also tried something like disable firewall...
What could it be? Must it have something to port configuration?
Thanks!
Is this a deployed app, or are you running in debug mode from Visual Studio? In visual studio debug mode, you will have to set your endpoint addresses to include whatever port # the webservice starts on when you click "run" in VS (it should popup in your notifications tray). Then when you publish the project later, you will have to remember to change these endpoints back to not include the port #... That's the only thing I can think of that has tripped me up in the past. If that's not it- good luck.

Resources