IBM Connections log file
Connections writes messages to the SystemOut.log file. Refer to this file if you encounter errors after installing an IBM
Connections application or if you encounter unexpected behavior in an application.
Use the codes included in the error messages generated by IBM
Connections to identify problems and find their solutions.
Troubleshooting a database connection
A faulty JDBC driver or data source can prevent you from accessing an IBM
Connections application. To troubleshoot and correct these problems, test the database connections.
Validating Search seedlists
If you experience problems when indexing, you can validate Search seedlists to help you identify the source of the problem. You can validate Search seedlists using the browser or the wsadmin client.
Troubleshooting inter-server communication
If you are having problems establishing communication between servers in your deployment, this might be because a server's URL is not configured correctly in the LotusConnections-config.xml
Troubleshooting Search-related memory issues
You can configure settings in the LotusConnections-config.xml
file to avoid out-of-memory issues or other problems caused by long response times from the Search application.
Troubleshooting the product help
Find out how to resolve problems accessing the product help. The product help is what is displayed in a separate window when you click the Help link from the product header.
Troubleshooting single sign-on problems with Lotus Domino
Troubleshoot problems when using single sign-on (SSO) with IBM Lotus
Troubleshooting virus scanning
Find out some of the common causes for scanning-related error messages.
Troubleshooting network shares on Windows 2003
® 2003 returns network errors when accessing shared content.
Rebuilding the look-aside indexes
In the event that the look-aside indexes do not get rebuilt or are not synchronized correctly, you can use the ProfilesService.rebuildLookAsideIndexes()
command to explicitly rebuild them.
Troubleshooting problems with Tivoli Directory Integrator
If you experience problems when using IBM Tivoli
® Directory Integrator to work with Profiles data, explore the different trace areas available for Profiles to find information that might help to identify and resolve the problem.
Troubleshooting user data propagation
If you experience problems related to user data propagation, enable traces in the IBM WebSphere
® Application Server so that you can access detailed information about the processes involved in propagating updates. You can use this information to help you verify if the processes are working as expected.
Troubleshooting connection timeouts when running a wsadmin script
Running a wsadmin administrative script that calls an MBean in a network deployment environment results in several connections between sever processes, such as the deployment manager, the node agent, and the cluster member using Java
™ Management Extensions (JMX) connectors. Some IBM
Connections administrative scripts can run for longer than the default connection timeout that is specified for the connector that is used.
Sometimes you cannot solve a problem by troubleshooting the symptoms. In such cases, you need to collect diagnostic data.
Verifying email digests
You can verify that your email digests are working correctly by logging into IBM
Connections and accessing specific URLs to trigger the email digests to be sent.