2

Up until now we have only had windows 7 pro clients connecting to our 2003 exchange server using Outlook 2010 email and public folder access with no problems. Today I have been attempting to get a Windows 10 pro client with it's built in email working with our exchange 2003 but I am seeing an error code 0x80090345.

I have also tried to use Outlook 2010 on the same windows 10 pro client, it automatically connects as a IMAP client where it can then poorly (piecemeal) search and show parts of our public folder store. When I try to get Outlook 2010 on Windows 10 Pro connected to our exchange 2003 then it fails with a message like "The connection to the Microsoft Exchange server is unavailable. Outlook must be online or connected to complete this action"

.... from what little I can determine online the 0x80090345 error and the msg "Microsoft Exchange Server is unavailable" may be the same error. Are they?

What can I do to resolve the problem?

Katherine Villyard
  • 18,510
  • 4
  • 36
  • 59
user2684161
  • 21
  • 2

2 Answers2

1

Exchange 2003 is end of life. It probably sounds glib for me to suggest you upgrade Exchange in order to fix your Windows 10 client problem, but... Microsoft doesn't guarantee that new products will work with end of life products.

My googling suggests that perhaps the issue is deprecated security standards. Some complete other third party product is suggesting adding a registry key to fix it, but I hesitate to suggest that based on a quick google.

In short: There may be completely unsupported workarounds, but the supported solution would be to upgrade Exchange. (Sorry.)

Katherine Villyard
  • 18,510
  • 4
  • 36
  • 59
  • I wish Microsoft had a spreadsheet list the products that are supported to work together. I have found that outlook 2010 works with exchange 2003 and also that outlook 2010 works with window 10. But here it seems clear it isn't working and giving errors that also aren't well documented as to what they mean. Then it seems Microsoft would have me pay $500 upfront to consider this problem, no guarantee of success? – Ron Whites Sep 30 '15 at 15:22
  • Yes we are planning to migrate our Windows server 2003 with exchange 2003 to exchange 2013/Windows sever 2012. I am as a matter for fact suppose to me determining the exacting steups for how to do that. Easier said then done for sure! – Ron Whites Sep 30 '15 at 15:25
  • I really wish I had something better for you. :( [This](https://social.technet.microsoft.com/Forums/windows/en-US/47faab6b-d717-4068-bee4-c694811e0066/credential-manager-problems-error-0x80090345) is the sort of thing I'm finding in Google. I'm not sure I'm endorsing it, but it might be worth testing. – Katherine Villyard Sep 30 '15 at 17:34
  • Katherine thanks for the help. Unfortunately I know of no one who has tried connecting windows 10 pro or windows 8 pro to an MAPI exchange 2003 either by outlook or by (windows 10 pro email?) and seen their public folders. The 0x80090345 is I guess undocumented by Microsoft and the online blog discussion I see relates to SAMBA and not my issue. – Ron Whites Oct 01 '15 at 18:06
0

6 years later but...

This is actualy error from Cridentials manager.

Locate HKEY_LOCAL_MACHINE\Software\Microsoft\Cryptography\Protect\Providers\df9d8cd0-1501-11d1-8c7a-00c04fc297eb

Create a new registry DWORD value, named ProtectionPolicy, and give it a value 1 Restart...

Boris
  • 1