Description of problem: Every use of RDP console in Windows XP SP3 IE 8 8.0.6001.18702 crashes IE but the IE tab is recovered. Event Type: Error Event Source: Application Error Event Category: None Event ID: 1000 Date: 2/7/2013 Time: 10:00:03 PM User: N/A Computer: TESTXP Description: Faulting application iexplore.exe, version 8.0.6001.18702, faulting module mstscax.dll, version 6.0.6001.18589, fault address 0x00059c19. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 41 70 70 6c 69 63 61 74 Applicat 0008: 69 6f 6e 20 46 61 69 6c ion Fail 0010: 75 72 65 20 20 69 65 78 ure iex 0018: 70 6c 6f 72 65 2e 65 78 plore.ex 0020: 65 20 38 2e 30 2e 36 30 e 8.0.60 0028: 30 31 2e 31 38 37 30 32 01.18702 0030: 20 69 6e 20 6d 73 74 73 in msts 0038: 63 61 78 2e 64 6c 6c 20 cax.dll 0040: 36 2e 30 2e 36 30 30 31 6.0.6001 0048: 2e 31 38 35 38 39 20 61 .18589 a 0050: 74 20 6f 66 66 73 65 74 t offset 0058: 20 30 30 30 35 39 63 31 00059c1 0060: 39 0d 0a 9.. Version-Release number of selected component (if applicable): sf6 How reproducible: 100% Steps to Reproduce: 1. windowx xp sp3 ie8 2. to make rdp client working you have to in IE: Tools -> Internet Options -> Advanced -> Reset (restart IE) 3. log in User Portal 4. have RDP as console, click once per active x, 2nd time for opening console (remote access to guest has to be enabled, vm name should be resolvable by dns) Actual results: after each rdp console session, ie with user portal crashes Expected results: should work without crash Additional info:
Regression from 3.1.2?
Windows XP sp3 IE8 with latest updates make same issue on 3.1 and 3.2.
But who's issue do we think this is, are we using the wrong activex control ID?
Since it happens on both 3.1 and 3.2, seems to me that it might be a winxp/sp3/rdp issue, rather than a GUI issue. google-ing this brought up a few suggestions: Jiri: - Did you try it on several clients (maybe this client that you have tried has a problem in particular)? - what happens on WinXP without sp3? - what happens on other browsers/OSs (win 7/8 + IE9/10)? - can you please try following the steps in http://compinfopro.com/remote-desktop-connection-encountered-problem-close/ to see if it helps? - there are also some suggestions on the web to try and re-install RD and clear Trojans... (http://www.pcreview.co.uk/forums/rdc-crashes-connect-t3837165.html) - any chance that this helps as well?
> - Did you try it on several clients (maybe this client that you have tried has a problem in particular)? Yes but this is Windows SP3 specific. > - what happens on WinXP without sp3? I have no Windows XP prior SP3. Anyway sugesting old Windows is problem as we have to expect users have their Windows XP up to date. > - what happens on other browsers/OSs (win 7/8 + IE9/10)? Works OK. > - can you please try following the steps in http://compinfopro.com/remote-desktop-connection-encountered-problem-close/ to see if it helps? > - there are also some suggestions on the web to try and re-install RD and clear Trojans... (http://www.pcreview.co.uk/forums/rdc-crashes-connect-t3837165.html) - any chance that this helps as well? I will check.
> - can you please try following the steps in http://compinfopro.com/remote-desktop-connection-encountered-problem-close/ to see if it helps? > - there are also some suggestions on the web to try and re-install RD and clear Trojans... (http://www.pcreview.co.uk/forums/rdc-crashes-connect-t3837165.html) - any chance that this helps as well? First one is irrelevent because my Windows XP includes SP3, it was part of installation media. Second one - scan for malware, well nothing was found.
(In reply to comment #6) > > - can you please try following the steps in http://compinfopro.com/remote-desktop-connection-encountered-problem-close/ to see if it helps? > > > First one is irrelevent because my Windows XP includes SP3, it was part of > installation media. > Can you please try following the steps there anyway? The article says "You could get this error by installing SP3" - I am not sure if the errors happens due to the SP3 installation process itself, or if it happens due to SP3 In general.
I would say it is probably part of Windows XP SP3, I cannot reinstall, the media used included inside itself SP3, thus it was not separate SP.
Same problem has started to appear on w2k8 32/64bit IE 9.0.8112.16421. It is even bigger problem when autoconnect is used and VM inside User Portal is Windows 8 or w2k12 because these ones use RDP as default. Thus in this scenario it is failing in the loop. Simon, it seems nobody was touching this, just talking and talking...
Are we sure that we shouldn't be using a different classid? See here : http://msdn.microsoft.com/en-us/library/windows/desktop/aa383541(v=vs.85).aspx
The problem is with incorrect cleanup of the rpd client object - that CLSID works ok on XP.
merged U/S fa10641c3484ea10d0b1b33ef8e3d656b5e6dd35
(In reply to comment #15) > The problem is with incorrect cleanup of the rpd client object - that CLSID > works ok on XP. Two questions First - under one circumstances would this be triggered. Second - if we're changing this code then why not add the conditional logic to put in the correct CLSID? It seems wrong that we're doing it this way - we are clearly going against the Microsoft documentation. Maybe we will remain "lucky" and this will not break later but it seems reckless to count on that.
Andy, we don't have time to investigate the impact of changing CLSID, I'd not rather risk it for 3.2 as it won't get proper testing of all combinations. For 3.3 it makes sense perhaps
OK, sf15 (wxp and w2008 as described above).
3.2 has been released