XADM: Edb.chk Does Not Move During Performance Optimization (196332)
The information in this article applies to:
- Microsoft Exchange Server 4.0
- Microsoft Exchange Server 5.0
- Microsoft Exchange Server 5.5
This article was previously published under Q196332 SYMPTOMS
The Edb.chk file is not moved after the Performance Optimizer is run.
CAUSE
The Edb.chk file is created on the original installation drive in the
ExchSrvr\Mdbdata and ExchSrvr\Dsadata directories and is not moved with
these directories if optimized to another drive.
This is by design.
WORKAROUND
To work around this problem, the *.CHK file can be moved to another drive
manually. To do this, perform the following steps:
- Start the Exchange Server Administrator program and retrieve the
properties of the server object. To get to the server object in the
Exchange Server Administrator program, click Organization, click Site,
click Configuration, click Servers, click <server>, and then on the File
menu, click Properties.
- Click the 'Database Paths' tab.
- To modify the location of the Edb.chk file for the information store,
select the 'Information Store Working Path,' and then click Modify.
Using the interface, select the drive letter and folder that the new
Edb.chk file will be created in, and then click OK. To change location
of the Edb.chk file for the directory, follow the above, but select the
'Directory Working Path'.
- Click Apply. This will stop and start the relative services creating
the new Edb.chk on the appropriate drive.
| Modification Type: | Minor | Last Reviewed: | 4/28/2005 |
|---|
| Keywords: | kbprb KB196332 |
|---|
|