|
chrisb2812 -> Info store mount issues (27.Feb.2007 4:55:40 AM)
|
OK guys and gals, this is a good one for all of you. I have raised this issue with Microsoft and yet they have not managed to come up with an answer so i am hoping that maybe someone out there in the wide community may have seen this before. Basically any new information stores which we create can not be mounted, exisitng information stores are fine. I have attempted to create them in new storage groups, and also in current storage groups but to no avail. On attempting to mount we get the good old traditional c1041724 error message which is common when they do not mount. We also get the following event error messages: Event Type: Error Event Source: MSExchangeIS Event Category: General Event ID: 9546 Date: 12/02/2007 Time: 12:07:21 User: N/A Computer: WILSVR500 Description: Failed to create the Event Registration Mailbox for Database Second Storage Group\SG2 1st Private Info Store. Error - 0xbf69. Event Type: Error Event Source: MSExchangeIS Event Category: General Event ID: 9519 Date: 12/02/2007 Time: 12:07:21 User: N/A Computer: WILSVR500 Description: Error 0x80004005 starting database "Second Storage Group\SG2 1st Private Info Store" on the Microsoft Exchange Information Store. <NULL>. Event Type: Error Event Source: MSExchangeIS Event Category: General Event ID: 9518 Date: 12/02/2007 Time: 12:07:21 User: N/A Computer: WILSVR500 Description: Error 0x80004005 starting Storage Group /DC=UK/DC=MIL/DC=R/DC=ARMY/CN=CONFIGURATION/CN=SERVICES/CN=MICROSOFT EXCHANGE/CN=ARMY/CN=ADMINISTRATIVE GROUPS/CN=FIRST ADMINISTRATIVE GROUP/CN=SERVERS/CN=WILSVR500/CN=INFORMATIONSTORE/CN=SECOND STORAGE GROUP on the Microsoft Exchange Information Store. MDB failed to start. The 9519 message does not always appear! We are running on a 2000 AD with pure exchange 2000. About 6 months ago a new info store was created and mounted fine, so it must be something that has changed since then. But no one is sure what change/s could have caused this. We do have a network which holds in excess of 90 exchange servers, the situation is the same with all servers, and we have even attempted building a new server onto the domain which still exhibits the same problem. As further info, the edb and stm files for the info store do not even get created. Public stores do not appear to be effected, but obviously we can not create a new public store without having to create a new public store tree, which change management would get upset with! I am waiting to here back as to whether or not the public store on the newly built server works ok.
|
|
|
|