Posted on May 15th, 2008 by thehabgroup
Here are a few event ids related to the Windows Task Scheduler:
Error 2147750678:
Could not start the Task Scheduler service on local computer. The service has returned a service-specific error code.
OR
Error 6200:
Could not start the Task Scheduler service on Local Computer. The Task Scheduler must be configured to run in the System to function properly. Individual tasks may be configured to run in other accounts.
SOLUTION:
To resolve this behavior change the Log On parameters from a User Account to the Local System Account.
Event ID: 7901
Source: Schedule
Category: Error
Description: The <job filename> command failed to start due to the following error: General access denied error.
SOLUTION:
Task Scheduler may create corrupted job files.
Delete all existing Task Scheduler and AT Scheduler jobs. Create one new job and check for corruption.
event id Task Scheduler task scheduler serviceevent id Task Scheduler task scheduler service
No Comments »
Filed under: Task Scheduler
Posted on September 4th, 2007 by thehabgroup
The following are system events that are symptoms of I/O hanging or blocking between a host
and storage device(s):
Event ID: 3
Source: LDM
Description: [computername] A Dynamic Volume
(\Device\HarddiskDmVolumes\(diskgroup)\Volume(n)) has failed.
Event ID: 9
Source: [scsi miniport driver]
Description: The device, \Device\ScsiPort1, did not respond within the
timeout period.
Event ID: 15
Source: [scsi miniport driver]
Description: The device, \Device\ScsiPort1, is not ready for access yet.
Event ID: 26
Source: Application Popup
Description: Application popup: Windows - Delayed Write Failed : Windows
was unable to save all the data for the file
\Device\HarddiskDmVolumes\PhysicalDmVolumes\BlockVolume{n}\… The data
has been lost.
Event ID: 50
Event Source: Disk
Description: {Lost Delayed-Write Data} The system was attempting to
transfer file data from buffers to \Device\Harddisk\Volume{n}. The write
operation failed, and only some of the data may have been written to the
file.
Event ID: 51
Event Source: Disk
Description: An error was detected on device \Device\Harddisk{n}\DR{n}
during a paging operation.
Event ID: 29
Event Source: dmio
Description: dmio: Harddisk2 read error at block {n}: status 0xc000009d.
Event ID: 41
Event Source: FTDISK
Description: The file system structure on the disk is corrupt and
unusable. Please run the chkdsk utility on the device
\Device\Harddisk{n}\Ft{n} with label {label}.
The following system events are symptoms of general hardware problems either with the host
or with the storage device:
Event ID: 2
Event Source: dmboot
Description: [computername] dmboot: Failed to start volume Volume7 (no
mountpoint)
Event ID: 7
Event Source: Disk
Description: The device, \Device\Harddisk{n}\DR{n}, has a bad block
Event ID: 11
Event Source: [scsi miniport driver]
Description: The driver detected a controller error on Device\ScsiPort1
Event ID: 29
Event Source: dmio
Event Type: Information Description:
dmio: Harddisk9 read error at block {########}: status 0xC000009A
Event ID: 30
Event Source: dmio
Description: dmio: Harddisk1 write error at block {########}: status
0xc000009d
Event ID: 37
Event Source: dmio
Description: dmio: Disk Harddisk1 block {########} (mountpoint D:):
Uncorrectable write error
Event ID: 55
Source: NTFS
Description: The file system structure on disk is corrupt and unusable.
Please run the chkdsk utility on the volume “Drive_letter:”
Here:
● status code 0xC000009A = STATUS_INSUFFICIENT_RESOURCES
● status code 0xC000009C = STATUS_DEVICE_DATA_ERROR
● status code 0xC000009D = STATUS_DEVICE_NOT_CONNECTED
The following event log entries are indicative of issues involving zoning or path configuration
issues:
Event ID: 1
Source: SDDMAN
Description: [computername] Device \Device\Harddisk1\DR0 path [n]
offline.
Event ID: 2
Source: SDDMAN
Description: [computername] Device \Device\Harddisk1\DR0 path [n] online.
Event ID: 31
Source: dmio
Description: [computername] dmio: Harddisk9 write error at block 6 due to
disk removal
The following event log entries indicate a change in the underlying hardware, such as a
volume expansion at the hardware level:
Event Type: Information
Event Source: dmio
Event Category: None
Event ID: 31
Description:
dmio: Harddisk0 write error at block {########} due to disk removal
Event Type: Warning
Event Source: LDM
Event Category: None
Event ID: 1000
Description:
Cannot grow LUN Harddisk{n}: Config copy write failed
Event Type: Warning
Event Source: LDM
Event Category: None
Event ID: 1000
Description:
Disk group CompernameDg{n}: Errors in some configuration copies:
Disk Harddisk0, copy 1: Block 0: Disk read failure
Event Type: Information
Event Source: dmio
Event Category: None
Event ID: 34
Description:
dmio: Harddisk0 is re-online by PnP
delayed write failed Disks event id harddisk hardware problems storage device windows delayed write faileddelayed write failed Disks event id harddisk hardware problems storage device windows delayed write failed
2 Comments »
Filed under: Disks
Posted on August 27th, 2007 by thehabgroup
If you have ever received the following error messages in your environment then these steps may help to get rid of the problem:
Event ID: 4321
Source NetBT
Type Error
Description The name “<server name>” could not be registered on the Interface with IP address <ip address 1>. The machine with the IP address <ip address 2> did not allow the name to be claimed by this machine.
- Stop and disable the computer browser service on the offending machine if you DO NOT have WINS in your environment.
- If you are in a WINS environment then add the WINS server entry in the network settings of the offending computer.
- Check if there is conflict between two machine with the same NetBios name.
- Delete the offending NETBIOS name on the WINS server
- Ensure the computer is in the correct network subnet
- Check network mask of the offending machine
computer browser service error messages Event id 4321 event id netbt error Network Uncategorizedcomputer browser service error messages Event id 4321 event id netbt error Network Uncategorized
No Comments »
Filed under: Network