SYMPTOMS :
When you use the fully qualified domain name (FQDN) or a custom host header to browse a local Web site that is hosted on a computer that is running Microsoft Internet Information Services (IIS) 5.1 or a later version, you may receive an error message that resembles the following:
HTTP 401.1 – Unauthorized: Logon Failed
This issue occurs when the Web site uses Integrated Authentication and has a name that is mapped to the local loopback address.

Note You only receive this error message if you try to browse the Web site directly on the server. If you browse the Web site from a client computer, the Web site works as expected.
CAUSE :
This issue occurs if you install Microsoft Windows XP Service Pack 2 (SP2) or Microsoft Windows Server 2003 Service Pack 1 (SP1). Windows XP SP2 and Windows Server 2003 SP1 include a loopback check security feature that is designed to help prevent reflection attacks on your computer. Therefore, authentication fails if the FQDN or the custom host header that you use does not match the local computer name.
WORKAROUND :
Method 1: Disable the loopback check
To set the DisableLoopbackCheck registry key yourself, follow these steps:

1. Set the DisableStrictNameChecking registry entry to 1. For more information about how to do this, click the following article number to view the article in the Microsoft Knowledge Base:
281308 (http://support.microsoft.com/kb/281308/ ) Connecting to SMB share on a Windows 2000-based computer or a Windows Server 2003-based computer may not work with an alias name
2. Click Start, click Run, type regedit, and then click OK.
3. In Registry Editor, locate and then click the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
4. Right-click Lsa, point to New, and then click DWORD Value.
5. Type DisableLoopbackCheck, and then press ENTER.
6. Right-click DisableLoopbackCheck, and then click Modify.
7. In the Value data box, type 1, and then click OK.
8. Quit Registry Editor, and then restart your computer.

Method 2: Specify host names
To specify the host names that are mapped to the loopback address and can connect to Web sites on your computer, follow these steps:

1. Set the DisableStrictNameChecking registry entry to 1. For more information about how to do this, click the following article number to view the article in the Microsoft Knowledge Base:
281308 (http://support.microsoft.com/kb/281308/ ) Connecting to SMB share on a Windows 2000-based computer or a Windows Server 2003-based computer may not work with an alias name
2. Click Start, click Run, type regedit, and then click OK.
3. In Registry Editor, locate and then click the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0
4. Right-click MSV1_0, point to New, and then click Multi-String Value.
5. Type BackConnectionHostNames, and then press ENTER.
6. Right-click BackConnectionHostNames, and then click Modify.
7. In the Value data box, type the host name or the host names for the sites that are on the local computer, and then click OK.
8. Quit Registry Editor, and then restart the IISAdmin service.
REFERENCE :
http://support.microsoft.com/kb/896861

Most of the time we have requirement like that this field should be shown only in new mode or it should not be shown only in Edit mode not in new mode.

We can hide it in view by not to show in grid view but what to do if you do not want to see that field in Dispforms.aspx?

Here is the way how to do that.
Option: 1
OBJECT MODEL

SPSite site = new SPSite(”http://Server:3000/”);
SPWeb web = site.OpenWeb();
web.AllowUnsafeUpdates = true;
SPList list = web.Lists[”Sample”];
SPField objField = list.Fields[”Sample1″];
objField.ShowInNewForm = true;
objField.ShowInDisplayForm = false;
objField.ShowInEditForm = true;
objField.Update();
list.Update();

Option: 2
List Definition
You can hide column appearing in New/Edit/View/ form by creating custom list defination for the list.

For creating custom list defination you can refer following MSDN link:
http://msdn.microsoft.com/en-us/library/ms466023.aspx

Now to hide a column from New/Edit/View/ form, you need to update content types of your list schema. Following is steps to do this (Assuming you have created custom list defination, following the steps mentioned in above URL):
1. Open schema.xml from your custom feature folder
2. Locate Content Types XML node, under that locates the Field which you want to hide from Edit form, set the ShowInEditForm value to FALSE.

Following example hides the Title column of custom list appearing in Edit form:

<FieldRef ID=”{fa564e0f-0c70-4ab9-b863-0177e6ddd247}” Name=”Title” Required=”TRUE” ShowInNewForm=”TRUE” ShowInEditForm=”FALSE” />

When you turn an existing site into a template and include the content, there is a size limit of 10 Mb by default. If you site content is greater than this, a site template will not be created.
You can change this maximum size using an stsadm command on the SharePoint server.

stsadm -o setproperty -propertyname max-template-document-size -propertyvalue  size_in_bytes
 
Where size can be up to 500Mb (524288000 bytes)

Services in SharePoint 2010 Products

Cross-farm Services in SharePoint 2010 Products

Topologies for SharePoint Server 2010

Hosting Environments in SharePoint 2010 Products

Search Technologies for SharePoint 2010 Products

Search Architectures for Microsoft SharePoint Server 2010

Design Search Architectures for Microsoft SharePoint Server 2010

Business Connectivity Services Model

Microsoft SharePoint Server 2010 Upgrade Planning

Microsoft SharePoint Server 2010 Upgrade from 2007 Approaches

Microsoft SharePoint Server 2010 — Test Your Upgrade Process

Choose tool for business intelligence in SharePoint Server 201

SharePoint Components

SharePoint has been build upon following basic components:

1. SharePoint Architecture: – Farm, Web Application, Site Collection, Site, Lists, Items.

2. Web Application: – Creation, Deletion, Setting

3. Site Collection:- Creation, Deletion, Setting

4. Document Library:- Creation, Deletion, Setting

5. List: – Creation, Deletion, Setting

6. Item: – Creation, Deletion, Setting

7. SharePoint Security: – Group, People. Permissions

8. SharePoint Designer: – Site, Page, List, Web Part, Check In, Check Out, Publish.

9. Out of the box Web Parts: – Type and Uses.

10. Custom Web Part Development: – Creation, Debugging, Deployment.

read more..

SharePoint 2010: Professional Developer Guide

SharePoint 2010: Labs in C# and Visual Basic Develop a Visual Web Parts in Visual Studio 2010 Develop a List Definition and Events Receiver in Visual Studio 2010 Develop Advanced Web Parts for SharePoint 2010 with Visual Studio 2010 LINQ Programming Client

Chapter 1: Develop a Visual Web Parts in Visual Studio 2010

Chapter 2: Develop a List Definition and Events Receiver in Visual Studio 2010

Chapter 3:  Develop  Advanced Web Parts for SharePoint 2010 with Visual Studio 2010

Chapter 4:  Develop with LINQ Programming to SharePoint in Visual Studio 2010

Chapter 5: Develop for SharePoint 2010 with the Client OM and REST in Visual Studio 2010

Chapter 6: Develop a BCS External Content Type with Visual Studio 2010

Chapter 7: Develop a SharePoint 2010 Workflow with Initiation Form in Visual Studio 2010

Chapter 8: Develop SharePoint 2010 User Interface with Silverlight in Visual Studio 2010

Chapter 9: Develop SharePoint 2010 Sandboxed Solutions in Visual Studio 2010

Chapter 10: Develop SharePoint 2010 User Interface Ribbon and Dialog Customizations
read more..

Aan een agenda web part een extra kolom toegevoegd met daarin keuzes, zoals verjaardag; vakantie; dienst en overlegvormen.
Getracht op basis van de default view “Current events” andere views aan te maken, gefilterd op eerder genoemde keuzes. Probleem hierbij is dat je geen ‘current events’ krijgt, maar alle events. Je kunt niet filteren op ‘Start time’.
Oplossing is een ‘Calculated’ kolom in te voegen, noem deze bijvoorbeeld Datum.
Als formule voer je in ‘=[Start Time] selecteer ‘Date and Time’ als data type en bij Date and Time Format ‘Date Only’en je hebt je kolom gemaakt waarmee je de views kunt filteren.
Met dank aan Michelle Pakron

SharePoint Designer Grid Filter
Solution Duplicate values in Filter selection,  Filter in SharePoint Grid control not work properly , it display duplicate values.

Grid filters in SharePoint display duplicate values in drop down.  There is no feature in SharePoint to correct this Theres is one great solution with help of SharePoint Designer.. more detail..

MOSS2010 vs MOSS2007

Stand-alone installation : List of Comparison between Microsoft SharePoint Sever 2010 and SharePoint 2007, Hardware requirements, Helps in How to migrate SharePoint 2007 to SharePoint2010. MOSS2010 requires : 64-bit edition of Windows Server 2008 Standard with SP2 and SQL Server 2008 Express with SP1. Compared: Operating System, Processor, RAM, Database….

Read more..

Vegas and SharePoint (and my birthday) all in one week!

The SharePoint DevConnections 2009 conference was held at the Mandalay Bay hotel in Los Vegas from Nov 8th to 13th (including pre and post workshops). I attended the SharePoint track from Tues to Thurs along with the pre-conference workshop on Performance Point dashboards and scorecards and I must say I was impressed with all of it aside form the content of the workshop.

The pre-conference workshop was a little misleading as it seemed like it would be focused on designing dashboards and scorecards yet it was more of an entire overview of data warehousing, SSIS, SSAS, SSRS and Performance Point with the last hour or so actually spent on design. Which was great since I’m not that familiar with BI and I gained insight into how all the pieces fit together. I think a more descriptive title would have helped.

Other sessions of note:

• HMS10: SharePoint Development Application Life cycle Management
• HDV303: Improvements to the SharePoint Developer Story
• HDV315: Client Side Programming in SharePoint 2010
• HDV302: Exploring SharePoint as a Service with Improvements in SharePoint Server 2010
• HIT301: Best Practices for SharePoint Governance and Design
• HDV301: Exploring Improvements to Enterprise Content Management in SharePoint Server 2010

The majority of these sessions were given by Andrew Connell and Scot Hillier both of whom I’d recommend as presenters/instructors and to attend one of their sessions or courses if you get the chance. The session on best practices and a later session on social networking by Dan Holme were also enlightening.

Getting a look at Visual Studio 2010 specifically the Test Centre was really cool. I had a brief conversation with one of the Microsoft guys on the Visual Studio application life cycle team about extending the test capabilities to UAT scenarios (either through a web based or package solution) however it looks like we’ll have to wait for this. I think this would be a huge enhancement so that not only could you author ALL test cases within Test Centre but you could then get it out of the developers hands and over to the users for the next stage of testing. Even without this feature, the ability to view the recording the of test being performed was very cool.

My new VM with SharePoint 2010 beta is in the works and can’t wait to dive in and explore some of the new enhancements such as the ad-hoc subscription based Service Application Architecture, ECM tools (such as Documents Sets and Metadata Manager Service) and the new Business Connectivity Services (BCS).

Other then that the sessions ran on time and the food was great. The Mandalay Bay is huge and Vegas was fun for the small amount of it I got to see. The week capped off for me with a dinner with Scot and some friends I met at the conference. I would have liked to attend the post conference workshop with Scot Hillier and Andrew Connell however my birthday plans took precedence. I did win a Critical Path Training Webcast however so that makes up for it!

Today while at work I was working to clean up our intranet’s site directory in SharePoint.

I noticed that the Navigation menu in one of our sites was only listing 50 page links, even though there were plenty more pages within that particular site.

Since I knew there were more and that this was probably the result of some inherent limit, I dug around and found this post which explains how to modify your web.config. It basically boils down to adding a property DynamicChildLimit=”XX” to the following entries in the web.config file, where XX is 0 (no limit) or whatever numeric limit you decide. By default it is 50. (The web.config file to modify is usually located in C:\Inetpub\wwwroot\wss\VirtualDirectories\80, with the last portion being whatever port number MOSS is running from).

Set the limit to 0 to give yourself flexibility.

I had recently set up a SharePoint site for large documents of varying size between 120-180 MB. I made changes to the web application general settings and increased maximum upload size 200 MB.

Now the users came back to me with the following error!

Server Out Of Memory

There is no memory on the server to run your program. Please contact your administrator with this problem.

I checked the logs but they were clean. So I made few more changes as below which are standard for configuring any site for large documents.

1. Increased connection time out setting on IIS

2. Made changes to the web.config to add the execution timeout value and increase maximum request length

location path=”upload.aspx”>

<system.web>

<httpRuntime executionTimeout=”999999″ maxRequestLength=”2097151″ />

</system.web>

</location>

3. Made changes to web.config to Increase the maximum size limit for Web Parts. [This is suggested but not required]

4. Increased large file size chunk value

stsadm -o setproperty -pn large-file-chunk-size -pv [value in bytes] –url “URL Name”

Even after this, i was getting the error. So I tried to replicate this on a different SharePoint environment, it worked perfectly fine here. The only difference between these environments was the first one had Microsoft Forefront installed where as the later did not. Then I started playing with forefront and realized that forefront treats each document like a container and it has maximum container file size and maximum container scan time. As the documents exceeded the size of the maximum container size and time to scan the large files exceeded the maximum container scan time, the upload/download of the documents failed. So I made following changes to ForeFront

Increased Max Container File Size (bytes)

Increased Max Container Scan Time (milliseconds) – Both real-time & manual

That’s it, this fixed the issue. The issue was not with SharePoint but Forefront! Hopefully, this can help somebody.

public void ShowAttachment(PlaceHolder PlaceHolderObj, string strListItemID)
{
WindowsIdentity objWindowsIdentity = WindowsIdentity.GetCurrent();
WindowsImpersonationContext objWindowsImpersonationContext = null;
//RevertToSelf();
SPSite siteCollection = null;
SPWeb topLevelSite = null;
string strDocumentLink = String.Empty;
string strDocLibraryWebLink = System.Configuration.ConfigurationManager.AppSettings["SPDocumentLibraryWeb"].ToString();
string strDocLibraryLink = System.Configuration.ConfigurationManager.AppSettings["SPDocumentLibrary"].ToString();
string strDocLibrary = System.Configuration.ConfigurationManager.AppSettings["SPDocLibrary"].ToString();
objWindowsImpersonationContext = WindowsIdentity.GetCurrent().Impersonate();
siteCollection = new SPSite(strDocLibraryLink);
topLevelSite = siteCollection.AllWebs[System.Configuration.ConfigurationManager.AppSettings["TopLevelSite"].ToString()];

SPList list = topLevelSite.Lists["ETAAttachments"];

foreach (SPListItem item in list.Items)
{
if ((Convert.ToString(item["ETAID"]).Equals(strListItemID)))
{
strDocumentLink = strDocLibraryWebLink + strDocLibrary + “/” + Convert.ToString(item["Name"]);

HyperLink hpl = new HyperLink();
hpl.NavigateUrl = strDocumentLink.ToString().Replace(” “, “%20″).Trim();
hpl.Text = Convert.ToString(item["Name"]);
hpl.Attributes.Add(“onclick”, “javascript:window.open(” + hpl.NavigateUrl + “);”);
PlaceHolderObj.Controls.Add(hpl);
PlaceHolderObj.Controls.Add(new LiteralControl(“
“));
}
}
objWindowsImpersonationContext.Undo();
}

public void UploadToMoss(string filename, int fileLength, Stream oStream, string strDocLibraryName)
{
WindowsIdentity wi = WindowsIdentity.GetCurrent();
WindowsImpersonationContext ctx = null;
//RevertToSelf();

bool blStatus = true;
try
{

ctx = WindowsIdentity.GetCurrent().Impersonate();

SPSite siteCollection = null;
SPWeb topLevelSite = null;
string strDocLibraryLink = System.Configuration.ConfigurationManager.AppSettings["SPDocumentLibrary"].ToString();

siteCollection = new SPSite(strDocLibraryLink);
topLevelSite = siteCollection.AllWebs[ConfigurationManager.AppSettings["TopLevelSite"].ToString()];

topLevelSite.AllowUnsafeUpdates = true;
SPFolder objFolder = topLevelSite.GetFolder(strDocLibraryName);
byte[] bufDoc = null;
string strFileName = Path.GetFileName(filename);
int nLen = fileLength;
bufDoc = new byte[nLen];
oStream.Read(bufDoc, 0, nLen);

SPList list = topLevelSite.Lists["ETAAttachments"];

topLevelSite.AllowUnsafeUpdates = false;

System.GC.AddMemoryPressure(200024);
SPFile file = objFolder.Files.Add(strFileName, oStream, true);
file.Update();

foreach (SPListItem item in list.Items)
{

if (item["Name"].ToString() == strFileName)
{

item["ETAID"] = 278;
item["Attachment Type"] = “test”;
item.Update();
break;
}

}

siteCollection.Dispose();
topLevelSite.Dispose();

}
catch (Exception ex)
{
throw;
}
finally
{
System.GC.RemoveMemoryPressure(200024);
ctx.Undo();
}
}

private void updateSharePoint(NewECRET_SubmitBLLFields objNewECRET, string strNotifiers)
{ SPSite siteCollection = null;
SPWeb topLevelSite = null;
string strNewXRef = String.Empty;
bool blnNoError = true;

try
{

SPSecurity.RunWithElevatedPrivileges(delegate()
{
siteCollection = new SPSite(System.Configuration.ConfigurationManager.AppSettings["SPDocumentLibrary"].ToString());
topLevelSite = siteCollection.AllWebs[ConfigurationManager.AppSettings["TopLevelSite"].ToString()];
});
topLevelSite.AllowUnsafeUpdates = true;

SPList list = topLevelSite.Lists[ConfigurationManager.AppSettings["ListName"].ToString()];

// Create List Item
SPListItem objListItem = list.Items.Add();

objListItem["Title"] = objNewECRET.Title;
objListItem["ECRETS #"] = strRetECRETSID.ToString();

string strUserName = Session["FullName"].ToString();
for (int i = 0; i 0)
{
objListItem["Estimated Completion Date"] = txtEstimateComplitionDate.Text;
}
objListItem["Request Date"] = DateTime.Today.ToShortDateString().ToString();
objListItem["Timing"] = txtTiming.Text;
objListItem["Cost"] = txtCost.Text;
objListItem["How Affect Product"] = txtHowAffectProduct.Text;

string strNList = string.Empty;
if (lstnotification.Items.Count > 0)
{
for (int i = 0; i < lstnotification.Items.Count; i++)
{
if(!string.IsNullOrEmpty(lstnotification.Items[i].ToString()))
{
strNList = lstnotification.Items[i].ToString() + ";";
}
}
objNewECRET.NotificationList = strNList.ToString();
objListItem["NotificationList"] = strNList;
}

objListItem.Update();

topLevelSite.AllowUnsafeUpdates = false;

UploadECRETSFiles();
hdnDupTitle.Value = "Yes";
}
catch (Exception ex)
{
blnNoError = false;
lblMsg.Text = "Error " + ex.StackTrace.ToString() + " While Updating Sharepoint List";
// lblSuccessMsg.Text = "";
}
finally
{
if (blnNoError)
{
lblMsg.Text = "";
// lblSuccessMsg.Text = "Document has been reserved successfully";
txtComments.Enabled = false;
//btnSubmit.Enabled = false;
}
}
siteCollection.Dispose();
topLevelSite.Dispose();
if (blnNoError)
{

//Response.Redirect("Confirm.aspx?id=9&ECRETSID=" + strRetECRETSID);
spnECRETSID.InnerText = strRetECRETSID.ToString();
ScriptManager.RegisterStartupScript(this, Page.GetType(), "", "ShowDivLayer('shadow','divShowECRETSID');", true);

}
}

public void ShowAttachment(string ListItemID, PlaceHolder PlaceHolderObj)
{

//Impersonating the user to perform this action
WindowsImpersonationContext ctx = null;
RevertToSelf();

SPSite siteCollection = null;
SPWeb topLevelSite = null;
SPList list = null;

string SPSiteCollection = string.Empty;
string SPTopLevelSite = string.Empty;
string SPListName = string.Empty;
string SPListSubFolderName = string.Empty;
string strSPListAttachmentLocation = string.Empty;
string strFileName = string.Empty;
int intID = 0;

SPSiteCollection = System.Configuration.ConfigurationManager.AppSettings["SPSite"];
SPTopLevelSite = System.Configuration.ConfigurationManager.AppSettings["TopLevelSite"];
SPListName = System.Configuration.ConfigurationManager.AppSettings["ListName"];
SPListSubFolderName = System.Configuration.ConfigurationManager.AppSettings["FolderName"];
strSPListAttachmentLocation = System.Configuration.ConfigurationManager.AppSettings["SPListAttachmentLocation"];

try
{
ctx = WindowsIdentity.GetCurrent().Impersonate();

using (SPSite site = new SPSite(SPSiteCollection))
{

//using (SPWeb web = site.OpenWeb(SPTopLevelSite))
using (SPWeb web = site.AllWebs[SPTopLevelSite])
{
web.AllowUnsafeUpdates = true;

list = web.Lists[SPListName];

SPListItem item = list.GetItemById(Convert.ToInt32(ListItemID.ToString().Trim()));

SPAttachmentCollection attachments = item.Attachments;
if (attachments.Count > 0)
{
SPFolder folder = web.Folders["Lists"].SubFolders[SPListSubFolderName].SubFolders["Attachments"].SubFolders[item["ID"].ToString()];

foreach (SPFile objSPFile in folder.Files)
{
if (folder.Files.Count != 0)
{
strFileName = strSPListAttachmentLocation + objSPFile.ToString().Replace(” “, “%20″);
HyperLink objHyperLink = new HyperLink();
objHyperLink.NavigateUrl = strFileName.Trim();
objHyperLink.Text = objSPFile.Name.ToString();
objHyperLink.ID = intID.ToString();
intID++;

string strFileExt = String.Empty;
strFileExt = objSPFile.Name.ToString().Substring(objSPFile.Name.ToString().LastIndexOf(“.”) + 1);
if (strFileExt.ToUpper().Equals(“PDF”))
{
objHyperLink.Target = “_blank”;
}
PlaceHolderObj.Controls.Add(objHyperLink);
PlaceHolderObj.Controls.Add(new LiteralControl(“
“));
}
}
}
}
}
}

catch (Exception ex)
{
throw ex;
}
finally
{
if (topLevelSite != null)
{
topLevelSite.AllowUnsafeUpdates = false;
topLevelSite.Dispose();
}
if (siteCollection != null)
siteCollection.Dispose();

// Ensure impersonation is reverted
if (ctx != null)
ctx.Undo();
}
}

public void AddChangeRequestFields(string strDocToRefer, string strUserFQN, string strMode)
{
SPSite siteCollection = null;
SPWeb topLevelSite = null;
string[] arrXRefDocs;
string strNewXRef = String.Empty;

siteCollection = new SPSite(System.Configuration.ConfigurationManager.AppSettings["SPDocumentLibrary"].ToString());
//topLevelSite = siteCollection.AllWebs["EPC"];
topLevelSite = siteCollection.AllWebs[ConfigurationSettings.AppSettings["TopLevelSite"].ToString()];

topLevelSite.AllowUnsafeUpdates = true;

SPList list = topLevelSite.Lists["Approved Documents"];

foreach (SPListItem item in list.Items)
{
if (strDocToRefer.Equals(Convert.ToString(item["Document Number"])))
{
if (strMode.Equals(“Add”))
{
item["Initiate Change Request"] = “”;
item["CR Initiated By"] = strUserFQN;
}
else
{
item["Initiate Change Request"] = System.Configuration.ConfigurationManager.AppSettings["SPDocumentLibrary"].ToString() + “?ID=” + strDocToRefer.Trim() + “&Type=CR”;
item["CR Initiated By"] = strUserFQN;
}

item.Update();
break;
}
}
topLevelSite.AllowUnsafeUpdates = false;

siteCollection.Dispose();
topLevelSite.Dispose();

}

I recently deployed some features, mainly web parts, to a client’s load balanced SharePoint farm. The features were created with the Visual Studio 2008 extensions for Windows SharePoint Services. When using features created with VSeWSS they work fine on a simple, non-load balanced, single server farm.

However when I tried to run the setup file produced by VSeWSS I got an error like “the feature is not available on the farm”. The reason is related to the following sentence from the stsadm installfeature operation’s help documentation: “Farm-scoped features are also automatically activated during this [installfeature] stage. Other features might still need to be activated.”

Now, if you open the feature.xml file, created by VSeWSS and look at the Feature element, you’ll see it has the following attribute: Scope=”Site” .

This means that the feature is defined at the Site level, and that it needs to be installed and then activated on a multiple server farm configuration. The standard VSeWSS setup.bat only takes care of activating the feature: “%SPAdminTool%” -o activatefeature -id 87f20850-ad52-4785-a680-195942270020 -url %TargetSiteUrl% . Whoops, that will indeed cause some problems.

Solution

First install the feature before activating it. There is one little gotcha here. Stsadm’s installfeature operation does not provide an option to specify the feature’s GUID. It only supports filename or name, and as you can expect VSeWSS only uses features’ GUIDs. So we have to modify setup.bat to use the file name, instead of the GUID and add the installfeature command for each feature:

“%SPAdminTool%” -o installfeature -filename WebPartFeature\feature.xml
“%SPAdminTool%” -o activatefeature -name WebPartFeature -url %TargetSiteUrl%

Cool, problem solved! If you don’t know this before hand, it can take a while to figure out.

public bool UploadToMoss(HttpPostedFile filename, string strDocLibraryName, string strDocCategory, string strDocType)
{

WindowsIdentity wi = WindowsIdentity.GetCurrent();
WindowsImpersonationContext ctx = null;
RevertToSelf();

bool blStatus = true;
try
{

ctx = WindowsIdentity.GetCurrent().Impersonate();

SPSite siteCollection = null;
SPWeb topLevelSite = null;
string strDocLibraryLink = System.Configuration.ConfigurationManager.AppSettings["SPDocLibrary"].ToString();

siteCollection = new SPSite(strDocLibraryLink);
topLevelSite = siteCollection.AllWebs[ConfigurationManager.AppSettings["TopLevelSite"].ToString()];

topLevelSite.AllowUnsafeUpdates = true;
SPFolder objFolder = topLevelSite.GetFolder(“” + strDocLibraryName + “/” + strDocCategory + “/” + strDocType + “”);
byte[] bufDoc = null;
string strFileName = Path.GetFileName(filename.FileName);
int nLen = filename.ContentLength;
bufDoc = new byte[nLen];
Stream oStream = filename.InputStream;
oStream.Read(bufDoc, 0, nLen);
System.GC.AddMemoryPressure(200024);
SPFile file = objFolder.Files.Add(strFileName, oStream, true);
file.Update();

}
catch (Exception ex)
{
blStatus = false;
throw;
}
finally
{
System.GC.RemoveMemoryPressure(200024);

ctx.Undo();

}
return blStatus;
}

Hi All,

Last week, I am being asked to work on a DB Maintenance Plan for the SharePoint environment as the database has crossed over 100 GB and we had experienced few serious issues in the last month.

In this regard, I have created a DB Maintenance Plan based on the white paper: “DB Maintenance – SharePoint Products & Technologies”. Please find attached documents for your reference.

DB Maintenance Plan

DB Maintenance Plan – SharePoint Products & Technologies

This is what I could come up with. Now, I am working on the DB Maintenance Specification – Steps for the SQL DBA Team. Will keep you posted once done.

Thanks

Pradeep Narsimhula MCT, CAPM, ITIL (Foundation)

Today i found an article for setting search configuration in Moss 2007 using API.

string url = “your site collection url”;
using (SPSite site = new SPSite(url))
using (SPWeb web = site.RootWeb)
{
string searchCenter = “your search center url”;
web.AllProperties["SRCH_ENH_FTR_URL"] = searchCenter;
web.Update();
}

Thanks to Gary Lapointe MVP.