srsdtech
asked on
Exchange 2003 server Error c1041724 when I try to mount mailbox stores
I am trying to set up Exchange 2003. I have never used Exchange before. I am basically starting from scratch and do not plan to migrate any settings or mailboxes. I will if I can, but am not sure if that functionality will be available from our present e-mail service and we only have 30 users anyway.
My initial problem with installation was trying to figure out what kind of drive / partition / storage configuration to use (is there any good, SPECIFIC information on this? The only thing I could find for sure is that you don't want to put it on a domain controller.) I put out a question to a tech forum (not this one) and waited for an answer. It took too long, so I went ahead with my installation.
I installed Exchange 2003 Standard Edition on a newly installed Windows 2003 SP1 RAID 5 server which provides no other network services. During the installation, I received a few errors to the effect of "Exchange Server 2003 has a known compatibility issue with this version of windows" but went ahead anyway because I know it works on Windows 2003. I figured the problem would go away after installing Exchange SP1 or raising my domain functional level to 2003, which was a plan for later on. After getting Exchange installed, but not configured, I finally got an answer to my question about drive configuration. I needed to use mirrored drives. I only want to do this installation once and I want to do it right so after much agonizing I decided to restart the whole process using the recommended drive configuration.
I tried to uninstall Exchange before reconfiguring the server. I was unable to because "there are users accessing the mailbox store" (not the exact error, but the general idea.) I searched active directory users by email address and found ONE user that had one. I disabled that account and tried to uninstall again. No dice. A few more things didn't work so finally I figured "I am going to wipe everything and start from scratch anyway; what's the harm?" I shut down the server without uninstalling exchange, reconfigured it with mirrored drives, reinstalled the OS with SP1 and hotfixes and reinstalled exchange 2003 and then Exchange SP1.
During the second Exchange 2003 installation:
I still got the compatibility errors.
I could not initially install the entire Exchange program. I had to install the tools first. The error was that I had to shut something down with the Exchange System Manager. I can't remember what that was, but I did it and was able to go back and install the rest of Exchange.
I moved the mailbox stores to my second mirrored drive.
Now we get to my problem.
The mailbox stores will not mount. When I try to mount them, I get error c1041724 “try restarting a bunch of stuff.” I restarted that and more and it didn’t work.
I found MS kb274534 which said I probably had two System mailbox objects and needed to delete one. I checked (in ADUC/MSEx System Objects), and there was only one of them, but it was disabled. I enabled it, but still could not mount the stores.
But while I only found one System mailbox object, I found two of everything else. Each of the other entries had one “bare entry” and one that had a serial number of some kind appended to it.
MY QUESTIONS:
How do I get my stores to mount?
I think I have some stuff in Microsoft Exchange System Objects that should not be there and that is causing problems.
I think there are some other remnants of the first Exchange installation still residing in my network that I need to clear out before I can proceed. How do I verify this and if it is the case, how do I fix it?
If this is too big an issue, I have absolutely no problem with reinstalling the whole thing again. If someone can tell me what to do to make sure every remnant of Exchange is off the network, I can start over from the operating system on up.
My initial problem with installation was trying to figure out what kind of drive / partition / storage configuration to use (is there any good, SPECIFIC information on this? The only thing I could find for sure is that you don't want to put it on a domain controller.) I put out a question to a tech forum (not this one) and waited for an answer. It took too long, so I went ahead with my installation.
I installed Exchange 2003 Standard Edition on a newly installed Windows 2003 SP1 RAID 5 server which provides no other network services. During the installation, I received a few errors to the effect of "Exchange Server 2003 has a known compatibility issue with this version of windows" but went ahead anyway because I know it works on Windows 2003. I figured the problem would go away after installing Exchange SP1 or raising my domain functional level to 2003, which was a plan for later on. After getting Exchange installed, but not configured, I finally got an answer to my question about drive configuration. I needed to use mirrored drives. I only want to do this installation once and I want to do it right so after much agonizing I decided to restart the whole process using the recommended drive configuration.
I tried to uninstall Exchange before reconfiguring the server. I was unable to because "there are users accessing the mailbox store" (not the exact error, but the general idea.) I searched active directory users by email address and found ONE user that had one. I disabled that account and tried to uninstall again. No dice. A few more things didn't work so finally I figured "I am going to wipe everything and start from scratch anyway; what's the harm?" I shut down the server without uninstalling exchange, reconfigured it with mirrored drives, reinstalled the OS with SP1 and hotfixes and reinstalled exchange 2003 and then Exchange SP1.
During the second Exchange 2003 installation:
I still got the compatibility errors.
I could not initially install the entire Exchange program. I had to install the tools first. The error was that I had to shut something down with the Exchange System Manager. I can't remember what that was, but I did it and was able to go back and install the rest of Exchange.
I moved the mailbox stores to my second mirrored drive.
Now we get to my problem.
The mailbox stores will not mount. When I try to mount them, I get error c1041724 “try restarting a bunch of stuff.” I restarted that and more and it didn’t work.
I found MS kb274534 which said I probably had two System mailbox objects and needed to delete one. I checked (in ADUC/MSEx System Objects), and there was only one of them, but it was disabled. I enabled it, but still could not mount the stores.
But while I only found one System mailbox object, I found two of everything else. Each of the other entries had one “bare entry” and one that had a serial number of some kind appended to it.
MY QUESTIONS:
How do I get my stores to mount?
I think I have some stuff in Microsoft Exchange System Objects that should not be there and that is causing problems.
I think there are some other remnants of the first Exchange installation still residing in my network that I need to clear out before I can proceed. How do I verify this and if it is the case, how do I fix it?
If this is too big an issue, I have absolutely no problem with reinstalling the whole thing again. If someone can tell me what to do to make sure every remnant of Exchange is off the network, I can start over from the operating system on up.
Also try and clean up your log files
.log and .chk files in the mdbdata directory Give that a shot to. i know with Ex2000 I had to clear my logs and the mounts would restore no problem.
.log and .chk files in the mdbdata directory Give that a shot to. i know with Ex2000 I had to clear my logs and the mounts would restore no problem.
ASKER
No, I have not tried those two fixes. I will start on them now and let you know.
ASKER
Well, that was fast.
The link did not seem to apply, as I was not getting the specific error events it mentioned. Also, I do not have a "Restore.env" file on my server anywhere.
The MDBDATA directory is empty.
The link did not seem to apply, as I was not getting the specific error events it mentioned. Also, I do not have a "Restore.env" file on my server anywhere.
The MDBDATA directory is empty.
Mounting a Database After Restore Fails with Error Message c1041724
View products that this article applies to.
Article ID : 253931
Last Review : July 17, 2006
Revision : 4.0
This article was previously published under Q253931
SYMPTOMS
After restoring a database from an online backup, when you attempt to mount the database using Exchange System Manager, you may receive the following error message:
An internal processing error has occurred. Try restarting the Exchange System Manager or the Microsoft Exchange Information Store service, or both.
ID no: c1041724
Exchange System Manager
The following events are logged in the application log: Event Type: Error
Event Source: ESE98
Event Category: Logging/Recovery
Event ID: 619
Description:
Information Store (nnnn) Attempted to attach database
'D:\Exchsrvr\MyStorageGrou
restored from a backup set on which hard recovery was not started
or did not complete successfully.
For more information, click
http://search.support.microsoft.com/search/?adv=1.
Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 9519
Description:
Error 0xfffffde0 starting database "[GUID of database]" on the Microsoft
Exchange Information Store.
For more information, click
http://search.support.microsoft.com/search/?adv=1.
Back to the top
CAUSE
The Last Backup Set check box was not selected during the restore, so hard recovery was not run.
Back to the top
RESOLUTION
Before the database can be mounted, hard recovery must be completed. You can run hard recovery manually with the following command:
eseutil /cc [path to directory containing Restore.env]
For example, if the path specified for the "Temporary location for log and patch files" during the restore process is C:\TempRest, the command to run hard recovery is:
eseutil /cc c:\temprest
Note You need to run eseutil.exe from the Exchsrvr\Bin directory.
After hard recovery completes, mount the database using the Exchange System Manager.
Back to the top
MORE INFORMATION
To avoid this issue, select the Last Backup Set check box during the restore process.
Back to the top
--------------------------
APPLIES TO
• Microsoft Exchange Server 2003 Enterprise Edition
• Microsoft Exchange Server 2003 Standard Edition
• Microsoft Exchange 2000 Server Standard Edition
• Microsoft Windows Small Business Server 2003 Premium Edition
• Microsoft Windows Small Business Server 2003 Standard Edition
Back to the top
Keywords: kberrmsg kbprb KB253931
Back to the top
View products that this article applies to.
Article ID : 253931
Last Review : July 17, 2006
Revision : 4.0
This article was previously published under Q253931
SYMPTOMS
After restoring a database from an online backup, when you attempt to mount the database using Exchange System Manager, you may receive the following error message:
An internal processing error has occurred. Try restarting the Exchange System Manager or the Microsoft Exchange Information Store service, or both.
ID no: c1041724
Exchange System Manager
The following events are logged in the application log: Event Type: Error
Event Source: ESE98
Event Category: Logging/Recovery
Event ID: 619
Description:
Information Store (nnnn) Attempted to attach database
'D:\Exchsrvr\MyStorageGrou
restored from a backup set on which hard recovery was not started
or did not complete successfully.
For more information, click
http://search.support.microsoft.com/search/?adv=1.
Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 9519
Description:
Error 0xfffffde0 starting database "[GUID of database]" on the Microsoft
Exchange Information Store.
For more information, click
http://search.support.microsoft.com/search/?adv=1.
Back to the top
CAUSE
The Last Backup Set check box was not selected during the restore, so hard recovery was not run.
Back to the top
RESOLUTION
Before the database can be mounted, hard recovery must be completed. You can run hard recovery manually with the following command:
eseutil /cc [path to directory containing Restore.env]
For example, if the path specified for the "Temporary location for log and patch files" during the restore process is C:\TempRest, the command to run hard recovery is:
eseutil /cc c:\temprest
Note You need to run eseutil.exe from the Exchsrvr\Bin directory.
After hard recovery completes, mount the database using the Exchange System Manager.
Back to the top
MORE INFORMATION
To avoid this issue, select the Last Backup Set check box during the restore process.
Back to the top
--------------------------
APPLIES TO
• Microsoft Exchange Server 2003 Enterprise Edition
• Microsoft Exchange Server 2003 Standard Edition
• Microsoft Exchange 2000 Server Standard Edition
• Microsoft Windows Small Business Server 2003 Premium Edition
• Microsoft Windows Small Business Server 2003 Standard Edition
Back to the top
Keywords: kberrmsg kbprb KB253931
Back to the top
scratch what i just sent you.
Try this one:
C1041724 Error Occurs When You Try to Mount a Database
View products that this article applies to.
Article ID : 294318
Last Review : July 17, 2006
Revision : 7.0
This article was previously published under Q294318
SYMPTOMS
When you try to mount an Exchange database, you may receive the following error message:
An internal processing error has occurred. Try restarting the Exchange System Manager or the Microsoft Exchange Information Store service, or both.
ID no: C1041724
Exchange System Manager
Back to the top
CAUSE
This issue can occur if there is not a sufficient amount of free disk space on the drive that contains the databases that you are trying to mount.
Back to the top
RESOLUTION
To resolve this issue, free up some disk space on the drive, and then try to mount the database again.
Back to the top
MORE INFORMATION
When this issue occurs, the following event ID messages may be logged in the Application event log:
Event ID: 9519
Source: MSExchangeIS
Type: Error
Description: Error No space left on disk starting database "First Storage Group\Test" on the Microsoft Exchange Information Store.
-or-
Event Type: Error
Event Source: MSExchangeIS
Event Category: System Event
Event ID: 9559
Computer: SERVER
Description:
The log disk is full for storage group "First Storage Group". Attempting to unmount all databases in this storage group.
Back to the top
--------------------------
APPLIES TO
• Microsoft Exchange Server 2003 Enterprise Edition
• Microsoft Exchange Server 2003 Standard Edition
• Microsoft Exchange 2000 Server Standard Edition
• Microsoft Windows Small Business Server 2003 Premium Edition
• Microsoft Windows Small Business Server 2003 Standard Edition
Back to the top
Keywords: kberrmsg kbprb KB294318
Back to the top
C1041724 Error Occurs When You Try to Mount a Database
View products that this article applies to.
Article ID : 294318
Last Review : July 17, 2006
Revision : 7.0
This article was previously published under Q294318
SYMPTOMS
When you try to mount an Exchange database, you may receive the following error message:
An internal processing error has occurred. Try restarting the Exchange System Manager or the Microsoft Exchange Information Store service, or both.
ID no: C1041724
Exchange System Manager
Back to the top
CAUSE
This issue can occur if there is not a sufficient amount of free disk space on the drive that contains the databases that you are trying to mount.
Back to the top
RESOLUTION
To resolve this issue, free up some disk space on the drive, and then try to mount the database again.
Back to the top
MORE INFORMATION
When this issue occurs, the following event ID messages may be logged in the Application event log:
Event ID: 9519
Source: MSExchangeIS
Type: Error
Description: Error No space left on disk starting database "First Storage Group\Test" on the Microsoft Exchange Information Store.
-or-
Event Type: Error
Event Source: MSExchangeIS
Event Category: System Event
Event ID: 9559
Computer: SERVER
Description:
The log disk is full for storage group "First Storage Group". Attempting to unmount all databases in this storage group.
Back to the top
--------------------------
APPLIES TO
• Microsoft Exchange Server 2003 Enterprise Edition
• Microsoft Exchange Server 2003 Standard Edition
• Microsoft Exchange 2000 Server Standard Edition
• Microsoft Windows Small Business Server 2003 Premium Edition
• Microsoft Windows Small Business Server 2003 Standard Edition
Back to the top
Keywords: kberrmsg kbprb KB294318
Back to the top
Checkout this Technet about mounting error/issues:
http://www.microsoft.com/technet/prodtechnol/exchange/2003/wontmount.mspx
http://www.microsoft.com/technet/prodtechnol/exchange/2003/wontmount.mspx
ASKER
RE: http://www.microsoft.com/technet/prodtechnol/exchange/2003/wontmount.mspx
I have been through these steps earlier and didn't have any luck. There are a few I could not figure out, and I will go through again and determine the result of each fix listed under the error I am getting (c1041724.)
For the record,
1. The Application events I am getting are 9175 (lots, about one a minute), 8197, and 9518.
2. There is no antivirus currently installed on the server.
3. I can't mount a blank database because I have Exchange Standard and am maxed out. The stores are both (public and private) empty, so there is no size-limit issue.
4. I have a completely blank Exchange application on this server. There is absolutely no information that I would be concerned about losing. My only concern is doing something that leaves disruptive information trapped on the rest of the network (which I kind of think I may have already done.)
I'll work through the steps I mentioned above and then repost.
I have been through these steps earlier and didn't have any luck. There are a few I could not figure out, and I will go through again and determine the result of each fix listed under the error I am getting (c1041724.)
For the record,
1. The Application events I am getting are 9175 (lots, about one a minute), 8197, and 9518.
2. There is no antivirus currently installed on the server.
3. I can't mount a blank database because I have Exchange Standard and am maxed out. The stores are both (public and private) empty, so there is no size-limit issue.
4. I have a completely blank Exchange application on this server. There is absolutely no information that I would be concerned about losing. My only concern is doing something that leaves disruptive information trapped on the rest of the network (which I kind of think I may have already done.)
I'll work through the steps I mentioned above and then repost.
srsdtech,
I use a website call eventid.net for error codes : these could be helpful to you or not. I would start with this stuff thought.
Here is the report for 9175
Event ID: 9175
Source MSExchangeAdmin
Type Error
Description The MAPI call 'OpenMsgStore' failed with the following error: The attempt to log on to the Microsoft Exchange Server computer has failed. The MAPI provider failed. Microsoft Exchange Server Information Store ID no: 8004011d-0512-00000000
Things to understand What is MAPI?
Comments Mihai Andrei (Last update 11/28/2005):
You may see this event if you modify the default permissions on mailbox stores and public folder stores in Exchange 2000 Server or in Exchange Server 2003. See M328229 for additional information on this situation.
Ionut Marin (Last update 6/12/2005):
As per Microsoft: "This event can have several causes and the ID number in the Description section of the event will be the only difference between the events. Depending on what the underlying cause of the problem is, the ID number will vary". See MSEX2K3DB for more details on this event.
From a newsgroup post: "Before moving users, stop the ADC service and stop any antivirus software".
See M278888 for additional information on this event.
Ed Crowley (Last update 6/12/2005):
I received this error when the account was disabled but did not have the “Associated External Account” right set. Setting it allowed the mailbox to move.
Kevin Brinnehl (Last update 4/12/2005):
This event can also occur if the user account is disabled in Active Directory. This event should also be accompanied by Event ID 9548 from source MSExchangeIS. Once I enabled the account, I was able to move the mailbox.
Katherine Coombs (Last update 9/30/2004):
This error will also appear if the mailbox store is not mounted.
Anonymous (Last update 9/9/2004):
This can also occur if your mail server object is missing under the security tab of the mail store properties. We received this error message when we were practicing disaster recovery in an isolated environment. After we did a restore of the full mail db, we could not get the stores to mount. Once I added our mail server object to the ACL of the Security tab of the store, all was well.
Ken Gander (Last update 2/15/2004):
This also happens when running Norton/Symantec Antivirus Corporate/Enterprise and it is not configured properly. If it is set to scan the whole server without excluding the Exchange directories, Norton Antivirus deletes/quarantines “Exx.log” files. This all seems to be from MyDoom. Have had to Hard Repair four Exchange 200x servers already as Norton Antivirus deleted the log file since it was set to delete not to quarantine. You must exclude all the Exchange directories and the M: drive.
Adrian Grigorof (Last update 10/24/2003):
As per Microsoft: "These errors are reported because Move Mailbox cannot log on to the system attendant mailbox. The system attendant has a mailbox on each server, usually on the default mailbox store". There are several Microsoft articles with information about this event: M264413, M288598, M317338, M326990.
This is 8197
Event ID: 8197
Source MSExchangeFBPublish
Type Error
Description Error initializing session for virtual machine <virtual machine name>. The error number is <error>. Make sure Microsoft Exchange Store is running.
Comments Mihai Andrei (Last update 5/8/2006):
- Error: 0x80040111 - See M918006.
Andrei Ungureanu (Last update 9/17/2005):
See the link to "MSDN Posts" for general troubleshooting on this event and for information about related problems.
Ionut Marin (Last update 7/10/2005):
- Error: 0x80040111 - See M828764.
- Error: 0x8004011d - See M266312, M282964, M821889, M822579, and M896703.
As per Microsoft: "Free/Busy Publishing has encountered errors when attempting to log on to the private or public Exchange stores. Transient occurrences of this event are not a problem, but if the recurrence is every 25 to 30 minutes, then Free/Busy Publishing is down for all Outlook Web Access (OWA) users. This event can also be generated if relevant services have recently been cycled or re-started". See MSEX2K3DB for more information on this event.
Eric Suger (Last update 3/17/2005):
In our case, it turned out that Active Directory issues caused the problem. More precisely, there were multiple entries of a servicePrincipalName "HOST/<Machine>". To see if this is your problem look for KDC error messages in your Windows System event logs.
Anonymous (Last update 11/10/2004):
I recently upgraded Exchange 2000 to SP3. After the upgrade, the Information Store was unable to mount. I received the following Event IDs: 505, 8197, 9175, and 9519. I searched the Internet and found a solution. It turns out that Exchange 2000 SP3 is not able to mount a compressed store. My drive was not compressed but the folder where the Information store was located had compression enabled. The solution I found stated the following: “Although our drive that stores the database files was not compressed, the database files (priv1.edb, priv1.stm, pub1.edb, pub1.stm) themselves had their compressed attributes checked; I unchecked them and rebooted. Now everything appears to be working". See the links to “Google Thread” and “EventID 505 from source ESE” for additional information on this issue.
Richard Wesseling (Last update 11/2/2004):
A missing Schedule+ Free/Busy System Folder could cause this error. To correct this see M284200.
Fred Orcutt (Last update 7/20/2004):
- Error 0x8004011d - On an Exchange 2003 server, I received this message with Information Store running and both private and public stores mounted. I eliminated the error by stopping Exchange System Attendant and its dependent services, then restarting SA and each dependency individually. MS Exchange Free Busy Publish then initialized properly.
Anonymous (Last update 3/3/2004):
I was receiving EventID 8197 along with EventID 8207 in the application log every 50 minutes on my Exchange 2000 SP3 server. The 8197 event had the error code: 0x80040111. The 8207 error code was 0x80004003. Clicking on the link in the 8197 log entry, I found a suggestion from Microsoft to restart the System Attendant service. I did this and it cleared up the problem, and the events stopped.
Craig Curtis (Last update 2/23/2004):
- Error: 0x80040111 - This problem can be caused by having more then one domain in the same AD site with the Exchange 2003 server. Exchange will query AD for all the GCs in the AD site and pick one at random. If your Exchange 5.5 server has a trust with a child domain and not the parent, the error will happen every 25 minutes if Exchange picks a GC in the parent domain. Put the Exchange 2003 server in a new AD either site with a couple of GCs, or create a two-way trust between the Exchange 5.5 domain and all domains in the AD site. You could also see article M319206 to force a GC (not recommend).
Jean-Paul Leccia (Last update 12/24/2003):
- Error: 0x8004011c - Our users could not access the PF and the OAB but they could continue to send/receive mails. To fix this, in the "Mailbox Store <server name> Properties", we reapplied the Default Public Store and the Offline Address List (as before without changing anything).
Michel Spannenberg (Last update 11/19/2003):
Check the disk space remaining of the drive volumes where the exchange logs and/or Mailbox stores are located. If you are running out of disk space, free some by deleting or moving some old log files. When done, mount the information store in the exchange system manager.
Christophe Lubrano di Ciccone (Last update 8/4/2003):
This error was in fact generated due to the autonegotiate port configuration of a switch. The server network card had 100 full duplex and the switch port 100 half duplex. The switch port was changed to 100 full duplex and Autonegotiate disabled and all is workking fine after without any reboot. This event was accompanied with event id 8206 from MSExchangeFBPublish.
William A. Avellan
See M313865.
Mark Sivayavirojna
I recently added 2 new Exchange 2000 servers to my 5.5/2000 mixed environment (running parallel while migration is taking place), and encountered this error on both servers after installing Exchange 2000 server SP3. I was able to resolve this issue by performing the following steps:
1. Reinstall Exchange 2000 server using the 'reinstall' option in setup - Restart the system when reinstallation completes.
2. Reinstall Exchange 2000 server SP3 - Restart the system after completion.
Adrian Grigorof
- Error: 0x8004011d - See M252543, M261319, M266330, M313865, and M316709.
- Error: 0x80070005 - See M271410.
this is 9518
Event ID: 9518
Source MSExchangeIS
Type Error
Description Error <error code or description> starting Storage Group <storage group path> on the Microsoft Exchange Information Store.
<error description>
Things to understand What is the role of the Microsoft Exchange Information Store service?
Comments Adrian Grigorof
This event may sometimes be incorrectly reported. See M241629.
Error 0xfffff764 - as per M307790, this error may occur if the streaming file (.stm) that is associated with the store database is missing. To resolve this issue, restore the missing streaming file from a good backup to the Exchsrvr\Mdbdata folder.
As per M327065, this issue can also occura because the streaming file that is associated with the database has been deleted or moved to another location, possibly by your antivirus program.
Error 0xfffffea8 corresponds to JET_errDbTimeCorrupted. This issue occurs if the dbtime on the current page is greater than the global database dbtime. To work around this issue, run the eseutil /d command to defragment the database that is experiencing this issue, and then mount the database. See M312873.
Error 0xfffffde0 - This issue can occur because in Exchange 2000 SP2, the databases are upgraded to a newer version. Because of this database upgrade in Exchange 2000 SP2, earlier backups that were created before you applied Exchange 2000 SP2 cannot be restored to an Exchange 2000 SP2 system. See M316794.
Error 0x451 - This may occur due to a conflict of service packs on a Exchange cluster. See M326017 for resolution. Also, as per M328968 This issue occurs if one or both of the following conditions are true: after a system "crash, " you rebuild your system and restore the Exchange database without applying the correct service pack (Store.exe version) and you restore the Exchange database on the recovery server without applying the correct service pack (Store.exe version).
Error 0xfffff745 - As per M307242, this issue can occur if Exchange 2000 cannot create and access files in the folder that the TMP system environment variable specifies. This issue can also occur if Exchange 2000 does not have full control from the root of the drive down to the transaction logs and databases.
Error Disk IO error - This behavior can occur when Exchange 2000 cannot write to the hard disk, and generates an error message: Either software that has been installed has prevented the write operation or the hard disk itself is corrupted. The event message, which accompanies the error message, refers to an error 1022. This type of error occurs when there is a disk input/output (I/O) error: It may mean that the hard disk has been corrupted. See M300608.
Error 0xfffffb40 - This behavior occurs because the Extensible Storage Engine (ESE) attempts to bring all databases in a storage group to a consistent state during recovery. To accomplish this, ESE keeps track of all databases in the log files for the storage group. If a database is missing, ESE returns the error -1216, and does not start the storage group. See M264228.
Error Current log file missing - Error -1811 corresponds to JET_errFileNotFound, and can be caused by an E00.log file with mismatching signature and LGeneration. If the E00.log file has a mismatching signature, the information store might not mount even if the database is consistent. See M294367. As per M314916, this issue may also occur if you place the Exchange data files on network shares.
Error 0xfffffbf8 - This issue can occur if you do not have the appropriate permissions on the Mdbdata folder to mount the mailbox or public store. See M290215 and M282964.
Error Log disk full - As per M321825, this issue may occur if hackers use your Exchange Server to relay unsolicited e-mail messages (spam). As a result, the Badmail folder fills up with messages that your server cannot handle. The messages cannot be sent back, because the return addresses are not valid (spoofed).
Mihai Andrei (Last update 10/31/2005):
- Error: Current log file missing - See M896143.
- Error: 0xfffffbf8 - See the link to "Working with Store Permissions".
- Error: 0xfffff764 - See M822934.
- Error: 0xfffffde0 - See M329021.
- Error: 0xfffffc01 - See M816421.
Ionut Marin (Last update 5/30/2005):
- Error: 0xfffff764 - See M823169.
- Error: 0xfffffbf8 - See M823022.
- Error: 0x80040102 - See M827283.
- Error: 0xfffffd9a - See M834154 and M836611.
- Error: 0xfffffddc - See M830408 for a hotfix.
- Error: "Current log file missing" - See M819553.
- Error: 0xfffff743 - See M294462.
- Error: "Current log file missing" - See M895856.
- Error: 0xfffffdfe - See M899386.
See the link to "Veritas Support Document ID: 248098" and MSEX2K3DB for more details on this event.
Fred Orcutt (Last update 7/19/2004):
I received this error in conjunction with EventID 9175 from source MSExchangeSA. Attempts to mount stores terminated with report of corruption. Checking security on the storage group and assigning standard user permissions to Everyone account, then applying, resulted in successful mount of stores thereafter. See comments related to EventID 9175 from source MSExchange also.
Adam C. West (Last update 2/15/2004):
- Error: 0xfffffc01 - The drive that contained my log files was corrupt and did not even appear in Disk Management. Changing the location of the log files in Exchange System Manager fixed the error.
Paul Hong (Last update 2/15/2004):
This happened after I restored Exchange Server 2000 back a few days ago. What happened was that someone shut down the server while it was replicating over the weekend. From then on, the Exchange 2000 server did not work right. Therefore, I restored the data from a previous backup.
Dave Murphy
Basically, these errors are a symptom of event id 1087. After fixing the 1087 error, I was able to start the information stores and these errors cleared up.
I use a website call eventid.net for error codes : these could be helpful to you or not. I would start with this stuff thought.
Here is the report for 9175
Event ID: 9175
Source MSExchangeAdmin
Type Error
Description The MAPI call 'OpenMsgStore' failed with the following error: The attempt to log on to the Microsoft Exchange Server computer has failed. The MAPI provider failed. Microsoft Exchange Server Information Store ID no: 8004011d-0512-00000000
Things to understand What is MAPI?
Comments Mihai Andrei (Last update 11/28/2005):
You may see this event if you modify the default permissions on mailbox stores and public folder stores in Exchange 2000 Server or in Exchange Server 2003. See M328229 for additional information on this situation.
Ionut Marin (Last update 6/12/2005):
As per Microsoft: "This event can have several causes and the ID number in the Description section of the event will be the only difference between the events. Depending on what the underlying cause of the problem is, the ID number will vary". See MSEX2K3DB for more details on this event.
From a newsgroup post: "Before moving users, stop the ADC service and stop any antivirus software".
See M278888 for additional information on this event.
Ed Crowley (Last update 6/12/2005):
I received this error when the account was disabled but did not have the “Associated External Account” right set. Setting it allowed the mailbox to move.
Kevin Brinnehl (Last update 4/12/2005):
This event can also occur if the user account is disabled in Active Directory. This event should also be accompanied by Event ID 9548 from source MSExchangeIS. Once I enabled the account, I was able to move the mailbox.
Katherine Coombs (Last update 9/30/2004):
This error will also appear if the mailbox store is not mounted.
Anonymous (Last update 9/9/2004):
This can also occur if your mail server object is missing under the security tab of the mail store properties. We received this error message when we were practicing disaster recovery in an isolated environment. After we did a restore of the full mail db, we could not get the stores to mount. Once I added our mail server object to the ACL of the Security tab of the store, all was well.
Ken Gander (Last update 2/15/2004):
This also happens when running Norton/Symantec Antivirus Corporate/Enterprise and it is not configured properly. If it is set to scan the whole server without excluding the Exchange directories, Norton Antivirus deletes/quarantines “Exx.log” files. This all seems to be from MyDoom. Have had to Hard Repair four Exchange 200x servers already as Norton Antivirus deleted the log file since it was set to delete not to quarantine. You must exclude all the Exchange directories and the M: drive.
Adrian Grigorof (Last update 10/24/2003):
As per Microsoft: "These errors are reported because Move Mailbox cannot log on to the system attendant mailbox. The system attendant has a mailbox on each server, usually on the default mailbox store". There are several Microsoft articles with information about this event: M264413, M288598, M317338, M326990.
This is 8197
Event ID: 8197
Source MSExchangeFBPublish
Type Error
Description Error initializing session for virtual machine <virtual machine name>. The error number is <error>. Make sure Microsoft Exchange Store is running.
Comments Mihai Andrei (Last update 5/8/2006):
- Error: 0x80040111 - See M918006.
Andrei Ungureanu (Last update 9/17/2005):
See the link to "MSDN Posts" for general troubleshooting on this event and for information about related problems.
Ionut Marin (Last update 7/10/2005):
- Error: 0x80040111 - See M828764.
- Error: 0x8004011d - See M266312, M282964, M821889, M822579, and M896703.
As per Microsoft: "Free/Busy Publishing has encountered errors when attempting to log on to the private or public Exchange stores. Transient occurrences of this event are not a problem, but if the recurrence is every 25 to 30 minutes, then Free/Busy Publishing is down for all Outlook Web Access (OWA) users. This event can also be generated if relevant services have recently been cycled or re-started". See MSEX2K3DB for more information on this event.
Eric Suger (Last update 3/17/2005):
In our case, it turned out that Active Directory issues caused the problem. More precisely, there were multiple entries of a servicePrincipalName "HOST/<Machine>". To see if this is your problem look for KDC error messages in your Windows System event logs.
Anonymous (Last update 11/10/2004):
I recently upgraded Exchange 2000 to SP3. After the upgrade, the Information Store was unable to mount. I received the following Event IDs: 505, 8197, 9175, and 9519. I searched the Internet and found a solution. It turns out that Exchange 2000 SP3 is not able to mount a compressed store. My drive was not compressed but the folder where the Information store was located had compression enabled. The solution I found stated the following: “Although our drive that stores the database files was not compressed, the database files (priv1.edb, priv1.stm, pub1.edb, pub1.stm) themselves had their compressed attributes checked; I unchecked them and rebooted. Now everything appears to be working". See the links to “Google Thread” and “EventID 505 from source ESE” for additional information on this issue.
Richard Wesseling (Last update 11/2/2004):
A missing Schedule+ Free/Busy System Folder could cause this error. To correct this see M284200.
Fred Orcutt (Last update 7/20/2004):
- Error 0x8004011d - On an Exchange 2003 server, I received this message with Information Store running and both private and public stores mounted. I eliminated the error by stopping Exchange System Attendant and its dependent services, then restarting SA and each dependency individually. MS Exchange Free Busy Publish then initialized properly.
Anonymous (Last update 3/3/2004):
I was receiving EventID 8197 along with EventID 8207 in the application log every 50 minutes on my Exchange 2000 SP3 server. The 8197 event had the error code: 0x80040111. The 8207 error code was 0x80004003. Clicking on the link in the 8197 log entry, I found a suggestion from Microsoft to restart the System Attendant service. I did this and it cleared up the problem, and the events stopped.
Craig Curtis (Last update 2/23/2004):
- Error: 0x80040111 - This problem can be caused by having more then one domain in the same AD site with the Exchange 2003 server. Exchange will query AD for all the GCs in the AD site and pick one at random. If your Exchange 5.5 server has a trust with a child domain and not the parent, the error will happen every 25 minutes if Exchange picks a GC in the parent domain. Put the Exchange 2003 server in a new AD either site with a couple of GCs, or create a two-way trust between the Exchange 5.5 domain and all domains in the AD site. You could also see article M319206 to force a GC (not recommend).
Jean-Paul Leccia (Last update 12/24/2003):
- Error: 0x8004011c - Our users could not access the PF and the OAB but they could continue to send/receive mails. To fix this, in the "Mailbox Store <server name> Properties", we reapplied the Default Public Store and the Offline Address List (as before without changing anything).
Michel Spannenberg (Last update 11/19/2003):
Check the disk space remaining of the drive volumes where the exchange logs and/or Mailbox stores are located. If you are running out of disk space, free some by deleting or moving some old log files. When done, mount the information store in the exchange system manager.
Christophe Lubrano di Ciccone (Last update 8/4/2003):
This error was in fact generated due to the autonegotiate port configuration of a switch. The server network card had 100 full duplex and the switch port 100 half duplex. The switch port was changed to 100 full duplex and Autonegotiate disabled and all is workking fine after without any reboot. This event was accompanied with event id 8206 from MSExchangeFBPublish.
William A. Avellan
See M313865.
Mark Sivayavirojna
I recently added 2 new Exchange 2000 servers to my 5.5/2000 mixed environment (running parallel while migration is taking place), and encountered this error on both servers after installing Exchange 2000 server SP3. I was able to resolve this issue by performing the following steps:
1. Reinstall Exchange 2000 server using the 'reinstall' option in setup - Restart the system when reinstallation completes.
2. Reinstall Exchange 2000 server SP3 - Restart the system after completion.
Adrian Grigorof
- Error: 0x8004011d - See M252543, M261319, M266330, M313865, and M316709.
- Error: 0x80070005 - See M271410.
this is 9518
Event ID: 9518
Source MSExchangeIS
Type Error
Description Error <error code or description> starting Storage Group <storage group path> on the Microsoft Exchange Information Store.
<error description>
Things to understand What is the role of the Microsoft Exchange Information Store service?
Comments Adrian Grigorof
This event may sometimes be incorrectly reported. See M241629.
Error 0xfffff764 - as per M307790, this error may occur if the streaming file (.stm) that is associated with the store database is missing. To resolve this issue, restore the missing streaming file from a good backup to the Exchsrvr\Mdbdata folder.
As per M327065, this issue can also occura because the streaming file that is associated with the database has been deleted or moved to another location, possibly by your antivirus program.
Error 0xfffffea8 corresponds to JET_errDbTimeCorrupted. This issue occurs if the dbtime on the current page is greater than the global database dbtime. To work around this issue, run the eseutil /d command to defragment the database that is experiencing this issue, and then mount the database. See M312873.
Error 0xfffffde0 - This issue can occur because in Exchange 2000 SP2, the databases are upgraded to a newer version. Because of this database upgrade in Exchange 2000 SP2, earlier backups that were created before you applied Exchange 2000 SP2 cannot be restored to an Exchange 2000 SP2 system. See M316794.
Error 0x451 - This may occur due to a conflict of service packs on a Exchange cluster. See M326017 for resolution. Also, as per M328968 This issue occurs if one or both of the following conditions are true: after a system "crash, " you rebuild your system and restore the Exchange database without applying the correct service pack (Store.exe version) and you restore the Exchange database on the recovery server without applying the correct service pack (Store.exe version).
Error 0xfffff745 - As per M307242, this issue can occur if Exchange 2000 cannot create and access files in the folder that the TMP system environment variable specifies. This issue can also occur if Exchange 2000 does not have full control from the root of the drive down to the transaction logs and databases.
Error Disk IO error - This behavior can occur when Exchange 2000 cannot write to the hard disk, and generates an error message: Either software that has been installed has prevented the write operation or the hard disk itself is corrupted. The event message, which accompanies the error message, refers to an error 1022. This type of error occurs when there is a disk input/output (I/O) error: It may mean that the hard disk has been corrupted. See M300608.
Error 0xfffffb40 - This behavior occurs because the Extensible Storage Engine (ESE) attempts to bring all databases in a storage group to a consistent state during recovery. To accomplish this, ESE keeps track of all databases in the log files for the storage group. If a database is missing, ESE returns the error -1216, and does not start the storage group. See M264228.
Error Current log file missing - Error -1811 corresponds to JET_errFileNotFound, and can be caused by an E00.log file with mismatching signature and LGeneration. If the E00.log file has a mismatching signature, the information store might not mount even if the database is consistent. See M294367. As per M314916, this issue may also occur if you place the Exchange data files on network shares.
Error 0xfffffbf8 - This issue can occur if you do not have the appropriate permissions on the Mdbdata folder to mount the mailbox or public store. See M290215 and M282964.
Error Log disk full - As per M321825, this issue may occur if hackers use your Exchange Server to relay unsolicited e-mail messages (spam). As a result, the Badmail folder fills up with messages that your server cannot handle. The messages cannot be sent back, because the return addresses are not valid (spoofed).
Mihai Andrei (Last update 10/31/2005):
- Error: Current log file missing - See M896143.
- Error: 0xfffffbf8 - See the link to "Working with Store Permissions".
- Error: 0xfffff764 - See M822934.
- Error: 0xfffffde0 - See M329021.
- Error: 0xfffffc01 - See M816421.
Ionut Marin (Last update 5/30/2005):
- Error: 0xfffff764 - See M823169.
- Error: 0xfffffbf8 - See M823022.
- Error: 0x80040102 - See M827283.
- Error: 0xfffffd9a - See M834154 and M836611.
- Error: 0xfffffddc - See M830408 for a hotfix.
- Error: "Current log file missing" - See M819553.
- Error: 0xfffff743 - See M294462.
- Error: "Current log file missing" - See M895856.
- Error: 0xfffffdfe - See M899386.
See the link to "Veritas Support Document ID: 248098" and MSEX2K3DB for more details on this event.
Fred Orcutt (Last update 7/19/2004):
I received this error in conjunction with EventID 9175 from source MSExchangeSA. Attempts to mount stores terminated with report of corruption. Checking security on the storage group and assigning standard user permissions to Everyone account, then applying, resulted in successful mount of stores thereafter. See comments related to EventID 9175 from source MSExchange also.
Adam C. West (Last update 2/15/2004):
- Error: 0xfffffc01 - The drive that contained my log files was corrupt and did not even appear in Disk Management. Changing the location of the log files in Exchange System Manager fixed the error.
Paul Hong (Last update 2/15/2004):
This happened after I restored Exchange Server 2000 back a few days ago. What happened was that someone shut down the server while it was replicating over the weekend. From then on, the Exchange 2000 server did not work right. Therefore, I restored the data from a previous backup.
Dave Murphy
Basically, these errors are a symptom of event id 1087. After fixing the 1087 error, I was able to start the information stores and these errors cleared up.
ASKER
pterranova13--
I really appreciate all the help. Your last post made me a little weak in the knees. That is a lot of information to digest. I realize that this is not going to be the quick fix I was hoping it would be. My concern is that in trying to fix my one problem--which I think is actually a lot bigger than just a store not mounting--I will create or leave unsolved other problems that build further down the line. Since the server has not even been brought online yet, I think my best bet is to clean the slate and rebuild it. My concern about doing this initially was my difficulty in uninstalling Exchange the first time. I just did that however, diligently following the steps in this knowledge base article.
http://support.microsoft.com/kb/833396/
I then reinstalled my OS and Exchange, and the stores mounted fine. I really didn't think the issue was going to be this involved.
I really appreciate all the help. Your last post made me a little weak in the knees. That is a lot of information to digest. I realize that this is not going to be the quick fix I was hoping it would be. My concern is that in trying to fix my one problem--which I think is actually a lot bigger than just a store not mounting--I will create or leave unsolved other problems that build further down the line. Since the server has not even been brought online yet, I think my best bet is to clean the slate and rebuild it. My concern about doing this initially was my difficulty in uninstalling Exchange the first time. I just did that however, diligently following the steps in this knowledge base article.
http://support.microsoft.com/kb/833396/
I then reinstalled my OS and Exchange, and the stores mounted fine. I really didn't think the issue was going to be this involved.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
i want to see solution if there is any please let me know i have the same please send me resolution i am waiting
Regards,
gul_hameed@hotmail.com
Regards,
gul_hameed@hotmail.com
http://support.microsoft.com/?scid=kb;en-us;253931&spid=1773&sid=78