Hi
i refer to this:
http://support.microsoft.c
Are you running it from the same server where your store resides ?
Main Topics
Browse All TopicsI am running an sbs server, the server had the power unplugged by accident. When booted back up the exchange server would not mount and gave the error c1041724
I ran a eseutil /g and saw that the database was not up to date so i ran eseutil /p but it would still not mount. I tried to run a eseutil /r but it was unable to do this due to a jet direct error:
Operation terminated with error -1003 (JET_errInvalidParameter, Invalid API para
meter) after 0.47 seconds.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Hi
i refer to this:
http://support.microsoft.c
Are you running it from the same server where your store resides ?
The error you are getting suggests that you are running out of disk space:
http://support.micro
Is
Ah fair enough....
is there enough space free on the database disk? (http://support.microsoft.
try and read this:
http://www.mcse.ms/message
Relevant copy paste:
--------------------------
If you have run an eseutil /p (hard repair), the next step is to defrag the
database with an eseutil /d.
You then need to clean out all files from the mdbdata directory except the
edb and stm files.
Thne mount the store. Once mounted, dismount and run isinteg.
Eseutil /p assigns and new header to database leaving all existing log files
useless, then traverses the database and removes any pages it feels is
corrupted. No guarantee on amount of data that will be recouped.
Eseutil /d MUST be run after a hardrepair (/p). This process beyond the
defrag process, makes this database new.
Stores MUST be mounted and dismounted after eseutil has been run prior to
attempting an isinteg.
--------------------------
No over 300 gig free disk space, exchange store is 6 gig. I am going to try the following detail from another post that worked for someone else
Ran the eseutil /p frorm the BIN folder and repaired both the priv1.edb and pub1.edb files.
Deleted the log and chk files.
Ran a defrag on the stores . eseutil /d
Ran isinteg (isinteg -s servername -fix -test alltests) frorm the bin folder.
Mounted the stores.
Have a look at this:
http://support.microsoft.c
First part done
Scanning Status (% complete)
0 10 20 30 40 50 60 70 80 90 100
|----|----|----|----|----|
.........................
leting unicode fixup table.
........................
pair completed. Database corruption has been repaired!
te:
It is recommended that you immediately perform a full backup
of this database. If you restore a backup made before the
repair, the database will be rolled back to the state
it was in at the time of that backup.
eration completed successfully with 595 (JET_wrnDatabaseRepaired, Database cor
ption has been repaired) after 1758.188 seconds.
Business Accounts
Answer for Membership
by: Sid_FPosted on 2009-11-03 at 06:26:02ID: 25729202
The output of the priv1.integ.raw file had a lot of errors for
ERROR: page 5: dbtime is larger than database dbtime (0xaa8c54, 0x6f7c86)
when eseutil /p was run