Troubleshooting StarTeamMPX

To determine whether your Microsoft Windows-based StarTeamMPX system is operating correctly, you can perform the following steps.

  1. Review the following configuration files to ensure that the server addresses and endpoints are correct:
    MPXEventTransmitter.xml
    For the Event Transmitter installed for each StarTeam Server.
    FileTransmitter.xml
    For the File Transmitter installed for each StarTeam Server.
    STMessageBroker68.ini
    For each Message Broker.
    RootCAConfig.xml
    For each Root MPX Cache Agent.
    RemoteCAConfig.xml
    For each Remote MPX Cache Agent.
  2. If they are not already running, start the Message Brokers.
  3. For each Message Broker you start, start a StarTeamMPX-enabled server configuration that communicates with that Message Broker.
  4. For each server configuration you start, review its server log file. If the Event Transmitter has any problems connecting to the Message Broker, the error messages will be written to the server log file (for example, Server.en-US.log), which is located in the root folder of the server configuration’s repository.
  5. Start a client and ensure that support for StarTeamMPX is enabled for your workstation.
  6. Enable client StarTeamMPX options:
    1. In your client, click Tools > Personal Options. The Personal Options dialog box opens.
    2. Select appropriate options on the Workspace and MPX tabs. The StarTeam Cross-Platform Client has MPX options on the Workspace tab. This option allows the StarTeam log file to include MPX information. The log file can be viewed at any time by clicking Tools > StarTeam Log. It also has settings for enabling and disabling MPX.

      Only the StarTeam Cross-Platform Client and IDEs based on StarTeam Cross-Platform Client and .NET components have options for MPX Cache Agent.

    3. Click OK. Test these settings.
  7. In your client, open a view from aStarTeamMPX-enabled server configuration. If MPX is enabled in both the client and the server configuration, a yellow lightning bolt appears in the status bar.
  8. Ensure that the machines running the different message brokers have their clocks synchronized. Failure to do this could cause message expiration and clients may not receive messages.