Exchange 2007-As Delegate Cannot Accept Equipment Scheduling Request

I have set up several equipment accounts, similar to the way I currently have functioning room accounts set up, but some of my equipment accounts are not working as expected.  The scenario I want to achieve is that a requestor of a piece of equipment receives a tenative email until the delegate has approved the request, then they receive an acknowledgement.  This is working on all of my rooms, and also on some of my equipment, but on others, it is not.  On the non-working equipment, as the delegate, I receive a message:  "cannot open calendar folder for user ***.  Operation failed.  The odd thing is that I have several identically set equipment resources and several work, while others does not.  Through group membership, I have set up the delegates and also added the group to have full access permissions on both .  I have attached the settings for each of two pieces of equipment--one working, one not.  I"m not sure where I have gone wrong, so any assistance would be much appreciated.
SRC_ITAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

SRC_ITAuthor Commented:
I have discovered more about this issue and it doesn't appear to be Exchange-related after all.  It seems that if a delegate has authenticated to one of our domain controllers, they receive the message that they cannot open the calendar folder.  Another user in the same delegate group, who has authenticated to a different domain controller is able to accept the meeting that the first user cannot.  We appear to have an issue with one of our domain controllers, which is perhaps a replication issue.  
0
seb_ackerCommented:
Lol
That was my first thought after reading your intro :)

Let us know if it's going better ;)
0
SRC_ITAuthor Commented:
In Active Directory Sites and Services found that domain controllers did not have automatically generated connections in NTDS settings to all of the other domain controllers, so I manually added connections to those that did not have them, and this seems to have cleared up the issue.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.