The %1 service terminated with service-specific error %2.

Details
Product: Windows Operating System
Event ID: 7024
Source: Service Control Manager
Version: 5.2
Symbolic Name: EVENT_SERVICE_EXIT_FAILED_SPECIFIC
Message: The %1 service terminated with service-specific error %2.
   
Explanation

The specified service stopped unexpectedly with the error indicated in the message. Windows does not recognize the service’s error code.

   
User Action

To display the service-specific error code in the Service_Exit_Code field, at the command line, type
sc query
service nameThe information displayed might help you troubleshoot why the error occurred.

Related:

DCOM got error “%%%1” attempting to start the service %2 with arguments “%3” in order to run the server:%4

Details
Product: Windows Operating System
Event ID: 10005
Source: DCOM
Version: 5.2
Symbolic Name: EVENT_RPCSS_START_SERVICE_FAILURE
Message: DCOM got error “%%%1” attempting to start the service %2 with arguments “%3”
in order to run the server:%4
   
Explanation

The Component Object Model (COM) infrastructure could not start the named Windows NT service.

   
User Action

Review the Windows error code displayed in the message. If the error indicates that the system is out of memory, save your work, close other programs, and then try to start the service again. Alternatively, increase the amount of RAM installed on the computer.

If the message displays a system, server, or configuration error, contact your service support vendor.

To determine the service vendor

  1. Using Regedit, navigate to the following registry value
    HKLM\System\CurrentControlSet\Services\Service Name
    The service name is the information displayed in the message.
  2. In the right pane, double-click ImagePath.The Edit String dialog box is displayed. Leave this dialog box open. If Svchost.exe is displayed in the Value data box, then under the service name, navigate to the Parameters folder and then double-click ServiceDll.
  3. Click Start, and then click My Computer.
  4. Using the information displayed in the Value data box of the Edit String dialog box, navigate to the program.
  5. Right-click the program name, and then click Properties.
    The Properties dialog box for the program is displayed.
  6. To determine who the vendor is for this service, refer to the Version tab.You can also find the path to the executable file in this tool.

Related:

%1: %2 failure on backup device ‘%3’. Operating system error %4.

Details
Product: SQL Server
Event ID: 18210
Source: MSSQLServer
Version: 8.0
Component: SQL Engine
Message: %1: %2 failure on backup device ‘%3’. Operating system error %4.
   
Explanation
This message indicates that an I/O error was reported by the operating system after a file handle was successfully opened. The error occurs when reading from or writing to a device specified as part of a BACKUP or RESTORE command, often when there is not enough disk space available for a write operation. This error may also be seen if third-party software that uses a virtual device to perform SQL Server backups cancels the operation.
   
User Action
The steps to take will depend upon the operating system error received.

  • Verify that the specified path has sufficient disk space for the file.
  • Test to see if the problem is isolated to this particular server, path, or file.
  • Run hardware diagnostics to verify that the media specified in the path is healthy.
  • If the operating system error only returns a number and not any text, you can open a command prompt and execute NET HELPMSG with the operating system error number as the parameter. In many cases, this will return text that can help you to isolate the problem.
  • If you received this error while using third-party backup software, check that application’s logs to see if it canceled the backup operation, and if so, why.

Related:

%1 (%2) %3An attempt to read from the file “%4” at offset %5 for %6 bytes failed after %10 seconds with system error %8: “%9”. The read operation will fail with error %7. If this error persists then the file may be damaged and may need to be restored from a previous backup.

Details
Product: Exchange
Event ID: 481
Source: ESE
Version: 8.0
Symbolic Name: OSFILE_READ_ERROR_ID
Message: %1 (%2) %3An attempt to read from the file “%4” at offset %5 for %6 bytes failed after %10 seconds with system error %8: “%9”. The read operation will fail with error %7. If this error persists then the file may be damaged and may need to be restored from a previous backup.
   
Explanation

This Warning event indicates that an unexpected error occurred while reading the file specified in the message. ESE Event ID 481 refers to a failed read attempt from the database. For comparison, ESE Event ID 482 refers to a failed write operation to a log file or a database.

