exchange 5.5 highlog number, lowlog number

v_alber,

I still don't understand what 5 logs I need.
Could you or someone else spell these out for me one by one. Thanks.
What if I don't have the logs I need then what?

Here is what I have
-------------------------------------------------------------
 Volume in drive C has no label.
 Volume Serial Number is 9C04-5CCF

 Directory of C:\mdbdata

10/12/2004  07:50 AM    <DIR>          .
10/12/2004  07:50 AM    <DIR>          ..
10/11/2004  01:38 PM             8,192 edb.chk
10/11/2004  01:38 PM         5,242,880 edb.log
10/11/2004  09:14 AM         5,242,880 edb.log.old
07/10/2003  05:34 PM         5,242,880 edb.old
07/10/2003  05:05 PM         5,242,880 edb00B8F.old
07/10/2003  05:06 PM         5,242,880 edb00B90.old
07/10/2003  05:07 PM         5,242,880 edb00B91.old
07/10/2003  05:34 PM         5,242,880 edb00B92.old
10/11/2004  04:19 PM         5,242,880 edb01A9C.log
10/11/2004  04:19 PM         5,242,880 edb01A9D.log
10/11/2004  04:19 PM         5,242,880 edb01A9E.log
10/11/2004  04:19 PM         5,242,880 edb01A9F.log
10/11/2004  04:19 PM         5,242,880 edb01AA0.log
10/08/2004  03:36 PM         5,242,880 edb01AB9.log
10/08/2004  03:43 PM         5,242,880 edb01ABA.log
10/08/2004  03:46 PM         5,242,880 edb01ABB.log
10/08/2004  03:47 PM         5,242,880 edb01ABC.log
10/08/2004  03:56 PM         5,242,880 edb01ABD.log
10/12/2004  07:50 AM    <DIR>          old
10/11/2004  04:19 PM             8,192 PRIV.pat
10/11/2004  04:19 PM             8,192 PUB.pat
05/07/2003  01:32 PM         5,242,880 res1.log
05/07/2003  01:32 PM         5,242,880 res2.log
              22 File(s)     99,639,296 bytes
               3 Dir(s)  60,699,680,768 bytes free
-----------------------------------

Actually you don't have those log files on that drive.
Try to locate them some place else. Maybe it was restored to a different location.
If don't have all the log files, you can try an earlier backup or eseutil /p after you have removed the RIP key from the registry.
If you go for /p, keep in mind you are going to loose some data.

Hello

I have not read the comments from Microsoft, but I have found out that restoring a database is always trouble.

When I have had to restore a database (not very often though), I usually run Exmerge on the database and create PST files for all users.  Once I have this data, I simply create a brand new PRIV and get this on-line (2 MB).

Run Exmerge once again and import the PST back in.  Problem solved.  The only thing that you will lose is the permissions set on the mailboxes.  (calendar access etc).

I hope this helps...

JC

This is crazy. This is the third time in less than 2 years I have had to go through this. I hate MS exchange server. I have however purchased a new server and exchange 2003. I gave up and decided to pay the local MS partner to fix the old 5.5 server for me. Even after I did a restore of the information store files from last week I am still getting error messages indicateing that the information stores are corrupt.

So here is my question while I am waiting to get the exchange 5.5 server fixed is it a possibility to get the 2003 exchange server up and running for the users. Of course all of thier legacy email would still be on the old 5.5 server and would need to somehow be transfered over after the repairs were done. But in the meantime this would give them email. Is this a good idea or a bad idea?

First, you gonna have to migrate user accounts to AD and then install Exchange 2003.
You can use Exchange 2003 SP1 wizards for that.
After you done with restoring 5.5 you can exmerge every-thing out of there and import it back to Exchange 2003.
If you are unsure how to do this, it probably would be a good idea to use a consulting company for that.
Here is the link for E2k3 deployment guide:
http://www.microsoft.com/downloads/details.aspx?FamilyID=77B6D819-C7B3-42D1-8FBB-FE6339FFA1ED&displaylang=en 

>First, you gonna have to migrate user accounts to AD and then install Exchange 2003.
Users are already in AD, I don't understand. Did I mention we are on a windows 2000/2003 domain.
>You can use Exchange 2003 SP1 wizards for that.
Thats if you have a functioning 5.5 exchange server. Am I wrong?

Users are already in AD, I don't understand. Did I mention we are on a windows 2000/2003 domain ?????
I quote you "Running an old exchange 5.5 server on NT. "
So what is that question is about ?


Thats if you have a functioning 5.5 exchange server. Am I wrong?
This was meant for migrating user accounts using ADC wizards, but if you are on AD already this is irrelevant.

Any-thing else ?

Thanks : )

Since my exchange 5.5 server is down and I would like to install 2003 and give the users something to use, how should I go about this. Do I need to do anything speacial. Like; should I keep the orginization name the same for the 2003 server as it is on the 5.5 server?

You can have only one exchange org per AD forest.
I am not sure if you will be able to create a new org, but since you had e5.5 you might.
Any-way if you try to join existing org it should fail if your exchange 5.5 is completely down. In your case only the information store is down, so you should be able to join the existing org.
If you choose to join the org you have to make sure your exchange 5.5 server will be up and running as soon as possible, cause besides the mailboxes all your system folders(like Free/Busy, offline address book) are down.

It let me create a new exchange org.
I am not sure if this was the right thing to do or not?
How can I then view all of the exchange org. in AD?

5.5 very unstable, hence 2000/2003 were invented.

How many users are we talking about here?  Are these users setup on the AD already?

In regards to your 5.5 box, does the Directory service start? Because if it does then you should be able to repair the database.. I will search for a document that I might be to help you..two secs

You have two tools in windows support tools (it's on the installation CD).
1) ADSIEdit.msc, run it, Go to Configuration->Services->Microsoft Exchange, under that you gonna see your exchange orgs
2) ldp