List of Known Issues for Afaria

This topic lists known issues associated with Afaria.

Table 1. Afaria issues
CR#	Description
568862	Afaria database port cannot be changed after installation. Sybase Unwired Platform 1.2 does not support changing the Afaria database port after installation. Workaround: None.
566617	Afaria fails to download files if the primary Unwired Server in a cluster is stopped. If you set up a cluster for Afaria servers and Unwired Servers, and then stop the primary Unwired Server, Afaria can fail to download files, and this error is recorded in the authorizor.log file: Unwired Server unavailable on known ports Workaround: Restart the primary Unwired Server.
563716	Assignments information unavailable from Afaria Administrator if LDAP server has not been started. If the LDAP server has not been started, clicking the Policies and Profiles link in the Afaria Administrator displays the error message, `Unable to access assignments information`. This is normal behavior when Afaria is not able to connect to the LDAP Server. Workaround: When this message displays, click OK to close the message box and open the profiles page. You can avoid this problem by configuring Afaria to use the same server as Sybase Control Center and Unwired Server. See the online help topic, Sybase Control Center > Configure > Unwired Platform > Configuring Afaria in the workflow that is appropriate to your deployment type.
563494	Afaria client cannot communicate with relay server version 11.0.0.1578. If relay server version 11.0.0.1578 is not configured, Afaria and Unwired Server clients both encounter the error message below when they attempt to communicate with the relay server: The connection to the server failed. Session did not complete. Workaround: Use relay server version 11.0.0.1562. If you must use version 11.0.0.1578, follow these steps: Change the directory to: \Inetpub\AdminScripts. Run the following console commands: `cscript adsutil.vbs set w3svc/1/uploadreadaheadsize 0` `iisreset`
558417	Changing Afaria server host or port requires manual update to the Afaria Administrator URL. If you change the Afaria server host name or port number, you must manually change the Afaria Administrator launch URL to match. Workaround: See the online help: Sybase Control Center > Configure > Unwired Platform > Configuring Afaria and locate the Configuring the Afaria Administrator URL topic in the workflow that is appropriate for your deployment.