|
| |
| Sun Java System Application Server 8.1 Enterprise Edition 2005Q1 Error Message Reference | |
Chapter 12
SYNC Error MessagesThis chapter describes messages for errors with a SYNC prefix.
SYNC002Message
User name, password, host name or port number may be incorrect.
Cause
DAS may be down or unreachable.
Solutions/Workarounds
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).
SYNC006Message
Synchronization module subsystem's meta-data.xml file is corrupted.
Solutions/Workarounds
- Please check 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.
SYNC029Message
This could be either a config Exception or IOException
Solutions/Workarounds
Please 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 re-start the server. The local repository will be synchronized again.
SYNC047Message
Solutions/Workarounds
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.
SYNC049Message
File(s) could not be written to synchronization store.
Solutions/Workarounds
Check if synchronization repository has enough space and has permission. If the repository is on NFS, may be NFS is down.
SYNC052Message
domain.xml is incorrect.
Solutions/Workarounds
Make sure domain.xml errors are fixed. It may have been manually edited.
SYNC074Message
This could be a network communication error.
Solutions/Workarounds
Please check domain.xml, das.properties and server log.
SYNC075Message
This could be a network communication error or Domain Administration Server is not running.
Solutions/Workarounds
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 re-start the server. The local repository will be synchronized again.