Event ID 3250 (Windows SharePoint Services health model)

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

Applies To: Windows SharePoint Services 3.0

 

Topic Last Modified: 2008-04-27

The Windows SharePoint Services Tracing (SPTrace) service is used by Windows SharePoint Services 3.0 to manage trace output of the call stack. When trace logging is enabled, administrators can specify the path used to store the trace logs. This log file is reused by many applications that are built on top of Windows SharePoint Services 3.0.

Event Details  

Product:

Windows SharePoint Services

ID:

3250

Source:

Windows SharePoint Services 3

Version:

12.0

Symbolic Name:

ULSEvtTag_3250

Message:

Unable to write to Trace Log: 0x%1

Diagnose

Windows SharePoint Services 3.0 could not create, or write to, the trace log. This trace log contains information that is useful in troubleshooting issues.

This error might be caused by one of the following conditions:

  • The account that Windows SharePoint Services 3.0 is using does not have sufficient rights to the trace log.

  • The hard disk or partition does not have enough room.

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.

The account that Windows SharePoint Services 3.0 is using does not have sufficient rights to the trace log
To check the permissions assigned to the log file folder

  1. If you do not know the location of the folder, see the “To find the location of the log file folder” procedure. By default, the location is “Program Files\Common Files\Microsoft Shared\web extensions\12\LOGS” but the location can be changed in Central Administration.

  2. Navigate to the folder, right-click the folder, and then click Properties.

  3. On the Security tab, the WSS_ADMIN_WPG Windows group should have Full Control and the WSS_WPG Windows group should have Read & Execute, List Folder Contents, and Read permissions or higher on the folder. If they do not, assign these permissions by using the procedure in the “Assign sufficient permissions” section.

The hard disk or partition does not have sufficient room
To check the space on the disk or partition

  1. If you do not know the location of the folder, see the “To find the location of the log file folder” procedure. By default, the location is “Program Files\Common Files\Microsoft Shared\web extensions\12\LOGS” but the location can be changed in Central Administration.

  2. Navigate to the disk or partition, right-click it, and then click Properties.

  3. On the General tab, check the free space. The drive or partition should have at least 500 MB for the log files. Note: the space required for the log files depends upon the diagnostic logging settings. To see these settings, use the “To find the location of the log file folder” procedure.

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 account that Windows SharePoint Services 3.0 is using does not have sufficient rights to the trace log

Assign sufficient permissions to the trace log

The hard disk or partition does not have enough room

Free up disk space or relocate the trace log

Assign sufficient permissions to the trace log

Windows SharePoint Services 3.0 could not write to the trace log because the account that Windows SharePoint Services 3.0 is using does not have sufficient permissions to the trace log or its parent directory. This trace log contains information that is useful in troubleshooting issues.

Ensure that the WSS_ADMIN_WPG Windows group has Full Control and the WSS_WPG Windows group has Read & Execute, List Folder Contents, and Read permissions or higher on the folder containing the trace log. To perform this procedure, you must be a member of the Administrators group on the local computer.

Free up disk space or relocate the trace log

Windows SharePoint Services 3.0 could not write to the trace log. This trace log contains information that is useful in troubleshooting issues.

You can free up space on the drive containing the trace log by removing unneeded files. To perform this procedure, you must be a member of the Administrators group on the local computer.

You can change the location of the trace log to a partition that has more drive space.

To change the location of the trace log file

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

  2. On the Operations page, in the Logging and Reporting section, click Diagnostic logging.

  3. On the Diagnostic Logging page, in the Trace Log section, type the new location for the trace log file in the Path box.

  4. Click OK.

Verify

Ensure that Windows SharePoint Services 3.0 can create, and write to, the trace log file.

To check if Windows SharePoint Services 3.0 can create, and write to, the trace log file

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

  2. On the Operations page, in the Logging and Reporting section, click Diagnostic logging.

  3. On the Diagnostic Logging page, in the Trace Log section, copy the path to the trace log file from the Path box.

  4. In Windows Explorer, navigate to the trace log file by using the copied path and open the file in Notepad, or another text editor.

    You should see log entries in the log file for events after the time that logging failed.

Related Management Information

Diagnostic system (Health model)

Windows SharePoint Services 3.0 health model

Related:

Event ID 2100 (Windows SharePoint Services health model)

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

