Calendar Sharing not available error message

Question

Trying to share my calendar with staff at the office here. I get the error:
Calendar sharing is not available with the following entries because of permission settings on your network.
I am using Offiice 2007 SP1, Exchange Server 2007 SP1
I can however go to the other workstation and use the "open a shared calendar" option to access my shared calendar.
It does work on some accounts, but not the majority of accounts.
Where do I start trouble shooting this issue? How do I check the "permission settings on my network"
Sorry if this is an easy one, I'm a new user to exchange. This is not a full production setup yet, still testing before I let folks know what it can do.
Thanks
Kevin Maracle
First Nations Technical Institute

Answer 1

Issue description: You can’t share calendar to other people
“Calendar sharing is not available with the following entries because of permission settings on your network”
Collect info:
1.       Do the users you want to share belong to other forests?
2.       Is the issue only happened on your account?
3.       Is there any error info in the application log on the server or client if you reproduce the issue?
Troubleshooting:
1.       How did you grant the permission to other users, from the “Properties” of the calendar or share it in the invitation? Please check which permissions stay in the “Properties” of calendar by default
2.       Check if DACL status is “GOOD” on your calendar by using PFDavAdmin
a.       Launch tool on client [Install NET Framework 1.1 at first]
b.      “File” menu->”connect”->select “mailbox” to connect->OK
c.       Right-click your mailbox->”Folder permissions”
d.      Check the “DACL state” on the right-up corner
3.       Check if “automatically update e-mail addresses based on e-mail address policy” option is checked
a.       EMC->Recipient Configuration->Mailbox, go to the “Properties” of your mailbox
b.      “E-Mail Address” tab, check the option
4.       Please recreate your mail profile on another test PC, see if you can reproduce the issue. in this way, we can isolate the issue to server or client side