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/

Sharepoint ,MS.net and Biztalk PPTs and vedios

http://www.dotnet-u.com/CourseMaterials.aspx

Are U Tired with Googling For Sharepoint Blogs ?Click Here

Hi frnds ,
r u tired up googling for sharepoint sites? dont worry now Try these blogs u will find the answers for ur Queries...... and lot more fun in technical side.....:) happies.................enjoy the
Journey..........

Click here...

http://www.sharepointjoel.com/Lists/Posts/Post.aspx?ID=32

Thanks
Raju...................................
Be Happy:)

Sharepoint Nuggets

Sharepoint Startup:

One of the primary functions of a network is file sharing, but these days, simply sharing files isn’t enough: Workers need the ability to collaborate and become more efficient. To meet this need, Microsoft created SharePoint, which extends Windows 2000’s basic file-serving power to a new level. SharePoint helps you create a powerful, easy-to-use portal that lets users share, collaborate on, and search for documents and other data files and links. In this Daily Drill Down, I’ll introduce you to some of SharePoint Portal Server’s capabilities and how they work.

A tale of two SharePoints :

When Microsoft first started talking about "Tahoe" (SharePoint Portal Server's name during development), there was intense interest among beta testers and reviewers, many of whom had already faced the challenge of managing large document collections. Tahoe promised to solve document management needs with integrated access to Microsoft's Office suite of products.SharePoint came out in two different versions, each with a different perspective on how to solve the document management problem. SharePoint Team Services, available with FrontPage 2002, is designed to manage tasks. It provides a storage area for documents, but doesn't handle document version control or have any features that could be legitimately considered advanced.SharePoint Portal Server (SPS), on the other hand, is a very different animal. Despite the similarity in name, there is very little else that SPS has in common with SharePoint Team Services.

While SharePoint Team Services handles basic tasks and rudimentary document management, SPS does more.

It has three main benefits:

1. Portal generation
2. Document management
3. Searching

You can use SharePoint Portal Server to build a portal on your network. Let's look at SharePoint Portal Server’s main benefits one-by-one.

Portal generationSimply put, a portal is a home page for Web-based information that is important to your users. Internet portals like MSN.com and Yahoo.com provide a convenient, centralized place to access the Internet, with collections of links to interesting or pertinent pages.

SPS can do the same thing for your organization. SPS lets you define workspaces, which are essentially root folders that will contain information. A workspace can be made up of a single portal with a few dozen documents, or it can contain many different portals connecting to an array of options. The portal's main page, or home page, allows you to navigate to the content contained in the workspace and other areas of the Internet or your intranet.

Document management

The second key advantage of SPS is its ability to manage documents. Document management systems have been around for years. Historically, however, they’ve been very expensive programs that didn't integrate well with Microsoft Office or other applications. SPS doesn't offer all of the advanced features of high-end document management systems, such as document routing, but it does have the basic functionality that most organizations need. It also integrates well with Microsoft's Office suite of products, giving it capabilities that most document management systems struggle with.

There are essentially two levels to document management. At the first level is a tool that lets you perform check-in and check-out operations. This is a simple way to control the number of people working on the same document at the time. SPS expands this slightly to encompass the idea that documents should not be available to the users at large until they’ve been approved, or “published” in the terminology of SPS.


Search;

SPS also provides a powerful, timesaving search feature. It has the ability to read and index documents of several types, including Word documents, Excel worksheets, and PDF files. The indexing process reads all of the words in the document and places them in a search database that you can query. The architecture is also extensible, allowing vendors to provide the ability to index other kinds of files, such as AutoCAD files.

SPS can index Public Folders on an Exchange Server, a file share, Lotus Notes databases, and other kinds of storage. By indexing all of the text in the documents on your network in all of the places where they might be stored, you create a central place to look for a document, and you don't have to know the document title or where it's filed on the network to find it. This can be particularly helpful for large organizations that have no centralized knowledge repository.

For example, let's say that you work for a company that sells flooring. You're getting ready to quote a job for a new mall opening in your area. You've heard that one of your colleagues did a really spectacular job in another region, but you don't remember the name of the mall so you can't look up the job by the client’s name. Your colleague is on vacation for a week and is unreachable. You really want to look at that proposal, but you don't have enough information to find it.

SharePoint can help you organize your networkSPS doesn't solve every problem, but its mix of solutions and its cost-effective price make it a great tool for an organization that needs a single, easy-to-manage portal for employees, a basic document management system, or a searching tool.

Thanks
Raju.
Be Happy

Technical Requirements for the MOSS Developer

Hi frnds,
The Technical requirements for the Moss Developer are mentioned Below


1)Knowledge on Microsoft Technologies Like MOSS 2007/WSS, .Net(asp.net,C#.net) ,MSOffice(Sharepoint Desginer,infopath)

why ASP.net?

In MOSS we use Master pages and page layouts These are dictate the overall look and feel of your SharePoint site. Master pages contain controls that are shared across multiple page layouts, such as navigation, search, or language-preference for multilingual sites. Page layouts contain field controls and Web Parts. here comes the role of Asp.net ,in asp.net we used to develop the master pages.if we have the knowledge on the master pages creation it would be added advantage for the MOSS Development.

Why C#.Net?

In MOSS We Use Webparts.

what is Webpart:

• Web Parts are one of the core ASP.NET technologies used by SharePoint to
  present dynamic information to users.
• They are the most common customization created for SharePoint.
• A Web Part is a reusable component which exists on a Web Part Page and can present any type of web-based information.

By using the C# Language we can Develop the Custom Webparts.How to develope the Webpart i will give u the clear Picture in "Development of Webparts" post.

Why MSoffice :

In MS office there are So many Tools like Word,excel,PowerPoint ,sharepoint designer ,infopath etc.

Sharepoint Designer:

• Microsoft SharePoint Designer (full name Microsoft Office SharePoint Designer) is a WYSIWYG HTML editor and general web Design program from Microsoft, replacing Microsoft Office FrontPage, and part of the SharePoint family of products.
• It is part of the Microsoft Office 2007 family but not included in any of the Office 2007 suites. The name change, from FrontPage, reflects the emphasis on designing and customizing SharePoint websites. SharePoint Designer shares its HTML rendering engine with Microsoft Expression Web.

Infopath:

• The most common usage of InfoPath is to integrate it with Microsoft SharePoint technology using InfoPath Form Services (included in the enterprise commercial version of MOSS or as the separate Microsoft Office Forms Server 2007 product.
• In SharePoint, a "Form Library" can be created and developed by using InfoPath. InfoPath fields will be exported as "Columns" in the library and can be directly read in SharePoint or be used as part of web services results in workflow development.

2)Databases Like Sql Server 2005/2008

3)Active Directory:

