Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
After Mail Store Move
95 views
Skip to first unread message
FastEddie
Oct 29, 2007, 8:27:01 PM10/29/07
to
After a mail store move, it appears that the priv1.mdb and .stm are not
updating as the modify date has not changed in 24 hours.
Log files are being updated (E00tmp.log E00.log E000009E.log E00.chk ).
I have check the permissions and they as correct as described in
http://support.microsoft.com/kb/821915.
The database move went smoothly to the new drive.
I also seem to have aquired a temp.edb file that is update periodically.
No Events message pertaining to the Information Store are found.
This was all brought about by a client error message:
updating as the modify date has not changed in 24 hours.
Log files are being updated (E00tmp.log E00.log E000009E.log E00.chk ).
I have check the permissions and they as correct as described in
http://support.microsoft.com/kb/821915.
The database move went smoothly to the new drive.
I also seem to have aquired a temp.edb file that is update periodically.
No Events message pertaining to the Information Store are found.
This was all brought about by a client error message:
17:15:58 Synchronizer Version 12.0.6024
17:15:58 Synchronizing Mailbox 'Shashi Nagpure'
17:15:58 Synchronizing local changes in folder 'Calendar'
17:15:58 Uploading to server 'webexch.Minecode.com'
17:15:58 Error synchronizing folder
17:15:58 [80040111-520-80040111-0]
17:15:58 Microsoft Exchange is currently busy. If this
message is still displayed in 30 minutes, contact your Exchange administrator.
17:15:58 Microsoft Exchange Information Store
As if the Information Store can not be updated.
Any help would be appreciated
Thanks in advance,
Ed S
Fibercloud, Inc.
Ed Crowley [MVP]
Oct 30, 2007, 2:51:44 AM10/30/07
to
The dates on the files won't update unless you stop the Information Store,
so that's normal, and I'm very confident that it has nothing to do with the
synchronization failure. Sorry, but I don't have an answer for that
problem, though. I get those from time to time myself. If it goes away,
chalk it up to a transient problem. If it persists, start searching in
Google and the Microsoft KB, or you could open a support ticket with PSS.
Be aware that this could be caused by just about anything between Outlook
and the Exchange storage subsystem, inclusive, based upon my experience.
--
Ed Crowley
MVP - Exchange
"Protecting the world from PSTs and brick backups!"
so that's normal, and I'm very confident that it has nothing to do with the
synchronization failure. Sorry, but I don't have an answer for that
problem, though. I get those from time to time myself. If it goes away,
chalk it up to a transient problem. If it persists, start searching in
Google and the Microsoft KB, or you could open a support ticket with PSS.
Be aware that this could be caused by just about anything between Outlook
and the Exchange storage subsystem, inclusive, based upon my experience.
--
Ed Crowley
MVP - Exchange
"Protecting the world from PSTs and brick backups!"
"FastEddie" <Fast...@discussions.microsoft.com> wrote in message
news:1322320A-DD20-4A6A...@microsoft.com...
FastEddie
Oct 30, 2007, 1:54:01 PM10/30/07
to
Thanks for the info. When a new error creeps up after a change, you never
know.
know.
Thanks again,
Ed S
Fibercloud, inc.
0 new messages