MS Library [ Moss SharePoint Library ]

Error installing .Net Framework 3.5 in Sql Server 2012

2014-03-03T07:51:00.001-08:00

During installation of Sql Server 2012 on Windows server 2012 or addition of roles and features for SharePoint 2013, the setup wizard will end with the error shown in the below images.

The problem is that SQL Server 2012 installation wizard requires NetFx3 Windows feature enabled, and if that feature is not enable, the SQL Server 2012 setup will throw "Error while enabling Windows feature : NetFx3" error.

Installing NetFx3 on Windows Server 2012

1) Go to Server Manager Tool of Windows Server 2012 --> click on the Add Roles and Features item in the Manage menu.

2) On "Before your Begin", Click Next.

3) On Installation Type section, select the Role-based or feature-based installation option that it has used to configure this server by adding roles, role services and features.

4) On Server Selection section, we have to select the Server on which we want to install NetFx3 feature, so click Select a server from the server pool.

5) On Server roles section, No selections are required because we have to add a feature (NetFx3 is a Windows feature) and not a Server Roles.

6) On Features section, select .Net Framework 3.5 Features that has not installed yet.

7) Click Next button, the wizard will shows the Confirmation section.

8) On Confirmation section, Click the Specify an alternative source patch link.
The required source files for the .Net Framework 3.5 are in Windows Server 2012 DVD (or in the related ISO file). If the DVD device is associated to the letter "F", then, we can specify this alternative path "F:\Sources\SxS". Click OK button to return in the previous window.

9) click Install button to start the installation process.

For more details, you can visit http://support.microsoft.com/kb/2734782

Error while enabling Windows feature : NetFx3. Please try enabling Windows feature : NetFx3 from Windows management tools and then run setup again.

2014-03-03T07:12:00.000-08:00

During installation of Sql Server 2012 on Windows server 2012 for SharePoint 2013, the setup wizard will end with the error shown in the below image.

9) click Install button to start the installation process.

For more details, you can visit http://support.microsoft.com/kb/2734782

Windows Server 2012 - VMware windows cannot find the microsoft software license terms.

2014-03-01T01:16:00.001-08:00

If you have problem installing Windows Server 2012 on VMware Player with following error message : "windows cannot find the microsoft software license terms", chances are when you first create the virtual machine and you have selected the Installer disc image file (iso) option.

Instead, choose I will install the operating system later. Then set the path of the ISO file in VM -> settings -> CD-DVD... -> Use ISO image file, and boot.

This will run the installer without the error above.

Code blocks are not allowed in this file.

2013-05-26T23:48:00.001-07:00

In Moss 2007 or SharePoint 2010, most of the times we need to create the custom master pages. In order to perform certain actions/functions, we need to insert code within those master pages.

Main problem comes into arena, when we try to use upload that master page into the master page gallery or copying into the file system, and use as system master page or site master page. Since the custom master page contains code with in it, so we used to get the below screen.

In order to solve this problem, we need to make entries into the corresponding web.config file by following the below steps.

1) Go to corresponding web.config file location which is located at the below location ( under c drive)

2) Open the web.config file , and under the <SafeMode><PageParserPaths> tag make the below entries.

< PageParserPath VirtualPath="/_catalogs/masterpage/*" CompilationMode="Always" AllowServerSideScript="true" IncludeSubFolders="true"/>

VirtualPath attribute should contains location where the master page is located. "/*" at the end of the /_catalogs/masterpage" in the virtual path attribute indicates to also include the subfolders.

Window could not start the SharePoint 2010 Timer service on Local Computer.

2013-05-26T23:26:00.000-07:00

In SharePoint 2010, while starting the SharePoint 2010 Timer service, we get Error 1069 : The service did not start due to a logon failure like the below screen.

The main cause of this problem is that password of the account under which the SharePoint 2010 Timer service is running has been changed. So, we need to update this password in SharePoint 2010 Timer properties.

