Jump to content

Outlook Shared Mailbox - exchange - 2013 ok, 2019 error


Recommended Posts

Posted (edited)

Hi Everyone! Hope you're all ok.

 

I really need some help on something that is driving me crazy here.

 

1. School has emails managed by LGfL / Atomwide.

2 A shared mailbox [email protected] is setup with Atomwide.

 

A member of staff has full permissions to the shared mailbox and can open it fine on Outlook 2013 - can see folders etc.

 

On Outlook 2019 we get the error: The set of folders cannot be open :

 

This error usually occurs if the Outlook Data File (.pst or .ost) you are using is:

Unavailable

Protected with file permissions

On a share on a server and the network is down

Corrupted

To correct this problem, save the Outlook Data File (.pst or .ost) on the computer hard disk.

You might also want to run the scanpst.exe tool drive:\Program Files\Microsoft Office\Office15 folder to check the data file for errors.

 

PST etc are fine... and I am totally out of ideas. Hoping someone here has had the same problem.

 

OS = Windows 10 LTSC

Office: Office pro plus 2019

 

Any ideas how to see the shared mail box?

 

Please let me know.

 

Kind regards

 

5nowman

Edited by 5nowman
Posted
Is the server hosting the mailbox an exchange server? If it is what version of exchange as Outlook 2019 is not officially supported client for exchange 2010 so there may be comparability issues
Posted

Crud! I did not even think of that!

I even went to Outlook 2013 > upgrade to 2019 .. and then BAM error.

I'll have to ask Atomwide about exchange! Will do more digging.

  • 7 months later...
Posted

Good morning,

 

Sorry to resurrect an old post but I was wondering if you got anywhere with this?

 

We upgraded the 2016 a while back but shared mailboxes haven't worked on that version. A number of staff are still using 2010 and it works on that.

 

Thanks.

  • 3 weeks later...
Posted

Which mailboxes are you connecting to?

 

The issue I had never got resolved... I didn't get much help and strongly believe it was linked to the licensing on the exchange server itself) however no help was given except an excuse to say we don't support end clients.

 

The solution in the end was running outlook 2013 / rest of office 2019. Very very bad solution however we had 2 machines that needed this thus it was ok.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...