Re: Information Stores becomes inaccessible error 0x80004005, 0xb72

I have been doing some further investigation, and have gone through our system and made sure we are up to date with the latest updates (windows updates and exchange updates). I have done some basic performance testing and can't see any immediate issues with memory,hdd, cpu usage etc. Now the problem is still sporadic but it doesn't stop me from accessing the server from ESM (which it did before), and after a while people can get access from Outlook 2003 (which pops up with the message outlook is trying to retreive data from xxx when it goes wrong).

But funny thing is people can still get access through OWA - which we have instructed users to use when this happens. Now the permissions change suggested relates to a MAPI call (Outlook Problem/missed update?). The majority of our users access using outlook 2003 through windows 2003 terminal services (could this be an issue?), with the remainder accessing through XP PC's again with Outlook 2003, we have a couple of Vista PC's as well again Office 2003. Now not all of the terminal servers and client pcs are up to service pack 3 for office, could that be an issue?

When doing some troubleshooting I did notice a lot of failed rpc calls in performance monitor, on the exchange server. How many outlook connections can exchange handle - we have about 350 email users.

Thanks for any suggestions - I am at the end of my tether with this one!!!!

"legpeg2008" <mattj@xxxxxxxxxxxxxxxxxxxxxxx(donotspam)> wrote in message news:3849E715-4F04-4935-9A8B-5B6455F66C1C@xxxxxxxxxxxxxxxx
This problem went away for a couple of days, but we had sporadic problems again yesterday. It happened for about an hour each time but went away by itself. Is there anything else I should be looking at? I don't know whether it makes a difference but we have do have two domains, now I have made the permissions change on both.

The exchange servers for the whole company are at head office (domain A).
Domain B only has a file/print/dc (which is also a GC) and is running Windows 2003. Unfortunately the set up of B was performed by an external contractor, and is something I've inherited. I do remember they had a lot of problems getting the users of domain B to see the exchange server in Domain A, when they were setting it up a year ago. My suspicions point me to domain b causing the problem - Could there be something simple they missed or misconfigured?

Thanks in advance.

Matt

"legpeg2008" <mattj@xxxxxxxxxxxxxxxxxxxxxxx(donotspam)> wrote in message news:7F7CA1B2-0571-4D9D-9CB8-D5DFBFAE93A0@xxxxxxxxxxxxxxxx
Thanks for your help. It all seems to be ok now.

Matt

"John Fullbright" <fjohn@donotspamnetappdotcom> wrote in message news:ePJ%23DzKpIHA.2188@xxxxxxxxxxxxxxxxxxxxxxx
Although the article state Exchange 2000, this applies to 2003 also. The problem is a mapi call failed when calling FindOrCreateTokenContextEx. The solution in the article assumes the Read tokenGroupsGlobalAndUniversal permission is missing, which happens occasionally when applying security templates or otherwise mucking with GPOs. I'd try this first.




"Oliver Moazzezi [MVP]" <o.moazzezino@xxxxxxxxxxxxxxxxx> wrote in message news:ea7c5lJpIHA.4736@xxxxxxxxxxxxxxxxxxxxxxx
Here you go: http://support.microsoft.com/kb/291397

Oliver







.