J
Jamie Smith
I am having recurring problems with the edb.chk file
whereby access is not granted momentarily. Having checked
kb articles over and over, I have found no solution to my
problem.
As background:
1. There is no anti-virus program running
2. All service accounts and administrators have full
writes to all directories, sub-directories and files
3. There are no I/O issues with the hardware
4. The edb.chk (and indeed all edb based files) are not
specified as read-only
5. Index Server is not checking against these files
6. I run an offline ArcServe, rather than online, backup,
overnight, having shutdown all services via a batch file,
although invariably the problems happen during the day
anyway - I realise that online backup is the recommended
option but I do not find this resiliant enough.
This problem has only started occurring since migrating
Exchange 5.5 to a new server, named and domained exactly
the same as the previous one, running on NT4.0 SP6a and
Exchange SP4 (as per the previous server).
The priv, pub, and dir databases are consistent and were
patched accordingly following the offline restore for the
new server. Only these files were restored as recommended
by the MS technical article.
I am at a loss. There does not seem to be any other
information taking the above eliminations into
consideration. Has anybody else had a similar problem and
if so what is the solution?
Many thanks
Jamie Smith
whereby access is not granted momentarily. Having checked
kb articles over and over, I have found no solution to my
problem.
As background:
1. There is no anti-virus program running
2. All service accounts and administrators have full
writes to all directories, sub-directories and files
3. There are no I/O issues with the hardware
4. The edb.chk (and indeed all edb based files) are not
specified as read-only
5. Index Server is not checking against these files
6. I run an offline ArcServe, rather than online, backup,
overnight, having shutdown all services via a batch file,
although invariably the problems happen during the day
anyway - I realise that online backup is the recommended
option but I do not find this resiliant enough.
This problem has only started occurring since migrating
Exchange 5.5 to a new server, named and domained exactly
the same as the previous one, running on NT4.0 SP6a and
Exchange SP4 (as per the previous server).
The priv, pub, and dir databases are consistent and were
patched accordingly following the offline restore for the
new server. Only these files were restored as recommended
by the MS technical article.
I am at a loss. There does not seem to be any other
information taking the above eliminations into
consideration. Has anybody else had a similar problem and
if so what is the solution?
Many thanks
Jamie Smith