Sametime server Configuration Bridge service fails to start

Technote (troubleshooting)


Problem

The Sametime server's Configuration Bridge service will not start, and this failure prevents all the Sametime Meeting server services from starting properly.

Symptom

The following errors appear in the Notes log (log.nsf) under the Miscellaneous Events view:
08/12/2002 08:05:15 AM Sametime Server: Starting services
08/12/2002 08:05:16 AM Sametime: Building service start order from dependencies...
08/12/2002 08:05:16 AM Sametime: Found event server service.
08/12/2002 08:05:16 AM Sametime: Starting services...
08/12/2002 08:05:16 AM Sametime: Starting event server service.
08/12/2002 08:05:24 AM Sametime: Service started.
08/12/2002 08:05:24 AM Sametime: Starting service Java Services.
08/12/2002 08:05:24 AM Sametime: Process 430 created.
08/12/2002 08:05:27 AM Sametime: Service started successfully.
08/12/2002 08:05:27 AM Sametime: Starting service Latitude Integration Service.
08/12/2002 08:05:28 AM Sametime: Service started successfully.
08/12/2002 08:05:28 AM Sametime: Starting service Configuration Bridge.
08/12/2002 08:05:33 AM Sametime: Service failed to start.
08/12/2002 08:05:33 AM Sametime: One or more services failed to start.
08/12/2002 08:05:33 AM Sametime: Server startup failed. Shutting down...
08/12/2002 08:05:33 AM Sametime: Stopping services...
08/12/2002 08:05:33 AM Sametime: Service Activity Provider is not started.
08/12/2002 08:05:33 AM Sametime: Service H.323 MCU is not started.
08/12/2002 08:05:33 AM Sametime: Service A/V MMP is not started.
08/12/2002 08:05:33 AM Sametime: Service Broadcast Controller is not started.
08/12/2002 08:05:33 AM Sametime: Service Broadcast Gateway is not started.
08/12/2002 08:05:33 AM Sametime: Service Calendar Service is not started.
08/12/2002 08:05:33 AM Sametime: Service Capacity Monitor is not started.
08/12/2002 08:05:33 AM Sametime: Service Material Manager is not started.
08/12/2002 08:05:33 AM Sametime: Service Shared Object Server is not started.
08/12/2002 08:05:33 AM Sametime: Service Statistics Server is not started.
08/12/2002 08:05:33 AM Sametime: Service Whiteboard Server is not started.
08/12/2002 08:05:33 AM Sametime: Service T.120 MCU is not started.
08/12/2002 08:05:33 AM Sametime: Service Token Server is not started.
08/12/2002 08:05:33 AM Sametime: Service Logger is not started.
08/12/2002 08:05:33 AM Sametime: Service Event Bridge is not started.
08/12/2002 08:05:33 AM Sametime: Service Configuration Bridge is not started.
08/12/2002 08:05:33 AM Sametime: Service Latitude Integration Service is not started.
08/12/2002 08:05:33 AM Sametime: Stopping service Java Services.
08/12/2002 08:05:35 AM Sametime: Service stopped.
08/12/2002 08:05:35 AM Sametime: Stopping event server service.
08/12/2002 08:05:35 AM Sametime: Service stopped.
08/12/2002 08:05:35 AM Sametime: All services stopped successfully.

In the SametimeAdminDiagnosticsOutput file, you might notice Bootstrap failure at the beginning, and fatal errors throughout. In the SametimeHealthDiagnosticsOutput.txt file you might notice a FATAL error. Additionally, you might notice that several lines are missing from the Sametime.log file.


Cause

This issue can be the result of any number of things. Typically it is caused by a misconfiguration.


Resolving the problem

What follows is descriptions of the most common reasons for this error code, and how to troubleshoot this type of failure.


Section 1: Verify your configuration settings

1. Check the Server document
Open the Domino directory (names.nsf) located on the Sametime server using a Notes or Administration client.

a. Check for replication or save conflicts
Please verify that there are no replication or save conflict documents attached as responses to the Server document. Notes shows replication or save conflicts as responses to the main document with a diamond symbol in the left margin. Any conflicts must be resolved prior to attempting other troubleshooting steps. Please reference the Lotus Notes help for additional information on replication or save conflicts.

b. Ensure any changes are made to the correct replica
If the Domino directory replicates between servers in your environment, you should consult the administrator of your Domino domain prior to making any changes. If the Server document will be replicating, make sure the changes are made on the appropriate replica.

