Re: Some services not working after raid repair

Only guesses...

1. You installed 64-bit Windows drivers for the new raid card or some
service pack
2. The Promise raid card isn't compatible with the server hardware (maybe
it's 64-bit only)

If Exchange is the only thing affected, maybe try reinstalling Exchange 2003
SP2:

Exchange Server 2003 Service Pack 2
http://www.microsoft.com/downloads/d...displaylang=en

--
Merv Porter [SBS-MVP]
============================

"Jessica" <> wrote in message
news:afe71363-63e3-46fd-b5a4-...
> Hi and good morning. Isn't this great for a Monday?
>
> We had a server raid behave badly, basically at boot up it said the
> RAID was functional. Yet once in the OS (sbs2003) we saw two physical
> drives and clearly not a functioning RAID. This is an HP ML 150 setup
> in May of this year.
>
> We tried to resolve the raid problem by updating all the drivers but
> this did not resolve. We made an image for safekeeping then installed
> a promise raid card and rebuilt the raid. All seemed fine yet there
> were signs that there might be problems. CHKDSK ran and fixed ALOT of
> errors.
>
> Server boots but all exchange services refuse to start.
>
> What are my best options? Do a restore? Or should I remove the Raid
> card and put in the original (known good) harddrive and redouble my
> backup efforts?
>
> Some errors include:
>
> The Microsoft Exchange System Attendant service failed to start due to
> the following error:
> Access is denied.
>
> The Simple Mail Transfer Protocol (SMTP) service terminated with the
> following error:
> Simple Mail Transfer Protocol (SMTP) is not a valid Win32
> application.
>
> The Microsoft Exchange Information Store service depends on the EXIFS
> service which failed to start because of the following error:
> The specified driver is invalid.
>
> ISAPI Filter 'C:\Program Files\Exchsrvr\ExchWeb\bin\auth\OwaAuth.dll'
> could not be loaded due to a configuration problem. The current
> configuration only supports loading images built for a x86 processor
> architecture.
>
> Windows cannot open the 64-bit extensible counter DLL MSExchangeUCF in
> a 32-bit environment. Contact the file vendor to obtain a 32-bit
> version.

To add to Merv's response:

3. Call HP if your having problems with their controller. A system from
May of this year is still under HP warranty?

Two physical drives implies RAID1. If the RAID table on the drives is
corrupted by a power hit or whatever, this can be the response. The last
one of these that I had beeped (loudly) for 48 hours before staff noticed,
and by the time they called me the tables on both drives was corrupted so
that we had to completely rebuild the OS. Fortunately we found a way to
rescue off the data.

--
Larry


"Merv Porter [SBS-MVP]" <mwport@no_spam_hotmail.com> wrote in message
news:...
> Only guesses...
>
> 1. You installed 64-bit Windows drivers for the new raid card or some
> service pack
> 2. The Promise raid card isn't compatible with the server hardware (maybe
> it's 64-bit only)
>
> If Exchange is the only thing affected, maybe try reinstalling Exchange
> 2003 SP2:
>
> Exchange Server 2003 Service Pack 2
> http://www.microsoft.com/downloads/d...displaylang=en
>
> --
> Merv Porter [SBS-MVP]
> ============================
>
> "Jessica" <> wrote in message
> news:afe71363-63e3-46fd-b5a4-...
>> Hi and good morning. Isn't this great for a Monday?
>>
>> We had a server raid behave badly, basically at boot up it said the
>> RAID was functional. Yet once in the OS (sbs2003) we saw two physical
>> drives and clearly not a functioning RAID. This is an HP ML 150 setup
>> in May of this year.
>>
>> We tried to resolve the raid problem by updating all the drivers but
>> this did not resolve. We made an image for safekeeping then installed
>> a promise raid card and rebuilt the raid. All seemed fine yet there
>> were signs that there might be problems. CHKDSK ran and fixed ALOT of
>> errors.
>>
>> Server boots but all exchange services refuse to start.
>>
>> What are my best options? Do a restore? Or should I remove the Raid
>> card and put in the original (known good) harddrive and redouble my
>> backup efforts?
>>
>> Some errors include:
>>
>> The Microsoft Exchange System Attendant service failed to start due to
>> the following error:
>> Access is denied.
>>
>> The Simple Mail Transfer Protocol (SMTP) service terminated with the
>> following error:
>> Simple Mail Transfer Protocol (SMTP) is not a valid Win32
>> application.
>>
>> The Microsoft Exchange Information Store service depends on the EXIFS
>> service which failed to start because of the following error:
>> The specified driver is invalid.
>>
>> ISAPI Filter 'C:\Program Files\Exchsrvr\ExchWeb\bin\auth\OwaAuth.dll'
>> could not be loaded due to a configuration problem. The current
>> configuration only supports loading images built for a x86 processor
>> architecture.
>>
>> Windows cannot open the 64-bit extensible counter DLL MSExchangeUCF in
>> a 32-bit environment. Contact the file vendor to obtain a 32-bit
>> version.
>
>

Jessica, this makes little sense. Your seeing apples, and I am not hearing
"apples", nor even oranges, but kangaroos instead.

If A then B. Can't be C.

Are you certain that what you saw as two distinct hard drives from Windows?
Or maybe it is two partitions on the mirrored drives, which would be,
usually C and D, but could be C and E depending on the letter assigned to
the cd/dvd drive.

The other possibility is that although there is a RAID controller in the
computer, it is not being used, and the RAID was configured using windows
native mirroring capability, AKA "software raid", and that is / was broken.

With a discrete controller card you have a better chance of moving the
installation to another computer should you need to, but be aware that the
licensing becomes an issue. OEM licenses are only good for the computer
they came with, hence the non movable sticker on the side of the case.

Now as to your problem with Exchange. While very robust data bases they are
not immune. What happens if you open the services applet and start the
exchange services manually? What errors are in your event logs?

--
Larry

"Jessica" <> wrote in message
news:db805a81-b762-4883-b2b9-...
> OK, I spoke to HP and they say that if on bootup, raid is functional,
> then any problem on the OS side they dont support.
>
> Should I do a fresh install onto working Promise card and do a restore
> from there?
> Or with HP support (updated all bios and controller drivers) then do
> fresh install and restore from there?
>
> Is a restore even going to work?
>
> Right now, with Promise working beautifully, the only things not
> working are exchange.
>
> Is this a simple permissions problem?

Install Windows - up to the point that the CD finishes. Then stop. There
will be a little icon on your desktop to Continue Setup.

At this point you have to apply whatever service packs bring you back to
your previous position. Since the server seems to be fairly new, I think
your media should be SP1, so if you did not apply SP2, you should be good to
go out of the box.

Once you have it up to the same version of Windows and SP, you can run your
restore.

Larry


"Jessica" <> wrote in message
news:d0de0764-bc58-4bd5-a362-...
> Status: raid is rebuilt and shows optimal. Inside OS Online with HP
> support now and they are recommending removing existing array and
> build new one, then fresh install of OS.
>
> QUick question, how much of the OS do I install before attempting
> restore. If there is a simple answer to this, perhaps you can direct
> me to the link.

Hmmmm... restore an AD system without restoring the system state? Not on my
radar, but:

BKU_BkupRstr.doc

http://www.microsoft.com/downloads/d...displaylang=en

is the official Microsoft Document on Backup and Restore for Small Business
Server 2003.

--
Larry


"Jessica" <> wrote in message
news:50174b1c-25e4-429e-9dc3-...
> Larry,
> Thanks so much for your reply.
>
> I used nlite to make a modified install with cd one plus the raid
> driver.
>
> I will apply the service pack after i get successful basic install (HP
> didn't want to confuse the situation by slipstreaming the service
> pack).
>
> QUESTION: when I am prepared for the RESTORE, I was told not to
> restore anything except data. Does that mean that I am only to attempt
> restore of data plus exchange and not attempt system state? I think
> so, but please advise if I am wrong.
>
> This restore will be done to all same hardware but this time it will
> be onto a functioning raid!
>
> I wish I could tell you it was a very new server. Indeed the hardware
> is quite new but unfortunately, the software is only SBS2003 standard
> (not R2)
>
> I'll post again in about 30 minutes.
>