Prev: TS Cals with Technet?
Next: TSE 2008 AND FUNCTION DOMAIN 2003
From: John Källén on 15 Jan 2009 17:16
Ever since December I've been having serious problems connecting to remote
machines using RDC. I have version 6.0.6001 of RDC on my fully patched
Windows XP SP3 system, no weird plug-ins that I'm aware of.

Two to four seconds after clicking on 'Connect' it displays the "...has
encountered a problem and needs to close..." dialog box. Always.

Since I'm a programmer, I gleefully push the "Debug" button. The VS2005
debugger informs me of an unhandled exception at virtual address 0x4D86B2F5
in mstsc.exe reading a null pointer. The stack trace looks like this:
> mstscax.dll!4d86b2f5()
[Frames below may be incorrect and/or missing, no symbols loaded for
mstscax.dll]
mstscax.dll!4d883f4a()
mstscax.dll!4d86b44c()
mstscax.dll!4d7a5249()
mstscax.dll!4d85c558()
mstscax.dll!4d85a852()
mstscax.dll!4d85a8b0()
mstscax.dll!4d7e96e9()
mstscax.dll!4d7eaba4()
mstscax.dll!4d787579()
mstscax.dll!4d787579()
mstscax.dll!4d787579()
mstscax.dll!4d8267f6()
mstscax.dll!4d7a5172()
mstscax.dll!4d862e5c()
mstscax.dll!4d86428c()
mstscax.dll!4d862681()
mstscax.dll!4d883f4a()
mstscax.dll!4d8647e4()
mstscax.dll!4d862b02()
ntdll.dll!7c90f641()
ntdll.dll!7c90dccc()
mswsock.dll!71a67dd6()
mswsock.dll!71a60f6b()
mswsock.dll!71a60f79()
mswsock.dll!71a544a8()
mstscax.dll!4d7f93eb()
mswsock.dll!71a544a8()
ws2_32.dll!71ab67de()
mstscax.dll!4d83b21d()
mstscax.dll!4d78062a()
mstscax.dll!4d787311()
mstscax.dll!4d780650()
mstscax.dll!4d787324()
mstscax.dll!4d7e97db()
mstscax.dll!4d805864()
mstscax.dll!4d7f8944()
mstscax.dll!4d7fa242()
mstscax.dll!4d7f1e4f()
mstscax.dll!4d7ec468()
mstscax.dll!4d8392dd()
mstscax.dll!4d83b453()
mstscax.dll!4d83b99e()
user32.dll!7e418734()
user32.dll!7e418816()
user32.dll!7e4189cd()
user32.dll!7e419402()
user32.dll!7e418a10()
mstscax.dll!4d78084f()
mstscax.dll!4d8646eb()
mstscax.dll!4d7d1389()
mstscax.dll!4d7c21ec()
mstscax.dll!4d865b82()
mstscax.dll!4d78216e()
kernel32.dll!7c80b713()

Is this a known issue? RDC is totally broken for me now, and I really need
to be able to use it for my work.
--
John Källén - johnkal(a)DELETEMEgmail.com
From: TP on 16 Jan 2009 14:10
Hi,

I do not know what is happening in your case. Here are
some suggestions:

- Delete the bitmap cache files located here:

C:\Documents and Settings\username\Local Settings\Application Data\Microsoft\Terminal Server Client\Cache

- Unregister and re-register the mstscax.dll:

regsvr32 /u c:\windows\system32\mstscax.dll
regsvr32 c:\windows\system32\mstscax.dll

Thanks.

-TP

John Källén wrote:
> Ever since December I've been having serious problems connecting to
> remote machines using RDC. I have version 6.0.6001 of RDC on my fully
> patched Windows XP SP3 system, no weird plug-ins that I'm aware of.
>
> Two to four seconds after clicking on 'Connect' it displays the
> "...has encountered a problem and needs to close..." dialog box.
> Always.
>
> Since I'm a programmer, I gleefully push the "Debug" button. The
> VS2005 debugger informs me of an unhandled exception at virtual
> address 0x4D86B2F5 in mstsc.exe reading a null pointer. The stack
> trace looks like this:
>> mstscax.dll!4d86b2f5()
> [Frames below may be incorrect and/or missing, no symbols loaded for
> mstscax.dll]
> mstscax.dll!4d883f4a()
> mstscax.dll!4d86b44c()
> mstscax.dll!4d7a5249()
> mstscax.dll!4d85c558()
> mstscax.dll!4d85a852()
> mstscax.dll!4d85a8b0()
> mstscax.dll!4d7e96e9()
> mstscax.dll!4d7eaba4()
> mstscax.dll!4d787579()
> mstscax.dll!4d787579()
> mstscax.dll!4d787579()
> mstscax.dll!4d8267f6()
> mstscax.dll!4d7a5172()
> mstscax.dll!4d862e5c()
> mstscax.dll!4d86428c()
> mstscax.dll!4d862681()
> mstscax.dll!4d883f4a()
> mstscax.dll!4d8647e4()
> mstscax.dll!4d862b02()
> ntdll.dll!7c90f641()
> ntdll.dll!7c90dccc()
> mswsock.dll!71a67dd6()
> mswsock.dll!71a60f6b()
> mswsock.dll!71a60f79()
> mswsock.dll!71a544a8()
> mstscax.dll!4d7f93eb()
> mswsock.dll!71a544a8()
> ws2_32.dll!71ab67de()
> mstscax.dll!4d83b21d()
> mstscax.dll!4d78062a()
> mstscax.dll!4d787311()
> mstscax.dll!4d780650()
> mstscax.dll!4d787324()
> mstscax.dll!4d7e97db()
> mstscax.dll!4d805864()
> mstscax.dll!4d7f8944()
> mstscax.dll!4d7fa242()
> mstscax.dll!4d7f1e4f()
> mstscax.dll!4d7ec468()
> mstscax.dll!4d8392dd()
> mstscax.dll!4d83b453()
> mstscax.dll!4d83b99e()
> user32.dll!7e418734()
> user32.dll!7e418816()
> user32.dll!7e4189cd()
> user32.dll!7e419402()
> user32.dll!7e418a10()
> mstscax.dll!4d78084f()
> mstscax.dll!4d8646eb()
> mstscax.dll!4d7d1389()
> mstscax.dll!4d7c21ec()
> mstscax.dll!4d865b82()
> mstscax.dll!4d78216e()
> kernel32.dll!7c80b713()
>
> Is this a known issue? RDC is totally broken for me now, and I really
> need to be able to use it for my work.

From: johnkal on 9 Feb 2009 14:34
On 16 Jan, 20:10, "TP" <tperson.knowsp...(a)mailandnews.com> wrote:
> Hi,
>
> I do not know what is happening in your case.  Here are
> some suggestions:
>
> - Delete the bitmap cache files located here:
>
> C:\Documents and Settings\username\Local Settings\Application Data\Microsoft\Terminal Server Client\Cache
>
> - Unregister and re-register the mstscax.dll:
>
> regsvr32 /u c:\windows\system32\mstscax.dll
> regsvr32 c:\windows\system32\mstscax.dll
>
> Thanks.
>
> -TP

No joy, the error perseveres. Any other tips? This is a killer problem
for me.

John.
 | 
Pages: 1
Prev: TS Cals with Technet?
Next: TSE 2008 AND FUNCTION DOMAIN 2003