Beginning SharePoint Troubleshooting & page Loading issues

Beginning SharePoint Troubleshooting :


please follow the Links:

http://nextconnect.blogspot.com/2009/05/beginning-sharepoint-troubleshooting.html

Troubleshooting Page Loading Issues :


http://nextconnect.blogspot.com/2010/01/troubleshooting-page-loading-issues.html

thanks to Mike Oryszak.


regards,
raju.

Understanding Sharepoint 2007 Database Structure

SharePoint 2007 is a portal application with a high flexibility. How the basic structure of the database? Let's see ...

Microsoft SharePoint 2007 applications that can be said to be a very good example in building a web-based application. With a flexible design of the portal on the SharePoint 2007, it is not surprising that many people choose to switch to SharePoint or affairs for the web portal

One indicator of a good application to the design of the database. If the database structure that is made regular and very futuristic, the application can be good even though this will not always depend on how the implementation of the application and how mengonsumsi database. SharePoint 2007 database can be designed so that the support for personalization so that more lives will be portalnya applications.

At the time this article push to point on how the structure of the database sSharePoint 2007. Microsoft itself is not the official to give details about the structure of the database so that SharePoint is often said Undocumented. Not all of the database structure we will study here and we'll see tables and data that are frequently used in SharePoint.

Configuration Database

In general, the SharePoint 2007 database can be divided into three parts, namely:
• Core Configuration
• Web Farm
• Global Tables

Following explanation:

Core Configuration

From the name, it is core, which means that the information in it is very important. At the core configuration contains important information SharePoint 2007, including:
• Virtual Server
• Sites
• Database

Core configuration we can see that the database is usually named SharePoint_Config, for we can certainly see it on the SharePoint Central Administration portal. Virtual Server server farm contains information on the SharePoint Server. Each virtual server will have many databases in it. Each database will have a lot of this site in it. Each database will have a lot of this site in it. All this information can be obtained on the table Virtual Servers, Databases, and Sites.

Web Farm

Farm contains a web server and service that are served. A server can be host to the multi-service (web and database). Each virtual server can serve a multi-server. Meanwhile, virtua IIS server ID in SharePoint have any ID in the registry.

Global Data

Global data is data that contains general information about SharePoint. This data includes:
• Globals (farm-wide configuration)
• Anti Virus Vendors
• Custom Templates
• Web Part Packages
• Web Part Packages installed

All the above data are stored in the database. Meanwhile, general information on the database or SharePoint globals can include:
• Core content
• Web part
• Alerts
• Security
• Doc management
• Web management
• Global table

At the core content, we will see all the data that is used on a site. Each site will have a database and the database name is usually preceded by the name WSS_Content_XXXX

SharePoint 2007 Site Database

As we know, the SharePoint application seen by the client is called and each SharePoint site SharePoint site will have a database that begins with the name WSS_Content_XXX the information in it can include the following:
• Sites
• Webs
• Docs
• Lists
• User Data

Sites in the table contains information on the site as the URL of the site owner to use, quotas imposed on the site, search optimization.

Sites other than the table, there is also the Webs table contains information on the web such as frontpage, theme, navigation, and so forth.

Docs on the SharePoint site can be said that this data is one of the frequently used data. All the documents we upload to SharePoint document libraries will be stored in the data this docs. Data stored in the docs table AllDocs. This table provides information AllDocs directory name, quota, status Check in / out, to remove the trigger and so on.

No less important is also the table AllUserData give all the information data with various types of data content used by the user. Meanwhile, the information list of the SharePoint site can be found in the table AllLists. Information provided such as a name list, type the list, the available field, ACL, event handler, e-mail, etc
Information system security SharePoint

SharePoint 2007 also stores all information into the database used sekuritiyang SharePoint Site information is stored, among others:
• User info
• Web Members
• Web Groups
• Site Groups

User info contains information about the user-user applications that use SharePoint, especially for the SharePoint Site. Here also provides information on the admin user. Data stored as user name, e-mail, and system ID (NT User Token ID) All this information is stored in the SharePoint Site database, the table called UserInfo.
Web members provide information about the mapping between the user and the web and Token STS. Meanwhile, Web Site Groups and Groups to provide information about users and NT group.

WebParts