Steps to update password for timer service

1) Right click the SharePoint 2010 Timer service > properties

2) Click on Log On tab and enter password under This account option.

3) Click apply > Ok > restart the SharePoint 2010 Timer service.

This page allows a limit of 200 controls, and that limit has been exceeded.

2013-05-19T21:32:00.001-07:00

In Moss/Sharepoint, some while playing with placeholders in the master pages we face the error like the below screen.

The above screen shows that the number of placeholders that can be included in a master page has been exceeded.

Solution

The solution for the above problem is that either
1) To remove placeholders from the master page or
2) (Best One) Increase the value of the MaxControls attribute in the web.config of the corresponding web application as highlighted below.

Align inner div at center of outer div

2013-04-17T21:45:00.000-07:00

While development you must have noticed that <div> tags are used more frequently in all programming languages. So, it is easier to align one <table><tr><td> at center of anothet <table><tr><td>.

But to align, one div at center of another div, we can use style's margin attribute like below.

<Div style="width:100%">
       <Div style="width:50%;margin:0 auto">
            Inner div at center of outer div
       </Div>
</Div>

Activating Publishing Infrastructure Feature

2012-11-04T20:46:00.001-08:00

To make a site publishing type, we need to activate "Office SharePoint Server Publishing Infrastructure". Sometimes, activating Office SharePoint Server Publishing Infrastructure feature on a site collection throws error. There are two ways to activate the same feature.

1) Clicking on Activate button in feature gallery and
2) By using stsadm commands.

To activate publishing infrastructure feature through commands, use the below commands:

stsadm -o activatefeature -filename publishing\feature.xml -url http://sitecollectionurl -force

stsadm -o activatefeature -filename publishingresources\feature.xml -url http://sitecollectionurl -force

stsadm -o activatefeature -filename publishingSite\feature.xml -url http://sitecollectionurl -force

stsadm -o activatefeature -filename publishingweb\feature.xml -url http://sitecollectionurl -force

stsadm -o activatefeature -filename publishinglayouts\feature.xml -url http://sitecollectionurl -force

stsadm -o activatefeature -filename navigation\feature.xml -url http://sitecollectionurl -force

Extracting DLL from assembly

2012-10-15T03:40:00.001-07:00

Sometimes, based on the requirements , we get into a situation when we want to extract DLL's from assembly. In direct words, it is not possible to drag-drop the DLL's from the assembly folder which is generally located at C:\windows\assembly location.

So, extract the dll from assembly folder, perform these steps

1) Click Start > Run.
2) In Run window, enter "C:\windows\assembly\gac" without quotes and press enter.
3) The window that open, contains dll's in folder, which you can easily copy or drag-drop.

Searching Document or Form Library items using JQuery

2012-08-12T23:56:00.000-07:00

JQuery plays an important role in the Sharepoint or you can say, web development. It will sound interesting to you that we can use the jquery even for searching items from a document, form or images library.

I have used the jquery , found on the "Sharepoint Kings Blog" ( thanx for sharing this jquery), with the custom searching scope to search the items from a particular document library.

To implement the jquery for searching, we need to do the following steps:
1) Create custom search scope.
2) Create webpart page.
3) Adding CEWP (content editor webpart) and pasting the jquery in source editor tab.
4) Changing the Scope attribute to the custom new scope (if required).

So, to create the custom scopes,
1) Go to Site Actions > Site Settings
2) Under Site Collection Administration > Search Scopes
3) On next page, click New Scope
4) Click OK.

After creating the custom scope, we need to add rules to the custom scopes. On the view scopes page, click Add Rules, next to the newly created search scope.

1) In Scope Rule Type, Select the Web Address option.
2) In Web Address, Select Folder and enter the url of the library from which you want to search the items( you can create the rules as per your requirement).
3) In Behaviour, Select Require.
4) Click OK.

