Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Windows 2000 Server a mess

Status
Not open for further replies.

bumbles

IS-IT--Management
Joined
Apr 11, 2001
Messages
4
Location
IE
Where do i begin ...to tell the story of how lonley life can be...especially at 3.00am in the morning when everyone else is snugged up in bed and muggins here is still at work for the 5th night in a row trying to get some incling of why Mr. Gates hates me so much! Well it all started last week when w2k suddenly crashed on a program launch...dumped some information to disk...and shutdown of its own accord... did it recover and bristle back to life? no siree. Unfortunately my introduction to w2k was but a week old i.e. i knew absolutely nothing about it. The Server began at a snails pace...took over 1.5hrs to boot...well i never waited longer than 0.5 - 1.0 hr to find out the exact time as the drawing office was busy and now the drafties had no files to work on. Windows 2k was installed as an upgrade to the old NT4.0 PDC...the server is a Compaq Proliant 3000...runs Exchange 2000...has a mirrored system disk(SCSI) and 3no. SCSI Data disks Raid 5 config...the server has always been reliable under NT4.0 but its one drawback is it only has 256MB RAM.. I went through all the repair proceedures but none really worked...not even restoring the last known good config. The following night i booted to safe mode and began setting the services to manual and kept rebooting until i got a satisfactory boot to normal mode. I left that night at about 3.30am and left the machine to normal boot with all the services set to manual.....i did attempt to reapply all the Compaq management resources before this.. by the morning the logon screen was up but when the admin password was entered it became obvious that I'd be better off with a cup of tea and toast with my feet up! I then restarted( powercycle) and indesperation tried the restore last known config again and Ureka it worked. When i went to the services manager...all the services were set to manual...as i had left them the night before... so i started to start all the services that i thought were necessary for Exchange and File access functionality and sure enough mail was back and the Drafties could logon again. Then my first big mistake..i uninstalled Arcserve...i never thought i'd say that!!!..this package has been bagged more than any other for mucking things up...i had no backup now for 3 nights so i was getting anxious...the Proliant machine is one of two DCs(same domain) but has the 4mm DDS4 DAT drive attached...i needed to backup but decided to use the Windows backup instead. For the life of me the w2k backup would not run...did not recognise the media as blank(it was) I treid to install the latest driver for the HP surestore DAT... another mistake as i was later to learn...which i downloaded from the site...Windows did not like this at all and when i pointed to the new driver it died...not crashed...i had to kill the process in the end. From this point all attempts to unload the DAT device or reinstall the driver have simply died...Also, I've tried to start other services but they have timed out...Microsoft will tell you that this does not mean that they don't work just that the service does not respond in a timely fashion... I went back to reinstalling Arcserve but now i got an installer error...(Also,I tried to reinstall SP2 but this also died i.e. nothing wants to install anymore.) Computer Associates assurred that this was a windows installer error and i should go and download myself a new one...which i did..but it seems you cannot replace the MSI.DLL, MSIEXEC.EXE & MSIHND.DLL files as they are SPA protected....i tried anyway using Msciexe /unregister but of course and got rid of two of the above installer files but not MSI.DLL as one would expect...My server thankfully retains its email and file sharing capabilities but my backup is doomed. I'm sure i need to reregister the msiexec.exe file as noww when i log on the desktop will no longer appear. I will travel to buy beer if nyone can help...maybe i'll become a novelist and bounce this IT Career. Thanks for listening.
Bumble
 
mmm.. interesting problem.. lemmie see.. my guess u are having major hardware problems, or driver-hardware problems.. maybe a compatibility issue.. there might be something about your compaq, and other components that Windows doens't like..

i had a somehwat similar problem when i upgraded a chipset driver to enable DMA on my controllers, and after that, my machine took 8 minutes to boot... i later realised that one of my 3 disks had errors on it.. or bad sectors..it was generally failing.. i got the same errors in the logs.. that the device didn't respond in timely fashion.. after removing the disk and replacing it with a new one, i could boot in less than 15 seconds...

u might want to start the system in a very minimal environment, back up all your data, then re-install.. that's why i always save my data on a D partition, and just progs on C .. monitor your re-install and see whether the system finds any problems with the hardware detection...

good luck..
 
StarTAC,

Thanks for your response...a disk error may indeed have resulted from the original crash...the fact that the HP Surestore DAT driver downloaded from the HP web site was not Microsoft 'signed' probably did not help...unfortunately the sluggish system response for service control and computer management functions is also evident in safe mode. Which now makes it impossible to troubleshoot. Of course i've dried to update the DAT driver several times but the process keeps dying.

The server does boot in normal mode in reasonable time(circa 2min) it is very slow to shutdown from this mode but when booting to or shutting down from safe mode it takes an age...the plot thickens!

It does look like i will have to start from scratch again...my problem is that my backup tape drive is on this server...i could move it i suppose...think of the overtime...yeah right!

Bumbles
 
Kind of going out on a limb here, but I'm thinking that part of your sluggishness problem might be a lack of RAM. The recommended minimum for W2K Server is 256 MB, and if you are using this server for e-mail, file sharing and authentication as a domain controller, that's eating up a lot of memory. We have a similar setup, and our DC has over 1 GB of RAM.

You know, this is a pretty radical solution, but you might try just completely starting over. Download all your data off the server, save all your e-mail stores to .pst files and download them, then do a complete format of your hard drives. You'll have to reinstall Windows, re-enter your user accounts and download your .pst files. It's a pain in the butt, but it's the way we upgraded our domain from NT 4.0 to W2K in December. It took an entire weekend for an enterprise of two servers, 75 users, but it could be worse. Me: We need a better backup system.
My boss's boss: Backup? We don't need no stinkin' backup!
 
I'd run a memory checker (like MemoryDoc) and some drive utilities. The slow boot could be from a bad memory chip or bad sectors in one (or more) harddrives. I have 30 users on a domain controller/file share with (1)133MHz processor, 128MB RAM, and (2)9Gb HD that will boot in around 1min (but I DONT have Exchange on it!!) If it used to work, then changed, try to find a hardware fault (also interrogate the usual suspects to see if anyone had "walked by" the server room...*I just wanted it to have a pretty screen saver*...aargh!

Somewhere on M$ techinfo you can find a list of reasons why you should NOT put Exchange on the domain controller, I recommend your next upgrade be a second server for Exchange.

Alex
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top