| |
|
| |
The document talks about the flowcharts to be followed while troubleshooting a Sametime infrastructure problem |
| |
|
| |
Sametime Configuraiton Validator is now part of the IBM Serviceability Tool for Sametime. |
| |
|
| |
Installation Tips and Troubleshooting
Keep installation paths short. WebSphere has an 80 character limit for profile path names. When installing multiple products on same machine, only Cell profile types can coexist. (Do select a Network deployment if you intent to install multiple Sametime ... |
| |
|
| |
BlackBerry Support Community Forums
BlackBerry Technical Solution Center (knowledge articles) Collection of articles on troubleshooting Lotus Sametime on BlackBerry |
| |
|
| |
There are a few options when turning on tracing and logging. You can get severe errors and system errors as well as package specific tracing (if enabled). Logging/tracing usually found in /WebSphere/AppServer/profiles//logs/. See ... |
| |
|
| |
==Where to look for exceptions or errors==
db2diag.log About DB2 diagnostic log (db2diag.log) files: [[http://publib.boulder.ibm.com/infocenter/db2luw/v9/topic/com.ibm.db2.udb.pd.doc/doc/t0020814.htm|Setting the diagnostic log file error capture level] Related ... |
| |
|
| |
Using the Information Center, there is a page about http:publib.boulder.ibm.cominfocenterwmbhelpv6r0m0topiccom.ibm.support.core.doctopicsgettingfixes.htmGetting Fixes. A product fix might be available to resolve your problem. Is it running
Make sure the Event Broker is started, ... |
| |
|
| |
Where to look for errors (SystemOut, SystemErr, ffdc)
Loggingtracing usually found in WebSphereAppServerprofilesprofilenamelogs. See Logging and tracing at the Info Center. Server logs: Look in system error logs, found in ... |
| |
|
| |
For debugging the Sametime 8.0 Client, we have two options. Help Support View Log
Help Support View Trace How to turn the log level up By default, the Logging and Trace is set to only capture Severe errors. You can change this setting by changing the following file: ... |
| |
|
| |
Use the following articles to help you troubleshoot Sametime Advanced client, WebSphere Application Server, Event Broker, and DB2 components. http:www10.lotus.comlddstwiki.nsfdxHowtoturntheloglevelupTroubleshooting the Sametime Advanced 8 Client ... |
| |
|
| |
This article contains an overview of LDAP components and how Lotus Sametime Community Server works with LDAP to provide authentication, name lookups, and name resolution. The article describes best practices for creating search filters, setting sametime.ini parameters, and enhancing Sametime and ... |
| |
|
| |
In this section, we discuss some strategies and items to check for the network. ==Introduction==
The network plays a key part in the performance of the STResolve service. The key areas to investigate are on, and also between, the Sametime Server and LDAP server. Certain operating systems have ... |
| |
|
| |
The intent of this white paper is to give you a better understanding of the different components of IBM Lotus® Sametime® 7.5.1 and 8.x servers and their environments, so you can better troubleshoot problems that may occur. We address both the stand-alone Sametime (chat or meeting) server as well ... |
| |
|
| |
IBM Support hosted a Webcast on the topic of troubleshooting the Lotus Sametime Gateway, which covered topics such as: Troubleshooting common Gateway install issues Troubleshooting Sametime community connection Setting up SSL Troubleshooting SIP connectivity (TCP TLS) for SIP Communities (AOL) ... |
| |
|
| |
IBM Support hosted a Webcast on the topic of troubleshooting the Lotus Sametime Gateway, which covered topics such as: Troubleshooting common Gateway install issues
Troubleshooting Sametime community connection
Setting up SSL
Troubleshooting SIP connectivity (TCP TLS) for SIP Communities (AOL or ... |
| |
|
| |
Issue 3 you cannot add a room server When you try to add a room server, a log file is created detailing any successes
and failures. When you add a room server to EMS it verifies that the LDAP
configuration is the same, reads in applet version files, reads in Sametime
deployment information ... |
| |
|
| |
In order to be truly effective at solving problems, you need to have a firm
understanding of not only how things work, but how they all work together. That
way if one specific piece of functionality is not working, you can go backwards
and find the cause. It is a very good idea to check out log ... |
| |
|
| |
Troubleshooting Event Broker password changes
If you have changed the password that is used either as the password for the ServiceUserId or DataSourceUserId for any of the IBM® WebSphere® Event Broker components, for example a remote DB2® server, you might find these components have access ... |
| |
|
| |
Troubleshooting authentication
If users are having difficulties authenticating, check their browser settings for cookies and language
Authenticated users cannot enter chat rooms unless they accept cookies. If a user logs in to IBM® Lotus® Sametime® Advanced and cannot enter a chat room where the ... |
| |
|
| |
Troubleshooting a failed WebSphere Application Startup
In the event that a change is made to a WebSphere® Application Server component of IBM® Lotus® Sametime® Advanced, WebSphere Application Server could fail to start. 1. Use a text editor to open the WebSphere Application Server file here: ... |
| |
|
| |
Troubleshooting using JVM logs
To start troubleshooting a problem, check the JVM log files first. These log files collect output for the System.out and System.err output streams for the application server process. One log file is specified for the SystemOut.log output stream and one file ... |
| |
|
| |
Logging and tracing
The Integrated Solutions Console provides logs to collect logging messages. System messages for IBM Lotus Sametime Advanced are written to the IBM service log. The IBM service log can be helpful in monitoring the health of the application server, however, the problem ... |
| |
|
| |
You can enable Trace for the Name Change Application in Sametime 8. Set the following sametime.ini variable in the debug section of the file: VP_NCSA_TRACE=1 View the results of the trace here: %domino_directory%\trace\namechange_080318_1742.txt Read more about the name conversion task in the ... |
| |
|
| |
Troubleshooting Sametime Advanced
Here are some steps for checking your IBM Lotus Sametime Advanced Server deployment(s). 1. Identify the deployment scenario (ISMP/Archive installer, clustered, etc.). 2. ISMP - Make sure you have installed and configured Prereqs first. 3. Simple techniques to ... |
| |
|
| |
The purpose of this document is to describe some of the test infrastructures that were set up at IBM to provide you with hints and tips for your own deployment. Overview
1. In this particular case we were testing connection to AOL clearinghouse Community. We set up two separate Sametime ... |