accucom
asked on
exchange 2003 to 2008 on SBS - move all replicas for public store
The migration was going well when migrating from sbs2003 to sbs2008. Moved all mailboxes per MS from Exchange 2003 to 2007 except a couple of large mailboxes, and then attempted to move all replicas on the public store. This seemed to be going well until the information store stopped. Each time started, a few seconds later it would stop. Event errors are below.
Source: Application error
event ID: 1000
faulting application store.exe, version 6.5.7653.38 faulting module exsmtp.dll, version 6.5.7638.1, fault address 0x000096f6
Source: EXOLEDB
event ID: 131
The events subsystem for the public folder database was not initialized because the system folder named 'StoreEvents{2D0D9D5C-057C -4DA6-A467 -61D3F4E00 AAF}' and its subfolders do not have a replica on this server. If you are not in the process of removing the public folder database, add a replica for these folders on this server, wait for content to replicate from another server, and then dismount and remount the database.
Source: Microsoft Exchange Serv
Event ID: 1000
The description for Event ID ( 1000 ) in Source ( Microsoft Exchange Server ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: store.exe, 6.5.7653.38, 484e994d, exsmtp.dll, 6.5.7638.1, 430e8020, 0, 000096f6.
Searched left and right in all forums, google and MS. As of now, I can start the Info store and when looking at the EMC on 2003, i can expand mailbox store but when looking at the Mailboxes, get "An error occurred while retrieving the requested information. The MS Exchange Info Store service is not running or the MS Exchange Server computer is unavailable.
ID no: c103074d
Exchange System Manager
Is this a corrupted database? It has been 8 hours since the replica was triggerred and there isnt much in the public store. Help.
Source: Application error
event ID: 1000
faulting application store.exe, version 6.5.7653.38 faulting module exsmtp.dll, version 6.5.7638.1, fault address 0x000096f6
Source: EXOLEDB
event ID: 131
The events subsystem for the public folder database was not initialized because the system folder named 'StoreEvents{2D0D9D5C-057C
Source: Microsoft Exchange Serv
Event ID: 1000
The description for Event ID ( 1000 ) in Source ( Microsoft Exchange Server ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: store.exe, 6.5.7653.38, 484e994d, exsmtp.dll, 6.5.7638.1, 430e8020, 0, 000096f6.
Searched left and right in all forums, google and MS. As of now, I can start the Info store and when looking at the EMC on 2003, i can expand mailbox store but when looking at the Mailboxes, get "An error occurred while retrieving the requested information. The MS Exchange Info Store service is not running or the MS Exchange Server computer is unavailable.
ID no: c103074d
Exchange System Manager
Is this a corrupted database? It has been 8 hours since the replica was triggerred and there isnt much in the public store. Help.
ASKER
hierarchy has been replicated and completed. still cannot keep info store running on 2003sbs, thus preventing move of final mailboxes. Any other suggestions?
ASKER
unbelievable! I disabled all of Symantec's services for Endpoint and was able to get into the EMC on 2003. Endpoint has been on this server for years and all of a sudden, starts trouble? Anybody have an idea why this has happened for the points? at least the issue is resolved. thanks.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
yes, that is what I meant. I disabled it on the source sbs 03 server. Not sure why all of a suddent it had a conflict after years of being on it.
Sorry, I didn't refresh before posting before. It can be that a recent update cause issue.
On the other hand, when "replicating" you generator quite some traffic/log files etc. It might be possible that it started giving issues because of that.
Grts,
Michael
On the other hand, when "replicating" you generator quite some traffic/log files etc. It might be possible that it started giving issues because of that.
Grts,
Michael
Check here for more information:
http://msexchangeteam.com/archive/2007/10/30/447339.aspx