The cause depends on the error number in the Description section of the event. The most common error codes for event 481 are as follows:

  • Error -1022 = 0xfffffc02 = 4294966274 = Jet_errDiskIO = Disk I/O error. The -1022 error is a generic error that appears whenever a disk I/O problem prevents Exchange from gaining access to a requested page in the database or to a check file. A disk or controller failure may have occurred, and access to the entire drive has been lost, sometimes temporarily. Check the System log for I/O or drive errors near the time of the 490 event. This issue may occur because the path for the check file (such as E00.chk) is not correct, which may be caused by a drive failure.

  • Error -1811 = 0xfffff8ed = Jet_errFileNotFound = File not found. The database may be missing or there may be other causes for this error. Another reason for error -1811 could be that the Exchange database and log files may have been put on network storage, which is not supported. Also, the checkpoint file may be corrupt, or the log drive itself may have failed. Exchange will disconnect from the storage group due to an inability to locate the database files. Typically, this is due to a hardware problem.

  • Error -1011 = 0xfffffc0d = Jet_errOutOfMemory = Out of Memory. This error indicates that there is no more available memory and the read operation has failed. Other ESE events with out-of-memory errors in the Description section for reading the header of a database, recovery/restore, and starting a storage group are often seen in the application event log at the same time. Review these events for further information.

  • Error -1003 = 0xfffffc15 = Jet_errInvalidParameter = Incorrect API parameter. This error generally means that the file size of the database is not a multiple of 4,096 bytes.

   
User Action

To resolve this warning, do one or more of the following:

  • Review the disk and file that you are trying to read. Check the integrity of the file system. Check the memory usage. Check the system portion of the event log for related entries. Review and change the access permissions properties and then note the disk space available. Check the file size of the database in bytes.

  • For error -1022, check to ensure that the drive for the Exchange store files is accessible and that the path for the Exchange store files is specified correctly. If it is, run chkdsk /f /r. If chkdsk does not resolve the issue, examine the permissions on the C:\Program Files\Microsoft\Exchange Server folder, where C:\ is the directory to which you installed Exchange 2007. Ensure that System has full control of the Exchange Server folder and all subfolders on each partition that contain Exchange data. If you still cannot mount the databases, troubleshoot any Windows NT file-level antivirus software running on the Exchange server. Check the System log for I/O or drive errors near the time of the 413 event.

  • For error -1811, ensure that the antivirus software is not running against the Exchange store, the SRS database directories. Make sure that you have properly configured your antivirus software. For more information, see the Microsoft Knowledge Base article 328841, Exchange and Antivirus Software.

  • Ensure that the database drive has not run out of space. Ensure that the database file is where it is supposed to be.

  • For error -1011, check the memory usage of the server. Check the settings for the page file. Check for memory-related events in the application event log and in the System log and check the Microsoft Knowledge Base for troubleshooting of the events found. For error -1003, check the size of the database in bytes. It must be a multiple of 4,096 bytes, or 1 page. If it is not, contact Microsoft Product Support Services.

  • For information about ESE error codes other than the ones explained in this topic, see the following Microsoft Knowledge Base articles:

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:

Unable to start a DCOM Server: %3. The error:”%%%2″Happened while starting this command:%1

Details
Product: Windows Operating System
Event ID: 10000
Source: DCOM
Version: 5.2
Symbolic Name: EVENT_RPCSS_CREATEPROCESS_FAILURE
Message: Unable to start a DCOM Server: %3.
The error:”%%%2″Happened while starting this command:%1
   
Explanation

The Component Object Model (COM) infrastructure could not activate the requested server. Possible causes include:

  • There is not enough memory available
  • An error occurred with another file that the COM infrastructure depends on.
       
    User Action

    Review the Windows error code displayed in the message. If the error indicates that the system is out of memory, save your work, close other programs, and then try to start the service again. Alternatively, increase the amount of RAM installed on the computer.

    If the message displays a system, server, or configuration error, contact your service support vendor.

    To determine the service vendor

    1. Click Start, and then click My Computer.
    2. Using the executable file name displayed in the message after ‘command:,’ navigate to the program.
    3. Right-click the program name, and then click Properties.
      The Properties dialog box for the program is displayed.
    4. To determine who the vendor is for this service, refer to the Version tab.You can also find the path to the executable file in this tool.

    Related:

    Faulting application %1, version %2, faulting module %3, version %4, fault address 0x%5.

    Details
    Product: Windows Operating System
    Event ID: 1000
    Source: Application Error
    Version: 5.2
    Symbolic Name: ER_USERCRASH_LOG
    Message: Faulting application %1, version %2, faulting module %3, version %4, fault address 0x%5.
       
    Explanation

    The indicated program stopped unexpectedly. The message contains details on which program and module stopped. A matching event with Event ID 1001 might also appear in the event log. This matching event displays information about the specific error that occurred.

       
    User Action

    If an error report was generated for this error, you might be able to obtain more information about the error by sending the report to Microsoft for analysis.

    What to expect

    Microsoft actively analyzes all error reports and prioritizes them based on the number of customers affected by the error signature contained in the report. When a report is submitted, Microsoft will try to determine the cause of the error, categorize it according to the type of issue encountered, and send you relevant information when such information is available. However, because error reports do not always contain enough information to positively identify the source of the issue, Microsoft may need to collect a number of similar reports from other customers before a pattern is discovered. Although Microsoft might not be able to provide a solution for your particular error at this time, all information submitted is used to further improve the quality and reliability of our products.

    Related:

    DCOM got error “%%%1” from the computer %2 when attempting to activate the server:%3

    Details
    Product: Windows Operating System
    Event ID: 10006
    Source: DCOM
    Version: 5.0
    Component: System Event Log
    Symbolic Name: EVENT_RPCSS_REMOTE_SIDE_ERROR
    Message: DCOM got error “%%%1” from the computer %2 when attempting to activate the server:%3
       
    Explanation

    A program on this computer could not access a program on the remote computer.

       
    User Action

    Do one or all of the following:

    • Review the Windows error code displayed in the message.
    • Review the remote computer’s Event Viewer for any related events indicating that a program could not be started or that an access denied error occurred.
    • If this event log indicates an out-of-memory error, tell the user to save his work, close other programs, and then try to access the server again. Or, add more system RAM.
    • If the event log indicates an access-denied error, change the DCOM permissions.

    To change permissions

    1. Using Regedit, navigate to the following registry valueHKCR\Clsid\clsid value\localserver32The clsid value is the information displayed in the message.
    2. In the right pane, double-click Default.The Edit String dialog box is displayed. Leave this dialog box open.
    3. Click Start, and then click Control Panel.
    4. Double-click Administrative Tools and then double-click Component Services.
    5. In the Component Services snap-in, navigate to Computers\My Computer\DCOM Config.
    6. In the right pane, locate the program by using its friendly name.
    7. Right- click the program name and then select Properties.
    8. On the Security tab, select Customize, and then click Edit.
    9. Add the user to the permissions list.

    If these steps don’t solve the problem, contact your technical support provider.

    Related:

    The %1 service failed to start due to the following error: %2.

    Details
    Product: Windows Operating System
    Event ID: 7000
    Source: Service Control Manager
    Version: 5.0
    Symbolic Name: EVENT_SERVICE_START_FAILED
    Message: The %1 service failed to start due to the following error: %2.
       
    Explanation

    Service Control Manager (SCM) could not start the specified service, probably because the service is not configured correctly.

       
    User Action

    Do one or all of the following:

    • Review the error information displayed in the message.
    • Verify that the service password has not expired.
    • Verify that the service is in the correct location.
    • Verify that the service is not infected with a virus.
    • To display the WIN32_EXIT_CODE error that SCM encountered when trying to start the program, at the command prompt, type
      sc query service nameThe information displayed can help you troubleshoot possible causes for the error.

    If the WIN32_EXIT_CODE is zero, then SCM did not attempt to start the service because the error was detected first.

    Related:

    Find cross-site scripting errors in your Bluemix application with AppScan Dynamic Analyzer

    In this short demo video, Ori Pomerantz shows a Bluemix
    application that has a cross-site scripting error in it. Then he
    shows how to add the AppScan Dynamic Analyzer service to the
    application and run a scan. He shows that the scan report
    detects the cross-site scripting error and provides guidance on
    how to fix it.

    Related: