Server List Not Retrieved

Problem: No list of Unwired Servers displays in Sybase Control Center. Instead, an Error Retrieving Server List message appears in the left navigation pane.

Scenario 1: No other error message appears.

If this is the case, one of the following explanations may apply:

You are attempting to connect to a remote server that is not properly registered in Sybase Control Center.
Solution: Manually register the remote server. By default, only Unwired Servers installed to the same host computer are automatically registered with Sybase Control Center. See Getting Started with Unwired Server Administration in the Sybase Control Center online help. If you have recently made changes to the environment, for example, by modifying server resource properties (login, password, host name, IP address, or port number), ensure that you reauthenticate after making the changes.
Jetty caching in Sybase Control Center prevents the console from displaying the server tree. This is indicated by 404 errors in both the console URL and <UnwiredPlatform_InstallDir>\SCC-X_X\services\EmbeddedWebContainer\log\http-service.log (the HTTP access log).
Solution:
1. Close Sybase Control Center.
2. Stop Sybase Control Center X.X Service.
3. Delete the contents of: <UnwiredPlatform_InstallDir>\SCC-X_X\services\EmbeddedWebContainer\container\Jetty-X.X.XX\work.
4. Restart Sybase Control Center X.X service.

Scenario 2: The right administration pane shows an Authentication has failed error message.

If this is the case, one of the following explanations may apply:

You have not performed the "Authenticate" step in Sybase Control Center after registering the resource or changing their credentials.
Solution: In the Perspective Resources view, right click the server name and select Authenticate. In the default configuration, if you have used "supAdmin" to log in to Sybase Control Center, select Use my current SCC login.
You do not have the required administration privileges.
Solution: Ensure that:
1. The administrator login is assigned one of the physical roles attached to the "SUP Administrator" or "SUP Domain Administrator" logical roles in the "admin" security configuration. To change the "admin" role mapping outside of Sybase Control Center, manually edit <UnwiredPlatform_InstallDir>\UnwiredPlatform\Servers\UnwiredServer\Repository\CSI\conf\role-mapping.xml on all nodes in the cluster.
2. The <UnwiredPlatform_InstallDir>\SCC-X_X\conf\roles-map.xml configuration for the "SUP LDAP Login Module" and your security repository are being used to authenticate Sybase Control Center users. Ensure that the administration roles configured for the "SUP LDAP Login Module" exist in the security repository.
The server IP may have changed.
Solution: Update server resource properties, and repeat the "Authenticate" step described above. See the topic Sybase Control Center Fails to Start.

Scenario 3: The right administration pane shows a Connection unknown. Ensure Server is running.... message.

If this is the case, one of the following explanations may apply:

Unwired Server responded with an exception indicating a problem on the server.
Solution: Check <UnwiredPlatform_InstallDir>\UnwiredPlatform\Servers\UnwiredServer\logs\<hostname>-server.log for details.
The Sybase Control Center security provider is down or a system condition prevents Sybase Control Center from authenticating the user for administration access.
Solution: Ensure that the security provider is running and that its host is reachable from the Sybase Control Center host.

Scenario 4: In some rare cases, the connection between Sybase Control Center and Unwired Server cannot be established after trying the previous recommendations.

Solution: You may need to stop and restart the Sybase Control Center X.X windows service. After stopping the window service, make sure the process uaservices.exe is not running (or stop it from Windows task manager). Then log in to Sybase Control Center again.

Scenario 5: This may happen if you upgraded Sybase Unwired Platform to a newer version, and changed the server host name.

Solution: You need to complete some extra steps:

Change the listener prefix of httpListeners and iiopListeners for the new hostname in the new server's properties file:
```
Repository\Instance\com\sybase\djc\server\ApplicationServer\default.properties,  <new_hostname>.properties
```
In Repository\Instance\com\sybase\djc\server\SocketListner\*.properties, rename all the <old_hostname>_<protocol>.properties into <new_hostname>_<protocol>.properties.
Use dbisqlc to update the table: cluster_installation in clusterdb, update cluster_installation set hostname='<new_hostname>' where hostname='<old_hostname>'.