hello. i'm getting the above error when i'm trying to expand the "first storage group". i click ok and then i can't see any of the stores - not the mail and not the public. in all my searches i came across the solution that this is a registry problem with the location of the "gatherlogs" folder. this is not my case. the key points to the correct location (both the private and the public folder key). i have an sbs 2003 with sp2 installed. i installed the r2 in addition, but that didn't solve the problem. further more, i did the following: 1. update /domainprep from the sp2 package to update all the pointers - didn't help. 2. dismounted (with a .vbs script) the mailbox store and run isinteg with the fix switch on it - no good either. 3. try to dismount the public store - couldn't do it. i'm getting an error on the script, which goes like this: Set oDB = CreateObject("CDOEXM.MailboxStoreDB") strDB = "CN=Public Folder Store (Server),CN=First Storage Group,CN=InformationStore,CN=Server,CN=Servers,CN=First Administrative Group,CN=Administrative Groups,CN=MASLUL,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Domain,DC=Domain" oDB.DataSource.Open strDB oDB.Dismount() the error regards the 5th line, char 1... i don't see any syntax problem there...(i just removed the server and domain name from the script for privacy. the script worked well for the mailbox store, and all i changed is the store name from Mailbox Store (Server) to Public Folder Store (Server), so i suspect it's a store problem, not a syntax one) let me just say that the store itself work great. users send and receive e-mails, no errors what so ever from the users point of view... i suspect a future problem, so i try to fix it before one happens... one last thing...the store is around 13GB in size... (the .edb file...) - close to the 15GB limit...can this be the issue? all of the above didn't do any good. i suspect it's a store problem. i can't create new stores also... i can't manage any of the stores... anyone with any thoughts? that would be a great help. thanks guys . . . p.s. i also thought it's an exchange system manager issue, so i tried to install esm on a windows xp workstation in the domain, but that didn't help either....

Hi, I understand that you have performed troubleshooting steps on the gatherlogs from your side and. Greatly appreciate your time and efforts. Based on my research, this issue is possibly related to the corrupted Index file. For the time being, please perform the following steps to try to resolve this issue: Step 1: ================== 1). On the Exchange server, open Registry Editor and back up the entire registry as a precaution. 2). Locate and then click the following registry subkey, where COMPUTERNAME is the name of your server (e.g. MEMEXCHANGE1), and where privcatalog or pubcatalog is the name of the catalog, for example, privF0857535: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Search\1.0\Gather\ExchangeServerMEMEXCHANGE1\privF0857535 3). Verify first that ALL paths listed under that key are valid. Compare with the folders as viewable in Explorer. If any are missing, create new folders to match the path as found in the registry and restart the Microsoft Search service. 4). If that does not work, export and delete the priv<catalog number> keys. 5). Restart Microsoft Search service. 6). Close and open the ESM agin. Can you view the new store now? if the issue still occurs, please go to step 2. Step 2: ===================== Important: Please fully backup your Exchange server and AD first. 1). On Exchange server, stop MS search service. 2). Install the Windows Support tool on your Domain Controller server. 3). On the DC, open ADSIEDIT, navigate to: Config_Container/Configuration/Services/Microsoft Exchange/<Organization_Name>/Administrative Groups/<Administrative_Group_Name>/Servers/<Server_Name>/Information Store/<Storage_Group_affected_by_issue>. 4) For each mailbox store on this SG (Storage Group), clear the following attributes: - msExchCatalog - msExchCIUpdateSchedule - msExchCIUpdateStyle - msExchCIAvailable - msExchCILocation 5) On Exchange server, open registry editor and navigate to HKLM\Software\microsoft\search\1.0\Gather\ExchangeServer_<Computer_Name> Delete all keys with catalog names that match with events ID related to the 80040d1b in the application log. 6) Restart the MS search service. 7). Close and open the ESM again. Whats the result? You can also try to download Exchange Best Practices Analyzer (ExBPA) for fixing the basic error. http://www.microsoft.com/downloads/details.aspx?FamilyID=dbab201f-4bee-4943-ac22-e2ddbd258df3&DisplayLang=en Thanks Allen

Hi Allen. Your solution definetly did the trick - the ADSIEDIT tool solved the problem. thanks a lot for the detailed solution, it worked exactly as u said. I've been searching the web for about a month now for the solution, and finally got one. that's a reliefe.... another problem accoured, as a result of the change...i can't creat full text index on the store (mailbox or public..). i get the error that a catalog with the same name already exists (id: 80041901). any quick solution for that? i'm gonna dig in anyway, but if you can give me a quick one that will save me a lot of time... thanks a lot, you're a real pro!