what is Active Directory?

Active Directory is a directory service used to store information about the network resources across a Domine and also centralize the network.

Role of Active Directory in Sharepoint?

The sharepoint portal or site is to integrate with the Active Directory because the users present in the Domine will get the permissions to access the Portal or Site.

Thanks

Nagaraju.

Be Happy :)

Installing a New Microsoft Office SharePoint Server 2007 Portal: Step-by-Step Instructions

http://www.mindsharpblogs.com/bill/archive/2006/06/27/1153.aspx

Thanks,

Nagaraju

Be Happy:)

History Of Sharepoint

The first version, called SharePoint Team Services (usually abbreviated to STS), was released at the same time as Office XP and was available as part of Microsoft FrontPage. STS could run on Windows 2000 Server or Windows XP.
Windows SharePoint Services 2.0 was marketed as an upgrade to SharePoint Team Services, but was in fact a completely redesigned application[citation needed]. SharePoint Team Services stored documents in ordinary file storage, keeping document metadata in a database. Windows SharePoint Services 2.0 on the other hand, stores both the document and the metadata in a database, and supports basic document versioning for items in Document Libraries. Service Pack 2 for WSS added support for SQL Server 2005 and the use of the .NET Framework 2.0.
Windows SharePoint Services 3.0 was released on November 16, 2006 as part of the Microsoft Office 2007 suite and Windows Server 2008. WSS 3.0 is built using .NET Framework 2.0 and .NET Framework 3.0 Windows Workflow Foundation to add workflow capabilities to the basic suite. By the beginning of 2007 WSS 3.0 was made available to the public. Windows 2000 Server is not supported by WSS 3.0, nor is SQL Server 2000.

Thanks
Nagaraju
Be Happy :)

Sharepoint

SharePoint is an enterprise information portal, from Microsoft, that can be configured to run Intranet, Extranet and Internet sites. Microsoft Office SharePoint Server 2007 allows people, teams and expertise to connect and collaborate. A SharePoint enterprise portal is composed of both SharePoint Portal and Windows SharePoint Services, with SharePoint being built upon WSS. WSS is typically used by small teams, projects and companies. SharePoint Server is designed for individuals, teams and projects within a medium to large company wide enterprise portal.

Thanks,
Nagaraju.

Be Happy :)