Now, you are done with creating custom search scope and rules. Its time to add the CEWP. Edit the page where you want to display the search results and add CEWP. In the source editor button, paste the below Jquery and update the following
1)url of the jquery-1.3.2.min.js file (at the top of the jquery).
2) update the Scope with the name of the new custom search scope under "Customizable parameters ".

<script type="text/javascript" src="/_LAYOUTS/1033/jquery-1.3.2.min.js"></script>
<script type="text/javascript">

// *** Customizable parameters ***
var quickSearchConfig = {
delay: 500, // time to wait before executing the query (in ms)
minCharacters: 3, // minimum nr of characters to enter before search
scope: "CustomSearchScopeName", // search scope to use
numberOfResults: 75, // number of results to show
resultsAnimation: 200, // animation time (in ms) of the search results
resultAnimation: 0 // animation time (in ms) of individual result (when selected)
};
</script>

<style type="text/css">
.quickSearchResultDivUnselected
{
background: white;
border: 1px solid white;
margin-left: 2px;
overflow: hidden;
text-overflow: ellipsis;
}
.quickSearchResultDivSelected
{
background: #EEEEEE;
border: 1px solid Gray;
margin-left: 2px;
overflow: hidden;
text-overflow: ellipsis;
}
</style>
<table id="quickSearchTable" class="ms-sbtable ms-sbtable-ex" border="0" style="width:50%">
<tbody>
<tr class="ms-sbrow">
<td class="ms-sbcell">
<input style="width: 50%" id="quickSearchTextBox" class="ms-sbplain" title="Enter search words"
style="width: 170px" alt="Enter search words" maxlength="200" value="" />
</td>
<td class="ms-sbgo ms-sbcell" style="width: 14px">
<img title="Go Search" style="border-top-width: 0px; border-left-width: 0px; border-bottom-width: 0px;
border-right-width: 0px" alt="Go Search" src="/_layouts/images/gosearch.gif" />
</td>
<td style="width: 1px">
</td>
</tr>
</tbody>
</table>
<div id="quickSearchResults" style="display: none;">
</div>

<script type="text/javascript">
var quickSearchTimer;
var quickSearchSelectedDivIndex = -1;

function showResultsDiv(text) {
var div = $("#quickSearchResults");
var prevTable = div.prev();

var divCss = {
"left": prevTable.offset().left,
"padding": 2,
"position": "absolute",
"top": prevTable.offset().top + prevTable.height() + 1,
"border": "1px solid #7f9db9",
"width": prevTable.width() - 3,
"background": "white",
"max-width": prevTable.width() - 3
};

div.css(divCss).append(text).slideDown(quickSearchConfig.resultsAnimation);
}

$(document).ready(function() {
$('#quickSearchTextBox').keyup(function(event) {
var previousSelected = quickSearchSelectedDivIndex;

// catch some keys
switch(event.keyCode) {
case 13: // enter
var selectedDiv = $("#quickSearchResults>div:eq(" + quickSearchSelectedDivIndex + ") a");
if(selectedDiv.length == 1)
window.location = selectedDiv.attr("href");
break;
case 38: // key up
quickSearchSelectedDivIndex--;
break;
case 40: // key down
quickSearchSelectedDivIndex ++;
break;
}

// check bounds
if(quickSearchSelectedDivIndex != previousSelected) {
if(quickSearchSelectedDivIndex < 0)
quickSearchSelectedDivIndex = 0;
if(quickSearchSelectedDivIndex >= $("#quickSearchResults>div").length -1)
quickSearchSelectedDivIndex = $("#quickSearchResults>div").length - 2;
}

// select new div, unselect the previous selected
if(quickSearchSelectedDivIndex > -1) {
if(quickSearchSelectedDivIndex != previousSelected) {
unSelectDiv( $("#quickSearchResults>div:eq(" + previousSelected + ")"));
selectDiv($("#quickSearchResults>div:eq(" + quickSearchSelectedDivIndex + ")"));
}
}

// if the query is different from the previous one, search again
if($('#quickSearchTextBox').data("query") != $('#quickSearchTextBox').val()) {
if (quickSearchTimer != null) // cancel the delayed event
clearTimeout(quickSearchTimer);
quickSearchTimer = setTimeout(function() { // delay the searching
$("#quickSearchResults").fadeOut(200, initSearch);
} , quickSearchConfig.delay);
}
});
});

