Contents Previous Next

SYNC Messages

----SYNC002
User name, password, host name or port number may be incorrect.

Cause:

DAS may be down or unreachable.

Solution:

Check if User name, password, host name and port number are correct. Make sure DAS is running and can connect from the current instance(host).

----SYNC006
Synchronization module subsystem's meta-data.xml file is corrupted.

Solution:

There are several possible solutions:

• Check that synchronization-meta-data.xml and na-synchronization-meta-data.xml exist in appserv-se.jar and is a valid XML file.

• Check if synchronization-meta-data.xml is not part of server classpath.

• synchronization-meta-data.xml is not valid.

• synchronization-meta-data.xml found in server classpath is not well formed.

----SYNC029
This could be either a config Exception or IOException

Solution:

Check domain.xml and das.properties. If the problem persists, you may backup and remove applications, generated, config, docroot and lib directories in the local repository and restart the server. The local repository will be synchronized again.

----SYNC047
Connection problem during download.

File(s) could not be written to synchronization store.

Solution:

Check if DAS is up. Check for connection errors during download. Check if synchronization repository has enough space and has permission. If the repository is on NFS, may be NFS is down.

----SYNC049
File(s) could not be written to synchronization store.

Solution:

Check if synchronization repository has enough space and has permission. If the repository is on NFS, may be NFS is down.

----SYNC052
domain.xml is incorrect.

Solution:

Make sure domain.xml errors are fixed. It may have been manually edited.

----SYNC074
This could be a network communication error.

Solution:

Please check domain.xml, das.properties and server log.

----SYNC075
This could be a network communication error or Domain Administration Server is not running.

Solution:

Please ensure that Domain Administration Server is running. If DAS is accessible and the problem persists, you may backup and remove applications, generated, config, docroot and
lib directories in the local repository and restart the server. The local repository will be synchronized again.

Contents Previous Next