Sharepoint Versions - v.2 & v,3

I guess that at least once you found yourself asking what version of Sharepoint i got installed on my server? do i have any KB's? Cumulative Update?

Here's something that might help you out:

If you're asking yourself how can i find what the version installed on my server the answer quite simple all you need to do is:
connect to you central administration and access your server farms.

Version Number	Sharepoint Version	Installed Updates	Description	Date
12.0.0.6535	MOSS 2007/WSS 3.0	KB960011/KB960010	Cumulative Update	Dec-09
12.0.0.6524	MOSS 2007/WSS 3.0	KB977026/KB977027	Cumulative Update	Dec-09
12.0.0.6520	MOSS 2007/WSS 3.0	KB974988/KB974989	Cumulative Update	Oct-09
12.0.0.6514	MOSS 2007/WSS 3.0	KB973409/KB973410	Cumulative Update	Aug-09
12.0.0.6510	MOSS 2007/WSS 3.0	KB971537/KB971538	Cumulative Update	Jun-09
12.0.0.6504	MOSS 2007/WSS 3.0	KB968851/KB968850	Cumulative Update	Apr-09
12.0.0.6421	MOSS 2007/WSS 3.0	KB953334/KB953338	SP2	Apr-09
12.0.0.6341	MOSS 2007/WSS 3.0	KB956056/KB956057	Cumulative Update	Feb-09
12.0.0.6335	MOSS 2007/WSS 3.0	KB960010/KB960011	Cumulative Update	Dec-08
12.0.0.6331	MOSS 2007/WSS 3.0	KB957691/KB957693 KB958567/KB958569	Cumulative Update	Oct-08
12.0.0.6327	MOSS 2007/WSS 3.0	KB956056/KB956057	Cumulative Update	Aug-08
12.0.0.6318	MOSS 2007/WSS 3.0	KB951695/KB951297	Infrastructure Update	Jul-08
12.0.0.6303	MOSS 2007/WSS 3.0	KB948945	post-SP1 hotfix	Feb-08
12.0.0.6301	MOSS 2007/WSS 3.0	KB941274	post-SP1 hotfix	Jan-08
12.0.0.6300	MOSS 2007/WSS 3.0	KB941422	post-SP1 hotfix	Feb-08
12.0.0.6219	MOSS 2007/WSS 3.0	KB936984/KB936988	SP1	Dec-07
12.0.0.6039	MOSS 2007/WSS 3.0	KB942017	Cumulative Update	Oct-07
12.0.0.6036	MOSS 2007/WSS 3.0	KB941422	Hotfix Package	Aug-07
12.0.0.4518	MOSS 2007/WSS 3.0	N/A	RTM	Nov-06
12.0.0.4407	MOSS 2007/WSS 3.0	N/A	Beta 2 TR	Jan-06
12.0.0.4017	MOSS 2007/WSS 3.0	N/A	Beta 2	Jan-06
11.0.8168.0/ 11.0.8173.0	SPS/WSS 2.0	KB923644	SP3	Sep-07
11.0.8126.2/ 11.0.8000.0	SPS/WSS 2.0	KB919175	Post SP2 Rollup	Oct-05
11.0.8126.0/ 11.0.7969.0	SPS/WSS 2.0	LB887623	SP2	Oct-05
11.0.6551.0	SPS/WSS 2.0	N/A	WSS R2	Sep-05
11.0.6411.0	SPS/WSS 2.0	KB887981	Security Update	Feb-05
11.0.6715.0/ 11.0.6361.0	SPS/WSS 2.0	KB841883	SP1	Aug-04
11.0.5704.0/ 11.0.5608.0	SPS/WSS 2.0	N/A	RTM	N/A
6.0.2.8165	WSS 2.0	KB923644	SP3	Sep-07
6.0.2.8117	WSS 2.0	KB924881	Hotfix Package	Jan-07
6.0.2.8000	WSS 2.0	KB900929	Hotfix Package	Nov-05
6.0.2.6568	WSS 2.0	KB887623	SP2	Oct-05
6.0.2.6551	WSS 2.0	N/A	WSS R2	Sep-05
6.0.2.6411	WSS 2.0	KB887981	Security Update	Feb-05
6.0.2.6361	WSS 2.0	KB841883	SP1	Aug-04
6.0.2.5530	WSS 2.0	N/A	RTM	N/A

