L
Lynn
We have a user who receives an error each time her Outlook
attempts to synchronize on her laptop. In the
synchronization log in her deleted items, it appears as:
8:57:13 Error synchronizing folder
8:57:13 [8004010F-501-8004010F-521]
8:57:13 The client operation failed.
8:57:13 Microsoft Exchange Server
Information Store
8:57:13 For more information on this
failure, click the URL below:
8:57:13
http://www.microsoft.com/support/prodredirect/outlook2000_u
s.asp?err=8004010f-501-8004010f-521
The strange thing is, it does not appear that anything is
synchronizing incorrectly. In the properties for each
folder that is being synchronized, the # of items on the
server always equals the # of offline items. I just don't
know what the above error is referring to.
We have recreated her .ost several times. Even though
the .ost is reaching a critical size (1.7Gb), we
eliminated that as an issue by reducing its size to 100mb
and still received the same error. We have also run a
detect and repair on Outlook.
Does anyone have any idea what might be going on here?
attempts to synchronize on her laptop. In the
synchronization log in her deleted items, it appears as:
8:57:13 Error synchronizing folder
8:57:13 [8004010F-501-8004010F-521]
8:57:13 The client operation failed.
8:57:13 Microsoft Exchange Server
Information Store
8:57:13 For more information on this
failure, click the URL below:
8:57:13
http://www.microsoft.com/support/prodredirect/outlook2000_u
s.asp?err=8004010f-501-8004010f-521
The strange thing is, it does not appear that anything is
synchronizing incorrectly. In the properties for each
folder that is being synchronized, the # of items on the
server always equals the # of offline items. I just don't
know what the above error is referring to.
We have recreated her .ost several times. Even though
the .ost is reaching a critical size (1.7Gb), we
eliminated that as an issue by reducing its size to 100mb
and still received the same error. We have also run a
detect and repair on Outlook.
Does anyone have any idea what might be going on here?