|
|
|
date: Thu, 19 Jun 2008 13:45:01 -0700,
group: microsoft.public.exchange.admin
back
Re: Exchange 5.5 restore problem
On Jun 20, 4:50 am, "Ed Crowley [MVP]"
wrote:
> Right. I suspect that you remember inaccurately and NT was at SP6a while it
> was Exchange 5.5 that was at SP4.
> --
> Ed Crowley
> MVP - Exchange
> "Protecting the world from PSTs and brick backups!"
>
> "Roan Daley" wrote in message
>
> news:BF4C31A4-7E9E-41B8-8621-9414F3A3D898@microsoft.com...
>
>
>
> > David, did you try to install the SP6 on the NT Box?
>
> > "David B" wrote:
>
> >> #We are currently running Exchange 2003. We took our Exchange 5.5 box
> >> offline
> >> about 2 years ago. We now find that we need to recover an old mailbox
> >> from
> >> one of EX5.5 backups.
>
> >> I found a piece of hardware and loaded NT 4.0 on it, patched, etc.
> >> Installed
> >> Exchange 5.5 using the same Organization and Site as our previous server.
>
> >> Current config: NT4 SP4, Exchange 5.5 SP4
>
> >> Dusted off the old Backup Exec 8.6 and got it installed. Kicked off the
> >> exchange restore. It completed successfully, however, we can not mount
> >> the
> >> mailstore. When I attempt the mount, I get the message:
>
> >> "The Microsoft Exchange Information Store service returned a service
> >> specific error 3355443730"
>
> >> My research into that error indicates a service pack level conflict. I'm
> >> reasonably sure the old server was SP4, but have no way now to verify
> >> that.
> >> I've also found information that suggested running ESEUTIL integrity
> >> check.
>
> >> Everything I've tried fails to get this mailstore online. Does anybody
> >> have
> >> any suggestions on how to proceed?- Hide quoted text -
>
> - Show quoted text -
Also, not enough information is given about the state of the DB your
working with - along with relevant events seen in app logs while
mounting stores.
Lets have this info in place before proceeding on to troubleshooting.
date: Thu, 19 Jun 2008 20:41:30 -0700 (PDT)
author: Tushar Shah
Re: Exchange 5.5 restore problem
David...
Take a look at this..
http://support.microsoft.com/kb/184830/en-us
This might help you.
Roan D. Daley , MCSE, MCTS.
"Tushar Shah" wrote:
> On Jun 20, 4:50 am, "Ed Crowley [MVP]"
> wrote:
> > Right. I suspect that you remember inaccurately and NT was at SP6a while it
> > was Exchange 5.5 that was at SP4.
> > --
> > Ed Crowley
> > MVP - Exchange
> > "Protecting the world from PSTs and brick backups!"
> >
> > "Roan Daley" wrote in message
> >
> > news:BF4C31A4-7E9E-41B8-8621-9414F3A3D898@microsoft.com...
> >
> >
> >
> > > David, did you try to install the SP6 on the NT Box?
> >
> > > "David B" wrote:
> >
> > >> #We are currently running Exchange 2003. We took our Exchange 5.5 box
> > >> offline
> > >> about 2 years ago. We now find that we need to recover an old mailbox
> > >> from
> > >> one of EX5.5 backups.
> >
> > >> I found a piece of hardware and loaded NT 4.0 on it, patched, etc.
> > >> Installed
> > >> Exchange 5.5 using the same Organization and Site as our previous server.
> >
> > >> Current config: NT4 SP4, Exchange 5.5 SP4
> >
> > >> Dusted off the old Backup Exec 8.6 and got it installed. Kicked off the
> > >> exchange restore. It completed successfully, however, we can not mount
> > >> the
> > >> mailstore. When I attempt the mount, I get the message:
> >
> > >> "The Microsoft Exchange Information Store service returned a service
> > >> specific error 3355443730"
> >
> > >> My research into that error indicates a service pack level conflict. I'm
> > >> reasonably sure the old server was SP4, but have no way now to verify
> > >> that.
> > >> I've also found information that suggested running ESEUTIL integrity
> > >> check.
> >
> > >> Everything I've tried fails to get this mailstore online. Does anybody
> > >> have
> > >> any suggestions on how to proceed?- Hide quoted text -
> >
> > - Show quoted text -
>
> Also, not enough information is given about the state of the DB your
> working with - along with relevant events seen in app logs while
> mounting stores.
> Lets have this info in place before proceeding on to troubleshooting.
>
date: Fri, 20 Jun 2008 05:34:01 -0700
author: Roan Daley
|
|