Applies To: Windows SharePoint Services 3.0

 

Topic Last Modified: 2008-04-27

The Windows SharePoint Services Tracing (SPTrace) service is used by Windows SharePoint Services 3.0 to manage trace output of the call stack. When trace logging is enabled, administrators can specify the path used to store the trace logs. This log file is reused by many applications that are built on top of Windows SharePoint Services 3.0.

Event Details  

Product:

Windows SharePoint Services

ID:

2100

Source:

Windows SharePoint Services 3

Version:

12.0

Symbolic Name:

ULSEvtTag_2100

Message:

Unable to start service to Trace Log: 0x%1

Diagnose

Windows SharePoint Services 3.0 could not create, or write to, the trace log. This trace log contains information that is useful in troubleshooting issues.

This error might be caused by one of the following conditions:

  • The account that Windows SharePoint Services 3.0 is using does not have sufficient rights to the trace log.

  • The hard disk or partition does not have enough room.

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.

The account that Windows SharePoint Services 3.0 is using does not have sufficient rights to the trace log
To check the permissions assigned to the log file folder

  1. If you do not know the location of the folder, see the “To find the location of the log file folder” procedure. By default, the location is “Program Files\Common Files\Microsoft Shared\web extensions\12\LOGS” but the location can be changed in Central Administration.

  2. Navigate to the folder, right-click the folder, and then click Properties.

  3. On the Security tab, the WSS_ADMIN_WPG Windows group should have Full Control and the WSS_WPG Windows group should have Read & Execute, List Folder Contents, and Read permissions or higher on the folder. If they do not, assign these permissions by using the procedure in the “Assign sufficient permissions” section.

The hard disk or partition does not have sufficient room
To check the space on the disk or partition

  1. If you do not know the location of the folder, see the “To find the location of the log file folder” procedure. By default, the location is “Program Files\Common Files\Microsoft Shared\web extensions\12\LOGS” but the location can be changed in Central Administration.

  2. Navigate to the disk or partition, right-click it, and then click Properties.

  3. On the General tab, check the free space. The drive or partition should have at least 500 MB for the log files. Note: the space required for the log files depends upon the diagnostic logging settings. To see these settings, use the “To find the location of the log file folder” procedure.

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 account that Windows SharePoint Services 3.0 is using does not have sufficient rights to the trace log

Assign sufficient permissions to the trace log

The hard disk or partition does not have enough room

Free up disk space or relocate the trace log

Assign sufficient permissions to the trace log

Windows SharePoint Services 3.0 could not write to the trace log because the account that Windows SharePoint Services 3.0 is using does not have sufficient permissions to the trace log or its parent directory. This trace log contains information that is useful in troubleshooting issues.

Ensure that the WSS_ADMIN_WPG Windows group has Full Control and the WSS_WPG Windows group has Read & Execute, List Folder Contents, and Read permissions or higher on the folder containing the trace log. To perform this procedure, you must be a member of the Administrators group on the local computer.

Free up disk space or relocate the trace log

Windows SharePoint Services 3.0 could not write to the trace log. This trace log contains information that is useful in troubleshooting issues.

You can free up space on the drive containing the trace log by removing unneeded files. To perform this procedure, you must be a member of the Administrators group on the local computer.

You can change the location of the trace log to a partition that has more drive space.

To change the location of the trace log file

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

  2. On the Operations page, in the Logging and Reporting section, click Diagnostic logging.

  3. On the Diagnostic Logging page, in the Trace Log section, type the new location for the trace log file in the Path box.

  4. Click OK.

Verify

Ensure that Windows SharePoint Services 3.0 can create, and write to, the trace log file.

To check if Windows SharePoint Services 3.0 can create, and write to, the trace log file

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

  2. On the Operations page, in the Logging and Reporting section, click Diagnostic logging.

  3. On the Diagnostic Logging page, in the Trace Log section, copy the path to the trace log file from the Path box.

  4. In Windows Explorer, navigate to the trace log file by using the copied path and open the file in Notepad, or another text editor.

    You should see log entries in the log file for events after the time that logging failed.

Related Management Information

Diagnostic system (Health model)

Windows SharePoint Services 3.0 health model

Related:

Event ID 6857 (Windows SharePoint Services health model)

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

Applies To: Windows SharePoint Services 3.0

 

Topic Last Modified: 2008-09-17

