Each section below uses the symptom as its title and then provides the cause and actions to take to resolve the situation.

To develop a mashup that responds to the user not having the Remote Access Client installed, the ClientNotInstalled event will fire if after a timeout period the client does not identify itself to the mashup. The value of that timeout can be configured, and may need to be adjusted from the default (10 seconds, specified in milliseconds) if there is a long wait time for some mashup feature to display to the user (a link to download the client, for instance) or if that mashup feature is displaying in error when the client is installed.

CAUSE: The "Timeout to indicate that the Remote Access Client is not installed locally" configuration parameter needs adjustment.

ADMINISTRATOR ACTION: From the Configuration page for the RemoteAccessSubsystem, raise or lower the timeout to fit the needs of the installation environment. Specify the new value in milliseconds. Here is the page, with the default timeout setting displayed:

CAUSES: The majority of the reasons the launch of the client might fail are specific to the type of Remote Access and are enumerated in the following topics:

However, one general reason for this symptom is that the call to the StartSession service failed. This cause is the common reason for this event to be fired. Refer to Symptom: Call to StartSession service fails for cause and administrator actions.