Randomly my Exchange 2007 box no longer starts the information store service.. If I check the event log I get Event ID's:- 2050 - Process STORE.EXE (PID=4844). The shared memory heap could not be created. This may be caused if physical memory limits have been exceeded. It may also be caused if too many other processes are running DSAccess. You may be able to resolve this error by restarting the Exchange server that logged this event. 1121 - Error 0x80004005 connecting to the Microsoft Active Directory. 5000 - Unable to initialize the Microsoft Exchange Information Store service. - Error 0x80004005. I have 2 DC's both are up and working fine. The GC Server is the Primary DC and I can connect to it fine. Any suggestions would be greatly apreciated?

Hello, i recommend you run Exbpa and then check for any memory issue warnings it will tell you. Can you post the critical errors it will show up?

Hi I get the following Critical errors:- The specified Exchange server <server> for processing Recipient Update Service 'Recipient Update Service (Enterprise Configuration)' is running Exchange Server 2007. The service will not process updates in this configuration, please choose a non-Exchange Server 2007 server to host the service. 'MailboxRole' is partially configured on server <server>. Either setup is configuring it right now or setup failed while configuring it. Please rerun the setup if isn't being run.

Okay now just this message - which I presume is because the service has not started? 'MailboxRole' is partially configured on server <server>. Either setup is configuring it right now or setup failed while configuring it. Please rerun the setup if isn't being run.

Ok some questions: Has it ever worked nicely, i mean, without this issue? Can you please look for any errors on your Exchange Server setup log? Its inside: C:\Exchangesetuplogs\Exchangesetup.log Open the file on notepad and do a search by "error". Tell me the last lines you will find, not the first ones. If you use the command get-exchangeserver | fl, it will show you the current DCs, GCs and Config DCs you are using. I suppose it will show your both DCs for the field "DCs", but only one for GC and only one for Config DC's. Do the "get-exchangeserver | fl" command and tell me if the fields for "Currentdomaincontrolers, currentGCDomainControllers, and CurrentConfigDomainControllers" are set to "<>". Initially, if its really an AD communication problem, since you're not having problems on doing Exchange Server configurations inside EMC or EMS, and since the problem is intermitent, i can suppose that DSAccess, while doing round robin, is selecting a faulty DC (from your 2 DCs) to read information from AD, or is having a communication problem with it. Let's get a better logging for the topology discovery proccess and see what's going on when DSAccess is trying to read information from AD: Get into regedit, go to HKLM\system\currentcontrolset\services\MSExchange Topology\Diagnostics Change the reg_dword "topology discovery" to 7 Try to start the MSExchange Information Store service again Look for any Topology Discovery related events on your application log, and tell us here We can continue after this information is seen by you.

Been setup and working since December. Went from 2003 to 2007. Hasnt had a single issue yet. Although I havent been able to remove 2003. Okay sifting through the log now, but if I run get-exhangeserver | fl it lists DC's as {}. I also get an additional Event 9154 Log now:- DSACCESS returned an error '0x80040920' on DS notification. Microsoft Exchange System Attendant will re-set DS notification later.

Most common error in the Log file is [1] [ERROR] A Setup failure previously occurred while installing the Mailbox role. Either run Setup again for just this role, or remove the role using Control Panel.

Try running: Setup.com /mode:install /roles:MB from the Exchange media. It seems like the mailbox role never completed setup. After you get the message that the installation completed successfully, reapply any service packs and hotfixes you previously installed.-- Ed Crowley MVP"There are seldom good technological solutions to behavioral problems.". "Theelk" wrote in message news:92757936-eaa6-4d23-a15d-5b8567ccecec... Most common error in the Log file is [1] [ERROR] A Setup failure previously occurred while installing the Mailbox role. Either run Setup again for just this role, or remove the role using Control Panel. Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Ok dude, it seems you have got an error while on the installation proccess, regarding contacting a DC and doing the required AD configurations. Also, your DCAccess is not using any static DCs. I think that while on the setup proccess, you had some errors while contacting the AD but you could finish it anyways. We should start the setup proccess again but specifying a DC instead of using one randonmly. I would specify the GC. The Exchange Setup proccess can fail and if you start it again later, it will continue from where it stopped, so you can follow Ed's tips and try to reinstall it again. As your issue is intermitent, we can state it is working sometimes. So, in my opinion Exchange is reading info from AD from a bad DC and thus the Information Store service cannot start. I would recommend you specify a static DC on some parameters of set-exchangeserver cmdlet. set-exchangeserver -StaticDomainControllers Then you specify your GC as the source domain controller, for reading information from AD. If it still doesn't work, try to specify the other DC as the "StaticDomainControllers", but for testing purposes only specify ONE AT A TIME. If this doesn't work, then use Ed Crowley's tip and specifying the GC on the command: Setup.com /mode:install /roles:MB /DomainControler:GCName Afer this, watch if the Setup finishes and look again for any errors on Exchangesetup.log. If there are errors like the one you told us regarding the "Setup failure", then try the command again specifying the other DC. Let us know after you do these procedures.

