KBA-01231: Spitfire Dashboard on Terminal Server


You experience unexpected load from sfPMS users on a terminal server.


The easiest solution is to run sfPMS on the user‘s local computer rather than via remote desktop terminal server sessions.  Some sfPMS users may need resources such as office or Microsoft Dynamics SL, but other users may only need the browser-based tools which are readily available on their native workstations. If terminal server users report they cannot log on to the terminal server (or get the ‘RPC server is too busy to complete this operation‘ error message)  on a computer that is running Windows Server 2003 with Service Pack 1, see http://support.microsoft.com/?kbid=905700. If the terminal server event log is filling up with .NET Runtime errors indicating ‘Unable to open shim database‘, see FIX: A .NET Framework 2.0-based application may require read/write permissions to a registry key even though the application only has to read the registry key at http://support.microsoft.com/kb/918642/en-us.

KBA-01231; Last updated: October 14, 2016 at 13:44 pm;