RE: Remote Desktops MMC snapin causing error report
- From: nass <nass@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 18 Jan 2007 12:14:01 -0800
Thanks Rob for the Feedback and the Info.
Good luck.
Regards,
nass
"Rob" wrote:
My problem is solved. I went through my current user registry hive and.
deleted items having to do with the terminal server client and remote
desktops and everything seems to be working now.
"Rob" wrote:
No, the antivirus/firewall is not causing the problem. I tried using the
Remote Desktops as another user and the error did not come up so it must be
something with my user profile. I tried searching through the registry for
remote desktop and deleted certain entries that I knew would be safe to
delete but that didn't help.
I did find that if I deleted the cache files in the Terminal Server Client
cache "C:\Documents and Settings\{Username}\Local Settings\Application
Data\Microsoft\Terminal Server Client\Cache" that the crash report wouldn't
come up as quickly. Normally the crash occurs after I click on the server I
want to connect to and before the login screen comes up for that server. When
I clear the cache and try to connect, the error pops up after the login
screen appears which is right when a new cache file is generated. I tried
this a few times just to be sure it wasn't a coincidence. I also tried
excluding that folder from the antivirus scan but that didn't help.
I know I could trash my profile to generate a new one which would probably
fix it but I don't want to have to reset all my settings. If someone can
think of a fix for this that would be much appreciated.
"nass" wrote:
"Rob" wrote:
Also I forgot to mention that I don't have problems with any other MMC
snapins. Here's a copy of the Event Viewer entry as well:
Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date: 1/17/2007
Time: 1:23:00 PM
User: N/A
Computer: XXXXXX
Description:
Faulting application mmc.exe, version 5.1.2600.2180, faulting module
unknown, version 0.0.0.0, fault address 0x1002b1af.
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 6d 6d 63 ure mmc
0018: 2e 65 78 65 20 35 2e 31 .exe 5.1
0020: 2e 32 36 30 30 2e 32 31 .2600.21
0028: 38 30 20 69 6e 20 75 6e 80 in un
0030: 6b 6e 6f 77 6e 20 30 2e known 0.
0038: 30 2e 30 2e 30 20 61 74 0.0.0 at
0040: 20 6f 66 66 73 65 74 20 offset
0048: 31 30 30 32 62 31 61 66 1002b1af
0050: 0d 0a ..
"Rob" wrote:
I am having a problem with the Remote Desktops MMC (Microsoft Management
Console) snapin causing an error popup every time I try to connect to a
server. When I first got the error it was actually DEP (Data Execution
Prevention) saying it had to close MMC. I then disabled DEP for MMC and
rebooted the machine. After that I started getting the error reporting
window. If I move the error report window out of the way I can continue to
work in the MMC snapin so it seems as though Windows is incorrectly detecting
a crash.
I am running Windows XP SP2 and the error occurs when I try to connect to
Windows 2003 SP1 and Windows 2000 SP4 servers. I have been using the Remote
Desktops snapin for a long time with no problems. I tried using Remote
Desktop Connection and that connects with no problems.
I also tried deleting the snapin and reinstalling it using the adminpak.msi
install. Still having the problem.
Any suggestions on how to stop the error report from coming up?
Do you have Anti-virus/firewall that can block the traffics?.
If you have another user account does the error occur when you try or try to
create another account and try to see if that help.
HTH.
Regards,
nass
- References:
- Prev by Date: Re: Msconfig
- Next by Date: Re: Alternative to Slipstream XP/SP2?
- Previous by thread: RE: Remote Desktops MMC snapin causing error report
- Next by thread: Active Program detection/Flash drive hits
- Index(es):
Relevant Pages
|
