Unable to Logon to Windows Server 2003 R2 by RDP - the RDP client would not even entertain the idea of a connection. Just had a quick look and 'computer said NO!'.
Also, when trying to log on locally, the local profile cannot be loaded due to insufficient resources (WHAT!!) and events 1508 and 1505 in the event log. I have thoughtfully been given a temporary profile to use.Cause:
Initially i thought it was something to do with the Terminal Services having some stale profiles. Indeed in the past, I have been able to use another server, connect to the main servers Terminal Server Management and log out the sessions and reset the RDP TCP listener. After a few minutes i was able to log in.Not this time.
After some searching, an unlikely culpret seemed to be the ctfmon.exe file that Windows aparently uses for voice recognition. Interestingly this is installed as part of the Office install which then becomes part of the OS - however this server has never had Office installed on it.
After killing the process, immediately RDP worked.
More info on this issue can be found here;How to turn off the speech recognition and the handwriting recognition features in Office 2003
another possible issue that may arise, could use this solution;Error message when you try to log on to a Windows Server 2003-based terminal server: "Windows cannot load the user's profile but has logged you on with the default profile for the system"