September 5, 2011 
I got this message a few weeks ago and it scared me. Why? Let me tell you.
The company where I do a lot of consultancy called me in the middle of the day that users started receiving this message. People could not check-in, create work items or add/edit any TFS information.
The support engineer already had looked in the Event Log and found the following result.
Detailed Message: TF30065: An unhandled exception occurred.
That scared me. I had had this message before and back then it was a full disk of the database server. That still is not nice as it not easily fixed sometimes, but at least it is obvious.
When searching the internet I found many suggestions, but most of them indicated that I should put the DB in Simple recovery mode, or clean things up.
Do not do that because this can have serious implications!
Our disk was not full, and existing artefacts (work items, source, builds etc.) where still accessible. The database was about 50Gb. I was not planning to do anything about the database structure or data so more investigation was needed.
Strange….When we looked a little bit further in the event log there were also different kind of messages.
“Could not allocate space for object ‘dbo.WorkItemsWere’.’PK_WorkItemsWere’ in database ‘Tfs_DefaultCollection’ because the ‘PRIMARY’ filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup”
Aha ! That was actually the hint I was looking for. As we already checked disk space I thought of SQL Server. You can fix a database. What I understood is that this is a trick a lot of DBA’s perform to increase performance on a database. Fix the size of the database file.
In order to fix the problem, we opened the properties of the TFS_DefaultCollection database and changed the autogrowth property to Unrestricted File Growth.
Hope this helps!
The Road to ALM 
Thanks for sharing the article. MTM was throwing a error message and i could pin point the issue by going through the article. Cheers.. Nav
My brother suggested I might like this website. He was entirely right. This post truly made my day. You cann’t imagine just how so much time I had spent for this info! Thank you!
Remember though that at some point with this solution though you will indeed hit a real space limitation. I would advise that proper growth planning is required after this is done.
Hi,
Increase size limit is an option, but not applicable when TLog is the source problem. In this case, a SHRINK of TLog is compulsory:
ALTER DATABASE [mydatabase] SET RECOVERY SIMPLE
DBCC SHRINKFILE()
ALTER DATABASE [mydatabase] SET RECOVERY FULL
Thx, AMag