Hello,
We have a number of users that we have upgraded Outlook from 2003 to Outlook 2010.
I am now trying to add an exchange account to these machines, but it doesn't work.
The exchange setup is correct, as we have some machines that came with Outlook 2010/2013 out of the box, and the exchange accounts work fine on them.
The first error that appears when adding the account is:
I have tried removing Outlook 2010, and then uninstalling Outlook 2003, reboot and re-install 2010. Same error.
I have tried setting up a new profile for the user, same error.
Our Exchange host pointed me to this http://support.microsoft.com/kb/2264398 which initially looked quite promising, as it describes the issue I am seeing. However, after carrying out the fix, I get the same error.
I checked in event viewer, and these issues seem to be relevant to the issue:
The description for Event ID 5000 from source Microsoft Office 14 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the
local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
Office11ShipAssert
6xk3
14.0.7015.0
the message resource is present but the message is not found in the string/message table
and
Fault bucket 8096914, type 21
Event Name: Office11ShipAssert
Response: Not available
Cab Id: 0
Problem signature:
P1: 6xk3
P2: 14.0.7015.0
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:
Attached files:
C:\Users\ntuser\AppData\Local\Microsoft\Office\ShipAsserts\outlook.exe.6xk3.dmp
C:\Users\ntuser\AppData\Local\Microsoft\Office\ShipAsserts\outlook.exe.6xk3.cvr
These files may be available here:
C:\Users\ntuser\AppData\Local\Microsoft\Windows\WER\ReportArchive\NonCritical_6xk3_cae7bb3efd629b7aa754c7bce3d3e93e0a6fd93_04a2c612
Analysis symbol:
Rechecking for solution: 0
Report Id: 3ec8802e-af73-11e3-89d4-c454b37af7b4
Report Status: 0
Any help would be appreciated, I don't fancy wiping the machines and starting from scratch, just to sort this issue out.