Contacts and ActiveSync warning with MSOXPsp3

Since implementing service pack 3 for our MS OfficeXP
Professional users, clients using ActiveSync 3.7.1.4034
are receiving a warning when they attempt to synchronize
their Contacts. The warning is that "a program is trying
to access e-mail addresses you have stored in Outlook. Do
you want to allow this?" Following a warning that the
message be related to a virus, the user is given the
option to allow for 1 - 10 minutes or deny access. As I
have deduced that the issue is the result of ActiveSync
attempting to read the contents of the Contacts folder, I
have advised my clients to allow access for 10 minutes.

While most clients are no longer receiving the warning,
some are. ActiveSync is the latest release and the warning
did not occur prior to incorporating MSOXP service pack 3.
Is there something about sp3 that is causing this happen?
Does the warning actually resolve itself with sufficient
time granted to complete the process?

Help! Some of my clients are threatening mutiny!

See my response to your other post on this issue.

--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx


"Teresa Schmidt" wrote in message
...
Since implementing service pack 3 for our MS OfficeXP
Professional users, clients using ActiveSync 3.7.1.4034
are receiving a warning when they attempt to synchronize
their Contacts. The warning is that "a program is trying
to access e-mail addresses you have stored in Outlook. Do
you want to allow this?" Following a warning that the
message be related to a virus, the user is given the
option to allow for 1 - 10 minutes or deny access. As I
have deduced that the issue is the result of ActiveSync
attempting to read the contents of the Contacts folder, I
have advised my clients to allow access for 10 minutes.

While most clients are no longer receiving the warning,
some are. ActiveSync is the latest release and the warning
did not occur prior to incorporating MSOXP service pack 3.
Is there something about sp3 that is causing this happen?
Does the warning actually resolve itself with sufficient
time granted to complete the process?

Help! Some of my clients are threatening mutiny!