Microsoft SharePoint Foundation 2010 uses Microsoft SQL Server 2008 databases to store configuration settings and most of the content for the Microsoft SharePoint Foundation Web site.
For example, all pages in the site, files in document libraries, files attached to lists, and information in lists are stored in the content database, and security and permission settings along with other configuration settings are stored in the configuration database in SQL Server. SharePoint Foundation 2010 uses a service account to communicate with the database on behalf of a user request. This service account can be either a specific user name or password (domain name and password), or a predefined system account, such as Local System or Network Service. When a SQL Server database is created, a value for the maximum database size is set. Each database has a separate database size setting. Note that a Web application might be associated with one or many databases.
This error indicates that Microsoft SharePoint Foundation could not connect to the SQL Server database.
One or more of the following symptoms might appear:
• Attempts to communicate with SQL Server fail and no content from databases hosted on the SQL Server can be accessed.
• This event appears in the event log: Event ID: 3355 Cannot connect to SQL Server. not found. Additional error information from SQL Server is included below.
One or more of the following might be the cause:
1. The SQL Server might be offline.
2. The SharePoint Foundation database access account might not have the necessary permissions to communicate with the SQL Server.
3. A firewall that runs on either the local server or on SQL Server might be blocking network communications.
Troubleshooting Steps:
Grant correct permissions to the database access account:
You must be a member of the Farm Administrators group to perform this task.
Assign the database access account:
a. On the Central Administration home page, click Security and in the General Security section click Configure service accounts.
b. On the Service Accounts page, in the Credential Management section, in the upper dropdown list click the correct Web application pool for your Web application.
c. In the Select an account for this component drop-down list, click the domain account that you want to associate with this Web application pool, or click Register new managed account to associate a new domain account with this application pool.
d. Click OK to save changes.
Verify that the account has correct permissions in SQL Server:
a. Connect to the computer that runs SQL Server by using an account that has Administrator permissions.
b. In SQL Server Management Studio, Object Explorer navigation pane, expand the Security node, and then expand the Logins node. The name of the database access account indicates that it is a SQL login.
c. If the account exists, in the Object Explorer navigation pane, expand the Databases node, expand the configuration database node, expand the Security, and then click Roles.
d. Expand the Database Roles node, right-click db_owner role and select Properties.
e. In the Database Role Properties dialog box, check whether the database access account is in the Members of this role list. If the account is not listed, click Add.
If you have any queries or questions regarding the above mentioned info then please let me know, Thanks...
Alert Name: ULS not enough free disk space
Event ID: 6457
The Microsoft SharePoint Foundation Tracing (SPTracev4) service is used by Microsoft SharePoint Foundation 2010 to manage trace message output. When trace logging is turned on,administrators can specify the path that is to be used to store the trace logs. This log file is used by many applications that are built on top of SharePoint Foundation. The trace log contains information that is useful for diagnosing server problems. SharePoint Foundation 2010 could not write to the trace
log. This event occurs when not enough free space is available for logging.
The following symptoms might appear:
• The trace log shows no new data.
• This event appears in the event log: Event ID: 6457 Description: Not enough free disk space available. The tracing service has temporarily stopped outputting trace messages to the log file. Tracing will resume when more than <# of MBs needed to resume logging> MB of disk space
becomes available.
Possible Cause:
The configured log location does not have sufficient free disk space for logging.
Troubleshooting steps:
Free up disk space
1. Use Disk Cleanup to free up disk space where the trace logs are stored.
2. Verify that the trace log has enough disk space to run properly.
3. If the trace log does not have enough disk space, clean up the Temp folders on the drive.
4. If this procedure does not solve the problem, it is also possible to relocate the trace log file to a partition that has more drive space.
Relocate the log file
1. On the SharePoint Central Administration Web site, click Monitoring and in the Reporting section, click Configure diagnostic logging.
2. On the Diagnostic Logging page, in the Trace Log section, type the new location for the trace log files in the Path text box.
3. Click OK.
If you have any queries/questions regarding the above mentioned info then please let me know, Thanks..
Alert Name: E-mail service cannot deliver e-mail
Event ID: 6873
The Microsoft SharePoint 2010 Products e-mail service processes e-mail destined for insertion into SharePoint lists. The service processes mail that the Windows Simple Mail Transfer Protocol (SMTP) service added to a drop folder.
One or more of the following symptoms might appear:
• SharePoint lists do not receive e-mail.
• This event appears in the event log: Event ID: 6599 Description: an error occurred while processing incoming email
One or more of the following might be the cause:
• There is no corresponding SharePoint list for the recipient of an e-mail.
• The sender does not have sufficient permissions to add content to the SharePoint list.
Troubleshooting Steps:
Verify that the list is configured to receive e-mail:
1. In the list provided in the event details, on the List menu, click List Settings.
2. On the List Settings page, under Communications, click Incoming e-mail settings.
3. Verify the following:
• The correct e-mail address is entered in the E-mail address box.
• The Yes option is selected under Allow this document library to receive e-mail?
Grant the sender the appropriate permissions to the recipient list:
1. In the list provided in the event details, on the List menu, click List Settings.
2. On the List Settings page, under Permissions and Management, click Permissions for this list.
3. Verify that the user account provided in the event details has at least Contributor permissions to the list.
If you have any queries/questions regarding the above mentioned information then please let me know, Thanks..
By default, a SharePoint farm uses content databases on SQL Server as its only data source. Farm content generally includes documents and pictures, which can each be on the order of several megabytes in size. Files and other unstructured data have historically been stored as binary large objects (BLOBs) within the database.
While there have been many improvements in the way that BLOBs are handled within a SQL Server database3, there are limitations. The VARBINARY(MAX) data type is used for native BLOB storage, and can accommodate files up to two gigabytes (2147483648 bytes) in size. In rare circumstances, this may not be adequate for all of the files that will be stored in the farm. Also, the performance of writing BLOBs to and retrieving BLOBs from the database is generally not as good as the performance offered by file systems, which can degrade users’ perception of a SharePoint solution.
Remote BLOB Storage (RBS) feature pack is available for SQL Server 2008 and SQL Server 2008 R2; it provides libraries and APIs that allow SQL Server to interact with BLOBs stored outside of the database. SQL Server 2008 and SQL Server 2008 R2 provide a data type called FILESTREAM that allows BLOBs to be stored within an NTFS volume, but managed by the database. This feature cannot be directly used by SharePoint4, but there is an RBS provider for FILESTREAM that can be used with local SharePoint databases (such as those often employed by SharePoint Foundation 2010); this local database requirement makes the FILESTREAM provider for RBS unsuitable for most farm-based architectures. For farm deployments with separate database servers, RBS providers other than FILESTREAM may still be used.
For example, a provider for a dedicated external store, such as an EMC2 Centerra system, that makes use of the SQL Server RBS API calls may be employed. These RBS providers allow third-party products to leverage RBS to store and retrieve files that reside outside of the database. Using Remote BLOB Storage requires configuration of both SQL Server 2008 (or SQL Server 2008 R2) and SharePoint Server 2010. These systems are expected to offer higher performance for reading and writing large files, but will generally require special attention when administering sites or performing backup/restore operations.
Central administration has been redesigned completely with features like a ribbon interface that is similar to Office 2007 and 2010 products. The ribbon is context-aware, and makes accessing the subtasks within any selected functional area more intuitive. The central administration site looks similar to Windows control panel, where different tasks and activities are grouped into categories. The new home page also provides convenient access to most common tasks by grouping them together into categories such as application management, monitoring, security, backup, and so on.
Backup and RestoreMicrosoft added a few very important enhancements to SharePoint backup and recovery. SharePoint 2010 provides several levels of granularity for performing backup and restore. This includes farm configuration, site collections, sub sites and lists.The central administration site provides a simple interface to perform full backup and restore, perform granular backup or configure backup settings. In earlier versions of SharePoint, administrators built a secondary farm to perform granular recovery of SharePoint content. This is no longer required with SharePoint 2010. In SharePoint 2010, administrators can perform content restore from unattached content databases. Using unattached content database feature, you can connect to a content DB restored to any SQL server in the network and use SharePoint 2010 to browse the contents of the database. An administrator will be able to restore content at a very granular level.Similar to any other administrative function within SharePoint 2010, you can automate or script your backups using Windows PowerShell. Every backup and restore activity that can be performed using central administration can also done at the command-line using PowerShell. Windows PowerShell also provides a few more additional backup/restore options such as file compression and SQL snapshots which are not available through central administration webpage.
SharePoint 2010 Health and Monitoring
SharePoint 2010 includes new tools to monitor health and track performance of a SharePoint farm. This includes features such as unified logging, developer dashboard, usage database, SharePoint maintenance engine, and out-of-box usage reports. Most of these improvements are done to provide a more proactive way of monitoring and reporting. Administrators can also use PowerShell cmdlets to monitor the health of a SharePoint farm.
The integrated Health Analyzer identifies common problems and provides prescriptive guidance to help administrators resolve them. The tool includes several default rules for Security, Performance, Configuration, and Availability. Each rule can be independently enabled and have its scope set to determine the servers that are checked. If a rule is enabled, then SharePoint 2010 will periodically check the conditions associated with the rule, based on a defined schedule. Certain rules can even be set to allow SharePoint automatically correct violations.
