Help - Outlook Client Crashing

Appologies if this has appeared before, but I am not an expert at using these forums. My Outlook (2003, all service packs), on XP Pro (all service packs), is crashing after about 6 or seven hours after the desktop redirector is activated. It might transmit 30 to 40 messages, and then in a send/ receive cycle, simple hang (outlook only, the redirector is still running). This does not happen with the redirector service off. I am using desktop software version 4.5.0.15 and redirector version 3.6.0.68. I have never had any kind issue with outlook until i have installed and activate the redirector software.
I cannot use the internet service as i have several incoming email addresses i need sent to my phone
Please help?

If I was a mind reader I could answer your problem in an instant. but since I'm not You are going to need to supply more information. What OS? What computer? for starters. does the problem persist in a new user?

Similar Messages

Since I've installed Mountain Lion, I am having lock up issues with multiple programs. MS Outlook has crashed and I've lost all my folders. HELP?

Since I've installed Mountain Lion, I am having lock up issues with multiple programs. MS Outlook has crashed and I've lost all my folders. HELP?

okay I've finally been able to get tor and all the other programs to work according to my plan the only thing that's still making problems is that iptables doesn't work as I want it to, when I start chromium without proxy settings privoxy doesn't seem to forward the information to polipo.. do I need to add another rule to iptables.rules in order for the program to know it has to reroute the information again or how can I get this to work? and is there any way to run rtorrent with proxy support?
anyway, problem 2 and 3 are still to be solved.
and does anybody know where i can get a good dansguardian blacklist that was not designed for 6 year old children and for which I don't need to subscribe? I'm still getting these partypoker popups -.-
//e: with iptables it's the same thing as described in the first post. https works, http doesnt. I get the output "Invalid header received from client." on http sites. still no idea why though.. (and the https-version of torcheck.xenubite says i'm tor unprotected while starting the browser with iptables)
Last edited by deF291 (2011-04-23 16:16:31)

After updating to Firefox 3.6.9 Microsoft Outlook and Eudora email client crashed repeatedly, unding update restored normal operation.

Firefox automatically updated when I turned computer on - 9 Sept - but repeated attempts to start M'soft Outlook resulted in calendar screen showing for a second then Outlook crashed. Eudora email client crashed when attempting to send emails. Tried rebooting, but same result. On 10 Sept selected System Restore and restored to 8 Sept restore point, Outlook and Eudora now operate normally.
Event viewer Application showed this for Eudora crash -
Faulting application eudora.exe, version 6.2.3.4, faulting module ntdll.dll, version 5.1.2600.5755, fault address 0x00010a19.
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 65 75 64 ure eud
0018: 6f 72 61 2e 65 78 65 20 ora.exe
0020: 36 2e 32 2e 33 2e 34 20 6.2.3.4
0028: 69 6e 20 6e 74 64 6c 6c in ntdll
0030: 2e 64 6c 6c 20 35 2e 31 .dll 5.1
0038: 2e 32 36 30 30 2e 35 37 .2600.57
0040: 35 35 20 61 74 20 6f 66 55 at of
0048: 66 73 65 74 20 30 30 30 fset 000
0050: 31 30 61 31 39 0d 0a 10a19..

Firefox automatically updated when I turned computer on - 9 Sept - but repeated attempts to start M'soft Outlook resulted in calendar screen showing for a second then Outlook crashed. Eudora email client crashed when attempting to send emails. Tried rebooting, but same result. On 10 Sept selected System Restore and restored to 8 Sept restore point, Outlook and Eudora now operate normally.
Event viewer Application showed this for Eudora crash -
Faulting application eudora.exe, version 6.2.3.4, faulting module ntdll.dll, version 5.1.2600.5755, fault address 0x00010a19.
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 65 75 64 ure eud
0018: 6f 72 61 2e 65 78 65 20 ora.exe
0020: 36 2e 32 2e 33 2e 34 20 6.2.3.4
0028: 69 6e 20 6e 74 64 6c 6c in ntdll
0030: 2e 64 6c 6c 20 35 2e 31 .dll 5.1
0038: 2e 32 36 30 30 2e 35 37 .2600.57
0040: 35 35 20 61 74 20 6f 66 55 at of
0048: 66 73 65 74 20 30 30 30 fset 000
0050: 31 30 61 31 39 0d 0a 10a19..

Crash of com.apple.Outlook.client.exe

Hello
we have a new Toshiba with windows 7 and outlook 2003.
Tried to sync with an iPhone 3GS
It tells in iTunes it synced succesfully; but in the background the "com.apple.Outlook.client.exe" crashes.
Outlook then tells me it cannot access the calendar/contacts because it cannot access the folders because a process accessing the folder crashed.
Quit outlook and reopen it again brings it back.
errors are (translated from German):
Name of faulty application : com.apple.Outlook.client.exe, Version: 17.89.0.10, timestamp: 0x4cb91bf4
Name of faulty moduls: mspst32.dll, Version: 11.0.8317.0, timestamp: 0x4ae0c06f
exception: 0xc0000005
Error-offset: 0x0001e58b
ID of faulty Process: 0x1984
starttime of faulty application: 0x01cbbbd0218270f5
path of faulty application: C:\Program Files (x86)\Common Files\Apple\Mobile Device Support\com.apple.Outlook.client.exe
path of faulty module: C:\Program Files (x86)\Common Files\SYSTEM\MSMAPI\1031\mspst32.dll
what can be done except:
- installed all updates (win and office)
- installed itunes a new
- rename mspst32.dll to mspst32-old.dll (got a new one with the same data)
greets,
Jack

I have a similar problem. I don't sync with outlook though, (I just sync with exchange server wirelessly). However, when iTunes starts, com.apple.outlook.client.exe uses alot of resources and I can't open any MS Office documents.
I close iTunes, process still runs, documents don't open. I highlight it and "end process" and all the documents I was trying to open pop up.
So far I haven't seen any effect of ending that process after iTunes is closed. I can't promise anything though. But it worked for me.
I'd like to see it fixed though, kind of a pain to have to do that.

Exchange Emails Not Showing Up On IPhone with Outlook Client Closed

I have been trying to fix this problem and I want to see if anybody else has run across this issue and found the fix. I am having a problem accessing Exchange Emails from my work system, but only under the following scenario:
1) When my work PC is powered on, logged in, and Outlook client is up and active I can send and receive emails on my IPhone with no problems and it correctly displays read and unread messages.
but...
2) When I close my Outlook client on my PC my IPhone is no longer able to retrieve new email messages. I have had this problem since first getting the 3G phone in August of '08 and it is has been updated with each firmware release but the problem persists.
This is driving me crazy, any help or confirmation that others are experiencing the problem is much appreciated.
Thanks.

If you select one month for mail days to sync, only one month's worth will be synced and available - the last month which will be constantly changing to the most recent 30 days. Select No Limit for Mail Days to Sync.
Show 1000 recent messages is for the selected mailbox only and if there are more than 1000 messages in a mailbox and you have one month for mail days to sync selected, if the last 30 days for the mailbox includes 100 messages, only 100 messages will be available.
Are these additional server stored mailboxes separate mailboxes and what I mean by that is not sub-mailboxes for the Inbox mailbox?
Since you have had this issue with other operating systems, the common denominator is your Hotmail account. Have you contacted Hotmail technical support regarding this issue you have had with other operating systems?
All server stored mailboxes with an Exchange account should be available with the email client used to access the account. If all are not available when accessing the account as an Exchange account with an email client, something is wrong with your setup for these mailboxes at the server level.

App-V CRM 2013 Outlook Client and Office 2013 Click to Run

Hi,
I'm trying to get going with enbing the CRM 2013 for Outlook client with the VL version of Office Pro Plus 2013. I have successfully published and use Office App-V package in a test environment. App-V version 5.0 SP2 is installed on the client
PC (Windows 7 64bit). SCCM 2012 R2 is used to publish APP-V applications to user groups.
I have sequenced the CRM 2013 Outlook client (offline mode disabled) with UR2 and published it using SCCM as a "Add-on or Plug-in. I've also created a connection group so that the App-V version of Office 2013 is able to connect to the sequenced
CRM client. The client installs successfully, but the CRM tab doesn't appear in the Outlook Ribbon, and the Configuration Wizard crashes each time it is launched. The App-V event log is blank (which I'm taking to be a good sign). All CRM
client prerequisites have been preinstalled on the target PC.
I'm thinking that the CRM client can't see the Outlook application and therefore crashes and doesn't integrate with the Outlook application. Problem Signature 09 (from the crash explanation) states "System.NullReference Exception".
I can't seem to find much out there for sequencing the 2013 version of the client. Has any else managed this yet or have any ideas where I'm going wrong?
Thanks,
Tim

Hello,
I would use Process Monitor to understand what happens and to see why Outlook isn't seeing the plugin, and why the wizard is crashing
Nicke Källén | The Knack| Twitter:
@Znackattack

Lync 2013 RTM client crashing on startup in Windows 8 RTM

Lync 2013 client crashes during startup with the following event:
Faulting application name: lync.exe, version: 15.0.4420.1017, time stamp: 0x5067326f
Faulting module name: KERNELBASE.dll, version: 6.2.9200.16384, time stamp: 0x5010ac2f
Exception code: 0xe06d7363
Fault offset: 0x00014b32
Faulting process id: 0x15bc
Faulting application start time: 0x01cdc372c8b81886
Faulting application path: C:\Program Files (x86)\Office 2013\Office15\lync.exe
Faulting module path: C:\Windows\SYSTEM32\KERNELBASE.dll
Report Id: 06d225ad-2f66-11e2-be7f-000ffedc7546
I'm running Windows 8 64-bit, but Office 32-bit for compatibility reasons. Office 2010 and Lync 2010 worked beautifully. Other Office 2013 applications work fine. Lync 2010 client works fine as well. Only see this problem with Lync 2013.
Any ideas how to troubleshoot or correct?

