Here is the another list of public sites built on MOSS platform
http://www.wssdemo.com/Shared%20Documents/Resources.aspx
"Eraser is not the tool only for 'one who makes mistakes', rather it is a great tool for 'one who is willing to correct his mistakes'"
Wednesday, July 22, 2009
Tuesday, May 5, 2009
How to send document to record center programatically in MOSS 2007 ?
Here is the code to send document programatically in MOSS 2007. The below code can be used in console/win apps - but in the SharePoint box because of using SharePoint Object Libraries
private void SendDocumentToRecordsCenter()
{
try
{
string MoreInfo= string.Empty
OfficialFileResult Result;
SPSite mySite = new SPSite("http://ServerName");
SPWeb myWeb = mySite.OpenWeb();
SPFile myDoc = myWeb.GetFile("LibreryName/Doc1.docx");
Result =
myDoc.SendToOfficialFile(out MoreInfo);
Console.WriteLine("Result after execution: " + Result);
}
catch (Exception ex)
{
Console.WriteLine("Error - " + ex.ToString());
}
}
private void SendDocumentToRecordsCenter()
{
try
{
string MoreInfo= string.Empty
OfficialFileResult Result;
SPSite mySite = new SPSite("http://ServerName");
SPWeb myWeb = mySite.OpenWeb();
SPFile myDoc = myWeb.GetFile("LibreryName/Doc1.docx");
Result =
myDoc.SendToOfficialFile(out MoreInfo);
Console.WriteLine("Result after execution: " + Result);
}
catch (Exception ex)
{
Console.WriteLine("Error - " + ex.ToString());
}
}
Error in MOSS 2007 Record Center Site : "The Record Center is not properly configured for this request"
I have received the error message when i try to push a document from a MOSS site collection to the record center of the server farm.
"The Record Center is not properly configured for this request."
After a hell lot of investigations, i have found that the URL used for configuring the record center in the server farm was wrong.
It should be like
http://< Site DNS or Server Name >/<Record Center Site Name >/_vti_bin/officialfile.asmx
</ SharePointCoder>
"The Record Center is not properly configured for this request."
After a hell lot of investigations, i have found that the URL used for configuring the record center in the server farm was wrong.
It should be like
http://< Site DNS or Server Name >/<Record Center Site Name >/_vti_bin/officialfile.asmx
</ SharePointCoder>
Monday, May 4, 2009
Best practice for building SharePoint Solutions
For any SharePoint solution project, I stongly recommend prototyping before writing the complete code. We have been successfull with our prototyping approach. Prototyping helps us to get the user feedback and gives room for more successful delivery of the solution to meet the business requirement.
If we are not able to achieve some functionalities out of the box in SharePoint, we can go for customization using ASP.net code or third party components.
If we are not able to achieve some functionalities out of the box in SharePoint, we can go for customization using ASP.net code or third party components.
How to customize application master page in MOSS 2007
Here is a way how to use the site master page in application pages like settings.aspx in MOSS.
http://superbranding.codeplex.com/
http://superbranding.codeplex.com/
Master Pages and Page Layouts in MOSS 2007
This is worth reading SharePoint Developers...
Approaches to Creating Master Pages and Page Layouts in SharePoint Server 2007
Approaches to Creating Master Pages and Page Layouts in SharePoint Server 2007
Wednesday, April 29, 2009
Announcing Service Pack 2 for Office SharePoint Server 2007 and Windows SharePoint Services 3.0
Service Pack 2 for Office SharePoint Server 2007 and Windows SharePoint Services 3.0 has been released to the Microsoft Download Center. It includes all the fixes prior to SP2, and also several enhancements to improve server farm performance, availability and stability. Plus, a new stsadm operation has been added to help customers prepare for the upgrade to the next version of SharePoint.
Download Links
Service Pack 2 for Windows SharePoint Services 3.0, x86 & x64
http://www.microsoft.com/downloads/details.aspx?FamilyId=79BADA82-C13F-44C1-BDC1-D0447337051B&displaylang=en
Service Pack 2 for Office SharePoint Server 2007, x86 & x64
http://www.microsoft.com/downloads/details.aspx?FamilyId=B7816D90-5FC6-4347-89B0-A80DEB27A082&displaylang=en
Installation Steps
To keep all the files in a SharePoint installation up-to-date, the following packages need to be applied on all servers in the farm. Service Pack 2 contains all fixes released through February of this year, so customers can install it directly on RTM build of the products.
Service Pack 2 for Windows SharePoint Services 3.0
Service Pack 2 for Windows SharePoint Services 3.0 Language Pack (if applicable)
Service Pack 2 for Office SharePoint Server 2007
Service Pack 2 for Office SharePoint Server 2007 Language Pack (if applicable)
After applying the preceding updates, run the SharePoint Products and Technologies Configuration Wizard or "psconfig –cmd upgrade –inplace b2b -wait” in command line. This needs to be done on every server in the farm with SharePoint installed. The version of content databases should be 12.0.0.6421 after successfully applying these updates.
For more in-depth guidance for the update process, we recommend that customers refer to the following articles. These articles provide a correct way to deploy updates, identify known issues (and resolutions), and provide information about creating slipstream builds
Download Links
Service Pack 2 for Windows SharePoint Services 3.0, x86 & x64
http://www.microsoft.com/downloads/details.aspx?FamilyId=79BADA82-C13F-44C1-BDC1-D0447337051B&displaylang=en
Service Pack 2 for Office SharePoint Server 2007, x86 & x64
http://www.microsoft.com/downloads/details.aspx?FamilyId=B7816D90-5FC6-4347-89B0-A80DEB27A082&displaylang=en
Installation Steps
To keep all the files in a SharePoint installation up-to-date, the following packages need to be applied on all servers in the farm. Service Pack 2 contains all fixes released through February of this year, so customers can install it directly on RTM build of the products.
Service Pack 2 for Windows SharePoint Services 3.0
Service Pack 2 for Windows SharePoint Services 3.0 Language Pack (if applicable)
Service Pack 2 for Office SharePoint Server 2007
Service Pack 2 for Office SharePoint Server 2007 Language Pack (if applicable)
After applying the preceding updates, run the SharePoint Products and Technologies Configuration Wizard or "psconfig –cmd upgrade –inplace b2b -wait” in command line. This needs to be done on every server in the farm with SharePoint installed. The version of content databases should be 12.0.0.6421 after successfully applying these updates.
For more in-depth guidance for the update process, we recommend that customers refer to the following articles. These articles provide a correct way to deploy updates, identify known issues (and resolutions), and provide information about creating slipstream builds
Subscribe to:
Posts (Atom)