function unSelectDiv(div) {
// first stop all animations still in progress
$("#quickSearchResults>div>div").stop(true,true);

div.removeClass("quickSearchResultDivSelected").addClass("quickSearchResultDivUnselected");
$("#details", div).hide();
}

function selectDiv(div) {
div.addClass("quickSearchResultDivSelected");
$("#details", div).slideDown(quickSearchConfig.resultAnimation);
}

function initSearch() {
// first store query in data
$('#quickSearchTextBox').data("query", $('#quickSearchTextBox').val());

// clear the results
$("#quickSearchResults").empty();

// start the search
var query = $("#quickSearchTextBox").val();
if(query.length >= quickSearchConfig.minCharacters) {
showResultsDiv("Searching ..."); // display status
search(query);
}
}

function search(query) {
quickSearchSelectedDivIndex = -1;
var queryXML =
"<QueryPacket xmlns='urn:Microsoft.Search.Query' Revision='1000'> \
<Query domain='QDomain'> \
<SupportedFormats><Format>urn:Microsoft.Search.Response.Document.Document</Format></SupportedFormats> \
<Context> \
<QueryText language='en-US' type='STRING' >SCOPE:\"" + quickSearchConfig.scope + "\"" + query + "</QueryText> \
</Context> \
<SortByProperties><SortByProperty name='Rank' direction='Descending' order='1'/></SortByProperties> \
<Range><StartAt>1</StartAt><Count>" + quickSearchConfig.numberOfResults + "</Count></Range> \
<EnableStemming>false</EnableStemming> \
<TrimDuplicates>true</TrimDuplicates> \
<IgnoreAllNoiseQuery>true</IgnoreAllNoiseQuery> \
<ImplicitAndBehavior>true</ImplicitAndBehavior> \
<IncludeRelevanceResults>true</IncludeRelevanceResults> \
<IncludeSpecialTermResults>true</IncludeSpecialTermResults> \
<IncludeHighConfidenceResults>true</IncludeHighConfidenceResults> \
</Query></QueryPacket>";

var soapEnv =
"<soap:Envelope xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:xsd='http://www.w3.org/2001/XMLSchema' xmlns:soap='http://schemas.xmlsoap.org/soap/envelope/'> \
<soap:Body> \
<Query xmlns='urn:Microsoft.Search'> \
<queryXml>" + escapeHTML(queryXML) + "</queryXml> \
</Query> \
</soap:Body> \
</soap:Envelope>";

$.ajax({
url: "/_vti_bin/search.asmx",
type: "POST",
dataType: "xml",
data: soapEnv,
complete: processResult,
contentType: "text/xml; charset=\"utf-8\""
});

function processResult(xData, status) {
var html = "";
$(xData.responseXML).find("QueryResult").each(function() {
var divWidh = $("#quickSearchTable").width() - 13;

var x = $("<xml>" + $(this).text() + "</xml>");
x.find("Document").each(function() {
var title = $("Title", $(this)).text();
var url = $("Action>LinkUrl", $(this)).text();
var description = $("Description", $(this)).text()

html +=
"<div class='quickSearchResultDivUnselected' style='width:" + divWidh + "px;max-width:" + divWidh +"px'> \
<a href='" + url + "'>" + $("Title", $(this)).text() + "</a> \
<div style='display:none' id='details' style='margin-left:10px'>"
+ description +
"<br/>" + url + " \
</div> \
</div>";
});
if(x.find("TotalAvailable").text() != "")
html += "<div style='text-align:right'>Total results: " + x.find("TotalAvailable").text() + "</div>";
else
html += "<div style='text-align:right'>Total results: 0</div>";
});

$("#quickSearchResults").empty().append(html);
$("#quickSearchResults>div>a").hover(
function() { selectDiv($(this).parent()); },
function() { unSelectDiv($(this).parent()); }
);
showResultsDiv();
}
}