Hi,
Have you tried to remove Lync 2010 client and test it again?
How about the other machines? Please also log on the problem machine with another account and test it.
Please try to disable any local antivirus software to see if that fixes the issue.
Please remove Silverlight and reinstall it:
http://www.microsoft.com/silverlight/
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

How to find out what server the outlook client is connected to/change it automatically

Hi,
I am performing a server migration from Exchange 2010 to Exchange 2010 (the previous installation was installed by an outsourced provider and is rubbish so I'm configuring it properly). On the of things the existing server lacks is a CAS array configured,
so I have built the new Exchange 2010 server, configured a new DB and CASArray. I have created a brand new mailbox for a new user and the user's outlook shows it is connected to casarray.domain.local, I have migrated my own mailbox but internally my outlook
shows it is connected to oldserver.domain.local (under the account settings when you go to change the settings for the account), this is on a domain joined internal desktop. But at home on my personal laptop non-domain joined, it has appeared to reflect the
new casarray.domain.local. The outlook client is 2007 in both situations.
When I run the following command, it shows my mailbox is indeed connected to the new exchange server, but this is not true in outlook
Get-LogonStatistics -Server "new-exch2010" | where {$_.clientname -eq "new-exch2010"}| ft username,servername,clientname
If I run the above command against the old server my name shows on that list as well. When I look at the connection status of my outlook it shows that it is connected to casarray for directory, but the old server for mail.
A couple of other things:
Mailflow is now going to the new exchange server from the gateway over port 25, the autodiscover record in the internal DNS is now also pointing to the new exchange server, outlook clients and users computers have been completely restarted but still don’t
seem to pick up the new settings, both the old server and new server functions as a multi-role exchange having the Hub, CAS and MBX roles.
Now that you have all that background info my question is two parts:
What is the correct powershell command I can run on the exchange server to ensure that all my outlook clients are connected to the new exchange server for all connection types (or identify those which are connected against the old server)?
How do I get the outlook clients to automatically pick up the casarray servername once their mailboxes have been migrated?
I am considering removing the CAS from the old server which may force outlook to find it’s new server but am unsure whether this will work or not, and I think I should migrate all the mailboxes into the new DB before I do this.
Other than that, I am out of ideas.
Appreciate, any help. Thanks
Steve

I had already run the command Get-MailboxDatabase | FL Identity,RpcClientAccessServer
and it only identified the old database as being tied to the server name, the new database has the correct casarray and all mailboxes are in this new database. should I also set the old database to point to my casarray as the second command indicates? can't
do any harm right?
also, I have outlook 2007 and 2013 at home and both of them had automatically reconfigured
themselves to point to casarray, my problem is with the internal clients.
today I have also noticed in DNS there is a Zone which points to autodiscover.domain.co.uk
and in there it points to my old server.
a few things to note about the above:
1. the zone is pointing to the .co.uk domain not the .local - is this correct?
2. should that zone even be in our internal DNS, i hadn't noticed on previous implementation
of Exchange I have done
3. if i change the record within that zone to point to my new server, will this likely show
up the popup message shown in this link http://www.rackspace.com/apps/support/portal/1218 I havent yet got a certificate for the new exchange server (few more days) and i dont want users seeing any kind of untrusted unsecure connection box or it
will only lead to panic and flooding the helpdesk
many thanks
Steve

Internal outlook client connectivity in exchange 2010 when coexist with exchange 2013

Hi all ,
on my side i would like to clarify few queries.
Say for instance i am coexisting exchange 2010 with exchange 2013 .Unfortunately if all of my exchange 2013 servers goes down .
Q1 .On that time will the internal outlook users having their mailboxes on exchange 2010 can be able to connect mailboxes without any issues ? In case if they face any issues what kind of issues will they be? Because why i am asking is we should have pointed
the autodiscover service to exchange 2013 during coexistence.
When an user closes and reopens the outlook after whole exchange 2013 environment failure ,outlook will first query the autodiscover service for the profile changes to get it updated on users outlook profile.In such case autodiscover service will not be
reachable and i wanted to know will that affects the internal client connectivity for outlook users having their mailboxes on exchange 2010.
Q2. Apart from outlook internal users connectivity ,what kind of exchange services(i.e owa,active sync,pop,external OA and imap) will get affected when whole exchange 2013 environment goes down during coexistence ?
I have read the below mentioned statement on this awesome blog but still i wanted to clarify with you all on my scenario.
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx<o:p></o:p>
Internal Outlook Connectivity
For internal Outlook clients using RPC/TCP connectivity whose mailboxes exist on Exchange 2010, they will still connect to the Exchange 2010 RPC Client Access array endpoint.
For internal Outlook clients using RPC/TCP connectivity whose mailboxes exist on Exchange 2007, they will still connect directly to the Exchange 2007 Mailbox server instance hosting the mailbox.
Please share me your suggestions and that would help me a lot .
Regards
S.Nithyanandham

Hi Winnie Liang ,
Thanks a lot for your reply.
Scenario 1 : for internal outlook connectivity
We have below settings for exchange 2010 autodiscover.
mail.domain.com - will be the namespace for internal autodiscover URI for all the exchange 2010 cas serves
We are going to have below settings for exchange 2013 autodiscover.
mail.domain.com - will be the namespace for internal autodiscover URI for all the exchange 2013 cas serves
During coexistence mail.domain.com will be pointed to exchange 2013 cas servers . I mean to say if we try to resolve the mail.domain.com it will get resolved in to the exchange 2013 cas servers.
So on such case if anything happened wrong to the new environment or else if entire environment goes down .Do we face any issues while outlook users connect to existing mailboxes in exchange 2010 ?
Because why i am asking is ,on the below mentioned article i have read all the autodiscover request will go via exchange 2013 cas servers during coexistence.That means all the existing mailboxes in exchange 2010 will also have to query exchange 2013 cas
servers for autodiscover request.During the whole exchange 2013 environemnt failure whenever the user tries to close and open outlook .Outlook will first queries the autodiscover service for any changes happened on that particular mailbox and it will try to
get it updated on user profile.
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
Would it be possible to make the exchange 2010 mailbox users to query only the scp points which belongs to the exchange 2010 cas servers for autodiscover request ?
Scenario 2: For exchange services
mail.domain.com - will be the namespace for all the exchange 2010 services (i.e owa,activesync,external outlook anywhere,pop,imap)
mail.domain.com - will be the namespace for all the exchange 2013 services (i.e owa,activesync,external outlook anywhere,pop,imap)
What about the above services will it get affected during whole exchange 2013 environment failure ?
Note : We are not facing this issue , i hope everything goes well in my environment while doing coexistence i am just asking this question on my own interest?
Regards
S.Nithyanandham
Thanks S.Nithyanandham

Exchange 2013 - Prevent Outlook Clients From Connecting To A CAS Server In A Different AD Site

Hi all,
I could really do with your help!
We have 3 physical sites, A, B & C, with sites A & B having a really fast low latency links between them, so from an AD point of view they are 1 site. Site C has links to both sites A & B, but the link is a lot slower.
We have an exchange design with 3 servers (one located at each physical site) that will form a DAG spread over the 3 physical sites. Ideally we will separate the CAS and mailbox server roles out and have them controlled by a hardware load balancer,
however we can have both roles on the same server if required.
What we want, is to prevent is a situation where an outlook client in site C connects to a CAS server in site A/B with the mail being hosted on a mailbox server in site C therefore traversing the network twice to get its mail.
From doing the Microsoft training course, my understanding is that in Exchange 2013, the CAS server only proxy's the request on to the mailbox server and does not redirect the request to the CAS server in the site where the mailbox server resides.
I have seen information online stating that a single namespace is the way to go as long as your site links/network bandwidth is good, but nothing to help with our scenario.
Has anyone else come across this situation and how did you get round it?
Thanks in advance :)

Hi Johnson,
Based on my knowledge, Outlook Client will connect to the CAS server which in local first.
Please check whether the CAS server that in site C is healthy.
If the CAS server in site C is healthy, please disable the CAS Load Balance for testing.
Also found a useful blog for your reference:
Exchange 2013 Client Access Server Role
http://blogs.technet.com/b/exchange/archive/2013/01/25/exchange-2013-client-access-server-role.aspx
Thanks
Mavis
Mavis Huang
TechNet Community Support

Buttons not working in CRM 2015 Outlook client

I have this strange problem where no user in an organisation (even administrators) can't click the new Account, Contact or Lead buttons in the CRM Outlook client. The button is visible and enabled but nothing happens when clicked. The CRM Activity button
is working. Any suggestions to why this is and what can be done about it? Thank you.

Can you check this and revert
https://community.dynamics.com/crm/b/dynamicscrmsupportblog/archive/2012/12/05/crm-for-outlook-client-add-in-disabled.aspx
Regards, Abhishek Bakshi If you find this post helpful then please Vote as Helpful and Mark As Answer. Check my blog on https://mydynamicscrmblog.wordpress.com/

IPad Air + iOS 8 GM -- RD Client Crash