HI <Randomly my Exchange 2007 box no longer starts the information store service.. If I check the event log I get Event ID's:-> that means that you already worked on this exchange server normally (send, receive, create mailboxes) !!!!!!!!!! Kindly adviceRegards A.Karam MCSE

Hi Ed, Is this possible? The server has been working for several months? Its only since the services has failed to start that, that error has started popping up? Thanks guys for your replies so far.

Yes has worked fine for months.....

Also Sam, I have tried to run set-exchangeserver -StaticDomainControllers DCname, but when I run get-exchangeserver | fl its still reports the DC's and GC as {}

Servers can indeed work indefinitely with setup not having completed. In fact, my current customer's entire collection of mailbox servers did not complete setup, something we're going to fix very soon before applying SP2 and RU2.-- Ed Crowley MVP"There are seldom good technological solutions to behavioral problems.". "Theelk" wrote in message news:eea1f3a9-b4f5-4d34-b52c-9ddc983c7f46... Hi Ed, Is this possible? The server has been working for several months? Its only since the services has failed to start that, that error has started popping up? Thanks guys for your replies so far. Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Have got this resolved now. Will post what I did once were completely out of the woods.

Be glad to hear you have resolved the issue. Please share with us the solution once you have time. That will benefit more people. Thanks, Elvis

Okay sorry for the delay coming back.Just so you know I double checked the installation log and the mailbox role reported that it installed fine during the original installation.I tried uninstalling the mailbox role but couldn't as it would error stating that another installation was currently running (this is after several restarts).After googling a bit I found the following http://itowns.blogspot.com/2009/09/cant-uninstall-exchange-2007-sp1.html which allowed me to uninstal the role. Only problem I had now is that it detected that there was a mailbox store and a public folder store.So I needed to remove/detach them before I could do anything, but without the information store starting this was not possible via EMS or EMC. In the end I used ADSI edit and removed reference to both stores from:-Configuration config domain Services Microsoft Exchange Administrative Groups exchange Admin Group Servers Your server name Information storeAfter this I tried to uninstall the mailbox role again and thank god it removed it. After a restart I tried to reinstall the mailbox role (and then planned to attach the Mailbox Store). Only problem was the installation process would get right to the last step and try to start the information store services but would fail so the problem still existed.I'm now clutching at straws and decided to install Exchange 2007 SP2 on the box which worked fine. This stage I'm crossing everything when trying to install the mailbox role again. Thankfully after SP2 it installed fine. I now tried to restore the mailstore to the server but of course a SP1 mail store will not restore over an SP2 one :( I say of course, but thats a bit awkward.I decided to take the current (new, empty) mail store offline and replace the files with the old ones that were still locally on the machine, brought it back online and happy days I have all the mailboxes (Disconnected but they are there).Next I had to remove all the users Exchange attributes by disabling them in EMC, then re-attached the disconnected mailboxes to the relevent user.Had some issues here where some users were unable to move or delete emails, but hey after 3 days without mail atleast they can now see and read them.Obviously the mail store was SP1 and Exchange is now SP2 so presumed that this was the cause so I created a new Storage group and mailstore, and began moving their mailboxes out of the old one into the new one. This resolved the access issues and we have been working fine since.We had Exchange 2003 for over 3 years and didnt have a hint of problems and moved to Exchange 2007 at the end of December so had it 3 months and I have to say that we have lost all confidence with it. The errors in the event log were so ambigious its impossible to even say what caused the problem or how to stop it happening again. Nothing had changed with our DC's and I have run dcdiag several times during this whole nightmare and no issues were reported. No AD related problems have occured either.