TF246069: The following database could not have its lease renewed because it cannot be reached

Question

I'm diagnosing a problem with TFS clients that lose connection to TFS.

One of the suspicious things is the next message that appears around time when people have problem accessing TFS server. Does anybody know what it means?

Update: Now I'm sure that this log message is the key to the issue. It appears in the log file at the same time when IIS log file register 503 access error for TFS web-services. There is nothing in all windows log files 10 minutes before and after this message. There is also nothing in SQL Server log file.

TF246069: The following database could not have its lease renewed because it cannot be reached: XXX. The database is hosted on the following server: XXX. Make sure that the database is online, and that no firewalls or network problems are preventing communication with the server.

Application Domain: /LM/W3SVC/8080/ROOT/tfs-1-129845101300789618

Service Host:       b4ee974a-67bd-4e00-a0ba-dc84d1d3ed73 (TEAM FOUNDATION)

Answer 1

Hi Dennis, 

Thanks for your post.

On your client, try connect to that database using SQL Server Management Studio, can connect correctly?   

What’s the version of your TFS and SQL Server? 

If you have any further research of this issue, please share your experience here.

---

John Qiao [MSFT]
MSDN Community Support | Feedback to us

Answer 2

Hi Dennis, 

Has this issue been resolved? If yes, please share your experience here. 

If misunderstood anything, please describe your question in more detail and we will be able to provide the better responses.

---

John Qiao [MSFT]
MSDN Community Support | Feedback to us

Answer 3

I'm now seeing this behavior on my server.

It's so far only been seen on our build server but we are working in a test environment before we do the real switch from TFS 2008 to 2010.

Any news/question ?

Answer 4

We do experience the same error on one of our Production TFS servers.

The TFS_Configuration database appears to be offline and all the check-in operations fail.

I did notice that the TFS transaction logs (scheduled every 15 minutes) were not backuped anymore during 45 minutes (and the problem TF246069 occurs during that period). We do use the Power Tools to backup the DB...

So, I did look at the backup logs and found this message : "System.IO.IOException: There is a time and/or date difference between the client and server." This is reported as an error.

We also often have this kind of issue when we check-in items from a "batch" which massively injecting files in TFS (those files are issued from another repository and  archived in TFS).

Could those two errors be related : the time difference and TF246069?

PS.: At the very same time as TF246069 appears, SQL Server reports "Setting database option COMPATIBILITY_LEVEL to 100 for database ReportServer." but as TF246069 is about TFS_Configuration, I am not sure if there is a link. No idea what's this message is about...

---

Valéry Letroye

Answer 5

We most probably found the root cause... our TFS are hosted on VM and this night several VM's went into loop. This caused instability on the Hyper-V cluster and ultimately all VM's went into sleep mode. 

I have only be notified of this issue now (I was unable to contact my "point of contact" in the Server Engineering team this morning - most probably very busy due to this Hyper-V issue).

I din't detect anything wrong in the event logs, etc... as the VM was sleeping, also reason why there was no backup for 45'...

---

Valéry Letroye