Sharepoint - Rename site column back to "Title"

I guess some of you bumped into a problem while changing the famous site column "Title" into something else and asking yourself OK... i made an error and now i need to fix it
but writing Title back and clicking OK pops up an error that saying that the column "Title" can't be used cause it saved value.

Well there's a simple explanation to this problem and as you can see the "Title" is a value that the Sharepoint environment keeps to itself

So you must be asking yourself, so OK now what? i need to be stuck with this error i made?
the answer is no...
not really.

As you know there are basically three, lets call it, layers to handle with Sharepoint environment stuff

• SQL
• IIS (Server Side)
• Sharepoint Code (AKA Object Module)

First two wont really help you out in this case and you need to approach it the programmer way (but don't worry there's nothing spooky about it)

All you're need to do is:

• Open your latest version of visual studio and create console application, based on vitual basic .Net 3+ framework.
•  Add the "Microsoft.SharePoint.dll" to your references (it can be found at your moss installation directory, or most of the time at "C:\Program Files\Common Files\microsoft shared\Web Server Extensions\12\ISAPI"
• Add the next code to your application:

using System;
using System.Collections.Generic;
using System.Text;
using Microsoft.SharePoint;

namespace RenameField
{
    class Program
    {
        static void Main(string[] args)
        {
            if (args.Length < 3)
            {
                Console.WriteLine("Usage: RenameField ");
                return;
            }

            SPSite site = new SPSite(args[0]);
            SPField f = site.RootWeb.Fields[args[1]];
            f.Title = args[2];
            f.Update();
        }
    }
}

• Build and try it on a side server. (Just keep in mind that you need to apply the change after the rename from the Site collection administration page or else the change wont be applied over your site collection.

TFS 2008 Deployment - 32000 Error

Although it burn in my groynes to start the blog with some Sharepoint or even SQL stuff i think its better to share with the world the solution to one hell of a problem installing (or Upgrading) TFS 2008.

Many of us "TFS" guys came with a error code that goes like this:

Error 32000.The Commandline '"C:\Program Files\Microsoft Visual Studio 2008 Team Foundation Server\Tools\TfsDb.exe" upgrade /server:"" /property:"TFS_SERVICE_ACCOUNT=QUALISYSTEMS\tfsservice;TFS_REPORTING_ACCOUNT=QUALISYSTEMS\TFSREPORTS;LCID=1033;VSTF_AS_INSTANCE=;VSTF_AS_DATABASE=TFSWarehouse" /showui:524548' returned non-zero value: 100

And now after weeks of searching, researching and what not i finally came to a solution to this problem.

For the matter of fact i believe there are many ways to resolve this problem cause, well there are many thing can cause this error code to pop up,

The way to find out what happens is by exploring to your %temp% folder and looking for files called:

• dd_install_vstf*.txt
• vsmsi*.txt

With this files you can accomplish everything (well almost)
In my case I've founded that while migrating the Databases from one server to another the new SQL server "lost" the permission that granted some users

I saw that by looking at the logs and finding the updating and connection to DB failed errors.

In my case i granted extended permission (you can find them under the login section for the user on your SQL Management Studio) and it worked like a charm.

also i came to the point that i needed to change my dbo user (that was assigned to tfsservice) to other user (lets say tfssetup).
i did it by running the stored procedure:

EXEC sp_changedbowner tfssetup

and assigning a new role to tfsservice (adding permissions such as dbo, dbdata-reader\writer)