Change in PC name, stops Reporting Service 2005

I deployed few reports on my Test Machine with TestMachine. As we wanted to implement a format of PC names, we happened to change the name of the Machine to e.g CompanyTestMachine
Before the rename happened, our system as well as the reports were working properly. Once the name was changed, we started getting error Report Server database not found.
Then I thought to redo the settings of Reporting service so as to change the required settings. On following the steps, I came across a error
User CompanyTestMachine\ASPNet not found
I then tried repairing the Microsoft Framework which didnt help. I ran the aspnet_regiis.exe /i command which also didn't help. I read many blogs but couldn't find a way out so I ended up renaming the machine to its original name.
I am still searching for a solution to this problem, if someone reading this has one I would appreciate if you could share it with me.

Unit Tests : Not Runnable - VSTS 2008 SP1

I am sure most of us are facing this issue. After adding ordered unit tests to our project and creating a test list for these whenever we open the project the Tests are indicated as Not-Runnable.

This can be sorted by pressing the Refresh button in the Test View as below

Read this for more details

http://social.msdn.microsoft.com/forums/en-US/vststest/thread/2f907f7b-c689-439e-9dfb-731b5b7795f4/

Delete a Team Project

One of the new team members accidently created a team project (Remiss of the administrator for giving him full control).
Found out a way to delete the team project
Open a command line on your team foundation server and cd to
drive:/%program files%\Microsoft Visual Studio 9.0\Common7\IDE (For VSTS 2008)

tfsdeleteproject /q /force /server:<tfs server> "<project name>"

Restoring TFS 2008

I am sure everyone will be taking backup of their TFS on regular basis. Being new to TFS I thought to try and restore the TFS on a new machine, to avoid the risk of not taking backup of anything.

I had a spare PC in which I installed the trial of TFS. the environment of the new machine was now exactly the same as that of the old (or existing)machine.
The link which helped me for this was
http://msdn.microsoft.com/en-us/library/ms404869.aspx

Error 28002 : Unknown Error

This was the forth time I was installing TFS 2008 and I got this error for the first time. It has to do with the DNS. TFS is not able to resolve the Domain Name as a result of which it gives TFS3010 (if you see the Event log).
Resolution:
1. Open the web.config from the path below (TFS Root)
%systemdrive%/Program Files\Microsoft Visual Studio 2008 Team Foundation Server/Web Services/Web.config

Add the below key
<add key="<DomainFullyQualifiedPath>" value="dcHostName" />

And hit Retry on the Error message.

Error (rsAccessDenied) - 'NT AUTHORITY\NETWORK SERVICE' are insufficient

I did all the necessary settings to the reporting service so that my domain users can access the reporting service, but still I was getting rsAccessDenied error.

Then I read once solution in one of the forums in which there were few steps mentioned which solved my problem
1. Open http://localhost/reports
2. Go to Home Properties
3. Add a BUILTIN\Users and gave it Browser permissions and the problem was solved.

TF30042: The database is full. Contact your Team Foundation Server administrator.

Since many days we were facing problems with Low disk space on our TFS machine. I noticed that the LoadTest database Log was around 19Gigs. Till then I was not aware that there is a setting for restricting growth of the Log file. I then moved my mdf and ldf files to a drive with ample space and then restricted the growth of Log not more than 20Gigs.

And subsequently I changed the settings of all the TFS database not to grow exponentially. But the next day I came and tried to start my VSTS, it started givine me the same error

TF30042: The database is full. Contact your Team Foundation Server administrator.

Reading few blogs, I decided to change the Recovery Model of all the database from full to simple. And I was able to use my TFS without any issues after that. Below are the steps

1. Go to properties of the database

2. In Options tab, change Recovery model from Full to Simple.

I read in couple of blogs that it is not advisable to use Full Recovery model for the database which is used for version control.