XADM: Error -530 Occurs When Starting the Directory or Information Store Service
ID: Q160024
|
The information in this article applies to:
-
Microsoft Exchange Server, versions 4.0, 5.0, 5.5
SYMPTOMS
When you try to start the Microsoft Exchange Server Directory or
Information Store service, the service does not start. The Event Viewer
indicates that the service returned an error -530.
CAUSE
Error 530 refers to the Jet error : JET_errBadLogSignature. This indicates
a problem with one or more log files.
RESOLUTION
To resolve this problem, do one of the following:
If the case the Directory Service is not starting:
- Move all the .log and .chk files out of the Exchsrvr\Dsadata directory
- Run edbutil /r /ds to regenerate the log and check files, and then try
to start the service again.
If the Information Store service is not starting:
- Move all the .log and .chk files out of the Exchsrvr\Mdbdata directory
- Run edbutil /r /is to regenerate the log and check files, and then try
to start the service again.
NOTE: The Dsadata and/or Mdbdata subdirectories that contain the .log files
may be on different drives, depending on whether the Performance Optimizer
or Administrator program has been used to move the database files. Moving
the .log files out of the corresponding directory may cause the service to
start, but any unflushed data in the .log files will not be written to the
Exchange Server database and will be lost. While the service (Directory or
Information Store) is running, any changes are first written to the .log
file and then periodically flushed out to the Exchange Server database.
When the Exchange Server service is properly shut down, all data is written
to the corresponding Exchange Server database.
Additional query words:
Keywords : XADM
Version : winnt:4.0,5.0,5.5
Platform : winnt
Issue type : kbprb
Last Reviewed: April 9, 1999