HTTP 500 – Internal server error page Sharepoint 2007

You can get more detailed error open debug functionality in web config

  • In the <system.web> tag, locate the <customErrors mode=”On”> tag and change it to <customErrors mode=”Off”> to see the ASP.NET exception when an error occurs instead of being redirected to the error page.
  • In the <SharePoint> tag, locate the <SafeMode MaxControls=”50″ CallStack=”false”/> tag and change it to <SafeMode MaxControls=”50″ CallStack=”true”/>. This causes the ASP.NET error message to display with stack trace information
  • In my case error caused by Language pack . You should check your server version and service packs also .

    See :

    https://blog.bugrapostaci.com/2010/10/21/sharepoint-2007-language-pack-service-pack-order/

    See you now.

    SharePoint 2010 Server with FILESTREAM RBS Provider

    What is RBS ?

    Remote Blob Storage is a library API set that is incorporated as an add-on feature pack for Microsoft SQL Server. It can be run on the local server running Microsoft SQL Server 2008 R2, SQL Server 2008,SQL server 2008 express or SQL Server 2008 R2 Express. To run RBS on a remote server, you must be running SQL Server 2008 R2 Enterprise edition. RBS is not supported for Microsoft SQL Server 2005.

    What is the benefits of RBS ?

    RBS can provide the following benefits:

    • BLOB data can be stored on less expensive storage devices that are configured to handle simple storage.
    • The administration of the BLOB storage is controlled by a system that is designed specifically to work with BLOB data.
    • Database server resources are freed for database operations.

    When we consider to use RBS ?

    • The BLOB data files are larger than 256 kilobytes (KB).
    • The BLOB data files are at least 80 KB and the database server is a performance bottleneck. In this case, RBS reduces the both the I/O and processing load on the database server.

    What is the difference of RBS with FILESTREAM and RBS without FILESTREAM feature ?

    This implementation of the FILESTREAM provider is known as the local FILESTREAM provider. You can conserve resources by using the local RBS FILESTREAM provider to place the extracted BLOB data on a different (cheaper) local disk such as RAID 5 instead of RAID 10. You cannot use RBS with the local FILESTREAM provider on remote storage devices, such as network attached storage (NAS). The FILESTREAM provider is supported when it is used on local hard disk drives only.

    A remote RBS FILESTREAM provider that is available in SQL Server 2008 R2 Express can store BLOB data on remote commodity storage such as direct-attached storage (DAS) or NAS. However, SharePoint Server 2010 does not currently support the remote RBS FILESTREAM provider.

    BLOBs can be kept on commodity storage such as direct-attached storage (DAS) or network attached storage (NAS), as supported by the provider. The FILESTREAM provider is supported by SharePoint Server 2010 when it is used on local hard disk drives only. You cannot use RBS with FILESTREAM on remote storage devices, such as NAS.

    The following table summarizes FILESTREAM benefits and limitations.

    Operational requirement RBS with FILESTREAM RBS without FILESTREAM
    SQL Server integrated backup and recovery of the BLOB Store Yes Yes
    Scripted migration to BLOBs Yes Yes
    Supports mirroring No No
    Log shipping Yes Yes, with provider implementation
    Database snapshots No1 No1
    Geo replication Yes No
    Encryption NTFS only No
    Network Attached Storage (NAS) Not supported by SharePoint 2010 Products Yes, with provider implementation

    1If the RBS provider that you are using does not support snapshots, you cannot use snapshots for content deployment or backup. For example, the SQL FILESTREAM provider does not support snapshots.

    If FILESTREAM is not a practical provider for your environment, you can purchase a supported third-party provider. In this case, you should evaluate the following criteria when shopping for a provider:

    • Backup and restore capability
    • Tested disaster recovery
    • Deployment and data migration
    • Performance impact
    • Long-term administrative costs

    What is the Prerequistes ?

    If you plan to store BLOB data in an RBS store that differs from your SharePoint Server 2010 content databases, you must run SQL Server 2008 with SP1 and Cumulative Update 2. This is true for all RBS providers.

    Important Notes

    • RBS does not enable any kind of direct access to any files that are stored in Microsoft SharePoint 2010 Products. All access must occur by using SharePoint 2010 Products only.
    • If you are storing many small (less than 256 KB) files that are frequently accessed by many users, you might experience increased latency on sites that have many small files that are stored in RBS. Increased latency is one cost factor that you should consider when you evaluate RBS for your storage solution. However, it is unlikely to be the strongest consideration. The amount of increased latency is also related to the RBS provider that you use.
    • RBS can be run on the local server running Microsoft SQL Server 2008 R2, SQL Server 2008 or SQL Server 2008 R2 Express. To run RBS on a remote server, you must be running SQL Server 2008 R2 Enterprise edition. SharePoint Server 2010 requires you to use the version of RBS that is included with the SQL Server Remote BLOB Store installation package from the Feature Pack for Microsoft SQL Server 2008 R2. Earlier versions of RBS will not work with SharePoint Server 2010. In addition, RBS is not supported in SQL Server 2005.
    • For best performance, simplified troubleshooting, and as a general best practice, we recommend that you create the BLOB store on a volume that does not contain the operating system, paging files, database data, log files, or the tempdb file
    • Microsoft SQL Server 2008 R2 Express supports databases up to 10 GB. If the installation includes content databases that are larger than 4 GB but smaller than 10 GB, you can upgrade to SQL Server 2008 R2 Express for your content database storage solution instead of implementing RBS. For more information, see Microsoft SQL Server 2008 R2 Express Edition
    • WARNING:We do not recommend that you install RBS by running the RBS_X64.msi file and launching the Install SQL Remote BLOB Storage wizard. The wizard configures the RBS Maintainer to run a scheduled task every 30 days. This setting might not be optimal for your environment. For more information about the RBS Maintainer, see the SQL Server Help documentation that is included with the SQL Server Remote BLOB Store installation package from the Feature Pack for Microsoft SQL Server 2008 R2. (ref : Install and configure Remote BLOB Storage (RBS) with the FILESTREAM provider (SharePoint Server 2010))UPDATE 18.04.2011: With new version RBS.msi you can use GUI interface to install rbs to your envoriment.
      You have to select “Show the optional advanced configuration options” when wizard in progress. And uncheck the maintaner  schedule configuration for disable maintainer.You can download from Microsoft SQL Server 2008 R2 Feature Pack Page
      http://www.microsoft.com/downloads/en/details.aspx?displaylang=en&FamilyID=ceb4346f-657f-4d28-83f5-aae0c5c83d52
      This is the only provider that Sharepoint Server 2010  with version 10.50.xxxx (R2) .But you can load this provider to SQL Server 2008 express loaded machine.


    Tips and Tricks

    • You can allow only big files to be put into FILESTREAM. Since FILESTREAM performance is not as good as the databases when it deals with small files (for example, <1M), you can change this threshold.  The following Windows PowerShell command change the setting to 1M (1048576 bytes), file below 1M will be stored in DB.

    $cbd = Get-SPContentDatabase “WSS_Content”
    $cbd.RemoteBlobStorageSettings.MinimumBlobStorageSize=1048576
    $cdb.Update()

    It would be good to test the performance based on your own storage and hardware.

    This Article base on below MSDN articles :

    And Blog Articles

    Other Resources

    Happy Codding…
    .

    Sharepoint List Type Numbers

    Hi everybody here is the sharepoint list type id list.

    List Id List Description
    100 Generic list
    101 Document library
    102 Survey
    103 Links list
    104 Announcements list
    105 Contacts list
    106 Events list
    107 Tasks list
    108 Discussion board
    109 Picture library
    110 Data sources
    111 Site template gallery
    112 User Information list
    113 Web Part gallery
    114 List template gallery
    115 XML Form library
    116 Master pages gallery
    117 No-Code Workflows
    118 Custom Workflow Process
    119 Wiki Page library
    120 Custom grid for a list
    130 Data Connection library
    140 Workflow History
    150 Gantt Tasks list
    200 Meeting Series list
    201 Meeting Agenda list
    202 Meeting Attendees list
    204 Meeting Decisions list
    207 Meeting Objectives list
    210 Meeting text box
    211 Meeting Things To Bring list
    212 Meeting Workspace Pages list
    301 Blog Posts list
    302 Blog Comments list
    303 Blog Categories list
    1100 Issue tracking

    Bye now.

    How to manage visibility of Site Actions by user in Sharepoint

    If you want to show site actions menu by user rights easy way of to do that using SPSecurityTrimmedControl .
    Conditionally renders the contents of the control to the current user only if the current user has permissions defined in the PermissionString

    <SharePoint:SPSecurityTrimmedControl runat=”server” PermissionsString=”ManageWeb”>
    <div class=”ms-siteaction”>
    ….
    </div>
    </SharePoint:SPSecurityTrimmedControl>

    Parameters and attributes:

    • PermissionString:
    EmptyMask Has no permissions on the Web site. Not available through the user interface.
    ViewListItems View items in lists, documents in document libraries, and view Web discussion comments.
    AddListItems Add items to lists, add documents to document libraries, and add Web discussion comments.
    EditListItems Edit items in lists, edit documents in document libraries, edit Web discussion comments in documents, and customize Web Part Pages in document libraries.
    DeleteListItems Delete items from a list, documents from a document library, and Web discussion comments in documents.
    ApproveItems Approve a minor version of a list item or document.
    OpenItems View the source of documents with server-side file handlers.
    ViewVersions View past versions of a list item or document.
    DeleteVersions Delete past versions of a list item or document.
    CancelCheckout Discard or check in a document which is checked out to another user.
    ManagePersonalViews Create, change, and delete personal views of lists.
    ManageLists Create and delete lists, add or remove columns in a list, and add or remove public views of a list.
    ViewFormPages View forms, views, and application pages, and enumerate lists.
    Open Allow users to open a Web site, list, or folder to access items inside that container.
    ViewPages View pages in a Web site.
    AddAndCustomizePages Add, change, or delete HTML pages or Web Part Pages, and edit the Web site using a SharePoint Foundation–compatible editor.
    ApplyThemeAndBorder Apply a theme or borders to the entire Web site.
    ApplyStyleSheets Apply a style sheet (.css file) to the Web site.
    ViewUsageData View reports on Web site usage.
    CreateSSCSite Create a Web site using Self-Service Site Creation.
    ManageSubwebs Create subsites such as team sites, Meeting Workspace sites, and Document Workspace sites.
    CreateGroups Create a group of users that can be used anywhere within the site collection.
    ManagePermissions Create and change permission levels on the Web site and assign permissions to users and groups.
    BrowseDirectories Enumerate files and folders in a Web site using Microsoft Office SharePoint Designer 2007 and WebDAV interfaces.
    BrowseUserInfo View information about users of the Web site.
    AddDelPrivateWebParts Add or remove personal Web Parts on a Web Part Page.
    UpdatePersonalWebParts Update Web Parts to display personalized information.
    ManageWeb Grant the ability to perform all administration tasks for the Web site as well as manage content. Activate, deactivate, or edit properties of Web site scoped Features through the object model or through the user interface (UI). When granted on the root Web site of a site collection, activate, deactivate, or edit properties of site collection scoped Features through the object model. To browse to the Site Collection Features page and activate or deactivate site collection scoped Features through the UI, you must be a site collection administrator.
    UseClientIntegration Use features that launch client applications; otherwise, users must work on documents locally and upload changes.
    UseRemoteAPIs Use SOAP, WebDAV, or Microsoft Office SharePoint Designer 2007 interfaces to access the Web site.
    ManageAlerts Manage alerts for all users of the Web site.
    CreateAlerts Create e-mail alerts.
    EditMyUserInfo Allows a user to change his or her user information, such as adding a picture.
    EnumeratePermissions Enumerate permissions on the Web site, list, folder, document, or list item.
    FullMask Has all permissions on the Web site. Not available through the user interface.
    • PermissionContext:
    CurrentSite Apply a permission mask to the current site.
    CurrentList Apply a permission mask to the current list.
    CurrentItem Apply a permission mask to the current list or document library item.
    RootSite Apply a permission mask to the root site of the site collection.
    CurrentFolder Apply a permission mask to the current folder.
    • PermissionMode
    All The user must have all of the rights specified in the permission mask to view a link.
    Any The user must have only one of the rights specified in the permission mask to view a link.

    Happy Codding…

    The security validation for this page is invalid.

    When you working with sharepoint and  you encounter with this error:

    The security validation for this page is invalid. Click Back in your Web browser, refresh the page, and try your operation again:

    Solution is easy:

    set “AllowUnsafeUpdates” propery true.

    Example:

    Guid webID = SPContext.Current.Web.ID;
    Guid siteID = SPContext.Current.Site.ID;
    SPSecurity.RunWithElevatedPrivileges(delegate()
    {
        using (SPSite site = new SPSite(siteID))
        {
            site.AllowUnsafeUpdates = true;
            using (SPWeb web = site.OpenWeb(webID))
            {
                web.AllowUnsafeUpdates = true;
                //your code here...
            }
        }
    }