I have searched for quite awhile but cannot find any reference to this
specific error log message. Below is the event log that I am getting.
-------
Event Type: Error
Event Source: ESENT
Event Category: Logging/Recovery
Event ID: 215
Date: 6/6/2005
Time: 7:24:23 AM
User: N/A
Computer: UNITED1
Description:
tcpsvcs (1216) The backup has been stopped because it was halted by the
client or the connection with the client failed.
-------
Windows help talks about Exchange server which I don’t have and about
Exchange aware backup software. I do have BackupExec 9 with full patches, but
do not have the Exchange plug-in. But I can backup the system just fine.
Last it says to check the Application log, which this only error comes from,
and the System log for hardware errors. The above error coincides with the 3
below DHCP server errors.
---------
Event Type: Error
Event Source: DhcpServer
Event Category: None
Event ID: 1010
Date: 6/6/2005
Time: 7:24:23 AM
User: N/A
Computer: UNITED1
Description:
The DHCP service encountered the following error while cleaning up the
database:
An error occurred while accessing the DHCP database. Look at the
DHCP server event log for more information on this error.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00004e2d
-----------
Event Type: Error
Event Source: DhcpServer
Event Category: None
Event ID: 1016
Date: 6/6/2005
Time: 7:24:23 AM
User: N/A
Computer: UNITED1
Description:
The DHCP service encountered the following error when backing up the
database:
An error occurred while accessing the DHCP database. Look at the
DHCP server event log for more information on this error.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00004e2d
----------
Event Type: Error
Event Source: DhcpServer
Event Category: None
Event ID: 1014
Date: 6/6/2005
Time: 7:24:23 AM
User: N/A
Computer: UNITED1
Description:
The following problem occurred with the Jet database -1032: Jet database
read or write operations failed. If the computer or database has just been
upgraded, then this message can be safely ignored. If this message appears
frequently, either there is not enough disk space to complete the operation
or the database or backup database may be corrupt. To correct this problem,
either free additional space on your hard disk or restore the database.
After you restore the database, ensure that conflict detection is enabled in
DHCP server properties. For information about restoring the database, see
Help and Support Center. Additional Debug Information: JetBackup.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: fffffbf8
--------------
Here are the times for the last month that I have received these messages.
6/6/2005 7:24:23 AM
6/6/2005 4:24:22 AM
6/5/2005 9:24:21 PM
6/5/2005 2:24:19 PM
6/5/2005 10:24:18 AM
6/4/2005 10:24:12 AM
6/4/2005 6:24:11 AM
6/4/2005 3:24:11 AM
6/3/2005 8:24:09 PM
6/3/2005 5:24:09 PM
6/2/2005 11:24:00 AM
6/2/2005 8:23:59 AM
6/2/2005 2:23:58 AM
6/1/2005 4:23:55 PM
6/1/2005 12:23:54 PM
6/1/2005 5:23:51 AM
As you can see there is a pattern, this really shows when compared with a
few weeks.
And I have done all applicable user actions that were listed in the help
files.
* Verify that the path of the DHCP server database is valid.
* If the database is corrupt, run the JETPACK.exe utility to repair it.
* To synchronize the database, at the command prompt, type reconcile
* Verify that other programs, such as an antivirus program, are not
accessing the database. If such a program is accessing the database, make
sure that the program does not scan the directory where the database is
stored.
* Verify that the database and its backup directories are located in the
default folder.
* Verify that the location to which the database is writing has sufficient
disk space.
* At the command prompt, run dskchk to verify that the hard disk has no bad
sectors.
* If the database is more than 30 MB, run the JETPACK.exe utility to compact
it.
Rebooting the computer does not fix the problem either.
This has been recently installed fresh and has had the problem from the get
go.
Any help would be greatly appreciated.
Thanks,
Jim