Posts Tagged MOSS 2007

MOSS 2007: Changing landing page (default.aspx)

We need to change the landing page of site from default.aspx to one of our customized page. We used the following code:


static void Main(string[] args)


            SPSite oSiteCollection = null;

            SPWeb oWibSite = null;

            SPFolder oFolder = null;




                oSiteCollection = new SPSite(http://site URL”);

                oWibSite = oSiteCollection.OpenWeb();

                oFolder = oWibSite.RootFolder;

                oFolder.WelcomePage = “document library/page name”;



            catch (Exception e)












Source: MSDN – forgot URL L

Leave a Comment

MOSS 2007: Enabling Anonymous Access

Steps are: 

  • Central Administration -> Application Management -> Authentication Providers (under “Application Security” heading)
  • Select the web application and click on “Default” zone.
  • Check “Enable anonymous access”
  • Move to the site on which you want to enable anonymous access.
  • Site Action -> Site Settings -> Advance Permissions -> Settings – > Anonymous access
  • Select the desired option.

Leave a Comment

Web Part Maintenance Page

It is sometimes difficult or rather impossible to delete or edit a web part. When clicked on “Modify Shared web part” link, error page appeared


“An unexpected error has occurred.


One way to delete the web part is to go to web part maintenance page and delete it. This can be done by adding “?contents=1” to default.aspx page.


An example can be http://portal/sitedirectory/abc/default.aspx?contents=1

Leave a Comment

MOSS 2007: MySite creation error



When clicked on “My Site” link on newly created MOSS 2007 server, following error displayed:


“Your personal site cannot be created because Self-Service Site Creation is not enabled. Contact your site administrator for more information.”




Open Central Administration, “Application Management” -> “Self-service site management” under “Application Security”. Select the web application and “Enable Self-Service Site Creation”.


Hope this works. 

Comments (1)

MOSS 2007: List column error while importing to Excel



When we try to export list to MS Excel using option “Export to SpreadSheet”, following error message displayed:


“Cannot get the list schema column property from SharePoint list.”











Quick resolution is that if you are using MS Excel 2003; try it using MS Excel 2007. This should solve the problem.


Other way is that this is due to a column which has type “Date” or “Date and Time”. Remove such columns from a list view and try to import, you will soon find the trouble making column.


Create a column, copy the data from trouble making column and delete the trouble making column. You are good to go.


Sometimes changes column type from “Date” or “Date and Time” to “Single line text” and change it back to original type will solve the problem but this may result in loss of existing data.


We have a hotfix available as well:

Leave a Comment

MOSS 2007: Site Usage Report Error



When click on “Site Usage Reports” under “Site Administration” in “Site Settings” page, the following message displayed:


Both Windows SharePoint Services Usage logging and Office SharePoint Usage Processing must be enabled to view usage reports. Please contact your administrator to ensure that these services are enabled.




You have to enable two options. Open “Central Administration” -> “Operation” and click on “Usage analysis processing” under “Logging and Reporting” and check “Enable Logging”. Then, move to “Shared Service Provider”, Click on “Usage reporting” under “Office SharePoint Usage Reporting” and check both options.

Comments (3)

STSADM: addcontentdb error



We created a web application and tried to replace the content database with another database. When run command:


stsadm –o addcontentdb –url http://abc –databasename WSS_ABC.


Following error displayed:


An update conflict has occurred, and you must re-try this action. The object SPWebApplication Name=SharePoint – 41272 Parent=SPWebService is being updated by domain\loging, in the OWSTIMER process, on machine ABC. View the tracing log for more information about the conflict.




The solution was to force cache refresh. This can be done as under:


1. On Central Administration machine, move from C\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config\ GUID.

2. Copy cache.ini file to another location.

3. Open the file and replace the current integer with 1.

4. Restart “Windows SharePoint Services Timer” service.
5. Run the command again.


Hope this workJ.

Comments (5)

« Newer Posts · Older Posts »