For example, if you have an administration server that pushes changes down, that server may overwrite all of the settings on the servers that it pushes updates to. This has been known to occur with new installations, where the Sametime installer makes changes to the server's Server document, and then when the server starts up and replicates with other servers, the settings are overwritten.

c. Check the settings in the Server document
The Sametime server's Server document settings should be set to the following:

Tab Section: Field Label Set to...
Basics Load internet configurations from Server/Internet Sites documents Disabled (See technote#  1157740 for more details).
Fully qualified Internet host name The fully-qualified host name as known by the DNS server.

Commonly: computername.internetdomain.com
Example: stserver1.acme.com
Is this a Sametime server? Yes
Security "Who can run unrestricted LotusScript/Java agents"

or, in Sametime 3.1:

"Who can run unrestricted methods and operations"
Must contain "Sametime Development/Lotus Notes Companion Products" and the server name
Ports / Notes Network Ports Netaddress field (for TCPIP) Must be the fully qualified internet hostname of the Sametime server. This needs to be resolvable in DNS where the Sametime server resides.
Ports / Internet Ports / Web SSL If SSL is enabled, please see below section on SSL
Anonymous Yes or No are both acceptable

If set to "No", additional entries are required in the sametime.ini. Refer to Section Two below for specifics.

Internet Protocols / Domino Web Engine Java Servlet Support Must be "Domino Servlet Manager"
Session State Tracking Enabled
Internet Protocols / HTTP DSAPI File Filternames This field should be blank.

DSAPI is not supported on Sametime servers.

If you are using Netegrity Siteminder and the policy server has problems with Netegrity Siteminder (DSAPI), the configuration bridge can fail as well. To test if this is the case remove the filter temporarily to see if configuration bridge loads.



2. Check sametime.ini
Note The Sametime.ini file is divided up into sections. Each section name is placed in square brackets (example: [Config], [Connectivity], etc). To work properly, the sametime.ini parameters must be placed in the correct sections.

Parameter(s) Set to...
ConfigurationPort=80

or

ConfigurationPort=8088
  • Place under the [Config] section
  • Default is 80 for non-tunneled servers
  • Default is 8088 for tunneled servers
  • This should match your HTTP port on the Server document (under Ports -> Internet Ports -> Web)
ConfigurationHost=
*see note below
  • Place under the [Config] section
  • Check for misspellings of the hostname
  • should be the fully qualified internet hostname (same as the Server document)
SametimeAdminUsername
SametimeAdminPassword

or

SametimeAdminAuthorization
  • Place under the [Config] section
  • If Anonymous is set to No in the Server document, the administration name and password account for the server must be present in the sametime.ini.
  • To enter the name and password, you use these two parameters:
    SametimeAdminUserName= (The user name)
    SametimeAdminPassword = (The password of that user)
  • These parameters must point to a valid user name which will be on the ACL of the stconfig.nsf, names.nsf, da.nsf (if applicable), etc. Please verify that this name and password can be used to access names.nsf and stconfig.nsf using a browser.
  • Once you have saved those two settings and restarted the server, the two lines will automatically change to:
    SametimeAdminAuthorization
All parameters that begin with:
javax.net.ssl...
  • These parameters are for SSL configured servers only.
  • Check for case sensitivity (i.e. javax.net.ssl.trustStorePassword will work, but Javax.net.ssl.trustStorePassword will fail). Incorrect case will result in failure of the Configuration bridge.

    WARNING: Do not copy and paste lines from the Help document "Configure the Sametime.ini file on the Sametime server" in the Sametime Administrator Help, where the beginning letter of each "javax" line is capitalized:
    Javax.net.ssl.keyStore=c:\lotus\domino\stkeys.pfx
    Javax.net.ssl.keyStorePassword=sametime
    Javax.net.ssl.trustStorePassword=sametime
ConfigurationSSLEnabled=
SSLManagerClassName=
javax.net.ssl.keyStore=
javax.net.ssl.trustStore=
javax.net.ssl.keyStorePassword=
javax.net.ssl.trustStorePassword=
  • Place under the [Config] section
  • These six lines are required for SSL.
  • An example of these parameters with their values assigned:

    ConfigurationSSLEnabled=true
    SSLManagerClassName=
    com.lotus.sametime.configuration.
    IBMJSSE118Manager
    javax.net.ssl.keyStore=
    F:\lotus\domino\stkeys.pfx
    javax.net.ssl.trustStore=
    F:\lotus\domino\stkeys.pfx
    javax.net.ssl.keyStorePassword=password
    javax.net.ssl.trustStorePassword=password
*Note:
    If the ConfigurationHost is set incorrectly, you will see errors similar to the following in the ST_Generic_Diagnostics.txt file (in the Lotus\Domino\Trace directory)
    03/30 10:24:30.880 [main] INFO (com.lotus.sametime.event.DBEventRequestServiceTCPServer) - Event server LISTENING on: localhost:9092
    03/30 10:24:33.020 [main] INFO (com.lotus.sametime.event.DBEventRequestServiceTCPProxy) - Connecting to localhost:9092.
    03/30 10:24:33.935 [Thread-0] INFO (com.lotus.sametime.event.DBEventRequestServiceTCPProxy) - Connecting to localhost:9092.
    03/30 10:24:40.154 [main] FATAL (com.lotus.sametime.event.DBEventListenerTCP) - shutdown exception
    java.net.SocketException: Socket closed

    Or you'll see this in ST_Configuration_Diagnostics.txt.
    java.net.UnknownHostException


3. Check Sametime database template and ACLs
a. Check template versions
If this is an upgraded or downgraded server, please verify that all Sametime databases on the server (stconf.nsf, stconfig.nsf, vpuserinfo.nsf, stsrc.nsf) have been upgraded to their appropriate template versions. Mismatch of template versions with server versions can result in problems.

b. Check the ACL of stconfig.nsf
  • The server name must be listed with "Unspecified" type, with Manager access and the STAdmin role. If you have the Anonymous web access set to No in the Server document (Ports Tab -> Internet Ports Tab -> Web sub-Tab -> Web [HTTP/HTTPS Section] -> Authentication Options), you must have the administrator's name specified here (as specified in the sametime.ini) with a type of "Unspecified", Manager access with STAdmin role. This name must be explicitly listed, and not simply part of a Group.
  • Ensure that the ACL on all Sametime databases and the server's names.nsf contain an entry for the server.


4. Check servlets.properties file
In some cases, other Domino applications may erase the servlets.startup line of the servlets.properties file which is located in the Domino Data directory. To correct this problem, add the following to the bottom of the file:

servlets.startup=bootstrap scs auth admin mmapi stcal fileupload rapfile

After making this change, a restart of the server is necessary. You should see the servlets attempt to start in the Domino Console on startup of HTTP.



5. Check Windows OS settings
a. Hostname and DNS suffix
The Configuration Bridge checks the workstation's Hostname and Primary DNS suffix. If they are not set or do not match the Net Address field in the Ports -> Notes Network tab of the Server document, the Configuration Bridge will fail to load.

This can be verified by running ipconfig /all. If the net address is set to server.domain.com, the first several lines should look similar to the following:

Windows 2000 IP Configuration
Host Name . . . . . . . . . . . . : server
Primary DNS Suffix . . . . . . . : domain.com

These values are set in Windows by right-clicking on "My Computer" and selecting Properties under the"Network Identification" tab.

b. Windows Services incorrectly configured
Under Control Panel -> Administrative Tools -> Services:
All of the Sametime services should be set to Manual.

c. Incorrect subnet mask
Verify that you have a correct subnet mask for your environment. This varies depending on your network configuration. Please contact your network administrator for details. An incorrect subnet mask may show an error similar to the following in the java stack traces (SametimeHealthDiagnosticsOutput.txt):
11/07 10:06:10.406 [main] FATAL (com.lotus.sametime.event.DBEventListenerTCP) - shutdown exception
java.net.SocketException: Socket closed



6. Check for "Set Secure"
Check to make sure "Set Secure" has not be used on the Domino server (refer to technote #1153464).



7. Check SSL configuration
These only apply if you have configured SSL:


Check the following:
  • the stkeys.pfx file is not expired
  • IBM Keyman program has been properly configured
  • the sametime.ini file must be properly configured for SSL

Below is the sample log:
    12/04/2002 11:01:06 AM Sametime Server: Starting services
    12/04/2002 11:01:06 AM Sametime: Building service start order from dependencies...
    12/04/2002 11:01:06 AM Sametime: Found event server service.
    12/04/2002 11:01:06 AM Sametime: Starting services...
    12/04/2002 11:01:06 AM Sametime: Starting event server service.
    12/04/2002 11:01:10 AM Sametime: Starting service Java Services.
    12/04/2002 11:01:10 AM Sametime: Process 1364 created.
    12/04/2002 11:01:13 AM Database Server started
    12/04/2002 11:01:14 AM Sametime: Service started successfully.
    12/04/2002 11:01:14 AM Sametime: Starting service Latitude Integration Service.
    12/04/2002 11:01:14 AM Sametime: Service started successfully.
    12/04/2002 11:01:14 AM Sametime: Starting service Configuration Bridge.
    12/04/2002 11:01:21 AM Addin: Agent printing: com.lotus.sametime.admin.authentication.AccessControlServlet: init
    12/04/2002 11:01:22 AM Addin: Agent printing: com.lotus.sametime.admin.AdminXPathRequestServletJAXP: init
    12/04/2002 11:01:22 AM Addin: Agent printing: com.lotus.sametime.meetingmanagement.remote.servlet.MMAPIServlet: init
    12/04/2002 11:01:22 AM Addin: Agent printing: loaded [MeetingManagement.properties] from file system.
    12/04/2002 11:01:23 AM Addin: Agent printing: com.lotus.sametime.calendar.NotesCalendarServlet: init
    12/04/2002 11:01:23 AM Addin: Agent printing: com.lotus.sametime.materials.servlets.FileUploadServlet: init
    12/04/2002 11:01:23 AM Addin: Agent printing: com.lotus.sametime.materials.servlets.RAPFileServlet: init
    12/04/2002 11:01:23 AM HTTP Web Server started
    12/04/2002 11:03:06 AM Sametime Server: Running
    12/04/2002 11:03:14 AM Sametime: Service start wait time exceeded.
    12/04/2002 11:03:14 AM Sametime: Service failed to start.
    12/04/2002 11:03:14 AM Sametime: One or more services failed to start.
    12/04/2002 11:03:14 AM Sametime: Server startup failed. Shutting down...



Section 2: Lesser known causes
The following may have been one time occurrences, or may not apply to your environment.


1. Virtual Server documents
Check for a Virtual Server document that may have been setup at a previous time. In one customer's case there was a residual Virtual Server document redirecting TCP connections to the SSL connection on the server. Once the document was disabled, the Configuration Bridge services started successfully.


2. For EMS managed servers
  • The Configuration Bridge may not start if an Enterprise Meeting Server (EMS) is used in the environment and WebSphere Application Server (WAS) is not started. Check the services of the EMS machine and make sure that the service IBM WS Admin Server 4.0 has a status of Started. If the status is blank, right-click and select the "Start" menu. Then start your Sametime servers.

  • After rebooting, the Room Server's meeting services may fail to launch successfully due to the Configuration Bridge service failing to load. See technote #1247039 for more details.



Section 3: How to enable and interpret debug for troubleshooting
If you are unable to determine the root cause of this issue, you may be asked by a Support Engineer to enable debug.

Enabling Debug
To obtain debug, a change can be made to the SametimeDiagnostics.properties file (located in c:\lotus\domino). To do this, open the SametimeDiagnostics.properties file in any text editor, such as Windows Notepad. Scroll down to the bottom of the file and locate the following line:

log4j.category.com.lotus.sametime.configuration.bridge= INFO, JavaServiceManagerAppender

Change the line to this:

log4j.category.com.lotus.sametime.configuration.bridge= DEBUG, JavaServiceManagerAppender

Save the file. Make sure your text editor does not append a file extension such as .txt. The name of the file must remain .properties.

For Sametime 3.1 and higher: The output will be to ST_Configuration_Diagnostics.txt (located in c:\lotus\domino\trace).
Open this file and search for the word "Exception" or "Fatal", this will help locate any errors.

For Sametime 3.0: The output will be to SametimeDiagnosticsOutput.txt and SametimeAdminDiagnosticsOutput.txt (located in c:\lotus\domino)
Open the files and search for the word "Exception" or "Fatal", this will help locate any errors.

Historical Number

194386

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Lotus End of Support Products
Lotus Sametime

Software version:

6.5, 7.0, 7.5

Operating system(s):

AIX, OS/400, Solaris, Windows, i5/OS

Reference #:

1098735

Modified date:

2008-08-29

Translate my page

Machine Translation

Content navigation