Microsoft Windows SharePoint Services 3.0 sends alerts and other administration messages by using an SMTP mail server. You can specify which SMTP server to use, and you can set the e-mail address to use for sending alerts and receiving replies for all sites, by using the Outgoing E-Mail Settings page in Central Administration.

Event Details  

Product:

Windows SharePoint Services

ID:

6857

Source:

Windows SharePoint Services 3

Version:

12.0

Symbolic Name:

ULSEvtTag_6857

Message:

Cannot connect to SMTP host %1.

Diagnose

Windows SharePoint Services 3.0 could not send an SMTP e-mail message. This error might be caused by one of the following conditions:

  • The SMTP host is not running

  • The SMTP service is not running on the SMTP server

  • The SMPT host is not correctly configured in Central Administration

To perform this procedure, you must be a member of the Administrators group on the local computer:

To confirm that the SMTP server is running and configured correctly

  1. In Internet Information Services Manager, connect to the SMTP server.

  2. Expand the server node and look for the SMTP virtual server. There might be more than one virtual server.

  3. The service should be running.

  4. To check the configuration, open the service’s properties.

  5. On the Delivery tab, click Outbound Security.

  6. In the Outbound Security dialog box, either the Anonymous access or Integrated Windows Authentication option must be selected. If the Integrated Windows Authentication check box is selected, ensure that the Windows SharePoint Services Central Administration application pool account has access by checking the Account and Password boxes.

To perform this procedure, you must be a member of the Administrators group on the local computer:

To confirm that the SMTP service on the local computer is running

  1. In the Services MMC snap-in, look for the Simple Mail Transfer Protocol (SMTP) service.

  2. The service should be started.

  3. To fix this, see the section titled Start and configure the SMTP service.

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

To confirm the SMTP host settings in Central Administration

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

  2. On the Operations page, in the Topology and Services section, click Outgoing e-mail settings.

  3. The SMTP server should appear in the Outgoing SMTP server box on the Outgoing E-Mail Settings page, under Mail Settings.

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

Windows SharePoint Services 3.0 cannot connect to the SMTP host

Start and configure the SMTP service

Windows SharePoint Services 3.0 cannot resolve name of the outbound SMTP server

Configure outbound e-mail settings in Central Administration

Start and configure the SMTP service

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

To start and configure the SMTP virtual server

  1. In Internet Information Services Manager, connect to the SMTP server.

  2. Expand the server node and look for the SMTP virtual server used by Windows SharePoint Services 3.0.

  3. Right-click the correct virtual server and click Start.

  4. To configure the virtual server, open the virtual server’s properties.

  5. On the Delivery tab, click Outbound Security.

  6. In the Outbound Security dialog box, either the Anonymous access or Integrated Windows Authentication option must be selected. If the Integrated Windows Authentication check box is selected, ensure that the Windows SharePoint Services Central Administration application pool account has access by checking the Account and Password boxes.

Configure outbound e-mail settings in Central Administration

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

To configure outgoing e-mail settings in Central Administration

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

  2. On the Operations page, in the Topology and Services section, click Outgoing e-mail settings.

  3. On the Outgoing E-Mail Settings page, under Mail Settings, type the correct SMTP server in the Outgoing SMTP server box.

Verify

Create a new instant alert and ensure that an e-mail message is sent properly.

To create an immediate alert e-mail message

  1. Navigate to a site that has a list of any type.

  2. Open an item on the list.

  3. Click Alert Me.

  4. On the New Alert page, in the Send Alerts To section, type your account name in the Users box.

  5. After verifying other settings, click OK.

    This should send an e-mail message to your e-mail Inbox informing you that you have created a new alert.

Related Management Information

E-mail (Health model)

Windows SharePoint Services 3.0 health model

Related:

Event ID 5061 (Windows SharePoint Services health model)

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

Applies To: Windows SharePoint Services 3.0

 

Topic Last Modified: 2008-04-27

Information Rights Management (IRM) allows content creators to assign rights to documents that they send to others. These documents are referred to as “rights-protected” documents. The data in rights-protected documents is encrypted so that it can be viewed only by authorized users. Furthermore, a rights-protected document stores an issuance license that specifies which rights users have to the content. For example, an author can specify the following rights for a document:

  • Document is read-only.

  • Text in the document cannot be copied.

  • Document cannot be printed.

