General discussion
| Thread display: Collapse - |
All Comments
Back to Networks Forum
3 total posts
(Page 1 of 1)
Start or search
Create a new discussion
If you're asking for technical help, please be sure to include all your system info, including operating system, model number, and any other specifics related to the problem. Also please exercise your best judgment when posting in the forums--revealing personal information such as your e-mail address, telephone number, and address is not recommended.
DHCP Event error
The event error is 1014, and the DHCP server had quit assigning leases to about half the clients, and hence the generated error messages. (Irebooted the server and it came back up immediately.) My question is this: the errors read:
DHCP Event 1014.
The JET Database call returned the following error : -529. Additonal Debug Information: DeleteCurrentRecord:Delete.
alternating with:
DHCP Event 1014.
The JET Database call returned the following error : -529. Additonal Debug Information: DhcpJetCommitUpdate.
I can't find an explanation for those specific messages. I CAN find documentation for two other DHCP error messages below (I am NOT getting these messages):
First one:
DHCP Event 1014.
The JET database call returned the following error with a hex data
status of ?ff fd ff ff (0xfffffdff=-513)?
(meaning the dhcp.mdb file is full - more hard drive space needs to be allocated)
and second one:
Event I
Source: DhcpServer
Description: The Jet database returned the following Error: ?510 (or ?1022 or ?1850)
(meaning that the dhcp.mdb file is corrupted and is usually caused by power failures and bad hard drives, or "curious users who try to open (it) using Microsoft Access.")
I am getting a different error message, however this server DOES have very little space left on C: drive, and I suppose it is always possible there was a shortpower outage of some sort, because this occurred over the holiday weekend when there was no one here. So, why the -529 error messages? Anyone know what these specific ones means? Thanks in advance.
This conversation is currently closed to new comments.