As we know, SharePoint in 2007 also have webparts. Are available and active SharePoint webparts on the Site can be obtained through the WebParts table and WebPartList. To find out who installed WebParts based on site and can be seen in the page table WebPartList

Alert

SharePoint 2007 application is also provided which alerts the system can provide notification of something, eg we ask SharePoint to provide alerts to send e-mail any document that is edited or new documents into a specific folder. For information Alert, SharePoint saves the information into several tables, namely:
• EventBatches
• EventCache
• EventLog
• EventReceivers
• EventSubsMatches
• ImmedSubscriptions
• SchedSubscriptions.

thanks to the Blog:
http://turnoncomputer.blogspot.com

regards,
raju

5 Different Sharepoint Roles

The Roles of sharepoint is Described Below.

Information Worker - People who use the site. They can be in charge of an individual list, maybe even a site, but no more than that. Most times they just have enough privilege to add documents to your document library and Check-in / Check-out items.
· SharePoint Site Admin - People who are delegated the responsibility of maintaining a site collection. These users are very much like a Power Users group within SharePoint. They have access to create additional subsites, create lists, restore documents using the Recycle Bin for other users, and so on.
· SharePoint Server Admin - People who are responsible for creating additional Web Applications, maintaining existing ones, enforcing Quotas on site collections, verifying backups, etc. Overall they are in charge of provisioning SharePoint and maintaining a healthy SharePoint environment.
· SharePoint Designer - People who are delegated the responsibility of customizing the SharePoint user experience, but do so in non-developer way. Typically these people are in charge of creating workflows using SharePoint Designer, adding content through the content management interface or through SharePoint Designer, and possibly are in charge of updating Layout pages or master pages to give your sites a more company intranet feel than a SharePoint intranet feel.
· SharePoint Developer - People who are delegated the responsibility of extending the capabilities of SharePoint via solution packages and features. Solution packages and features include things like: customized lists, customized site definitions, webparts, custom content types, extremely customized workflows, custom menus, etc.
With that being said, The SharePoint Consultant would most likely take the role of SharePoint Server Admin. They might (until somebody internally can be brought up to speed) be the SharePoint Site Admin as well. Possibly (as in my case) they might even be the SharePoint Developer role as well, but don't count on that. There aren't that many developers who understand the server-side of things, and vice-versa. This is especially true with SharePoint.

Thanks,
Raju.

Sharepoint Basic Definitions

WSS 3.0 - Windows SharePoint Services 3.0 which provides a mechanism to easily create, secure, store, search (per site collection), restore, perform workflow within, and customize sites with collaborative features

MOSS 2007 - The next version of SharePoint Portal Server 2003 which offers the same aspects as WSS 3.0, but includes "features" which extend it well beyond collaboration environment. Some of these additionally installed "features" include the following:
· Additional workflows
· Browser-based content management of pages
· Excel Services for rendering of trusted partial or full workbooks in a browser page or web part
· InfoPath Forms Services for electronic forms submittal through the web browser (no InfoPath client needed to run InfoPath-created forms)
· BDC - Business Data Catalog for accessing external data through database or webservice calls
· User Profiles and Audiences to locally store Active Directory information within SharePoint, so Audiences can be used to target information to the appropriate people (show / hide content based on rules you specify).
· MySite - What I like to refer to as the web-based My Documents or Home drive. MySite is a site collection created per user to host that users content (Documents and lists). It has a public and private facing section by default. The public section defaults to showing their contact information provided by your User Profile import
· Search extended to allow search through the sharepoint web applications, into other websites, your BDC, User Profiles, Exchange Public Folders, Shared Folders, and so forth
· Records Repository for compliance (keeping of records for some certain specified time usually)
· Many more things I just can't think of now

Feature - A simple way to think of a feature is to think of a packaged customization. This customization might be in the form of a workflow, web part, list definition, EventReceiver, etc

Solution - Usually multiple features packaged together to perform a much larger task, such as installation of custom Code Access Security policies, deploy web parts to multiple locations, install DLLs, or even create site definitions (highly customized site templates)

Web Part - Usually the primary point of customization within SharePoint. Web Parts consist of XML / XSL metadata in the case of a DataView (created in SharePoint Designer - the new FrontPage) or .NET code (created in Visual Studio 2005). Once the XML / XSL metadata, or .NET code has rendered contents to the web browser, this just becomes a snippet of HTML used within a page to provide content within the context of SharePoint that might not be SharePoint related (your custom application might be rendered here)

Farm - An environment in which multiple servers host the SharePoint Services in conjunction with each other. The farm is managed by a special web application called SharePoint 3.0 Central Administration

SharePoint 3.0 Central Administration - At first look, this site just looks like a normal web application with special links to help define your SharePoint architecture. Even though this site is so much more than that, trust is, it is also still a web application, and therefore you can still create lists / subwebs within it. Take care you are not in SharePoint 3.0 Central Administration when you create lists / subwebs, as this site should not be accessed by anybody other than designated SharePoint Farm administrators. Note: It is not invalid to create lists / subwebs within the Central Administration context as long as they correspond to SharePoint administrative functions. For example, you may decide to create a document library to host your SharePoint 3.0 Central Administration planning documents downloaded from the http://technet2.microsoft.com/Office/ site.

Shared Service Provider - A MOSS 2007 feature that gives boundaries for User Profiles and Audiences, BDC, Search, and Excel services configuration for sets of web applications

Web Application - A set of zone-based URLs that connect to a specific set of content databases. Content databases are what stores all your SharePoint content (documents, lists, sites, etc). You can have one or more IIS websites pointing to this web application. Each individual IIS website can facilitate Network Load Balancing or possibly differing authentication mechanisms.

Site Collection - A collection of webs that correspond to similar security requirements / roles. These are scoped per web application

Top-Level Site - A web that acts as the entry-point into your specific site collection

Web - A single site consisting of Pages and lists. Pages typically refer to a special document library MOSS 2007 uses to give the SharePoint site a friendly web interface (part of the content management aspect)

List - Content that would have normally been stored in a SQL database, but is propogated through the SharePoint UI to simply the application creation process. You might also think of this almost like an Excel spreadsheet with column headers and obviously your content in rows. Content within lists can be easily grouped by adding folders. List items (and folders) can be secured if necessary, but you should try to avoid that if possible to reduce administrative overhead.

Library - Special type of list that instead of thinking of the list as being the collective properties, is more centrally thought of via the document stored per row. Document Libraries, for example, store a document per row, but can have additional metadata (such as Subject, author, and other custom information) associated with it via columns within the same row. The new security feature of WSS 3.0 / MOSS 2007 allows for the securing of list items, which means you can "deny" access to a particular file if you need to. This is usually not recommended due to the complexity added to maintain such an environment. Again, folders can be created and secured individually if necessary.

Accessing Sharepoint Sites from Firefox

Hi guys ,

some times we use Firefox as your default browser, you probably dislike those exceptional sites that enforce you to use IE. One example is SharePoint. Using Internet Explorer you never have to log in on a Sharepoint site, at least not if you have a valid Windows session in the same domain. This works because Internet Explorer carries your Windows credentials to IIS on the server using NTLM. Firefox does not do this by default, forcing you to log in each time. Luckily, there is a config setting we can change to get rid of the login prompts:

1. Enter "about:config" in the address bar of Firefox and hit [Enter]
2. Do a search on "ntlm", at least three entries should appear
3. Set the value of "network.automatic-ntlm-auth.trusted-uris" to ".yourdomain" (do not forget the dot)

Restart Firefox. As of now, you never have to log on to that domain anymore. You can enter multiple domains by seperating them with a ",".

Note: this Content is Copied from http://www.ferdychristant.com/fchristant/production/fdm.nsf/archive/DOMM-78WSZQ

Thanks to FERDY CHRISTANT for valuable info. ,

regards,

Nagaraju...

Different type of SharePoint Server 2007 server farm topologies. (System Architecture)

http://faizal-comeacross.blogspot.com/2008/12/different-type-of-sharepoint-server.html

Step by Step SharePoint Server 2010 Installation Guide

http://www.codeproject.com/KB/sharepoint/SharePoint_Server_2010.aspx

Sharepoint Question & Answer

http://it.toolbox.com/wiki/index.php/Sharepoint_Interview_questions

List of 10 useful SharePoint Tools from CodePlex

http://www.praveenmodi.com/list-of-free-sharepoint-tools-from-codeplex/