Hello, I am an iOS Developer and I'm running into an issue with the iPad Air + iOS 8 and the iPad's Microsoft RD Client.
Whenever I click the "+" in the upper-right hand corner, and click "Add PC or Server" the client crashes.
iPad Information:
Device: iPad Air (A1474)
Model: MD788LL/A
Version: 8.0 (12A365)
The remote desktop information:
Version: 8.1.0.140902.3.0
Here's the crash log generated from from Xcode:
Incident Identifier: 40933394-D6A7-4EF4-8354-9C26690AB5B7
CrashReporter Key: 57246288c66b4cff81780eb31982d743c09097a8
Hardware Model: iPad4,1
Process: Microsoft Remote Desktop [582]
Path: /private/var/mobile/Containers/Bundle/Application/BCA3CEAD-6A01-4D3E-B0C6-D201BCF7EEC8/Microsoft Remote Desktop.app/Microsoft Remote Desktop
Identifier: com.microsoft.rdc.ios
Version: 8.1.0 (8.1.0)
Code Type: ARM (Native)
Parent Process: launchd [1]
Date/Time: 2014-09-12 08:16:25.257 -0700
Launch Time: 2014-09-12 08:16:22.224 -0700
OS Version: iOS 8.0 (12A365)
Report Version: 105
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Triggered by Thread: 0
Last Exception Backtrace:
0 CoreFoundation
0x29014e3f __exceptionPreprocess + 127
1 libobjc.A.dylib
0x36989c8b objc_exception_throw + 38
2 CoreFoundation
0x29014d85 +[NSException raise:format:] + 112
3 UIKit
0x2c6e3cbd -[UIPopoverController dealloc] + 156
4 libobjc.A.dylib
0x369a3d5f objc_object::sidetable_release(bool) + 166
5 Microsoft Remote Desktop
0x00110429 0xc7000 + 300073
6 UIKit
0x2c5c87c7 -[UITableView _selectRowAtIndexPath:animated:scrollnbsp; UIKit
0x2c67a0df -[UITableView _userSelectRowAtPendingSelectionIndexPath:] + 194
8 UIKit
0x2c52c1bd _applyBlockToCFArrayCopiedToStack + 308
9 UIKit
0x2c4a810b _afterCACommitHandler + 458
10 CoreFoundation
0x28fdb5cd __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 20
11 CoreFoundation
0x28fd8c8b __CFRunLoopDoObservers + 278
12 CoreFoundation
0x28fd9093 __CFRunLoopRun + 914
13 CoreFoundation
0x28f27621 CFRunLoopRunSpecific + 476
14 CoreFoundation
0x28f27433 CFRunLoopRunInMode + 106
15 GraphicsServices
0x3026c0a9 GSEventRunModal + 136
16 UIKit
0x2c511809 UIApplicationMain + 1440
17 Microsoft Remote Desktop
0x000d2f73 0xc7000 + 49011
18 libdyld.dylib
0x36f09aaf start + 2
Thread 0 name: Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0 libsystem_kernel.dylib
0x36fcfdfc __pthread_kill + 8
1 libsystem_pthread.dylib
0x3704dd33 pthread_kill + 59
2 libsystem_c.dylib
0x36f6f905 abort + 73
3 libc++abi.dylib
0x362ad9c5 abort_message + 85
4 libc++abi.dylib
0x362c766d default_terminate_handler() + 265
5 libobjc.A.dylib
0x36989f23 _objc_terminate() + 191
6 libc++abi.dylib
0x362c4de1 std::__terminate(void (*)()) + 77
7 libc++abi.dylib
0x362c48ab __cxa_rethrow + 99
8 libobjc.A.dylib
0x36989dcf objc_exception_rethrow + 39
9 CoreFoundation
0x28f276b9 CFRunLoopRunSpecific + 629
10 CoreFoundation
0x28f2742f CFRunLoopRunInMode + 103
11 GraphicsServices
0x3026c0a5 GSEventRunModal + 133
12 UIKit
0x2c511805 UIApplicationMain + 1437
13 Microsoft Remote Desktop
0x000d2f6f 0xc7000 + 49007
14 libdyld.dylib
0x36f09aad start + 1
Thread 1 name: Dispatch queue: com.apple.libdispatch-manager
Thread 1:
0 libsystem_kernel.dylib
0x36fbc2a0 kevent64 + 24
1 libdispatch.dylib
0x36ef59fd _dispatch_mgr_invoke + 277
2 libdispatch.dylib
0x36eeb31f _dispatch_mgr_thread + 35
Thread 2:
0 libsystem_kernel.dylib
0x36fd09cc __workq_kernreturn + 8
1 libsystem_pthread.dylib
0x3704aea9 _pthread_wqthread + 789
2 libsystem_pthread.dylib
0x3704ab80 start_wqthread + 4
Thread 3:
0 libsystem_kernel.dylib
0x36fd09cc __workq_kernreturn + 8
1 libsystem_pthread.dylib
0x3704aea9 _pthread_wqthread + 789
2 libsystem_pthread.dylib
0x3704ab80 start_wqthread + 4
Thread 4:
0 libsystem_kernel.dylib
0x36fd09cc __workq_kernreturn + 8
1 libsystem_pthread.dylib
0x3704aea9 _pthread_wqthread + 789
2 libsystem_pthread.dylib
0x3704ab80 start_wqthread + 4
Thread 5:
0 libsystem_kernel.dylib
0x36fd09cc __workq_kernreturn + 8
1 libsystem_pthread.dylib
0x3704aea9 _pthread_wqthread + 789
2 libsystem_pthread.dylib
0x3704ab80 start_wqthread + 4
Thread 6:
0 libsystem_kernel.dylib
0x36fd09cc __workq_kernreturn + 8
1 libsystem_pthread.dylib
0x3704aea9 _pthread_wqthread + 789
2 libsystem_pthread.dylib
0x3704ab80 start_wqthread + 4
Thread 7:
0 libsystem_kernel.dylib
0x36fd09cc __workq_kernreturn + 8
1 libsystem_pthread.dylib
0x3704aea9 _pthread_wqthread + 789
2 libsystem_pthread.dylib
0x3704ab80 start_wqthread + 4
Thread 0 crashed with ARM Thread State (32-bit):
r0: 0x00000000 r1: 0x00000000 r2: 0x00000000 r3: 0x00000003
r4: 0x00000006 r5: 0x394189dc r6: 0x39404840 r7: 0x00e843b8
r8: 0x146dc430 r9: 0x00000000 r10: 0x39403074 r11: 0x146dc454
ip: 0x00000148 sp: 0x00e843ac lr: 0x3704dd37 pc: 0x36fcfdfc
cpsr: 0x00000010
Binary Images:
0xc7000 - 0x6a2fff Microsoft Remote Desktop armv7 <b852e7357e0131f6b64799903120ca37> /var/mobile/Containers/Bundle/Application/BCA3CEAD-6A01-4D3E-B0C6-D201BCF7EEC8/Microsoft Remote Desktop.app/Microsoft Remote Desktop
0x1fe34000 - 0x1fe57fff dyld armv7s <fd3fef9c43c9382e8e46d5d59fb52f86> /usr/lib/dyld
0x27ab3000 - 0x27c1ffff AVFoundation armv7s <291c7a621b65396491697e7a7f728b16> /System/Library/Frameworks/AVFoundation.framework/AVFoundation
0x27c20000 - 0x27c7efff libAVFAudio.dylib armv7s <1b452a7a75513cf9aa82e59feb7eef33> /System/Library/Frameworks/AVFoundation.framework/libAVFAudio.dylib
0x27cb8000 - 0x27cb8fff Accelerate armv7s <3b40c742a7323214a5eb836630536bd1> /System/Library/Frameworks/Accelerate.framework/Accelerate
0x27cc9000 - 0x27ee4fff vImage armv7s <844c5a129a2f3dbe9c0b23824f3254f6> /System/Library/Frameworks/Accelerate.framework/Frameworks/vImage.framework/vImage
0x27ee5000 - 0x27fcbfff libBLAS.dylib armv7s <aaaefc0f51f23049871f65ea9c4c7151> /System/Library/Frameworks/Accelerate.framework/Frameworks/vecLib.framework/libBLAS.dylib
0x27fcc000 - 0x28290fff libLAPACK.dylib armv7s <ba74aac653423b3b9bae4122d84935d8> /System/Library/Frameworks/Accelerate.framework/Frameworks/vecLib.framework/libLAPACK.dylib
0x28291000 - 0x282a2fff libLinearAlgebra.dylib armv7s <3df96b6a86303adea6abea68b7b610ac> /System/Library/Frameworks/Accelerate.framework/Frameworks/vecLib.framework/libLinearAlgebra.dylib
0x282a3000 - 0x2831ffff libvDSP.dylib armv7s <fb3e0b030cc5346c89af71af2d17bc27> /System/Library/Frameworks/Accelerate.framework/Frameworks/vecLib.framework/libvDSP.dylib
0x28320000 - 0x28332fff libvMisc.dylib armv7s <abd4670b295c3f50a2658d0f3f86d78c> /System/Library/Frameworks/Accelerate.framework/Frameworks/vecLib.framework/libvMisc.dylib
0x28333000 - 0x28333fff vecLib armv7s <9495c9829e28344fb1820d2140fcaf35> /System/Library/Frameworks/Accelerate.framework/Frameworks/vecLib.framework/vecLib
0x28334000 - 0x2835afff Accounts armv7s <cf7ceabb9af233f0b657f23423988703> /System/Library/Frameworks/Accounts.framework/Accounts
0x2835c000 - 0x283ccfff AddressBook armv7s <eeeabdf6b9703b4f846b672d0bb50eeb> /System/Library/Frameworks/AddressBook.framework/AddressBook
0x283cd000 - 0x284f1fff AddressBookUI armv7s <6fe5557b059b3ff38179c43183cfe8c3> /System/Library/Frameworks/AddressBookUI.framework/AddressBookUI
0x28689000 - 0x288fcfff AudioToolbox armv7s <5cf7594c3e8e33a889f26f9d2b8f74b7> /System/Library/Frameworks/AudioToolbox.framework/AudioToolbox
0x28a64000 - 0x28bebfff CFNetwork armv7s <79b211df401f377fb05acc07a57db3ea> /System/Library/Frameworks/CFNetwork.framework/CFNetwork
0x28bec000 - 0x28c6cfff CloudKit armv7s <aa1d623f3be434a6a75d2e49b41d26b6> /System/Library/Frameworks/CloudKit.framework/CloudKit
0x28c6d000 - 0x28cccfff CoreAudio armv7s <5b3129e5e3c23c4fb1052346c18e63b9> /System/Library/Frameworks/CoreAudio.framework/CoreAudio
0x28ce5000 - 0x28d02fff CoreBluetooth armv7s <2040fbe8e91833e5a14c2e4961b5995b> /System/Library/Frameworks/CoreBluetooth.framework/CoreBluetooth
0x28d03000 - 0x28f0efff CoreData armv7s <db7e2287362438249bb753788c64a2b1> /System/Library/Frameworks/CoreData.framework/CoreData
0x28f0f000 - 0x2923bfff CoreFoundation armv7s <a76fd43513ee3af9af444082a92ad639> /System/Library/Frameworks/CoreFoundation.framework/CoreFoundation
0x2923c000 - 0x29366fff CoreGraphics armv7s <a3d08c6b246236fd9a078619f6c2010b> /System/Library/Frameworks/CoreGraphics.framework/CoreGraphics
0x293a6000 - 0x293a8fff libCGXType.A.dylib armv7s <8c8f282d69573460983d78cbaebfd8cf> /System/Library/Frameworks/CoreGraphics.framework/Resources/libCGXType.A.dylib
0x293a9000 - 0x293b3fff libCMSBuiltin.A.dylib armv7s <795fcab613223b6d833937453beb1048> /System/Library/Frameworks/CoreGraphics.framework/Resources/libCMSBuiltin.A.dylib
0x2959b000 - 0x295b6fff libRIP.A.dylib armv7s <ae6bf33909b531b6abae4b007d9dd46b> /System/Library/Frameworks/CoreGraphics.framework/Resources/libRIP.A.dylib
0x295b7000 - 0x296c5fff CoreImage armv7s <0dd5152defdf3200b22c29876b05e34b> /System/Library/Frameworks/CoreImage.framework/CoreImage
0x296c6000 - 0x2971dfff CoreLocation armv7s <1153f2e6bde036f4b611833aa85dd9ac> /System/Library/Frameworks/CoreLocation.framework/CoreLocation
0x2974f000 - 0x297e9fff CoreMedia armv7s <b3e1c2a8262b38a697b5fd5478376e97> /System/Library/Frameworks/CoreMedia.framework/CoreMedia
0x297ea000 - 0x298aafff CoreMotion armv7s <0e91543dde123205bbfb0eec336f82e4> /System/Library/Frameworks/CoreMotion.framework/CoreMotion
0x298ab000 - 0x29909fff CoreTelephony armv7s <32757860a7b23ee6b10cdfb2bcb5e5b9> /System/Library/Frameworks/CoreTelephony.framework/CoreTelephony
0x2990a000 - 0x299d1fff CoreText armv7s <4be50da4f4d13b59b32ca55d4660e5c5> /System/Library/Frameworks/CoreText.framework/CoreText
0x299d2000 - 0x299e7fff CoreVideo armv7s <b1d41cec8ddc3c27be6f5459e17f1d2d> /System/Library/Frameworks/CoreVideo.framework/CoreVideo
0x299e8000 - 0x29addfff EventKit armv7s <af7bcad4baa7326eb020d805b49df854> /System/Library/Frameworks/EventKit.framework/EventKit
0x29c53000 - 0x29e55fff Foundation armv7s <fadfe1d878803b27a0683288c1c7948b> /System/Library/Frameworks/Foundation.framework/Foundation
0x29e82000 - 0x29ea1fff GSS armv7s <a384f737744b3e67be4b006612b27b58> /System/Library/Frameworks/GSS.framework/GSS
0x29f35000 - 0x29f8bfff IOKit armv7s <df1bb671b5d5392cbb95b89ed6341e78> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x29f8c000 - 0x2a1cdfff ImageIO armv7s <5cd6989e5626302aa49787b87e78ce32> /System/Library/Frameworks/ImageIO.framework/ImageIO
0x2a1ce000 - 0x2a51cfff JavaScriptCore armv7s <0041abdf36ff318981798e691a194dda> /System/Library/Frameworks/JavaScriptCore.framework/JavaScriptCore
0x2a7ef000 - 0x2a7f7fff MediaAccessibility armv7s <5c1cbb4f664b3d049bc5c0ac98cb8a90> /System/Library/Frameworks/MediaAccessibility.framework/MediaAccessibility
0x2a7f8000 - 0x2a9d1fff MediaPlayer armv7s <2fbb4a5dc62938f999bd72c93b9f5a50> /System/Library/Frameworks/MediaPlayer.framework/MediaPlayer
0x2a9d2000 - 0x2ad49fff MediaToolbox armv7s <47c440c3064b3b9194c8ffe6a096c37c> /System/Library/Frameworks/MediaToolbox.framework/MediaToolbox
0x2ad4a000 - 0x2ae08fff MessageUI armv7s <6c45faa0e6fe34d399021095392d0f63> /System/Library/Frameworks/MessageUI.framework/MessageUI
0x2ae09000 - 0x2ae75fff Metal armv7s <2c1c274d748d330c81520ccdf07a8be1> /System/Library/Frameworks/Metal.framework/Metal
0x2ae76000 - 0x2af05fff MobileCoreServices armv7s <5e571169affe3b1f97863142d3438da5> /System/Library/Frameworks/MobileCoreServices.framework/MobileCoreServices
0x2b9e0000 - 0x2b9e8fff OpenGLES armv7s <b0df2c3e1d583413b2babe8e95a7e099> /System/Library/Frameworks/OpenGLES.framework/OpenGLES
0x2b9ea000 - 0x2b9eafff libCVMSPluginSupport.dylib armv7s <ab28723da4e234fd87a6e12dae52c3a2> /System/Library/Frameworks/OpenGLES.framework/libCVMSPluginSupport.dylib
0x2b9eb000 - 0x2b9edfff libCoreFSCache.dylib armv7s <f073564b5746376a945531dcb28ebdb9> /System/Library/Frameworks/OpenGLES.framework/libCoreFSCache.dylib
0x2b9ee000 - 0x2b9f1fff libCoreVMClient.dylib armv7s <70abd418d5523929a02f9f22f834962e> /System/Library/Frameworks/OpenGLES.framework/libCoreVMClient.dylib
0x2b9f2000 - 0x2b9fafff libGFXShared.dylib armv7s <2cbde78e8e6c3d9da3a7271b053294bc> /System/Library/Frameworks/OpenGLES.framework/libGFXShared.dylib
0x2b9fb000 - 0x2ba3dfff libGLImage.dylib armv7s <a418f2754f373d3395a6aad59e50c371> /System/Library/Frameworks/OpenGLES.framework/libGLImage.dylib
0x2becb000 - 0x2c01dfff QuartzCore armv7s <4a753d93b6033495b66178dd7535fd96> /System/Library/Frameworks/QuartzCore.framework/QuartzCore
0x2c01e000 - 0x2c071fff QuickLook armv7s <593a3c45e1693456bfc917526490e399> /System/Library/Frameworks/QuickLook.framework/QuickLook
0x2c260000 - 0x2c2a0fff Security armv7s <52c6a10cc12c33cda98ce09e002c6a35> /System/Library/Frameworks/Security.framework/Security
0x2c444000 - 0x2c4a0fff SystemConfiguration armv7s <0dfa14680b583dd2994e2cc0563ebd53> /System/Library/Frameworks/SystemConfiguration.framework/SystemConfiguration
0x2c4a3000 - 0x2cd3bfff UIKit armv7s <5e0a38c7a0a33afc9e0e51edbdc2e8f3> /System/Library/Frameworks/UIKit.framework/UIKit
0x2cd3c000 - 0x2cda3fff VideoToolbox armv7s <d19c7c7e97533cde961652039bbcc310> /System/Library/Frameworks/VideoToolbox.framework/VideoToolbox
0x2cda4000 - 0x2cf89fff WebKit armv7s <4e6d38f557ea3c2cb906c580d58723d5> /System/Library/Frameworks/WebKit.framework/WebKit
0x2d23a000 - 0x2d245fff AOSNotification armv7s <30ac6892bcf1347383b6ca73b0c447be> /System/Library/PrivateFrameworks/AOSNotification.framework/AOSNotification
0x2d39a000 - 0x2d3e6fff AccountsDaemon armv7s <440e21ee4a4e3ee9b1891b016268b59e> /System/Library/PrivateFrameworks/AccountsDaemon.framework/AccountsDaemon
0x2d3e7000 - 0x2d408fff AccountsUI armv7s <a85ce8aa63ef349f90b9fbf16a040a6e> /System/Library/PrivateFrameworks/AccountsUI.framework/AccountsUI
0x2d409000 - 0x2d40dfff AggregateDictionary armv7s <7cb2e7f3daac30dbba7a9cf452850eb8> /System/Library/PrivateFrameworks/AggregateDictionary.framework/AggregateDictionary
0x2d5d6000 - 0x2d601fff AirPlaySupport armv7s <10dd1721d0ac327f8f8714bb749de10a> /System/Library/PrivateFrameworks/AirPlaySupport.framework/AirPlaySupport
0x2d7fb000 - 0x2d839fff AppSupport armv7s <85ae995cc0083b8f861e9af66f426b8b> /System/Library/PrivateFrameworks/AppSupport.framework/AppSupport
0x2d83a000 - 0x2d880fff AppleAccount armv7s <c8d7c7cc33873ca184d666626d1e2e49> /System/Library/PrivateFrameworks/AppleAccount.framework/AppleAccount
0x2d968000 - 0x2d9a5fff AppleJPEG armv7s <9d28d8b8c27e3b4d9af820fe71478279> /System/Library/PrivateFrameworks/AppleJPEG.framework/AppleJPEG
0x2d9b0000 - 0x2d9c2fff ApplePushService armv7s <9019b7f0259b32e2bf08eb9e3e61b315> /System/Library/PrivateFrameworks/ApplePushService.framework/ApplePushService
0x2d9c3000 - 0x2d9c9fff AppleSRP armv7s <2bc7687cb4ea3b258e7412e03765e14c> /System/Library/PrivateFrameworks/AppleSRP.framework/AppleSRP
0x2d9fe000 - 0x2da07fff AssertionServices armv7s <5a349cdba4e63bb6a4d15bb6ed3266af> /System/Library/PrivateFrameworks/AssertionServices.framework/AssertionServices
0x2da08000 - 0x2da20fff AssetsLibraryServices armv7s <7419fc839e043757a22253d762c0a6fc> /System/Library/PrivateFrameworks/AssetsLibraryServices.framework/AssetsLibraryServices
0x2da21000 - 0x2da45fff AssistantServices armv7s <c1333e5e6c663276bc90f9a951c01cf8> /System/Library/PrivateFrameworks/AssistantServices.framework/AssistantServices
0x2da74000 - 0x2da78fff BTLEAudioController armv7s <2dcdae1d597e3f0fbf940c6df8a8ef27> /System/Library/PrivateFrameworks/BTLEAudioController.framework/BTLEAudioController
0x2da79000 - 0x2da90fff BackBoardServices armv7s <ffee59ef60f9330a9bdb28d8741b1b02> /System/Library/PrivateFrameworks/BackBoardServices.framework/BackBoardServices
0x2da93000 - 0x2dac8fff BaseBoard armv7s <f0482a734fba3477bd24881eb35f8dbe> /System/Library/PrivateFrameworks/BaseBoard.framework/BaseBoard
0x2dac9000 - 0x2dacffff BluetoothManager armv7s <fc99330ba35934c1b14610b4d86b7471> /System/Library/PrivateFrameworks/BluetoothManager.framework/BluetoothManager
0x2dad0000 - 0x2daf6fff Bom armv7s <554f954a2ece30fbbb343a1ad991af68> /System/Library/PrivateFrameworks/Bom.framework/Bom
0x2dbc1000 - 0x2dbeafff CalendarFoundation armv7s <6664e18ccf0d3b509037b2aa3e957b25> /System/Library/PrivateFrameworks/CalendarFoundation.framework/CalendarFoundation
0x2dcf6000 - 0x2dcfefff CaptiveNetwork armv7s <9a9f451fee273d698cb4497668b931a8> /System/Library/PrivateFrameworks/CaptiveNetwork.framework/CaptiveNetwork
0x2dcff000 - 0x2de21fff Celestial armv7s <00f08339e5a53f9c954529a1f5b2e124> /System/Library/PrivateFrameworks/Celestial.framework/Celestial
0x2de2f000 - 0x2de47fff CertInfo armv7s <cae40259896d3df8a24ef147a5676ffb> /System/Library/PrivateFrameworks/CertInfo.framework/CertInfo
0x2de48000 - 0x2de4dfff CertUI armv7s <3a27c29611f53011ad3379d387bb901b> /System/Library/PrivateFrameworks/CertUI.framework/CertUI
0x2df77000 - 0x2df98fff ChunkingLibrary armv7s <44b4f99b47dd3f0aa9619b8064a3e828> /System/Library/PrivateFrameworks/ChunkingLibrary.framework/ChunkingLibrary
0x2e431000 - 0x2e433fff CommonAuth armv7s <b00c1e8033303eb7a93fdf90e0a7a7e9> /System/Library/PrivateFrameworks/CommonAuth.framework/CommonAuth
0x2e434000 - 0x2e444fff CommonUtilities armv7s <06ffdaa9898d33ef816625bb3d93a92a> /System/Library/PrivateFrameworks/CommonUtilities.framework/CommonUtilities
0x2e445000 - 0x2e449fff CommunicationsFilter armv7s <60c2b30976e233299838015899c1ee13> /System/Library/PrivateFrameworks/CommunicationsFilter.framework/CommunicationsFilter
0x2e4b8000 - 0x2e4bcfff ConstantClasses armv7s <4b75b37195373a25ba38dca9b89e0e30> /System/Library/PrivateFrameworks/ConstantClasses.framework/ConstantClasses
0x2e4bd000 - 0x2e4f5fff ContentIndex armv7s <b8347f219df332a196a99e4ba397f7cd> /System/Library/PrivateFrameworks/ContentIndex.framework/ContentIndex
0x2e4f6000 - 0x2e4f9fff CoreAUC armv7s <c9d48abb96d6376c8778513f14f25180> /System/Library/PrivateFrameworks/CoreAUC.framework/CoreAUC
0x2e51d000 - 0x2e571fff CoreDAV armv7s <a7606dc393b039cf8560773d71df1b7f> /System/Library/PrivateFrameworks/CoreDAV.framework/CoreDAV
0x2e572000 - 0x2e58bfff CoreDuet armv7s <dadc8ae1a88f3d75b0d6c244dae2a71a> /System/Library/PrivateFrameworks/CoreDuet.framework/CoreDuet
0x2e590000 - 0x2e59ffff CoreDuetDaemonProtocol armv7s <cb3e7b1fe32a33b09abac1342eb48f99> /System/Library/PrivateFrameworks/CoreDuetDaemonProtocol.framework/CoreDuetDaemonProtocol
0x2e5a6000 - 0x2e5a8fff CoreDuetDebugLogging armv7s <17818c8f932336769943c9e74254af3d> /System/Library/PrivateFrameworks/CoreDuetDebugLogging.framework/CoreDuetDebugLogging
0x2e7f6000 - 0x2e891fff CorePDF armv7s <d4837a0178783c03b805e48fa08507ee> /System/Library/PrivateFrameworks/CorePDF.framework/CorePDF
0x2e8f2000 - 0x2e8fcfff CoreRecents armv7s <92a8ed6e10123437b685c544c7be89af> /System/Library/PrivateFrameworks/CoreRecents.framework/CoreRecents
0x2e974000 - 0x2e992fff CoreServicesInternal armv7s <4bf749d6d95030cba3a88850e33e7514> /System/Library/PrivateFrameworks/CoreServicesInternal.framework/CoreServicesInternal
0x2eb90000 - 0x2ec10fff CoreUI armv7s <6ca97dfeeebe37a1b74f651e56bbe561> /System/Library/PrivateFrameworks/CoreUI.framework/CoreUI
0x2ec11000 - 0x2ec7bfff CoreUtils armv7s <68e3551ba2023eeaa187682a19cfc6a4> /System/Library/PrivateFrameworks/CoreUtils.framework/CoreUtils
0x2ec7c000 - 0x2ec81fff CrashReporterSupport armv7s <a1d95e4d2034382e912ab4884d6a1157> /System/Library/PrivateFrameworks/CrashReporterSupport.framework/CrashReporterSupport
0x2ec82000 - 0x2ec88fff DAAPKit armv7s <a2479886e0bd3d7eb30a927bd06a2752> /System/Library/PrivateFrameworks/DAAPKit.framework/DAAPKit
0x2ec94000 - 0x2ecd9fff DataAccess armv7s <6dbf6d1637103f7d990accda11d76908> /System/Library/PrivateFrameworks/DataAccess.framework/DataAccess
0x2eece000 - 0x2eeeffff DataAccessExpress armv7s <4d78edc22bb430d19f8f513d779ebce7> /System/Library/PrivateFrameworks/DataAccessExpress.framework/DataAccessExpress
0x2eefa000 - 0x2ef11fff DataDetectorsCore armv7s <11248bce6d423839a1070b9dd1e8244f> /System/Library/PrivateFrameworks/DataDetectorsCore.framework/DataDetectorsCore
0x2ef13000 - 0x2ef2cfff DataDetectorsUI armv7s <747fdf85e19f3ca188b89bba7675181e> /System/Library/PrivateFrameworks/DataDetectorsUI.framework/DataDetectorsUI
0x2ef2d000 - 0x2ef33fff DataMigration armv7s <0d1c7a082dd23f5688c0af73bd52db7e> /System/Library/PrivateFrameworks/DataMigration.framework/DataMigration
0x2ef3d000 - 0x2ef3efff DiagnosticLogCollection armv7s <52071b4701ed3b2fa60d71a63efdc0ea> /System/Library/PrivateFrameworks/DiagnosticLogCollection.framework/DiagnosticLogCollection
0x2ef3f000 - 0x2ef59fff DictionaryServices armv7s <f087472c432733c9b0027e22a2fb8593> /System/Library/PrivateFrameworks/DictionaryServices.framework/DictionaryServices
0x2ef78000 - 0x2ef97fff EAP8021X armv7s <47b5191fd8d83584b7deaa2684e94a3a> /System/Library/PrivateFrameworks/EAP8021X.framework/EAP8021X
0x2f097000 - 0x2f099fff FTClientServices armv7s <134ad7a59577395caf7d96bfcf4422eb> /System/Library/PrivateFrameworks/FTClientServices.framework/FTClientServices
0x2f09a000 - 0x2f0cafff FTServices armv7s <9d002bd6316d3d499bfe9423c5cb3483> /System/Library/PrivateFrameworks/FTServices.framework/FTServices
0x2f0cb000 - 0x2f4eefff FaceCore armv7s <9b9520176ba23d5dabfb6a5a9c6b2646> /System/Library/PrivateFrameworks/FaceCore.framework/FaceCore
0x2f513000 - 0x2f513fff FontServices armv7s <ec4f36707bfa3ba28b63332e3cfcc4c0> /System/Library/PrivateFrameworks/FontServices.framework/FontServices
0x2f514000 - 0x2f5e7fff libFontParser.dylib armv7s <af8324e660b33765b5a52b10fea79492> /System/Library/PrivateFrameworks/FontServices.framework/libFontParser.dylib
0x2f5e8000 - 0x2f5f4fff libGSFontCache.dylib armv7s <fbca918852ed353faa45c4087a2f915f> /System/Library/PrivateFrameworks/FontServices.framework/libGSFontCache.dylib
0x2f6d7000 - 0x2f6f2fff FrontBoardServices armv7s <d4e89c7da75d38228c4e321cf076717e> /System/Library/PrivateFrameworks/FrontBoardServices.framework/FrontBoardServices
0x2ffda000 - 0x2fff0fff GenerationalStorage armv7s <e4701d31f30e30d19afa0fb211399f5c> /System/Library/PrivateFrameworks/GenerationalStorage.framework/GenerationalStorage
0x2fff1000 - 0x30262fff GeoServices armv7s <6276f6d9bc98380da0fab1f85a5138b5> /System/Library/PrivateFrameworks/GeoServices.framework/GeoServices
0x30263000 - 0x30273fff GraphicsServices armv7s <06eeafe698713fd79424f8fdf249bf52> /System/Library/PrivateFrameworks/GraphicsServices.framework/GraphicsServices
0x30310000 - 0x3035ffff Heimdal armv7s <87944068c3eb337ea606facaf6696c67> /System/Library/PrivateFrameworks/Heimdal.framework/Heimdal
0x303f2000 - 0x30472fff HomeSharing armv7s <32297e3cffff3fe0a28b70ee1bb09187> /System/Library/PrivateFrameworks/HomeSharing.framework/HomeSharing
0x304d1000 - 0x30527fff IDS armv7s <0edb980bee7d316fa0bb4832efbcfccb> /System/Library/PrivateFrameworks/IDS.framework/IDS
0x30528000 - 0x30549fff IDSFoundation armv7s <f6dfe45534aa34a6b8c5f74acee1cc72> /System/Library/PrivateFrameworks/IDSFoundation.framework/IDSFoundation
0x305b1000 - 0x3065ffff IMCore armv7s <51aec7ae856139079e6b39c804bad76e> /System/Library/PrivateFrameworks/IMCore.framework/IMCore
0x306f7000 - 0x3075efff IMFoundation armv7s <54a1298efd8a3a0ab968d7c513b0ee59> /System/Library/PrivateFrameworks/IMFoundation.framework/IMFoundation
0x30766000 - 0x30769fff IOAccelerator armv7s <b81286ef987d31bd9ae83f8322d94c6c> /System/Library/PrivateFrameworks/IOAccelerator.framework/IOAccelerator
0x3076c000 - 0x30772fff IOMobileFramebuffer armv7s <4ac5dd54ca853930aa6003839254ac1f> /System/Library/PrivateFrameworks/IOMobileFramebuffer.framework/IOMobileFramebuffer
0x30773000 - 0x30778fff IOSurface armv7s <1bb65b18a65936d3a3d8a28b7a7d5bf1> /System/Library/PrivateFrameworks/IOSurface.framework/IOSurface
0x30779000 - 0x3077afff IOSurfaceAccelerator armv7s <8765e45debb9384aa1f1f7cbbbde8b59> /System/Library/PrivateFrameworks/IOSurfaceAccelerator.framework/IOSurfaceAccelerator
0x30816000 - 0x3081cfff IntlPreferences armv7s <9d8c3e2813e53148a4a104e918dc640d> /System/Library/PrivateFrameworks/IntlPreferences.framework/IntlPreferences
0x3081d000 - 0x30853fff LanguageModeling armv7s <2787f19f6449349291859b40dfb88ff1> /System/Library/PrivateFrameworks/LanguageModeling.framework/LanguageModeling
0x3088f000 - 0x308cbfff MIME armv7s <f41ebcfe27ba37d295fb0143e08e45bb> /System/Library/PrivateFrameworks/MIME.framework/MIME
0x3096f000 - 0x3097bfff MailServices armv7s <1b6ef0ab8a0535ccb7281874d8f2f6f3> /System/Library/PrivateFrameworks/MailServices.framework/MailServices
0x309af000 - 0x30a4efff ManagedConfiguration armv7s <6b2a389e13373470952a4a94e2f451d1> /System/Library/PrivateFrameworks/ManagedConfiguration.framework/ManagedConfiguration
0x30a59000 - 0x30a5afff Marco armv7s <de1fa71308ac3a14b19c1ef2a8367ca6> /System/Library/PrivateFrameworks/Marco.framework/Marco
0x30a5b000 - 0x30ad3fff MediaControlSender armv7s <204933b2eecc3eb2a97550fa9a4d5238> /System/Library/PrivateFrameworks/MediaControlSender.framework/MediaControlSender
0x30b72000 - 0x30b84fff MediaRemote armv7s <8583c7eb810a35f392d0aa99daea5dcf> /System/Library/PrivateFrameworks/MediaRemote.framework/MediaRemote
0x30b85000 - 0x30b94fff MediaServices armv7s <4503fa3dbb5c3972b04811c5af18c873> /System/Library/PrivateFrameworks/MediaServices.framework/MediaServices
0x30c12000 - 0x30ceffff Message armv7s <d43361cd4d7b3cc6b0d5abda7e2e53b1> /System/Library/PrivateFrameworks/Message.framework/Message
0x30cf5000 - 0x30cf7fff MessageSupport armv7s <b4f04a3a3fc237d094c4b572f77cc10c> /System/Library/PrivateFrameworks/MessageSupport.framework/MessageSupport
0x30d09000 - 0x30d16fff MobileAsset armv7s <fec17b7104b732798ec0cda1e47a940c> /System/Library/PrivateFrameworks/MobileAsset.framework/MobileAsset
0x30d3d000 - 0x30d46fff MobileBluetooth armv7s <e5ee20534ea739e7bb01464e0e891cfc> /System/Library/PrivateFrameworks/MobileBluetooth.framework/MobileBluetooth
0x30d62000 - 0x30d69fff MobileIcons armv7s <605d7447b21a339bbb6fa67458c9a870> /System/Library/PrivateFrameworks/MobileIcons.framework/MobileIcons
0x30d6a000 - 0x30d71fff MobileInstallation armv7s <1bfe7b98d7aa306ea1df0dd42a4b56ce> /System/Library/PrivateFrameworks/MobileInstallation.framework/MobileInstallation
0x30d72000 - 0x30d7efff MobileKeyBag armv7s <9c010e348a7b3a148a60f7252d05084a> /System/Library/PrivateFrameworks/MobileKeyBag.framework/MobileKeyBag
0x30dab000 - 0x30daefff MobileSystemServices armv7s <ddb6afac1c233f5daab60a666ece59b2> /System/Library/PrivateFrameworks/MobileSystemServices.framework/MobileSystemServices
0x30dd0000 - 0x30dddfff MobileWiFi armv7s <7537e6cfb3b33b669c3d0c22b01f55fe> /System/Library/PrivateFrameworks/MobileWiFi.framework/MobileWiFi
0x30e1c000 - 0x30fbbfff MusicLibrary armv7s <9cc281ea71403e9587ccc5982e7c16f3> /System/Library/PrivateFrameworks/MusicLibrary.framework/MusicLibrary
0x31054000 - 0x31059fff Netrb armv7s <a56f447a04c834a3b2f37a34b13e4fa4> /System/Library/PrivateFrameworks/Netrb.framework/Netrb
0x3105a000 - 0x31060fff NetworkStatistics armv7s <7fbbf8e9b610335aadc96eeb658dcacc> /System/Library/PrivateFrameworks/NetworkStatistics.framework/NetworkStatistics
0x31061000 - 0x3107efff Notes armv7s <43297712e4a93338910ff622842273ab> /System/Library/PrivateFrameworks/Notes.framework/Notes
0x31084000 - 0x31086fff OAuth armv7s <0c2849dabc57305baa7b8605cab0eafd> /System/Library/PrivateFrameworks/OAuth.framework/OAuth
0x317e1000 - 0x3181dfff OpenCL armv7s <fb56731bf6b03180a163fab3ca15ddad> /System/Library/PrivateFrameworks/OpenCL.framework/OpenCL
0x31903000 - 0x3192afff PersistentConnection armv7s <2a02604fc4ba37c3ac46323f48df3082> /System/Library/PrivateFrameworks/PersistentConnection.framework/PersistentConnection
0x31cfa000 - 0x31d44fff PhysicsKit armv7s <abc65981a5243535be8f8b2bea0db902> /System/Library/PrivateFrameworks/PhysicsKit.framework/PhysicsKit
0x31d45000 - 0x31d5bfff PlugInKit armv7s <3ec17a1ff2cd3a70b88c2b9de8964b5a> /System/Library/PrivateFrameworks/PlugInKit.framework/PlugInKit
0x31d5c000 - 0x31d63fff PowerLog armv7s <a7ccb43187613877946faee1079b4c3e> /System/Library/PrivateFrameworks/PowerLog.framework/PowerLog
0x31f5d000 - 0x32004fff Preferences armv7s <4ad19193fb72316bba48d6d9073d1a60> /System/Library/PrivateFrameworks/Preferences.framework/Preferences
0x32005000 - 0x32042fff PrintKit armv7s <9195e5878ba23aaeabbbcf380cf76f02> /System/Library/PrivateFrameworks/PrintKit.framework/PrintKit
0x32047000 - 0x320dbfff ProofReader armv7s <b6934340f1c837e2b921785474d9b380> /System/Library/PrivateFrameworks/ProofReader.framework/ProofReader
0x320ec000 - 0x320f8fff ProtocolBuffer armv7s <e850daf92889358fb2a3ecaf3629a97f> /System/Library/PrivateFrameworks/ProtocolBuffer.framework/ProtocolBuffer
0x3212b000 - 0x3219afff Quagga armv7s <8ee67622284038ae9cd333b4f7220ede> /System/Library/PrivateFrameworks/Quagga.framework/Quagga
0x32387000 - 0x32413fff SAObjects armv7s <e061cf980a8936edbda44d4293c4907c> /System/Library/PrivateFrameworks/SAObjects.framework/SAObjects
0x3257a000 - 0x32594fff SpringBoardServices armv7s <f9f6add53c76327a8d73a55918c26ed7> /System/Library/PrivateFrameworks/SpringBoardServices.framework/SpringBoardServices
0x328ff000 - 0x32a17fff StoreServices armv7s <d1a60fa363623bf08dab5072d7b8f4fe> /System/Library/PrivateFrameworks/StoreServices.framework/StoreServices
0x32ae8000 - 0x32aeafff TCC armv7s <b8313eb23a6537a8861716ac21ecbc9e> /System/Library/PrivateFrameworks/TCC.framework/TCC
0x32b31000 - 0x32b6efff TelephonyUtilities armv7s <b28ce5ba7cca391691a32106911ebd66> /System/Library/PrivateFrameworks/TelephonyUtilities.framework/TelephonyUtilities
0x339b5000 - 0x339dcfff TextInput armv7s <d183b563c21438a6bbbc915d589ab962> /System/Library/PrivateFrameworks/TextInput.framework/TextInput
0x33a8f000 - 0x33b50fff UIFoundation armv7s <7562389936d635fab4dc251b290fabfb> /System/Library/PrivateFrameworks/UIFoundation.framework/UIFoundation
0x33b72000 - 0x33b75fff UserFS armv7s <c044878c4cd43943bb55f355b882bb67> /System/Library/PrivateFrameworks/UserFS.framework/UserFS
0x342f9000 - 0x34317fff VoiceServices armv7s <a552fc9f06473b49b98cccb119d71d0a> /System/Library/PrivateFrameworks/VoiceServices.framework/VoiceServices
0x343a1000 - 0x343c7fff WebBookmarks armv7s <89c6195615a531e4abb72a5e744ee219> /System/Library/PrivateFrameworks/WebBookmarks.framework/WebBookmarks
0x343dd000 - 0x34f60fff WebCore armv7s <723ae76958093166ba7762e96663bf00> /System/Library/PrivateFrameworks/WebCore.framework/WebCore
0x34f61000 - 0x3501ffff WebKitLegacy armv7s <dfc480439ce537ce8292eceb6c34b16d> /System/Library/PrivateFrameworks/WebKitLegacy.framework/WebKitLegacy
0x351bf000 - 0x351c7fff XPCObjects armv7s <69caaf09b0ee3596a7b420e092a5c482> /System/Library/PrivateFrameworks/XPCObjects.framework/XPCObjects
0x353b5000 - 0x353d9fff iCalendar armv7s <05eb09ddf7483831a7107a32f7ed31fb> /System/Library/PrivateFrameworks/iCalendar.framework/iCalendar
0x355cd000 - 0x35608fff iTunesStore armv7s <7a7a1cdae7dd305e816183c504382c88> /System/Library/PrivateFrameworks/iTunesStore.framework/iTunesStore
0x35d56000 - 0x35d5efff libAccessibility.dylib armv7s <094547582d723c27b8150d539f0eaf4e> /usr/lib/libAccessibility.dylib
0x35e90000 - 0x35ea6fff libCRFSuite.dylib armv7s <9c29786bd63f341f916aa6f6662ca675> /usr/lib/libCRFSuite.dylib
0x35ed8000 - 0x35fdcfff libFosl_dynamic.dylib armv7s <0052248414073cc78819925a431dd2fe> /usr/lib/libFosl_dynamic.dylib
0x35ff6000 - 0x3600dfff libMobileGestalt.dylib armv7s <16db2870e9443a669790f8bb678f572a> /usr/lib/libMobileGestalt.dylib
0x36033000 - 0x36034fff libSystem.B.dylib armv7s <916c64d9cab33b2a9bbb355f4be13a76> /usr/lib/libSystem.B.dylib
0x360a5000 - 0x360e9fff libTelephonyUtilDynamic.dylib armv7s <2a798667e6d1311ab5d20ce7640d856e> /usr/lib/libTelephonyUtilDynamic.dylib
0x361f9000 - 0x3621bfff libarchive.2.dylib armv7s <527e8c0122073f578d895580df8169f4> /usr/lib/libarchive.2.dylib
0x3621c000 - 0x3621cfff libassertion_extension.dylib armv7s <536e1abbba3b31d8a6560c6d5c7c99e2> /usr/lib/libassertion_extension.dylib
0x3624b000 - 0x36257fff libbsm.0.dylib armv7s <ae0d4a27677f3f318d5994bd5a299009> /usr/lib/libbsm.0.dylib
0x36258000 - 0x36261fff libbz2.1.0.dylib armv7s <cdff2930a8333bb689793675dee50df4> /usr/lib/libbz2.1.0.dylib
0x36262000 - 0x362acfff libc++.1.dylib armv7s <8fad3aace328348da9c59ce042a8f764> /usr/lib/libc++.1.dylib
0x362ad000 - 0x362c8fff libc++abi.dylib armv7s <7b486834c946373e8880760a56965ca5> /usr/lib/libc++abi.dylib
0x362ca000 - 0x362d7fff libcmph.dylib armv7s <361b1fe8b4673926b7116829e02d0b02> /usr/lib/libcmph.dylib
0x362d8000 - 0x362e0fff libcupolicy.dylib armv7s <e937a5f056543f0f85fc140f6c51a188> /usr/lib/libcupolicy.dylib
0x36307000 - 0x3631ffff libextension.dylib armv7s <bff08d045d4a318d863941427db9f018> /usr/lib/libextension.dylib
0x3633e000 - 0x36341fff libheimdal-asn1.dylib armv7s <c11a6c53a6ed39cc942b2534ca2d4f1a> /usr/lib/libheimdal-asn1.dylib
0x36342000 - 0x3642ffff libiconv.2.dylib armv7s <747ef3a673c63868af6c67855f7fbd44> /usr/lib/libiconv.2.dylib
0x36430000 - 0x3659efff libicucore.A.dylib armv7s <a9bb4dc7760e3184bec94e62a99ce135> /usr/lib/libicucore.A.dylib
0x365ab000 - 0x365abfff liblangid.dylib armv7s <c039470cbe2b39f2b7f5f80676b7b6d0> /usr/lib/liblangid.dylib
0x365ac000 - 0x365b6fff liblockdown.dylib armv7s <5c2434e5bec830ccb88db1fb9c139bd6> /usr/lib/liblockdown.dylib
0x365b7000 - 0x365ccfff liblzma.5.dylib armv7s <d9f0e9bc84273d28bb36dea3e8f362aa> /usr/lib/liblzma.5.dylib
0x36945000 - 0x36959fff libmis.dylib armv7s <02e6bf70c6bf376793e2c631a6f9807d> /usr/lib/libmis.dylib
0x36983000 - 0x36b7dfff libobjc.A.dylib armv7s <f6ae15f5da4a3ee1aa1a080c069e3a1c> /usr/lib/libobjc.A.dylib
0x36c32000 - 0x36c48fff libresolv.9.dylib armv7s <6f5e721723f73e079cad07f800ce7c16> /usr/lib/libresolv.9.dylib
0x36c73000 - 0x36d19fff libsqlite3.dylib armv7s <463044a8a4543b11ac70cdd88a6a4a54> /usr/lib/libsqlite3.dylib
0x36d67000 - 0x36d8dfff libtidy.A.dylib armv7s <ce3364e915d23d74ae1564c2f9532f7d> /usr/lib/libtidy.A.dylib
0x36d8e000 - 0x36d96fff libtzupdate.dylib armv7s <c23ed5e6c3b93a33afac2d1496094825> /usr/lib/libtzupdate.dylib
0x36d9a000 - 0x36e50fff libxml2.2.dylib armv7s <3c08bca3a51231749b43e35d4e627cdc> /usr/lib/libxml2.2.dylib
0x36e51000 - 0x36e72fff libxslt.1.dylib armv7s <f4c65edfeb6032e88ce570e92f5f9d24> /usr/lib/libxslt.1.dylib
0x36e73000 - 0x36e7ffff libz.1.dylib armv7s <b261d154b0633244af8249c457f13def> /usr/lib/libz.1.dylib
0x36e80000 - 0x36e84fff libcache.dylib armv7s <7f2ac0c12ea6341ab3fb0a9b20400244> /usr/lib/system/libcache.dylib
0x36e85000 - 0x36e8efff libcommonCrypto.dylib armv7s <de40d2d23c6f36ac88bf74e6551e22f8> /usr/lib/system/libcommonCrypto.dylib
0x36e8f000 - 0x36e93fff libcompiler_rt.dylib armv7s <da89cd909a9a3678b531951a88ba5519> /usr/lib/system/libcompiler_rt.dylib
0x36e94000 - 0x36e9afff libcopyfile.dylib armv7s <48cc5f26af163b4d9dca2ea06373c724> /usr/lib/system/libcopyfile.dylib
0x36e9b000 - 0x36ee7fff libcorecrypto.dylib armv7s <f1d32ffeb2c1366ebe631cb906a79737> /usr/lib/system/libcorecrypto.dylib
0x36ee8000 - 0x36f07fff libdispatch.dylib armv7s <7106cbb58b94372d9a4ae63f6dc39e1e> /usr/lib/system/libdispatch.dylib
0x36f08000 - 0x36f09fff libdyld.dylib armv7s <bf125933f7c33a63999c21ae82e4223c> /usr/lib/system/libdyld.dylib
0x36f0a000 - 0x36f0afff libkeymgr.dylib armv7s <00e2af5454d73aef9254cd299247d537> /usr/lib/system/libkeymgr.dylib
0x36f0b000 - 0x36f0bfff liblaunch.dylib armv7s <9dbb42926564306cb61af50e6f3fe65a> /usr/lib/system/liblaunch.dylib
0x36f0c000 - 0x36f0ffff libmacho.dylib armv7s <ffcab8e9628a3c93823adce1717ead38> /usr/lib/system/libmacho.dylib
0x36f10000 - 0x36f11fff libremovefile.dylib armv7s <741688071e8c3f54a2ffa7d5bbf0ad0f> /usr/lib/system/libremovefile.dylib
0x36f12000 - 0x36f23fff libsystem_asl.dylib armv7s <fde71151f3633b19897377baab64b521> /usr/lib/system/libsystem_asl.dylib
0x36f24000 - 0x36f24fff libsystem_blocks.dylib armv7s <28477932f242360c892f12c609f95419> /usr/lib/system/libsystem_blocks.dylib
0x36f25000 - 0x36f88fff libsystem_c.dylib armv7s <5d0717641c5e339da3ca1f21faa448e1> /usr/lib/system/libsystem_c.dylib
0x36f89000 - 0x36f8bfff libsystem_configuration.dylib armv7s <2e43e283d6be3ad685e50217cb2b8661> /usr/lib/system/libsystem_configuration.dylib
0x36f8c000 - 0x36f8dfff libsystem_coreservices.dylib armv7s <b5dcec2938633107b43383dfbf8e07e6> /usr/lib/system/libsystem_coreservices.dylib
0x36f8e000 - 0x36f9afff libsystem_coretls.dylib armv7s <2dc9e3d6317535f4b536f631decf4913> /usr/lib/system/libsystem_coretls.dylib
0x36f9b000 - 0x36fa1fff libsystem_dnssd.dylib armv7s <7482038666363dc0b1a435e57b513989> /usr/lib/system/libsystem_dnssd.dylib
0x36fa2000 - 0x36fbafff libsystem_info.dylib armv7s <ff47cce8338c3fea9614c8c91a104349> /usr/lib/system/libsystem_info.dylib
0x36fbb000 - 0x36fd5fff libsystem_kernel.dylib armv7s <0135350370a335d1acca9ce9858595df> /usr/lib/system/libsystem_kernel.dylib
0x36fd6000 - 0x36ff5fff libsystem_m.dylib armv7s <d1bc7f2b6bbd3ddc83930b9ba33dc507> /usr/lib/system/libsystem_m.dylib
0x36ff6000 - 0x37008fff libsystem_malloc.dylib armv7s <4285bc1fb79b3dc4a45fe1680ddb276b> /usr/lib/system/libsystem_malloc.dylib
0x37009000 - 0x37036fff libsystem_network.dylib armv7s <93a5fa1da38835b693fcdbf8e200fe17> /usr/lib/system/libsystem_network.dylib
0x37037000 - 0x3703cfff libsystem_networkextension.dylib armv7s <3c2cc31c08e534f994eae9e9390c0bda> /usr/lib/system/libsystem_networkextension.dylib
0x3703d000 - 0x37044fff libsystem_notify.dylib armv7s <bc57f62dd51b39b49d5ef5890b386f76> /usr/lib/system/libsystem_notify.dylib
0x37045000 - 0x37049fff libsystem_platform.dylib armv7s <485d83aa9719310982082cb9c6c5a2c4> /usr/lib/system/libsystem_platform.dylib
0x3704a000 - 0x37050fff libsystem_pthread.dylib armv7s <211207e983bc395f9c59668f9088bef2> /usr/lib/system/libsystem_pthread.dylib
0x37051000 - 0x37053fff libsystem_sandbox.dylib armv7s <ae0d736739bd3aef9fa1c29fcf22e90e> /usr/lib/system/libsystem_sandbox.dylib
0x37054000 - 0x37057fff libsystem_stats.dylib armv7s <63dea98a903b3b49a7db9ffd18bd3681> /usr/lib/system/libsystem_stats.dylib
0x37058000 - 0x3705dfff libsystem_trace.dylib armv7s <f1d18cb2a43c3e518ad37bcf31224eda> /usr/lib/system/libsystem_trace.dylib
0x3705e000 - 0x3705efff libunwind.dylib armv7s <1440671d926a3346abaa73fa726ddbfc> /usr/lib/system/libunwind.dylib
0x3705f000 - 0x3707afff libxpc.dylib armv7s <acfe5f1e68d93d249b65d604403a9625> /usr/lib/system/libxpc.dylib

Hi,
Thank you for posting in Windows Server Forum.
As from your description it seems that you are using version 8.1.0 for your remote desktop MAC. Here I can suggest you update to latest remote desktop version 8.1.3 and check the result.
Microsoft Remote Desktop
https://itunes.apple.com/in/app/microsoft-remote-desktop/id714464092?mt=8
Hope it helps!
Thanks.
Dharmesh Solanki

Connection beetween Exchange 2013 with outlook client 2007 SP3

Hi All,
My company reinstall exchange 2013 when the previous mailbox DB error. When I implemeted a new server. I configured step by step carefully. if we use outlook 2010 connect to exchange server, send/receive work normally. But someone, uses outlook 2007 SP3,
they have somer error. They work with "cached mode", the connection from outlook to exchange server connected normally, but mail items sometime disappear in outlook client, when i check in the OWA, the mailbox item appear on this.
I tested with "online mode", the mailbox items push into outlook.I switched to "cached mode", this items haven't in outlook. Everybody who's meet the problem, please help me the solution can resolve the problem? Many thanks.
Quoc Dao

Hi,
Would you please let me know edition information of the Windows Server? Is it a Windows Server 2012, Windows
Server 2012 R2 or other?
On current situation, please refer to following KB and check if can help you.
Sometimes e-mail messages do not appear in your
Cached mode Inbox even though they were synchronized down from your mailbox
By the way. Based on your description, this issue seems to be more related to Outlook 2007. If this issue still
exists, I suggest that you should post in
Outlook forum. I believe we will get a better assistance there.
If any update, please feel free to let me know.
Hope this helps.
Best regards,
Justin Gu
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Outlook 2013 crashes on forwards and replies - Process ID: 1214 and Exception code: 0xc0000005

outlook 2013, installed on Windows 7, email server is Exchange 2007.
user complains that often when he forwards, sometimes when he replies, outlook crashes on him.
here are the steps I have taken:
tried short and long repair of Office, no change.
tried a system restore going back 2 weeks in case it was a windows update, no change.
uninstalled Office, then reinstalled office, no change.
deleted his profile, then recreated his profile, no change.
user states that it happens most often when he forwards an email, and not any particular email, just random ones.
below is errors from event viewer:
The program outlook.exe version 15.0.4535.1508 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
Process ID: 1214
Start Time: 01cec8d2c976b49a
Termination Time: 47
Application Path: C:\Program Files\Microsoft Office 15\root\office15\outlook.exe
Report Id: def82e71-34c9-11e3-91b2-a45d3616a6b8
Faulting application name: outlook.exe, version: 15.0.4535.1508, time stamp: 0x52327cfa
Faulting module name: olmapi32.dll, version: 15.0.4535.1504, time stamp: 0x520a0b6e
Exception code: 0xc0000005
Fault offset: 0x0009fc64
Faulting process id: 0x990
Faulting application start time: 0x01cec86e9cd6957b
Faulting application path: C:\Program Files\Microsoft Office 15\root\office15\outlook.exe
Faulting module path: C:\Program Files\Microsoft Office 15\Root\Office15\olmapi32.dll
Report Id: 2d6a8d66-3462-11e3-97d2-a45d3616a6b8

Hi,
How is everything going?
Have you tried Scanpst? Please let me know the result.
In addition, which profile did you delete and recreate? Please try to delete the mail profile and recreate a new one with a different name to test this issue. Some people seems resolved
this issue with this method. See:
http://answers.microsoft.com/en-us/office/forum/office_2013_release-outlook/outlook-2013-crashes-when-i-try-an-send-a-email/85daf7d9-637a-4ba1-8c45-f1202bdb1ae0
To create a new mail profile, please refer:
http://support.microsoft.com/kb/829918
Hope this helps.
Thanks,
Steve Fan
TechNet Community Support
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Dynamic CRM connect outlook Client with different domain

Hi Guys,
I had installed CRM 2011 in cloud with different domain.
If I use browser is working fine just that when i use Outlook client it show
15:24:16| Error| Exception : The request for security token could not be satisfied because authentication failed. at System.ServiceModel.Security.SecurityUtils.ThrowIfNegotiationFault(Message message, EndpointAddress target)
at System.ServiceModel.Security.SspiNegotiationTokenProvider.GetNextOutgoingMessageBody(Message incomingMessage, SspiNegotiationTokenProviderState sspiState)
I found that is because you must connect to the same domain.
any idea that i can use my Outlook client to connect to CRM 2011 without changing my domain?
Regards,
Kim

Yes - I've been scarred with this for many years :(
If it is just CAS 1 that is causing issues, then focus in on that. The support statement for Win 2008 R2 is that NLB is still a 3rd party component and support may ask for it to be disabled.
http://support.microsoft.com/kb/278431
Does CAS1 and CAS2 have the same NICs (firmware as well), driver, teaming software, and teaming config?
I also want to ask what the network team did for configuring the switch ports on the servers? This will vary from vendor to vendor - did they do the same config on both?
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.
Thanks Rhoderick, issue still persists
can you also help clarify what you meant by "configuring the switch ports on the servers"?
thanks again

Help - Outlook Client Crashing

Similar Messages

Maybe you are looking for