Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2318
  • Last Modified:

exchange 2003 filled with 9099 errors!!

We recently upgraded our domain to windows 2003. in this  process we also upgraded one of our exchange 2000 standard member server to exchange 2003 enterprise edition (another server running exchange 2000 standard server still online).

The backup tape in our upgraded exchange 2003 member server was stuck in the tape drive so we restarted the machine to eject the tape. The machine restarted and gave the blue screen with stop error

Event Type:      Error
Event Source:      System Error
Event Category:      (102)
Event ID:      1003
Date:            4/26/2004
Time:            6:20:30 PM
User:            N/A
Computer:                     XXXXX
Description:
Error code 0000008e, parameter1 c0000005, parameter2 f8a4738f, parameter3 badfac8c, parameter4 00000000.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45   System E
0008: 72 72 6f 72 20 20 45 72   rror  Er
0010: 72 6f 72 20 63 6f 64 65   ror code
0018: 20 30 30 30 30 30 30 38    0000008
0020: 65 20 20 50 61 72 61 6d   e  Param
0028: 65 74 65 72 73 20 63 30   eters c0
0030: 30 30 30 30 30 35 2c 20   000005,
0038: 66 38 61 34 37 33 38 66   f8a4738f
0040: 2c 20 62 61 64 66 61 63   , badfac
0048: 38 63 2c 20 30 30 30 30   8c, 0000
0050: 30 30 30 30               0000    

we restarted the machine using last known good configuration. the startup was successful and all the databases mounted.

But the event viewer started giving the following errors every 5 mins

Event Type:      Error
Event Source:      MSExchangeSA
Event Category:      Disk
Event ID:                      9099
Date:            4/26/2004
Time:            7:19:41 PM
User:            N/A
Computer:

Description:
The description for Event ID ( 9099 ) in Source ( MSExchangeSA ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: 0x8004100a.

Another event viewer application log error is 9095


when i start the ESM the following error pops up:

exchange detected that c:\winnt\system32\mapi32.dll is not correct version required to run exchange system manager or exchange 2003.
for more information see Q266418

The Q article refers to exchange 2000, but the server is upgraded to exchange 2003.

how can i remove these error ?

The worst thing to happen is the M: drive is shown again in My computer, like in exchange 2000

I am clueless. any suggestions as to what had happened ?

Server is compaq ML370 with 512 MB RAM and 3 hard disks configured as RAID 5 (not recommended though!)


0
ikm7176
Asked:
ikm7176
  • 6
  • 6
1 Solution
 
David WilhoitSenior Consultant, ExchangeCommented:
Ouch....

http://support.microsoft.com/default.aspx?scid=kb;en-us;326011

Try this...was Outlook ever installed on here??

d
0
 
ikm7176Author Commented:
thanks kidego..

I aware of the link above, but it applies to exchange 2000. do i need to follow the same steps for Exchange 2003.

outlook was never installed on the system, but it had NAV for Microsoft exchange 2.X installed on it. After upgrading to exchange 2003 the NAV service never started, incompatiblity issue!!.

the following issues bothering me.

Why Blue screen came during normal boot. HARDWARE FAILURE ?

Why the M: drive is back ? i guess the "LAST KNOWN GOOD CONFIGURATION" had messed up my upgrade.

i need to know exact reason for the above problems. Any suggestions to troubleshoot this would be appreciated. No  problems with e-mails. Everything normal, except for the errors and the "M" drive.

0
 
David WilhoitSenior Consultant, ExchangeCommented:
yes, last known good broke it. the hardware failure most likely came from a driver incompatibility, NAV comes to mind :). The exact reason would be difficult for me to find, without looking at a bugcheck, but it looks like the win32k.sys file is the problem. Makes sense given the scenario....but Exchange is most likely broken. Before you try to upgrade it again, I would exmerge all my data, to ensure I have it all. If you get to Ex2003, you won't be able to restore an E2K database, so this would be safer.

D
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
ikm7176Author Commented:
upgrade what ?

upgrade to exchange 2003 only?

I think both windows 2003 upgrade and exchange 2003 upgrade has been broken

i need to reinstall windows 2003 and then reinstall exchange 2003,am i right ?

0
 
ikm7176Author Commented:
thanks kidego..for giving your expert advice

can you point me to any any link about this type of upgrade

if no link, can you tell me the steps to follow

i hope everything will be normal..  i am bit nervous :)

0
 
David WilhoitSenior Consultant, ExchangeCommented:
http://www.msexchange.org/tutorials/Upgrade_Exchange_2000_to_2003.html

this is a good link....Is the M: drive visible, but Exchange is running on the 2003 version of the files?? That would so weird...yea, reinstalling may need to happen, but I'd save my databases first, since they are up and running on 2003 store.exe ( at least that's what I'm assuming at this point)

D
0
 
ikm7176Author Commented:
thanks Kidego.. i agree with your suggestions. I need to re-analyze the whole thing again.

Kidego one last question . I forgot to describe you the upgrade proceedure followed. This was done by one of the Microsoft Partner's here, for free, as we purchased the license from them. well, the steps below

1. Installed new machine with windows 2003 and upgraded the AD to windows 2003.

2. Upgraded windows 2000 to windows 2003 on the Exchange 2000 standard member server.(i know that exchange 2000 cannot be installed directly on windows 2003 machine but it can be done by the upgrade procedure, as it was done in our case. This is not described by microsoft anywhere.). done Windows Update.reboot

3. OK! Then he upgraded the exchange 2000 standard edition to exchange 2000 enterprise edition. I didn't uderstand this upgrade, no need to do this.right ?. Upgrade successful, reboot .

4. Finally upgraded exchange 2000 enterprise edtion to exchange 2003 enterprise edition. (Run Forestprep and Domainprep before upgrade). Upgrade completed. Reboot not done (as i remember).

All these days it was normal. The restart performed by me was the first restart after the upgrade to exchange 2003 which gave me the blue screen and forced me to boot with "Last good Known... ".

I think the reboot with Last good.. took me back to windows 2003 with exchange 2000 enterprise edition.
Am i  right in assuming  this ?. Having said all this, everything seems to be in 2003 mode like ESM interface, windows OS interface, help files etc. THE "M" drive is unusuall and the error 9099. This two things driving me crazy...:)

Thanks again kidego for supporting me all the way
0
 
David WilhoitSenior Consultant, ExchangeCommented:
<2. Upgraded windows 2000 to windows 2003 on the Exchange 2000 standard member server.(i know that exchange 2000 cannot be installed directly on windows 2003 machine but it can be done by the upgrade procedure, as it was done in our case. This is not described by microsoft anywhere.). done Windows Update.reboot>

KAAABOOOOOOOM!!! exchange 2000 cannot be installed, nor will it run on Windows 2003. When upgrading an E2K/W2K server, Exchange MUST BE UPGRADED FIRST. Your MS partner should have known that, and if he didn't, shame on him. That's most likely where all this misery came from. At this point, I'd make him open a case with MS Support, on his dime.

D
0
 
ikm7176Author Commented:
hi Kidego again

check this link which supports the step 2). I agree that its non-microsoft link. But this worked out in my case and maybe it worked for short period before this disaster happened.

http://www.mike-tech.com/article.php?gif=exchange2k&article=254

Any suggestions ...?
0
 
David WilhoitSenior Consultant, ExchangeCommented:
http://support.microsoft.com/default.aspx?scid=kb;en-us;321648

Sorry bro, I don't have anything I can tell you at this point, I've not seen this. I will tell you however, that you're in unsupported territory, MS won't help you with this, because of the statement in the article above. Your partner needs to come over and fix this for you. That's best I can offer at this stage of the game....

D
0
 
ikm7176Author Commented:
Thanks kidego for your excellent support. Hard time for me ahead :).
0
 
David WilhoitSenior Consultant, ExchangeCommented:
Let me know how it turns out....good luck!

D
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

  • 6
  • 6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now