IRM relies on Windows Rights Management Services (RMS) to create the issuance license, and perform the encryption and decryption of rights-protected documents. When IRM is enabled on a list or library, Windows SharePoint Services 3.0 automatically adds the permissions that are assigned to an item to the issuance license of that item when that item is downloaded. This means that permissions that are set on documents in lists and libraries are enforced by IRM even after a document is downloaded from the site.

For more information about IRM and Windows SharePoint Services 3.0, see Deploying Active Directory Rights Management Services with Microsoft Office SharePoint Server 2007 Step-By-Step Guide (http://go.microsoft.com/fwlink/?LinkId=93136).

Event Details  

Product:

Windows SharePoint Services

ID:

5061

Source:

Windows SharePoint Services 3

Version:

12.0

Symbolic Name:

ULSEvtTag_5061

Message:

Information Rights Management (IRM): There was a problem while trying to activate a rights account certificate.

Memory could not be allocated.

Additional Data

Error value: %1

Server URL: %2

Resolve Delete stored licenses

The stored licenses might be corrupt. You must delete the current licenses. They will be automatically re-created. You must be a member of the SharePoint Administrators group to stop and start the Windows SharePoint Services 3.0 Web application. You must have write access to the license directories to delete these directories.

Note:
Restarting IIS will render all the Web content on that server unavailable to users while it is starting up. You might want to restart IIS during a regularly-scheduled service time.

To perform steps 1 and 4, you must be a member of the Administrators group on the local computer. To perform step 3, you must have Write permissions to the directory.

To delete stored licenses

  1. Stop the Windows SharePoint Services 3.0 Web application by running the following command at the command prompt.

    iisreset /stop

  2. On the Windows SharePoint Services 3.0 front-end Web server, navigate to the %allusersprofile%\Application Data\Microsoft\DRM\Server\ folder

  3. Delete all folders named after the Windows SharePoint Services 3.0 application pool identity account. The application pool identity is the user account that Windows SharePoint Services 3.0 is running under.

  4. Restart the Windows SharePoint Services 3.0 process by running the following command at the command prompt.

    iisreset /start

Verify

To verify that this problem is resolved, users should download and then re-upload a file from a rights-managed document library. If successful, then the problem is resolved.

To activate Information Rights Management on a document library, navigate to that library’s Document Library Settings page. Click Information Rights Management and select Restrict permission to documents in this library on download.

You must be a site administrator to perform this task.

Related Management Information

Information Rights Management (Health model)

Windows SharePoint Services 3.0 health model

Related:

Event ID 6398 (Windows SharePoint Services health model)

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

Updated: March 31, 2009

Applies To: Windows SharePoint Services 3.0

 

Topic Last Modified: 2009-03-31

Several features of Microsoft Windows SharePoint Services 3.0 rely on scheduled background processes called timer jobs. Administrators can configure, schedule, and view the status of timer jobs by using Central Administration.

Event Details  

Product:

Windows SharePoint Services

ID:

6398

Source:

Windows SharePoint Services 3

Version:

12.0

Symbolic Name:

ULSEvtTag_6398

Message:

The Execute method of job definition %1 (ID %2) threw an exception. More information is included below.

%3

Diagnose

One of two problems occurred. Either a timer job raised an exception or a timer job definition could not be loaded. Determine which assembly was faulty. Determine whether it was a Windows SharePoint Services 3.0 assembly, and then determine its status.

To determine the correct resolution

  • If the assembly cannot be found, or if it is corrupt, and it is not a Windows SharePoint Services 3.0 assembly, and the timer definition is a recurring job, then in this case do not use the feature that includes the timer job and consider removing the feature.

  • If the timer job is not listed on the Timer Job Definitions page, and is not a Windows SharePoint Services 3.0 assembly, then it is not a recurring timer job. In this case, do not use the feature that includes the timer job and consider removing the feature.

  • If the assembly cannot be found, or if it is corrupt, and it is a Windows SharePoint Services 3.0 assembly, then you must repair the Windows SharePoint Services 3.0 installation to restore or repair the assembly.

To determine which event receiver raised the exception and if it was a Windows SharePoint Services assembly

  1. In Computer Management, view the Application log.

  2. Look for event 6398 that has source of “Windows SharePoint Services 3”.

  3. The event will provide the assembly name.

  4. In Windows Explorer, on the Windows partition, in the WINDOWS\assemblyfolder, look for the assembly name in the list. If the assembly name begins with “Microsoft.Sharepoint.” then the assembly is a Windows SharePoint Services 3.0 assembly. If it does not, it might be a vendor-supplied assembly. Go to step 5 to determine the supplier of the assembly.

  5. Right-click the assembly and click Properties.

  6. In the Properties dialog box, on the Version tab, click Company Name in the Items name list. The Value box will display the name of the company that created the assembly.

    Note:
    The supplier might not have filled in this information.

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

To determine the status of the timer job definition in Central Administration

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

  2. On the Operations page, in the Global Configuration section, click Timer job definition.

  3. Look for the timer job in the list. If the definition is not on this list, it is a not a recurring timer job.

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 third party timer job cannot be found, or it is corrupt

Configure faulty timer job

The Windows SharePoint Services 3.0 timer job cannot be found, or it is corrupt.

Repair Windows SharePoint Services installation

Configure faulty timer job

If the faulty assembly cannot be found, or it is corrupt, and it is not a Windows SharePoint Services 3.0 assembly, and the timer definition is a recurring job, then you must disable the faulty time job.

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

To disable the faulty timer job

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

  2. On the Operations page, in the Global Configuration section, click Timer job definition.

  3. Look for the timer job in the list. Click the timer definition name.

  4. In the Edit Timer Job page, click Disable.

    Note:

    Disabled timer jobs will display “Disabled” under Schedule Type.

To enable a timer job

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

  2. On the Operations page, in the Global Configuration section, click Timer job definition.

  3. Look for the timer job in the list. Click the timer definition name.

  4. In the Edit Timer Job page, click Enable.

    Note:

    Disabled timer jobs will display “Disabled” under Schedule Type.

Repair Windows SharePoint Services installation

If the faulty assembly cannot be found, or it is corrupt, and it is a Windows SharePoint Services 3.0 assembly, then you must repair the Windows SharePoint Services 3.0 installation to restore or repair the assembly.

Note:
Repairing the installation will require you to restart the server. Web application modifications and other settings changes will be preserved.

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

To repair the Windows SharePoint Services 3.0 installation

  1. Open Add or Remove Programs.

  2. Select Microsoft Windows SharePoint Services 3.0 from the list and click Change.

  3. In the Microsoft Windows SharePoint Services 3.0 wizard, select the Repair option and click Continue.

Verify

If the timer job was a recurring job, go to the Timer Job Definition page, and Enable the timer job. The job should run at the next normally scheduled interval.

If the timer job was a one-time job, retry the command that triggered the timer job.

Related Management Information

Timer jobs (Health model)

Windows SharePoint Services 3.0 health model

Related:

Event ID 5112 (Windows SharePoint Services health model)

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

Applies To: Windows SharePoint Services 3.0

 

Topic Last Modified: 2008-04-27

Information Rights Management (IRM) allows content creators to assign rights to documents that they send to others. These documents are referred to as “rights-protected” documents. The data in rights-protected documents is encrypted so that it can be viewed only by authorized users. Furthermore, a rights-protected document stores an issuance license that specifies which rights users have to the content. For example, an author can specify the following rights for a document:

  • Document is read-only.

  • Text in the document cannot be copied.

  • Document cannot be printed.

IRM relies on Windows Rights Management Services (RMS) to create the issuance license, and perform the encryption and decryption of rights-protected documents. When IRM is enabled on a list or library, Windows SharePoint Services 3.0 automatically adds the permissions that are assigned to an item to the issuance license of that item when that item is downloaded. This means that permissions that are set on documents in lists and libraries are enforced by IRM even after a document is downloaded from the site.

For more information about IRM and Windows SharePoint Services 3.0, see Deploying Active Directory Rights Management Services with Microsoft Office SharePoint Server 2007 Step-By-Step Guide (http://go.microsoft.com/fwlink/?LinkId=93136).

Event Details  

Product:

Windows SharePoint Services

ID:

5112

Source:

Windows SharePoint Services 3

Version:

12.0

Symbolic Name:

ULSEvtTag_5112

Message:

Information Rights Management (IRM): The callback had a problem when contacting the Rights Management Services (RMS) server to acquire the server End User License (EUL).

Possibly an HTTP 401 error (an authentication error) was returned by an Internet request.

Current file: %1

GUID of current list: %2

Additional Data

Error value: %3

Resolve Configure RMS server to accept requests

An RMS server refused access to a computer running Windows SharePoint Services 3.0. This alert indicates that a front-end Web server contacted the RMS server but the RMS server denied access to the Web server. Generally, this error occurs when an administrator is first enabling IRM for the Web farm in Central Administration. If this is the case, IRM cannot be enabled in Central Administration, and list administrators will not be able to enable IRM on a document library or list until the error is resolved. If this error occurs after IRM is enabled, downloads from a rights-protected list or library will fail until the error is resolved.

To resolve this issue, the RMS server must be configured to accept requests from the server running Windows SharePoint Services 3.0 that caused this error. The RMS server settings that are required differ depending on whether:

  • You want the RMS server to accept requests from all computers on the domain, and Windows SharePoint Services 3.0 is installed as a single server on the same domain as your RMS server.

  • You do not want the RMS server to accept requests from all servers on the domain, and Windows SharePoint Services 3.0 is installed as a single server (recommended).

  • Windows SharePoint Services 3.0 is installed in a Web farm configuration.

    Note:
    It is recommended that you configure the RMS server to inherit permissions from certification folder on ServerCertification.asmx and then add the computer account of the Windows SharePoint Services 3.0 server (for single server install) instead of opening this up to all Domain Computers.

SharePoint administrators can discover the correct FQDN, NetBIOS name or service account name to configure on the RMS server by attempting to authenticate against the RMS server:

To discover the correct service account name

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

  2. On the Operations page, in the Security Configuration section, click Information Rights Management.

  3. On the Information Rights Management page, click either Use the default RMS server specified in Active directory or Use this RMS server, and then type the URL for the RMS server you want to use.

  4. Click OK.

Use the procedure that is appropriate for your situation.

You must be an administrator on the RMS server to make these changes.

To configure the RMS server to accept requests from all servers in the domain

  1. On the RMS server, navigate to the folder containing the ServerCertification.asmx file. This file is typically located in the %systemdrive%\Inetpub\wwwroot\_wmcs\Certification folder.

  2. Add the computer account of the Windows SharePoint Services 3.0 Server to the access control list (ACL) of the ServerCertification.asmx file and assign it the Read & Execute permission.

For a single server installation, the RMS server’s Server Certification service must be configured by using either the FQDN or the NetBIOS name of the stand-alone server running Windows SharePoint Services 3.0.

Note:
You must know the FQDN or NetBIOS name of the server before performing the following steps. If you do not know this name, see the To discover the correct service account name procedure, to determine the name before continuing.

To configure the RMS server to accept requests from Windows SharePoint Services installed as a single server

  1. On the RMS server, navigate to the folder containing the ServerCertification.asmx file. This file is typically located in the %systemdrive%\Inetpub\wwwroot\_wmcs\Certification folder.

  2. Add the FQDN or NetBIOS name of the server that cannot access the RMS server to the ACL of the ServerCertification.asmx file, and assign it the Read & Execute permission.

For a Web farm installation of Windows SharePoint Services 3.0, the Server Certification service running on the RMS server must be configured with the service account used by each Web application that is IRM-enabled.

Note:
You must know the exact service account name or names before performing the following steps. If you do not know the exact service account names that you need, see the “To discover the correct service account name” procedure before continuing.

To configure the RMS server to accept requests from Windows SharePoint Services 3.0 installed in a farm

  1. On the RMS server, navigate to the folder containing the ServerCertification.asmx file. This file is typically located in the %systemdrive%\Inetpub\wwwroot\_wmcs\Certification folder.

  2. Add each service account assigned to an application pool for the Web application on the server that cannot access the RMS server to the ACL of the ServerCertification.asmx file, and assign it the Read & Execute permission.

Note:
If the server farm uses multiple application pools, each application pool’s service account must be added to the RMS server ServerCertification.asmx file.

If the front-end Web server has not been configured on the RMS server, an error message appears that states that the computer running Windows SharePoint Services 3.0 could not authenticate against the RMS server. In this error message, the FQDN or NetBIOS name of the server or the service account that you must register with the RMS server will appear.

Note:
if you are using multiple application pools that use different service accounts, only the service account for the SharePoint Central Administration site will appear.

Verify

To verify that this problem is resolved, users should download and then re-upload a file from a rights-managed document library. If successful, then the problem is resolved.

To activate Information Rights Management on a document library, navigate to that library’s Document Library Settings page. Click Information Rights Management and select Restrict permission to documents in this library on download.

You must be a site administrator to perform this task.

Related Management Information

Information Rights Management (Health model)

Windows SharePoint Services 3.0 health model

Related:

Event ID 3351 (Windows SharePoint Services health model)

Event ID 3351 (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:

3351

Source:

Windows SharePoint Services 3

Version:

12.0

Symbolic Name:

ULSEvtTag_3351

Message:

SQL database login failed. 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 5586 (Windows SharePoint Services health model)

Event ID 5586 (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:

5586

Source:

Windows SharePoint Services 3

Version:

12.0

Symbolic Name:

ULSEvtTag_5586

Message:

Unknown SQL Exception %1 occurred. Additional error information from SQL Server is included below.

%2

Diagnose

An unhandled SQL Server exception occurred. Additional error information from SQL Server is included in the text of event 5586.

This error might be caused by one of the following conditions:

  • The account that Windows SharePoint Services 3.0 is using to access the database does not have sufficient permissions.

  • The wrong SQL Server collation is being used.

  • The wrong version of SQL Server is installed.

  • The database is set to Read-Only.

  • The database has run out of room.

  • The database has been corrupted.

To check if 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 it is not there, add the account by using the procedure in the Grant correct permissions to the database access account section.

To verify and change the database collation

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

  2. In SQL Server Management Studio, open the Databases node. You should look for the specific database that was indicated in event 4972 or 5586.

  3. In the database Properties, on the General page, the collation is listed in the Maintenance section.

  4. To change the collation, open the Options page.

  5. Select the correct collation from the Collation drop-down list. The collation should read “Latin1_General_CI_AS_KS_WS”. If it is not, you can change the collation by using the procedure in the “Select the correct SQL Server collation” section.

To verify and change the SQL Server version

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

  2. In SQL Server Management Studio, on the Help menu, click About.

  3. In the About Microsoft SQL Server Management Studio dialog box, under Component Name, look for Microsoft Database Access Components (MDAC). The version should be 2.8.1022.0 or later. SQL Server 2005 will have 2000.086.3959. This version is sufficient. If the version is not correct use the procedure in the “Update the MDAC Version section or the Install correct SQL Server version” section.

To verify and change the database collation

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

  2. In SQL Server Management Studio, open the Databases node. You should look for the specific database that was indicated in event 4972 or 5586.

  3. In the database Properties, on the Options page, under State, the Database Read-Only option should be “False”. If it is not set correctly, use the procedure in the “Change database to Read / Write” section.

To check if Autogrowth is enabled (Autogrowth will prevent the database from running out of room)

  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, the text should include “unrestricted growth”. If it does not, you enable unrestricted database growth by using the procedure in the “Increase the size of the SQL Server database” section.

If none of these is the problem, then the database might be corrupted. If this is the case, then restore the database using the procedure in the Restore database from backup section.

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

Insufficient SQL Server database permissions

Grant correct permissions to the database access account

SQL Server database is full

Increase the size of the SQL Server database

SQL Server database is full

Distribute Web applications across more databases

Incorrect MDAC version

Update the MDAC Version

SQL Server database not found

Restore database from backup

Incorrect version of SQL Server

Install correct SQL Server version

The SQL Server collation is not supported

Select the correct SQL Server collation

Database is Read-Only

Change database to Read / Write

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.

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.

Distribute Web applications across more databases

Windows SharePoint Services 3.0 cannot write to a database if the database has run out of room. One solution is to distribute the site content across multiple databases. You can do this by adding additional content databases to the Web application. For more information, see Plan for performance and capacity (http://technet2.microsoft.com/windowsserver/WSS/en/library/7bb49963-a511-40aa-b607-7eb244ec1d521033.mspx).

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

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.

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.

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.

Select the correct SQL Server collation

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

To verify and change the database collation

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

  2. In SQL Server Management Studio, open the Databases node. You should look for the specific database that was indicated in event 4972.

  3. In the database Properties, on the General page, the collation is listed in the Maintenance section.

  4. To change the collation, open the Options page.

  5. Select the correct collation from the Collation drop-down list.

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: