Team Services Troubleshooting
Overview
There are just a few items to note when troubleshooting Team Servcies.
- When you are performing Team Services Transfer, Swap or Share and you are in the menu where you select the session - Only sessions in the appropriate Accept Mode are displayed. For example, for Transfer, only sessions in Accept Transfer Mode are displayed. For Swap, only sessions in Accept Swap Mode are displayed, etc.
- When you are performing Team Services Recover and you are in the menu where you select the session to recover - Only suspended sessions are displayed.
- Check that the Team Services Registry settings are correct.
- Check that the logon script's Team Services environment variables are correct.
There are some session configuration items that must be the same for sessions participating in Team Services.
- The SSH settings must be the same (SSH in use or not in use)
- GSW Encryption settings must be the same (GSW Encryption in use or not in use).
- FIPS settings must be the same (FIPS in use or FIPS not in use).
Additionally, some configuration items and/or requirements for sessions participating in specific Team Services operations are:
Recovery
- Session Saver must be configured
- Session must be in suspended state
- Client types must match (GSW or 3rd Party)
- Unicode settings must match
Transfer
- Session must be in Accept Transfer mode
- Client types must match (GSW or 3rd Party)
- Unicode settings must match
Share
- Session must be in Accept Share mode
- Session must not already be monitored or shared
Swap
- Session must be in Accept Swap mode
- Client types must match (GSW or 3rd Party)
- Unicode settings must match
A quick way for the System Administrator to identify the Client, Unicode and SSH settings for a given session is to use the Session Administrator. Select the session and then use the menu item Session->Details. You will see a display similar to the one below.
You can identify if a client is a GSW FIPS session by the '*' pre-pended to the User Name in the User name column.