function escapeHTML (str) {
return str.replace(/&/g,'&').replace(/</g,'<').replace(/>/g,'>');
}
</script>

Save the page.

Now, enter the string into the text box and your search result will display like the below image.

Error while removing WSP from MOSS/Sharepoint

2012-08-08T04:14:00.000-07:00

I found this article on "Alex Thissen" blog. Thank"Alex" for sharing this topic with us.

Sometimes, while or after installing wsp(solution) into MOSS/Sharepoint, we face error. As a result, we could not even retract or remove the solution from Soution Management in Central Administration. So, follow the below specified steps and remove the malfunctioning wsp from moss.

It could happen that you (or whatever) accidentally break a deployed solution on a Windows SharePoint Services 3.0 (or MOSS 2007 for that matter) farm or site. If that happens, you can no longer retract and/or remove a solution by using the Operations part of the Central Administration website. It will show up as an error in the list of solutions under "Solution Management".
So how do you go about removing the solution entirely? You can use the command-line tool STSADM.exe which can be found under "C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN" for a normal installation of WSS 3.0. Let's assume that the malfunctioning solution is called HelloWorldWebPart.wsp.
To see a list of all solutions that are on the server run the enumsolutions operation. Operations are the commands that STSADM.exe will take after the -o command-line argument. This is the way you run all operations. If you need help on a particular one, call STSADM.exe -help operationname.

Like in the output above, the solution (even if malfunctioning) could be deployed. You will need to retract the solution first. This is where you probably run into trouble. When you run the operation retractsolution like this:

Two things can happen at this point: you either panic or stay cool (or panic in a cool way). Should panic kick in, you probably will try to still forcibly delete the solution by running the deletesolution operation anyway.

Oh no, what to do now? Calm down. Run an enumeration over the scheduled deployments (retractions are considered deployments as well)

