12-08-2010 12:22 AM
Every time I try to sync, the program aborts on my PC (Win7). This is a new problem for the last few days. Uninstalled and reinstalled desktop manager.
info from event log:
Log Name: Application
Source: Windows Error Reporting
Date: 12/8/2010 12:00:34 AM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: BobInnerSanctum
Description:
Fault bucket 1360865384, type 5
Event Name: CLR20r3
Response: Not available
Cab Id: 0
Problem signature:
P1: rim.desktop.exe
P2: 6.0.0.43
P3: 4c758111
P4: mscorlib
P5: 2.0.0.0
P6: 4bebd50b
P7: f50
P8: 7
P9: N3CTRYE2KN3C34SGL4ZQYRBFTE4M13NB
P10:
Attached files:
C:\Users\bob\AppData\Local\Temp\WER892D.tmp.WERInt
These files may be available here:
C:\Users\bob\AppData\Local\Microsoft\Windows\WER\R
Analysis symbol:
Rechecking for solution: 0
Report Id: df04e09f-0287-11e0-879f-001d609c8eb6
Report Status: 0
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/ev
<System>
<Provider Name="Windows Error Reporting" />
<EventID Qualifiers="0">1001</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2010-12-08T05:00:34.000000000Z" />
<EventRecordID>77668</EventRecordID>
<Channel>Application</Channel>
<Computer>BobInnerSanctum</Computer>
<Security />
</System>
<EventData>
<Data>1360865384</Data>
<Data>5</Data>
<Data>CLR20r3</Data>
<Data>Not available</Data>
<Data>0</Data>
<Data>rim.desktop.exe</Data>
<Data>6.0.0.43</Data>
<Data>4c758111</Data>
<Data>mscorlib</Data>
<Data>2.0.0.0</Data>
<Data>4bebd50b</Data>
<Data>f50</Data>
<Data>7</Data>
<Data>N3CTRYE2KN3C34SGL4ZQYRBFTE4M13NB</Data>
<Data>
</Data>
<Data>
C:\Users\bob\AppData\Local\Temp\WER892D.tmp.WERInt
<Data>C:\Users\bob\AppData\Local\Microsoft\Windows
<Data>
</Data>
<Data>0</Data>
<Data>df04e09f-0287-11e0-879f-001d609c8eb6</Data>
<Data>0</Data>
</EventData>
</Event>
HELP! Thanks
12-08-2010 01:07 PM
Any solutions to this issue yet? I am having the same problem.
12-08-2010 03:42 PM
I deinstalled and reinstalled the desktop manager. Now only occurs intermittently, but still an issue.
Anyway to get this stuff to RIM so they can fix it?