
I have a user who is running Windows 8.1 on a surface pro 3.
He has office 2013 and had CRM 2015 installed. He was having a problem with outlook crashing so it was uninstalled. He realized he really needs the app so it was reinstalled but we continue to have CRM problems.
Installed, plenty of reboots, checked and installed windows updates, reboots again, etc. Outlook starts fine. When running the config wizard, however, it bombs out within a few seconds after choosing the organizaton. It lt does lave an event log entry. Here are the details from the Windows Application Event Log:
| Log Name: Application |
| Source: Application Error |
| Date: 10/21/2015 3:54:38 PM |
| Event ID: 1000 |
| Task Category: (100) |
| Level: Error |
| Keywords: Classic |
| User: N/A |
| Computer: |
| Description: |
| Faulting application name: Microsoft.Crm.Application.Outlook.ConfigWizard.exe, version: 7.1.1.3113, time stamp: 0x55d6ea1e |
| Faulting module name: clr.dll, version: 4.0.30319.34209, time stamp: 0x5348961e |
| Exception code: 0xc00000fd |
| Fault offset: 0x004226a2 |
| Faulting process id: 0xa38 |
| Faulting application start time: 0x01d10c42ac9326ef |
| Faulting application path: C:\Program Files (x86)\Microsoft Dynamics CRM Client\Client\ConfigWizard\Microsoft.Crm.Application.Outlook.ConfigWizard.exe |
| Faulting module path: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll |
| Report Id: f0a5e438-7835-11e5-8306-f99f3f4c47a2 |
| Faulting package full name: |
| Faulting package-relative application ID: |
I confirmed the .NET install using a couple tools.. including this one: http://blogs.msdn.com/b/astebner/archive/2008/10/13/8999004.aspx
and received this confirmation from the log file: Verification succeeded for product .NET Framework 4 Client
I had this initially posted in a .NET forum and with the confirmation of a good .net install, it was suggested I try the CRM forums. We have 80 users with the same setup who are not having this problem so this is unique to just one user.
I'm stuck on this and could use a suggestion. thanks!
*This post is locked for comments
I have the same question (0)After struggling with this for a while, I believe the problem is with the end user's network connection. I had him connect to a different network and ran the install again. It then was able to complete the config wizard without error and he is up and running.