AutoSYNC Software User's Guide (Update 17)

Problem Resolution
HP AutoSYNC User’s Guide—522580-018
B-2
Scheduled Synchronization Problems
Scheduled Synchronization Problems
The source synchronization process creation fails with
security violation

Verify that the ASYSYNCP object file in the source product subvolume is
PROGID’ed to the Authorizer.

Verify that the Authorizer has permission to log down to the sync user ID. If not,
make ASYSYNCP callable, to bypass the restriction. See Bypassing Disabled Log
Down on page 4-7 for details.
The destination synchronization process creation fails with
a security violation

Verify that the syncuser’s remote passwords has been set correctly between the
source and remote destination system.

Is a SAFEGUARD ALIAS being used? If so, verify that the remote passwords have
been correctly set for the ALIAS.
The destination synchronization process starts but fails to
log down to the sync user ID

Verify that the Authorizer has permission to log down to the SYNCUSER ID without
specifying a password. If not, make ASYSYNCP callable to bypass the restriction.
See Bypassing Disabled Log Down on page 4-7 for details.
Errors replacing destination files
The following apply to both one-time and scheduled synchronizations:

Verify that this user has purge authority on destination files. AutoSYNC cannot
replace files if they cannot be purged by this user. In fact, setting purge security to
“-” on the destination implicitly excludes the file from synchronization, as shown by
the REPORT command.

Verify security settings for the destination file set. If security is restricted to local
users only, ASYSYNC (or ASYSYNCP if synchronizing over TCP/IP) on the
destination system can be made callable to operate as a local process. See
Running the Destination Synchronization Process as a Local Process on
page 3-21 for configuration instructions.

Verify that there are no SAFEGUARD volume or subvolume settings that prevent
creating the destination files.

Use FUP DUP to move a few files from the source to the destination. If the FUP
DUP operation succeeds, the synchronization will succeed.