Showing posts with label Moss Developer. Show all posts
Showing posts with label Moss Developer. Show all posts

May 9, 2012

Publishing Feature

To enable the SharePoint Server Publishing Infrastructure feature for a site collection
a. On the Site Actions menu, point to Site Settings, and then click Modify All Site Settings.
b. If you are not at the root of your site, under Site Collection Administration, click Go to top level site settings.
c. On the Site Settings page, under Site Collection Administration, click Site collection features.
d. On the Site Collection Features page, next to Office SharePoint Server Publishing Infrastructure, click Activate.







To enable the SharePoint Server Publishing feature for a site
a)    On the Site Actions menu, point to Site Settings, and then click Modify All Site Settings.
b)    On the Site Settings page, in the Site Administration section, click Site features.
c)    Next to Office SharePoint Server Publishing, click Activate.







Cannot connect to the configuration database Error in MOSS 2007

Sometimes in sharepoint, while opening the sites we got the "Cannot connect to configuration database" error. The below screen appears,



The problem occurs because the Sharepoint_config database is put to the SUSPECT mode in Sql Server. The following can be checked by logging to the SQL Server 2005 Management Studio. Expand Server > Databases > SharePoint_Config. A red mark next to the SharePoint_Config database appears with "Suspect" word.

To solve this problem, we have to follow this approach.

"Suspected" status > "Emergency" status> Multi User Mode > Enable database
(Convert the database to single user mode by going to properties of database >> options >> Restrict Access >> Single Use)


1) The solution to the above problem is to first convert the "SharePoint_Config" database to the "Emergency" mode by using the Following command/query.

alter database "Database_Name" set emergency

2) Convert database to Multi User Mode by using query


ALTER DATABASE Database_Name SET MULTI_USER


(Below command will convert database to Single User Mode)
ALTER DATABASE Database_Name SET single_USER


3) Finally Run below query

EXEC sp_resetstatus '
Database_Name'
GO
ALTER DATABASE
Database_Name SET EMERGENCY
DBCC checkdb('
Database_Name')
ALTER DATABASE
Database_Name SET SINGLE_USER WITH ROLLBACK IMMEDIATE
DBCC CheckDB ('
Database_Name', REPAIR_ALLOW_DATA_LOSS)
ALTER DATABASE
Database_Name SET MULTI_USER


For some seetings to take place (or if you face some errors) try restarting the highlighted sql services.


August 21, 2011

Dear Readers,
I have created this blog http://maksharepoint.blogspot.com/ to share my sharepoint development experience with you. Presently, i am working as a software engineer (Sharepoint) and my job role includes complete customization of the OOB features of the sharepoint.

Error installing .Net Framework 3.5 in Sql Server 2012

During installation of Sql Server 2012 on Windows server 2012 or addition of roles and features for SharePoint 2013, the setup wizard will...