Event ID 3363 (Windows SharePoint Services health model)

Event ID 3363 (Windows SharePoint Services health model)
Windows SharePoint Services 3.0

Applies To: Windows SharePoint Services 3.0

 

Topic Last Modified: 2008-04-27

Windows SharePoint Services 3.0 uses SQL Server databases to store most of the content for the Web site and configuration settings. 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.

Windows SharePoint Services 3.0 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 and 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.

Event Details  

Product:

Windows SharePoint Services

ID:

3363

Source:

Windows SharePoint Services 3

Version:

12.0

Symbolic Name:

ULSEvtTag_3363

Message:

SQL Server version %1 or greater required.

Resolve Install correct SQL Server version

The computer that hosts the database server role must have SQL Server 2000 with SP3a or later or Microsoft SQL Server 2005 SP1 or later. You can either install or upgrade the server to the correct version of SQL Server.

To perform this procedure, you must be a member of the Administrators group on the SQL Server computer.

Verify

You must be a member of the SharePoint Administrators group to perform this task.

To ensure that any database issues have been resolved

  1. Use the command Stsadm.exe -o enumsites to list the sites for each Web application to list all sites in the various databases, and locate one site in each database.

  2. Browse to that site, and ensure that the appropriate page rendered. If you get an access denied page with an option to request access, or the option to sign in as a different user, the operation completed successfully.

  3. In Central Administration, on the left-hand navigation pane, click Application Management.

  4. On the Application Management page, in the SharePoint Site Management section, click Quota templates.

  5. On the Quota Templates page, create a new quota template. The specific settings are not relevant to this verification test. You are creating the template to see if it can be accessed in step 7.

  6. Click OK to save the quota template.

  7. Refresh the browser window, and then return to the quota templates page. If the quota template that you created can be selected, then access to the Windows SharePoint Services 3.0 Configuration database has been restored.

  8. Click Delete to delete the quota template.

Related Management Information

Databases (Health model)

Windows SharePoint Services 3.0 health model

Related:

Event ID 3361 (Windows SharePoint Services health model)

Event ID 3361 (Windows SharePoint Services health model)
Windows SharePoint Services 3.0

Applies To: Windows SharePoint Services 3.0

 

Topic Last Modified: 2008-04-27

Windows SharePoint Services 3.0 uses SQL Server databases to store most of the content for the Web site and configuration settings. 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.

Windows SharePoint Services 3.0 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 and 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.

Event Details  

Product:

Windows SharePoint Services

ID:

3361

Source:

Windows SharePoint Services 3

Version:

12.0

Symbolic Name:

ULSEvtTag_3361

Message:

Incorrect Microsoft Data Access Component version. Windows SharePoint Services requires at least version 2.8.1022.0.

Resolve Update the MDAC Version