The JobId attribute of the deployment gives the GUID for the job that was scheduled but could not run. You can stop the scheduled retraction by running the operation canceldeployment (again, it's not cancelretraction).
stsadm -o canceldeployment -id 2529c788-971c-46a3-b69f-a2a0a1fcc851
At this point the scheduled retraction should be gone, which you can verify by using enumdeployments again.
Now you can read the message of the retractsolution operation again. You would have done so anyway if you just remained calm. The message says that the WSS Administration service hasn't been started yet. Not that strange, since by default it is configured to start manually.

Start the service and run the execadmsvcjobs operation to run all scheduled jobs.

There you go, no more deployed solution. Now it is just a matter of removing the solution. You can try using the Central Administation website again, because usually the error on the solution has disappeared.

Otherwise, run the deletesolution operation in STSADM.

Blank IIS Manager ( No website )

2012-07-24T23:03:00.002-07:00

Sometimes, in Moss 2007, we try to open a site but it doesn’t. Then we try to reset the IIS and got the following error.

Then, try to open the IIS Manager, and we are surprised to see it blank.

After, having a headache, we trying to run the IIS admin service, we again get the following error.

To find the cause for the error , we open the event viewer and get the following error description.

So, the main reason for this blank IIS manager and errors are the problem in the MetaBase.xml file, which can be found at C:\WINDOWS\system32\inetsrv location.

Look for the Date Modified and Size attributes of both the above files. There is a backup (or History) of these files in the History folder which can be found at the location C:\WINDOWS\system32\inetsrv\History. The folder contains backup of both MBSchema.xml and MetaBase.xml files. Now, we have to replace the either of the files MBSchema.xml or MetaBase.xml at C:\WINDOWS\system32\inetsrv, with the latest History found at C:\WINDOWS\system32\inetsrv\History location.

Suppose, if the Date Modified attribute of the MetaBase.xml file has the latest date, and then replace this file with the MetaBase.xml file found at location C:\WINDOWS\system32\inetsrv\History.(remove the appended _0000121786_0000000000 like strings). Now, reset the IIS and your IIS manager will get populated.

Drag Drop of webparts functionality is not working in Moss 2007

2012-07-24T02:41:00.000-07:00

In Moss 2007, most of the times we want to move the added webparts from one webpart zone to another webpart zone by drag and drop. But sometimes, this functionality is missing in moss 2007 customised pages. The solution of this problem is to add the script to the master page of the site.

Refer to the below image :

Add the script between the <WePartPages:SPWebPartManager> and <form> tag.

        <script language="javascript" type="text/javascript">
            function MSOLayout_GetRealOffset(StartingObject, OffsetType, EndParent)
            {
                var realValue=0;
                if (!EndParent) EndParent=document.body;
                for (var currentObject=StartingObject; currentObject && currentObject !=EndParent && currentObject != document.body; currentObject=currentObject.offsetParent)
                {
                    var offset = eval('currentObject.offset'+OffsetType);
                    if (offset) realValue+=offset;
                }
                return realValue;
            }
        </script>

Apply Custom CSS in MOSS 2007 through aspx pages

2012-07-08T23:55:00.002-07:00

In Moss 2007, sometimes we want to apply CSS through the aspx pages. Instead of including the complete css file, to write only few css we can use the PlaceHolderAdditionalPageHead content placeholder to include the custom css.

For example, the below code can be used.

<asp:Content id="Content11" runat="server" contentplaceholderid="PlaceHolderAdditionalPageHead">
<link rel="stylesheet" type="text/css" href="/_LAYOUTS/1033/STYLES/CustomCSSFileName.CSS">
</asp:Content>

Creating Site Content Types in Moss 2007

2012-05-09T02:35:00.003-07:00

Following are the steps to create content types in moss 2007.

• From any team site, on the Site Actions menu, click Site Settings.
OR
• From any portal area, click Site Actions, point to Site Settings, and then click Modify All Site Settings.
• On the Site Settings page, under Site Collection Administration, click Go to top level site settings.
• Under Galleries, click Site content types.
• On the Site Content Type Gallery page, on the menu bar, click Create.

• In the Name box, type the name for this content type. This name will appear in the Content Types list when we will create the page layout.
• In the Description box, type a description for this content type
• In the Select parent content type from list, click Publishing Content Types.
• In the Parent Content Type list, click Page.
• Under Put this site content type into, click Existing group, and then click Page Layout Content Types in the list.

Start workflow to approve content on Publishing sites in Moss 2007

2012-05-09T02:26:00.001-07:00

a.    Click on View All Site Content , then click on Pages Document Library
b.    Select Settings on Pages document Library then Document Library Settings
c.    Under Permission and Management click Workflow Settings and do the following changes.

Select Approval from workflow
Enter Workflow Name as HRPagesApproval
Check Start this workflow when a new item is created and start this workflow when an item is changed and click next.
Enter the Name of the person who will approve the newly created pages
Under complete this workflow, select Document is Rejected.

Enable the Content Approval in Publishing sites in Moss 2007

2012-05-09T02:15:00.001-07:00

To Enable the Content Approval for the new pages in Pages Document library in Sharepoint publishing sites.

a. Click on View All Site Content , then click on Pages Document Library
b. Select Settings on Pages document Library then Document Library Settings
c. Under General Setting click Versioning Settings and do the following changes.

Creating Sharepoint Groups in Moss 2007

2012-05-09T02:06:00.001-07:00

Group can be created at the site collection level. The following example will create group with Read only permission.

1) On the Site Actions menu, point to Site Settings.
2) On the Site Settings page, under Users and Permissions, click People and groups.
3) On the People and Groups page, Click New > New Group.
4) On Next page, Enter Group Name, Group Owner Name and select Read from the Permission Level.

Creating Custom Permission Level in Moss 2007

2012-05-09T01:58:00.002-07:00

Custom permission Level can be created at the site collection level with default rights/options or by creating own rules. The following example shows creating custom permission level using default Contributor permission level.

•    Go to Site Actions > Site Settings > Modify All site Settings > Advanced Permission under User and Permission heading.
•    On the next page , click settings > Permission Levels.
•    On permission Levels page, click Contribute.
•    On bottom of page, click copy permission level. On the copy permission level “Contribute”, enter name of custom permission level and description.
•    Clicks create.

Publishing Feature

2012-05-09T01:49:00.000-07:00

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

2012-05-09T00:57:00.001-07:00

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.

Change Text or Image of the MySite Link in Moss 2007

2012-04-25T03:16:00.002-07:00

C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\CONTROLTEMPLATES

Now, open that MySiteLink.ascx file in sharepoint designer and change the following line

Add visible="false"

The above line will become .

Now, finally to change the Mysite text add the following line with the text that you want to display. Here, i want to display "Hello".

To display image in place of MySite Text you can use the following line

Retriving URL Value of SharePoint Hyperlink Field

2012-04-25T03:16:00.001-07:00

To get the value of a SharePoint hyperlink field in a custom list using the object model, we generally use.

SPList mylist = myweb.Lists[Your_ListName];

SPQuery rootQuery = new SPQuery();
rootQuery.Query = "";

SPListItemCollection lstitemcol = mylist.GetItems(rootQuery);

foreach (SPListItem lstitem in lstitemcol)

{

string URL=lstitem[url_Column_Name].ToString();

}

The above URL string will contains the value but the only problem with this URl string is that it will contains two URL’s separated by a comma. This is because one is the actual display text for the field and the other is the value (the actual URL itself).

In order to get just the URL value, you need to use the following object model code:

SPFieldUrlValue rootUrl = new SPFieldUrlValue(lstitem[Column_Name].ToString());

string URL = rootUrl.Url;

You can also use value.Description to get the actual display text for the field.

The application attempted to perform an operation not allowed by the security policy. To grant this application the required permission please contac

2011-11-21T22:48:00.000-08:00

Sometimes, while executing an application in sharepoint environment, we get the following error.

The application attempted to perform an operation not allowed by the security policy. To grant this application the required permission please contact your system administrator or change the application's trust level in the configuration file. in sharepoint

This problem is basically related with the Trust Level. Just make the following changes in under element of the web.config file of the corresponding web application.

Change from,
< system.web >
< trust level="WSS_Minimal" originUrl="" / >

to in web.config

< system.web >

< trust level="Full" originUrl="" / >

Change Text or Image of the MySite Link in Moss 2007

2011-11-21T22:36:00.000-08:00

Sometimes the user wants to change the MySite Link text to something else like "My World". In that case, you can do that by making changes to the MySiteLink.ascx file. This MySiteLink.ascx file is located at

C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\CONTROLTEMPLATES
Now, open that MySiteLink.ascx file in sharepoint designer and change the following line

< asp:HyperLink id="hlMySite" runat="server" / >

Add visible="false"

The above line will become < asp:HyperLink id="hlMySite" runat="server" visible="false" / >.

Now, finally to change the Mysite text add the following line with the text that you want to display. Here, i want to display "My World"

< asp:HyperLink ID="NewMySiteHyperlink" runat="server" Text="My World" Visible="true" NavigateUrl="http://your mysite Url/_layouts/MySite.aspx"/ >

To display image in place of MySite Text you can use the following line

< asp:HyperLink ID="NewMySiteHyperlink" runat="server" ImageUrl="/_LAYOUTS/ Link to your image file" Text="My World" Visible="true" NavigateUrl="http:// Your MySite Url/_layouts/MySite.aspx"/ >