By the way...

Take a look at the SharePoint 2010 features! http://sharepoint.microsoft.com/2010/Sneak_Peek/Pages/default.aspx

Couldn’t find it easy to login every time on my blog and write an entry. On my laptop with Windows Vista, I never tried Windows Live Writer to create blogs quickly and easily until my colleague told me its usefulness. Now I will be able to write more regularly on what I have been doing in past few months and doing these days.

Sometimes The SSP you create in MOSS are not created properly. This can be result of interruption while SSP was being created or in result of bad migration from SPS03 or MCMS to MOSS. Symptoms: 1. In left nav of SharePoint Central Administration, the name of your new SSP will not render rather, it will show up as text. 2. If you try to delete that from the Central Admin, the Delete option is disabled. Resolution: You should delete the SSP using stsadm command line tool (NOTE: My SSP's name is "SSP" which is specified after "title" in command: C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN>stsa dm -o deletessp -title "SSP" However, if you have any dependencies, you will have to delete them first or you will get following error when you try deleting it through command line tool: An object in the SharePoint administrative framework, "SharedResourceProvider Na me=SSP Parent=SPFarm Name=SharePoint_Config...

If you want to move a MOSS 2007 databases over to a new DB server, do the following: 1. Run SharePoint configuration wizard (on the web server) 2. Disconnect from existing configuration database (on web server) 3. Move the SITE database over to the new database server (on DB server) 4. Run configuration wizard again and create a new farm (on web server) 5. Give NEW database server and NEW configuration database (on web server) 6. After configuration wizard is finished, create web application by going in the SharePoint Cetral Admin (on web server) 7. Give it any web site name. Here you'll specify the New database server and OLD SITE db name. Hit OK. That's it. So only the combination of New DB server and Old Database name are important to specify in all this scenario. Now open web browser and open the site with same URL that it had been running before. You can also follow other processes like descriped on "Ron Grzywacz's Blog"

In Upgrade.log file generated after running upgrade by clicking "Begin Upgrade" in central administration of MOSS, I found following errors in log when upgrading from SharePoint 2003 to MOSS 2007. "[ProfileDatabaseSequence] [ERROR] [12/21/2008 3:07:31 AM]: Action 12.0.18.0 of Microsoft.SharePoint.Portal.Upgrade.ProfileDatabaseSequence failed. [ProfileDatabaseSequence] [ERROR] [12/21/2008 3:07:31 AM]: The statistics 'SectionName' is dependent on column 'SectionName'. ALTER TABLE DROP COLUMN SectionName failed because one or more objects access this column." I used following query to find table having column "SectionName" in the database, since i didnt know which table had it: SELECT name FROM sysobjects WHERE id IN ( SELECT id FROM syscolumns WHERE name = 'SectionName') It returned "ProfileUI" table name. I expanded the "ProfileUI" table in SPS2003's Profile DB and then explanded "Statistics". T...

Msg 5074, Level 16, State 1, Line 1 The object 'IX_ProfileUI' is dependent on column 'SectionName'. Msg 5074, Level 16, State 1, Line 1 The statistics 'SectionName' is dependent on column 'SectionName'. Msg 4922, Level 16, State 9, Line 1 ALTER TABLE DROP COLUMN SectionName failed because one or more objects access this column.

To find out a column you are not sure of where in your entire database, select database from the dropdown and run following query: SELECT name FROM sysobjects WHERE id IN ( SELECT id FROM syscolumns WHERE name = 'COLUMN_NAME'