The Microsoft Data Access Components (MDAC) version needs to be updated. Version 2.8.1022.0 is the minimum required, and is available from the Microsoft Download Center (http://go.microsoft.com/fwlink/?linkid=5317).

You must be a member of the Administrators group to perform this action.

Verify

You must be a member of the SharePoint Administrators group to perform this task.

To ensure that any database issues have been resolved

  1. Use the command Stsadm.exe -o enumsites to list the sites for each Web application to list all sites in the various databases, and locate one site in each database.

  2. Browse to that site, and ensure that the appropriate page rendered. If you get an access denied page with an option to request access, or the option to sign in as a different user, the operation completed successfully.

  3. In Central Administration, on the left-hand navigation pane, click Application Management.

  4. On the Application Management page, in the SharePoint Site Management section, click Quota templates.

  5. On the Quota Templates page, create a new quota template. The specific settings are not relevant to this verification test. You are creating the template to see if it can be accessed in step 7.

  6. Click OK to save the quota template.

  7. Refresh the browser window, and then return to the quota templates page. If the quota template that you created can be selected, then access to the Windows SharePoint Services 3.0 Configuration database has been restored.

  8. Click Delete to delete the quota template.

Related Management Information

Databases (Health model)

Windows SharePoint Services 3.0 health model

Related:

Event ID 3360 (Windows SharePoint Services health model)

Event ID 3360 (Windows SharePoint Services health model)
Windows SharePoint Services 3.0

Applies To: Windows SharePoint Services 3.0

 

Topic Last Modified: 2008-04-27

When Windows SharePoint Services 3.0 is in Active Directory account creation mode, any user added to a site is automatically added to the Active Directory organizational unit identified for use by Windows SharePoint Services 3.0. When running in Active Directory account creation mode, every application pool that contains one or more sites must use an account that has permissions to create, read, and update accounts in the Active Directory organizational unit that the domain administrator configured for Windows SharePoint Services 3.0.

Event Details  

Product:

Windows SharePoint Services

ID:

3360

Source:

Windows SharePoint Services 3

Version:

12.0

Symbolic Name:

ULSEvtTag_3360

Message:

The Active Directory organization unit %1 registered in Windows SharePoint Services does not exist.

Resolve Ensure that the Active Directory organization unit exists

Ask the domain administrator to locate the correct organizational unit name in Active Directory. If the organizational unit has been deleted, ask the domain administrator to recreate the organizational unit.

Use the psconfig.exe adminvs -provision command to reprovision the site. You must be a member of the SharePoint Administrators group to perform this action.

For more information about this command-line operation, see the Windows SharePoint Services 3.0 online documentation (http://go.microsoft.com/fwlink/?linkid=73952) or the Command-line reference for the SharePoint Products and Technologies Configuration Wizard (Windows SharePoint Services) (http://technet2.microsoft.com/windowsserver/WSS/en/library/eae2818a-e247-43c2-932f-f914f271d8a41033.mspx) article on TechNet.

Verify

Ensure that a new user can be added to an end-user-accessible site. The action should succeed without error.

You must be a site administrator to perform this task.

To check if a new user can be added to an end-user-accessible site

  1. In the top level page of the site, on the left navigation pane, click People and Groups.

  2. On the Peoples and Groups page, click New, and then click Add users.

  3. On the Add Users page, type the user name in the Users/Groups box.

  4. Click the name-check icon to the right Users/Groups of the box.

If the name resolves (is underlined), the problem has been fixed.

Related Management Information

Active Directory Integration (Health model)

Windows SharePoint Services 3.0 health model

Related:

Event ID 3359 (Windows SharePoint Services health model)

Event ID 3359 (Windows SharePoint Services health model)
Windows SharePoint Services 3.0

Applies To: Windows SharePoint Services 3.0

 

Topic Last Modified: 2008-04-27

When Windows SharePoint Services 3.0 is in Active Directory account creation mode, any user added to a site is automatically added to the Active Directory organizational unit identified for use by Windows SharePoint Services 3.0. When running in Active Directory account creation mode, every application pool that contains one or more sites must use an account that has permissions to create, read, and update accounts in the Active Directory organizational unit that the domain administrator configured for Windows SharePoint Services 3.0.

Event Details  

Product:

Windows SharePoint Services

ID:

3359

Source:

Windows SharePoint Services 3

Version:

12.0

Symbolic Name:

ULSEvtTag_3359

Message:

The application pool account has insufficient permission to add user accounts to Active Directory.

Diagnose

Windows SharePoint Services 3.0 could not add a new user to an end-user-accessible site. This error might be caused by one of the following conditions:

  • The application pool account has insufficient permissions to add/read user accounts to/from Active Directory.

  • The Active Directory organization unit registered in Windows SharePoint Services 3.0 does not exist. To determine if the organizational unit exists, contact your domain administrator. To fix this, see the section titled “Ensure that the Active Directory organization unit exists”.

To see which account is being used by the application pool for the site where you could not add a user

You must be a member of the SharePoint Administrators group to perform this task.

  1. In Central Administration, on the left navigation pane, click Application Management.

  2. On the Application Management page, in the SharePoint Site Management section, click Site collection list.

  3. On the Site Collection List page, you will see the site collections listed for a specific Web application. If you do not see the site collection that contains the site where you could not add a user, then click the drop-down list next to Web Application to switch to another Web application.

  4. On the left navigation pane, click Application Management.

  5. On the Application Management page, in the SharePoint Application Management section, click Web application list. The name of the Application pool will be to the left of the URL.

  6. In Internet Information Services Manager, expand the server node and then expand the Application Pools node.

  7. Right-click the application pool and click Properties.

  8. In the Properties dialog box, on the Identity tab, the account is shown in the User name box.

  9. To fix permissions issues, see the section titled Assign the application pool account sufficient permissions.

Resolve

To resolve this issue, use the resolution that corresponds to the cause you identified in the Diagnose section. After performing the resolution, see the Verify section to confirm that the feature is operating properly

 

Cause

Resolution

The Active Directory organization unit registered in Windows SharePoint Services 3.0 does not exist

Ensure that the Active Directory organization unit exists

The application pool account has insufficient permissions to add/read user accounts to/from Active Directory

Assign the application pool account sufficient permissions

Ensure that the Active Directory organization unit exists

Ask the domain administrator to locate the correct organizational unit name in Active Directory. If the organizational unit has been deleted, ask the domain administrator to recreate the organizational unit.

Use the psconfig.exe adminvs -provision command to reprovision the site. You must be a member of the SharePoint Administrators group to perform this action.

For more information about this command-line operation, see the Windows SharePoint Services 3.0 online documentation (http://go.microsoft.com/fwlink/?linkid=73952) or the Command-line reference for the SharePoint Products and Technologies Configuration Wizard (Windows SharePoint Services) (http://technet2.microsoft.com/windowsserver/WSS/en/library/eae2818a-e247-43c2-932f-f914f271d8a41033.mspx) article on TechNet.

Assign the application pool account sufficient permissions

In order for Windows SharePoint Services 3.0 to have permissions to create accounts in the sharepoint_ou organizational unit, the identity account for the SharePoint Central Administration v3 application pool and the identity accounts for any Web applications must have the correct permissions delegated to it.

To see which account is being used by the application pool for the site where you could not add a user

You must be a member of the SharePoint Administrators group to perform this task.

  1. In Central Administration Web, on the left navigation pane, click Application Management.

  2. On the Application Management page, in the SharePoint Site Management section, click Site collection list.

  3. On the Site Collection List page, you will see the site collections listed for a specific Web application. If you do not see the site collection that contains the site where you could not add a user, then click the drop-down list next to Web Application to switch to another Web application.

  4. On the left navigation pane, click Application Management.

  5. On the Application Management page, in the SharePoint Application Management section, click Web application list. The name of the Application pool will be to the left of the URL.

  6. In Internet Information Services Manager, expand the server node and then expand the Application Pools node.

  7. Right-click the application pool and click Properties.

  8. In the Properties dialog box, on the Identity tab, the account is shown in the User name box.

Verify

Ensure that a new user can be added to an end-user-accessible site. The action should succeed without error.

You must be a site administrator to perform this task.

To check if a new user can be added to an end-user-accessible site

  1. In the top level page of the site, on the left navigation pane, click People and Groups.

  2. On the Peoples and Groups page, click New, and then click Add users.

  3. On the Add Users page, type the user name in the Users/Groups box.

  4. Click the name-check icon to the right Users/Groups of the box.

If the name resolves (is underlined), the problem has been fixed.

Related Management Information

Active Directory Integration (Health model)

Windows SharePoint Services 3.0 health model

Related:

Event ID 4971 (Windows SharePoint Services health model)

Event ID 4971 (Windows SharePoint Services health model)
Windows SharePoint Services 3.0

Applies To: Windows SharePoint Services 3.0

 

Topic Last Modified: 2008-04-27

Windows SharePoint Services 3.0 uses SQL Server databases to store most of the content for the Web site and configuration settings. 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.

Windows SharePoint Services 3.0 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 and 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.

Event Details  

Product:

Windows SharePoint Services

ID:

4971

Source:

Windows SharePoint Services 3

Version:

12.0

Symbolic Name:

ULSEvtTag_4971

Message:

Cannot update database on SQL Server instance ‘%1’. Database is read/only. Additional error information from SQL Server is included below.

%2

Resolve Change database to Read / Write

You must have db_owner access to the database to perform this action.

To increase the size of the database

  1. In SQL Server Management Suite, open the server node, right-click the database, and then click Properties. The database name is provided in the event message.

  2. On the Properties dialog box, on the left navigation pane, click Files.

  3. The Enable Autogrowth check box must be selected to make any changes.

  4. In the Database files box, in the Autogrowth column, click the ellipsis for the database file.

  5. In the Change Autogrowth dialog box, under Maximum File Size, if the Restricted File Growth option is selected, increase the maximum file size in the box to the right. You can also configure the database to grow without restrictions by selecting the Unrestricted File Growth option.

  6. Click OK.

Verify

You must be a member of the SharePoint Administrators group to perform this task.

To ensure that any database issues have been resolved

  1. Use the command Stsadm.exe -o enumsites to list the sites for each Web application to list all sites in the various databases, and locate one site in each database.

  2. Browse to that site, and ensure that the appropriate page rendered. If you get an access denied page with an option to request access, or the option to sign in as a different user, the operation completed successfully.

  3. In Central Administration, on the left-hand navigation pane, click Application Management.

  4. On the Application Management page, in the SharePoint Site Management section, click Quota templates.

  5. On the Quota Templates page, create a new quota template. The specific settings are not relevant to this verification test. You are creating the template to see if it can be accessed in step 7.

  6. Click OK to save the quota template.

  7. Refresh the browser window, and then return to the quota templates page. If the quota template that you created can be selected, then access to the Windows SharePoint Services 3.0 Configuration database has been restored.

  8. Click Delete to delete the quota template.

Related Management Information

Databases (Health model)

Windows SharePoint Services 3.0 health model

Related:

Event ID 3758 (Windows SharePoint Services health model)

Event ID 3758 (Windows SharePoint Services health model)
Windows SharePoint Services 3.0

Applies To: Windows SharePoint Services 3.0

 

Topic Last Modified: 2008-04-27

Windows SharePoint Services 3.0 uses SQL Server databases to store most of the content for the Web site and configuration settings. 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.

Windows SharePoint Services 3.0 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 and 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.

Event Details  

Product:

Windows SharePoint Services

ID:

3758

Source:

Windows SharePoint Services 3

Version:

12.0

Symbolic Name:

ULSEvtTag_3758

Message:

Database full error on SQL Server instance ‘%1’ in database ‘%2’. Additional error information from SQL Server is included below.

%3

Resolve Increase the size of the SQL Server database

Windows SharePoint Services 3.0 cannot write to a database if the database has run out of room. One solution is to increase the maximum size setting for the database that is full.

You must be a member of the Administrators group to perform this action.

To increase the size of the database

  1. In SQL Server Management Suite, open the server node, right-click the database, and then click Properties. The database name is provided in the event message.

  2. On the Properties dialog box, on the left navigation pane, click Files.

  3. In the Database files box, in the Autogrowth column, click the ellipsis for the database file.

  4. In the Change Autogrowth dialog box, under Maximum File Size, if the Restricted File Growth option is selected, increase the maximum file size in the box to the right. You can also configure the database to grow without restrictions by selecting the Unrestricted File Growth option.

  5. Click OK.

Verify

You must be a member of the SharePoint Administrators group to perform this task.

To ensure that any database issues have been resolved

  1. Use the command Stsadm.exe -o enumsites to list the sites for each Web application to list all sites in the various databases, and locate one site in each database.

  2. Browse to that site, and ensure that the appropriate page rendered. If you get an access denied page with an option to request access, or the option to sign in as a different user, the operation completed successfully.

  3. In Central Administration, on the left-hand navigation pane, click Application Management.

  4. On the Application Management page, in the SharePoint Site Management section, click Quota templates.

  5. On the Quota Templates page, create a new quota template. The specific settings are not relevant to this verification test. You are creating the template to see if it can be accessed in step 7.

  6. Click OK to save the quota template.

  7. Refresh the browser window, and then return to the quota templates page. If the quota template that you created can be selected, then access to the Windows SharePoint Services 3.0 Configuration database has been restored.

  8. Click Delete to delete the quota template.

Related Management Information

Databases (Health model)

Windows SharePoint Services 3.0 health model

Related:

Event ID 3760 (Windows SharePoint Services health model)

Event ID 3760 (Windows SharePoint Services health model)
Windows SharePoint Services 3.0

Applies To: Windows SharePoint Services 3.0

 

Topic Last Modified: 2008-04-27

Windows SharePoint Services 3.0 uses SQL Server databases to store most of the content for the Web site and configuration settings. 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.

Windows SharePoint Services 3.0 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 and 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.

Event Details  

Product:

Windows SharePoint Services

ID:

3760

Source:

Windows SharePoint Services 3

Version:

12.0

Symbolic Name:

ULSEvtTag_3760

Message:

SQL Database ‘%1’ on SQL Server instance ‘%2’ not found. Additional error information from SQL Server is included below.

%3

Resolve Restore database from backup

The SQL Server database is not present or accessible on the computer running SQL Server. Confirm that the database is online. If it is not, you will need restore the database from a backup, and re-connect it to Windows SharePoint Services 3.0. For information about restoring the database see the Windows SharePoint Services 3.0 documentation.

You must be a member of the SharePoint Administrators group to perform these tasks.

To restore the database from a previous backup

  1. In Central Administration, on the left navigation pane, click Operations.

  2. On the Operations page, in the Backup and Restore section, click Restore from backup.

  3. On the Restore from Backup page, type the backup share path in the Backup location box, and then click OK.

  4. Select the backup from the list.

    Important:
    The backup must be of at least the database and the accompanying Web application.
  5. Click Continue Restore Process.

  6. Select the check box next to the database and click Continue Restore Process.

  7. Under Restore Options, select the Same configuration option. This will overwrite the existing database.

  8. Click OK.

To reconnect the database in Central Administration

  1. In Central Administration, on the left navigation pane, click Application Management.

  2. On the Application Management page, in the SharePoint Web Application Management section, click Content databases.

  3. On the Manage Content Databases page, click Add a content database.

  4. On the Add Content Database page, in the Web Application section, select the Web application from the Web application drop-down list.

  5. Under Database Name and Authentication, type the name of the server in the Database Server box and the database name in the Database Name box.

  6. Click OK to save the changes.

Verify

You must be a member of the SharePoint Administrators group to perform this task.

To ensure that any database issues have been resolved

  1. Use the command Stsadm.exe -o enumsites to list the sites for each Web application to list all sites in the various databases, and locate one site in each database.

  2. Browse to that site, and ensure that the appropriate page rendered. If you get an access denied page with an option to request access, or the option to sign in as a different user, the operation completed successfully.

  3. In Central Administration, on the left-hand navigation pane, click Application Management.

  4. On the Application Management page, in the SharePoint Site Management section, click Quota templates.

  5. On the Quota Templates page, create a new quota template. The specific settings are not relevant to this verification test. You are creating the template to see if it can be accessed in step 7.

  6. Click OK to save the quota template.

  7. Refresh the browser window, and then return to the quota templates page. If the quota template that you created can be selected, then access to the Windows SharePoint Services 3.0 Configuration database has been restored.

  8. Click Delete to delete the quota template.

Related Management Information

Databases (Health model)

Windows SharePoint Services 3.0 health model

Related:

Event ID 3358 (Windows SharePoint Services health model)

Event ID 3358 (Windows SharePoint Services health model)
Windows SharePoint Services 3.0

Applies To: Windows SharePoint Services 3.0

 

Topic Last Modified: 2008-04-27

Windows SharePoint Services 3.0 uses SQL Server databases to store most of the content for the Web site and configuration settings. 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.

Windows SharePoint Services 3.0 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 and 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.

Event Details  

Product:

Windows SharePoint Services

ID:

3358

Source:

Windows SharePoint Services 3

Version:

12.0

Symbolic Name:

ULSEvtTag_3358

Message:

Specified SQL Server not found. Additional error information from SQL Server is included below.

%1

Resolve Grant correct permissions to the database access account

You must be a member of the SharePoint Administrators group to perform this task.

To assign the database access account

  1. In Central Administration, on the left navigation pane, click Operations.

  2. On the Operations page, in the Security Configuration section, click Security accounts.

  3. On the Security Accounts page, in the Credential Management section, select the Web application pool option.

  4. Select the Web service from the Web service drop-down list. The default is “Windows SharePoint Services Web Application”.

  5. Select the Web application pool from the Application pool drop-down list.

  6. Select the Configurable option.

  7. Type the correct domain account into the User name box and the password for that account into the Password box.

  8. Click OK to save changes.

  9. Restart IIS.

To ensure that this account has correct permission in SQL Server

  1. Connect to the computer running SQL Server by using an account with administrator permissions.

  2. In SQL Server Management Studio, open the Security node, and then open the Logins node. You should see the account listed as a SQL Login.

  3. If the account is there, then open the database node, open the Security node under the database, and then open the Roles node.

  4. Open the Database Roles node and double-click the db_owner role to open its properties.

  5. In the Database Roles Properties dialog box, under Members of this role, you should see the database access account. If the account is not there, add it by clicking Add.

Verify

You must be a member of the SharePoint Administrators group to perform this task.

To ensure that any database issues have been resolved

  1. Use the command Stsadm.exe -o enumsites to list the sites for each Web application to list all sites in the various databases, and locate one site in each database.

  2. Browse to that site, and ensure that the appropriate page rendered. If you get an access denied page with an option to request access, or the option to sign in as a different user, the operation completed successfully.

  3. In Central Administration, on the left-hand navigation pane, click Application Management.

  4. On the Application Management page, in the SharePoint Site Management section, click Quota templates.

  5. On the Quota Templates page, create a new quota template. The specific settings are not relevant to this verification test. You are creating the template to see if it can be accessed in step 7.

  6. Click OK to save the quota template.

  7. Refresh the browser window, and then return to the quota templates page. If the quota template that you created can be selected, then access to the Windows SharePoint Services 3.0 Configuration database has been restored.

  8. Click Delete to delete the quota template.

Related Management Information

Databases (Health model)

Windows SharePoint Services 3.0 health model

Related:

Event ID 3353 (Windows SharePoint Services health model)

Event ID 3353 (Windows SharePoint Services health model)
Windows SharePoint Services 3.0

Applies To: Windows SharePoint Services 3.0

 

Topic Last Modified: 2008-04-27

When you back up a Web site, you back up the content database for the site, including all pages in the site, files in document libraries, files attached to lists, security and permission settings, and feature settings. The backup process creates a single file that contains all of this data. The restore process uses this file to restore the content database for the site. For more information about backup and restore, see Administering backup and recovery for Windows SharePoint Services 3.0 technology (http://technet2.microsoft.com/windowsserver/WSS/en/library/64171b8c-5608-4e69-881a-67996080b7ff1033.mspx) on TechNet.

Event Details  

Product:

Windows SharePoint Services

ID:

3353

Source:

Windows SharePoint Services 3

Version:

12.0

Symbolic Name:

ULSEvtTag_3353

Message:

Backup failure: insufficient permissions on %1.

Resolve Assign sufficient permissions

Windows SharePoint Services 3.0 could not complete the backup because the account being used does not have sufficient permissions to the backup share. The backup might be performed either as an individual logon or using the Windows SharePoint Services Timer (SPTimer) service.

Correct the permissions and then retry the backup operation again.

On the file share, and in NTFS permissions, ensure that the following accounts are granted Change and Read permissions:

  • Account used by the SQL Server (MSSQLServer) service.

  • Windows SharePoint Central Administration application pool account if using Central Administration or a timer job to perform the backup.

  • The logged on account if using the Stsadm command-line tool to perform the backup manually.

  • If the backup is being performed by a timer job, the computer from which the backup operation is being performed must also be granted access. You can grant a computer permissions to a file share by using the following format: <Domain>\<Sharename>$. For example, “Contoso\WSSBackups$”

    Note:
    When backing up to a remote file share, you must use a domain account rather than a local system account. You must have Modify permissions to the share to perform these tasks.

Verify

Ensure that backups can complete successfully. You must be a member of the SharePoint Administrators group to perform this task.

To check if backups can complete successfully

  1. Important: Ensure that the target location has sufficient drive space for the backup.

  2. In Central Administration, on the left navigation pane, click Operations.

  3. On the Operations page, in the Backup and Restore section, click Perform a backup.

  4. On the Select Component to Backup page, choose the components you want to back up, such as a farm or an individual site. To test the backup job, choose a site or some smaller component.

  5. When you have selected all the components that you want to backup, click Start Backup Process.

  6. On the Start Backup page, in the Backup File Location section, enter the UNC path to the backup folder.

  7. Click OK.

  8. You can view the backup job status on the backup status page by clicking Refresh. The page will also refresh every 30 seconds automatically. Backup and Restore is a Timer service job, so it might take a few seconds for the backup to start.

  9. If you receive any errors, you can find more information by looking in the spbackup.log at the UNC path you specified previously.

To find the location of the log file folder

  1. In Central Administration, on the left navigation pane, click Operations.

  2. In the Logging and Reporting section, click Diagnostic Logging.

  3. On the Diagnostic Logging page, in the Trace Log section, the path to the log file is displayed in the Path box.

Related Management Information

Backup and Restore (Health model)

Windows SharePoint Services 3.0 health model

Related:

Event ID 3355 (Windows SharePoint Services health model) (Windows SharePoint Services health model)

Event ID 3355 (Windows SharePoint Services health model) (Windows SharePoint Services health model)
Windows SharePoint Services 3.0

Applies To: Windows SharePoint Services 3.0

 

Topic Last Modified: 2008-04-27

Windows SharePoint Services 3.0 uses SQL Server databases to store most of the content for the Web site and configuration settings. 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.

Windows SharePoint Services 3.0 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 and 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.

Event Details  

Product:

Windows SharePoint Services

ID:

3355

Source:

Windows SharePoint Services 3

Version:

12.0

Symbolic Name:

ULSEvtTag_3355

Message:

Cannot connect to SQL Server. %1 not found. Additional error information from SQL Server is included below.

%2

Resolve Grant correct permissions to the database access account

You must be a member of the SharePoint Administrators group to perform this task.

To assign the database access account

  1. In Central Administration, on the left navigation pane, click Operations.

  2. On the Operations page, in the Security Configuration section, click Security accounts.

  3. On the Security Accounts page, in the Credential Management section, select the Web application pool option.

  4. Select the Web service from the Web service drop-down list. The default is “Windows SharePoint Services Web Application”.

  5. Select the Web application pool from the Application pool drop-down list.

  6. Select the Configurable option.

  7. Type the correct domain account into the User name box and the password for that account into the Password box.

  8. Click OK to save changes.

  9. Restart IIS.

To ensure that this account has correct permission in SQL Server

  1. Connect to the computer running SQL Server by using an account with administrator permissions.

  2. In SQL Server Management Studio, open the Security node, and then open the Logins node. You should see the account listed as a SQL Login.

  3. If the account is there, then open the database node, open the Security node under the database, and then open the Roles node.

  4. Open the Database Roles node and double-click the db_owner role to open its properties.

  5. In the Database Roles Properties dialog box, under Members of this role, you should see the database access account. If the account is not there, add it by clicking Add.

Verify

You must be a member of the SharePoint Administrators group to perform this task.

To ensure that any database issues have been resolved

  1. Use the command Stsadm.exe -o enumsites to list the sites for each Web application to list all sites in the various databases, and locate one site in each database.

  2. Browse to that site, and ensure that the appropriate page rendered. If you get an access denied page with an option to request access, or the option to sign in as a different user, the operation completed successfully.

  3. In Central Administration, on the left-hand navigation pane, click Application Management.

  4. On the Application Management page, in the SharePoint Site Management section, click Quota templates.

  5. On the Quota Templates page, create a new quota template. The specific settings are not relevant to this verification test. You are creating the template to see if it can be accessed in step 7.

  6. Click OK to save the quota template.

  7. Refresh the browser window, and then return to the quota templates page. If the quota template that you created can be selected, then access to the Windows SharePoint Services 3.0 Configuration database has been restored.

  8. Click Delete to delete the quota template.

Related Management Information

Databases (Health model)

Windows SharePoint Services 3.0 health model

Related: