Open other user's folder

[Ladyelect]

I cannot access one person's calendar. The message is that "Could not read calendar. You do not have sufficient permission to perform this operation on this object. See the folder contact or your system administrator." I have gone so far as to log on as the other user and delegate myself and it still gives me the same message.

Of course, I can't find any useful information on the Microsoft website.

Any help would be greatly appreciated.
Pam

 

[brightstar]

have you tried adding yourself in the permissions?
not just in the "outlook today" but in each individual sub folder you want to access.

ie if you wanted to be able to open someones inbox you'd have to, as them, open up their outlook today options, go to permissions, add yourself with the appropriate permission. then go to the inbox and add yourself again.

if you add yourself as a delagate that gives you the option of opening their inbox on the opening of yours but you still need the permissions on each folder.

http://www.agonyonline.co.uk

free, anonymous advice provided by the whole world

 

[Ladyelect]

yes, I have. I even deleted myself from the permissions and gave them to myself again and still I cannot access that person's calendar. It's pretty much patchy for everyone here. Some days they can read someone else's calendar and some days they can't. But one person never has any problems with anyone and that's the boss and it isn't anything that she has done because she's computer illiterate.

I'm not too proud to take any more suggestions though.
Thanks.
Pam

 

[beckas]

Here are a few possible fixes:

Check the search order for addresses. Tools, services, addressing. Make sure that Global address list is listed at the top. If it is not, have them switch it and then file, exit and logoff out of Outlook. Relaunch Outlook and try to open the calendar again.

If addressing is listed correctly and they still have the problem, check to make sure that they do not have a personal address book entry for the person that they are trying to open the calendar. If they do have one, have them delete it or rename it to something other than the Global Address list name.

I saw this problem when we had a mixed Outlook environment (2000 and 98). Before we applied Office 2000 SR1, I was able to resolve the problem by changing the permission on the calendar to something other than "reviewer". I don't know why this fixed it but it did. If you are using Outlook 2000, you might want to upgrade to SR1 for the heck of it. See these articles for more info:

http://support.microsoft.com/default.aspx?scid=kb;en-us;252893&Product=out2K

http://support.microsoft.com/default.aspx?scid=kb;en-us;248149&Product=out2K

 

[Ladyelect]

Thanks, Beckas. That wasn't the problem either. We are running Outlook 2002 even though the rest of Microsoft Office is 2000.

But I did figure out that I didn't have the Company LDAP Directory listed in my address book.

So I haven't figured out the exact problem yet, but I feel like I'm getting there. I'll have to pursue the hunt tomorrow.

 

[pmcillin]

Ladelect, I hope by now you were able to fix the problem, if not, check your permissions from the server level on the user's mailbox rights. i.e Active Directory--Exchange Advanced, mailbox rights and add yourself with the appropraite permissions.

Hope this helps

pmcillin

 

[Ladyelect]

Interesting that you should mention that. While fiddling on something else, it hit me I should try changing permissions at the server level. It won't let me. I opened the properties in Exchange of the person's calendar I am trying to access. It gave me a message that the permissions are incorrectly ordered, which may cause some entries to be ineffective. Press OK to continue and sort the permissions correctly or cancel to reset the permissions.

Click on OK and you get the warning message Caution! Deny entries take priority over Allow entries, which can cause unintended effects due to group memberships.

Click on OK and Unable to save permission changes on Judy. The network request is not supported.

I think that's where the problem is. After I figure out how to get around that, I'll have it made. Thanks!