Event ID 7037 (Windows SharePoint Services health model)

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

7037

Source:

Windows SharePoint Services 3

Version:

12.0

Symbolic Name:

ULSEvtTag_7037

Message:

Error creating timer job to update central administration url location at %1. %2

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, 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 7037 — Basic Service Operations

Event ID 7037 — Basic Service Operations

Updated: December 11, 2007

Applies To: Windows Server 2008

Service Control Manager transmits control requests to running services and driver services. It also maintains status information about those services, and reports configuration changes and state changes.

Event Details

Product: Windows Operating System
ID: 7037
Source: Service Control Manager
Version: 6.0
Symbolic Name: EVENT_SERVICE_CONFIG_BACKOUT_FAILED
Message: The Service Control Manager encountered an error undoing a configuration change to the %1 service. The service’s %2 is currently in an unpredictable state. If you do not correct this configuration, you may not be able to restart the %1 service or may encounter other errors. To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC).

Resolve
Restore the default settings

If there were changes in the service settings (for example, the start up type was changed from Automatic to Manual), the service may be unable to start. To resolve this issue, first restore the default settings of the service and then start the service.

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

Restore the default settings of the service

To restore the default settings of the service:

  1. Open the Services snap-in by clicking the Start button, Control Panel, and Administrative Tools, then double-clicking Services.

    Note: For Windows Vista, use the Classic View display option in Control Panel to see the Administration Tools.

  2. In the details pane of the Services snap-in, right-click on the name of the service you want to start and select Properties.
  3. Click the Log On tab and note the account listed under Log On As.
  4. Restore the default settings, if necessary. For a list of the default settings for system services, see http://go.microsoft.com/fwlink/?LinkId=105223. For non-system settings, see the documentation for that product.

Start the service

To start a service:

  1. Open the Services snap-in by clicking the Start button, Control Panel, and Administrative Tools, then double-clicking Services.

    Note: For Windows Vista, use the Classic View display option in Control Panel to see the Administration Tools.

  2. In the details pane of the Services snap-in, right-click on the name of the service you want to start and select Start.

Verify

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To verify the state in which a service is operating:

  1. Click the Start button, Run, then type cmd to open a command prompt.
  2. Type sc interrogate service_name (where service_name is the name of the service) at the command prompt to update the status of that service in Service Control Manager.
  3. Type sc qc service_name at the command prompt to display the configuration status of the service.
  4. Type sc queryex service_name at the command prompt to display the extended status of the service. This command will provide the following information about a service: SERVICE_NAME (the service’s registry subkey name), TYPE (the type of service, for example, shared process, interactive), STATE (for example, running, paused, and the states that are not available), WIN32_EXIT_CODE (the Windows exit error code), SERVICE_EXIT_CODE (the service exit code), CHECKPOINT, WAIT_HINT (the time period the SCM waits before reporting a service failure), PID (ID of the process running the service), and FLAGS. If the service was started successfully, the WIN32_EXIT_CODE field should contain a zero (0). If the service failed to start when an attempt was made, this field should contain an exit code provided by the service when it could not start.
  5. Type net helpmsg exit_code (where exit_code is the 4 digit number of the error code) at the command prompt to display the meaning of the exit code.

For more information about the sc command, see SC Command Reference Help (http://go.microsoft.com/fwlink/?LinkID=84961). For more information about the net helpmsg command, see http://go.microsoft.com/fwlink/?LinkId=105087.

Related Management Information

Basic Service Operations

Core Operating System

Related:

The Microsoft Exchange Public Folder named ‘{folder name}’ already exists. Please rename or delete this folder and migrate shared folders again.

Details
Product: Exchange
Event ID: 7037
Source: MSExchangeMig
Version: 6.0
Component: Migration Wizard
Symbolic Name: LOG_ERR_SFOLD_COLLISION
Message: The Microsoft Exchange Public Folder named ‘{folder name}’ already exists. Please rename or delete this folder and migrate shared folders again.
   
User Action
Perform the user action specified in the message.

Related:

There are no replicas for the public folder %1 in any connected sites.

Details
Product: Exchange
Event ID: 7037
Source: MSExchangeIS
Version: 8.0
Symbolic Name: msgidNoActiveReplicas
Message: There are no replicas for the public folder %1 in any connected sites.
   
Explanation

This Error event indicates that the public folder specified in the event description has no replicas in any site. This situation should not happen under normal situations; however, it may occur in migration and server recovery scenarios.

   
User Action

To resolve this error, check to see if there are any replicas of this public folder in any sites. If the public folder has no replicas, add a replica to at least one site. You can add public folder replicas using the Set-PublicFolder Exchange Management Shell cmdlet. For more information, see Set-PublicFolder.

If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.

Related: