• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Mail server (windows 2k, exchange 5.5 died)

Bulldog13

Bulldog13

Golden Member
Hello,

Our mail server recently kicked the can today. We are unable to boot it into windows 2000. The error message we get is "A thread tried to release a resource it did not own."

0x000000e3 (0x80478B00, 0x89064420, 0x88FA0E8, 0x00000003)

Address 80478B00 base at 80400000 .

The thread is ntoskrnl.exe.

We have been having constant troubles with it as of late. The last problem was that it and symantec av could not play nice together. We ended up having the remove the AV for exchange. We are using Exchange 5.5 and a fully updated windows 2000.

We ran a full hardware diagnostic maybe a week ago, and everything was fine. We are using a Dell PowerEdge 2800.

Any references to that stop code on the Microsoft webpage just say to apply the latest service pack, which we already have.

We can barely get into safemode. It hangs awhile, but eventually we get in. Not sure how to proceed.

Thoughts ?
 
Yike, no AV for exchange?

I dont have an answer on how to proceed for you other than I hope you have backups 😉
 
Maybe this is just your Server's way of saying, "Hey! It's time to migrate to Server 2003 and Exchange 2003!". Even "Microsoft Extended Support" for Exchange 5.5 ended a month ago.

You didn't say how big your organization is. I'd probably install Windows 2000 and Exchange into Virtual PC or Virtual Server on a PC (or, put them on an empty PC, if you have one), do a restore to get it running (so you have mail again), install Exchange 2003 and Server 2003 on the Dell 2800, join the Domain, and then do the migration of the Exchange accounts over to the new Server 2003.

Or, if you have less than 75 computers, I'd consider migrating to SBS 2003.
 
Originally posted by: mechBgon
Out of curiosity Bulldog13, did you patch Exchange 5.5 against this vulnerability?
Click to expand...


Like 300 people in the organizations.

No idea if that was patched, I'm just a lowly tech, but saw my boss having the issue and threw it up on the forums.

Thanks for the hall.dll info.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top