Can't log off, reboot, or shutdown. Server 2003

[YeOldeStonecat]

No no..that's quite normal for small networks.
Just curious....cuz if there was another server, was going to suggest making sure it's another DC...if not ..doing a /dcpromo on it and moving the roles over. "just in case".

 

[nlinecomputers]

OK most of this appears to be corrected. Scheduled tasks all had to be reset up. GFi had to be reinstalled. Chkdsk was run on all volumes with no problems found. SFC also no problems. Shutdown and performance issues both were caused by corrupt Fortis document imaging install. Everything appears to be working correctly now.

 

[YeOldeStonecat]

Odd. I'd normally expect more than just a corrupted hosted app file to make a server act up like that.

 

[nlinecomputers]

Odd. I'd normally expect more than just a corrupted hosted app file to make a server act up like that.

It gets weirder. The backups are slow. Taking several hours longer than they use to. I'm thinking performance issues and never really check the damn file size. The backup is considerably larger than it used to be.

Come to find that the "missing" archive files were not deleted. They had been moved. The whole freeken archive that I had restored was sitting in a subdirectory unrelated to this one. As if it had been dragged and dropped there. The original directory had been restored from backup and has been added to sense so there is no reason to keep this so it is being deleted.

Also going to have all the passwords changed on this box. I'm wondering if someone has access to this who shouldn't. (Like a cleaning crew or something....)

 

[Mokester]

Unfortunately that happens...A LOT. You could install WinMerge. Use that to compare your backup directory once mounted to the current one...in my experience it works rather well...only had issues when I tried running it on a really large data set...but for majority of setups it works fine. Helps for those times when you have customers who like to drag and drop.

 

[nlinecomputers]

Yeah. But it doesn't usually happen after hours on a directory no one has direct rights to.

 

[YeOldeStonecat]

I recall a situation a few years ago, clients server started having major performance issues after a drive blew in the RAID and the drive was replaced. Was SBS03 on a rather beefy Proliant ML350, good 15krpm SCSI drives. My experience is that rebuilding RAID volumes goes well with good RAID controllers...but this one case...it appeared to not go well. HP support was involved....troubleshooting the RAID controller, updating its firmware, the OS drivers, all that stuff. Still she ran horribly. So I shut down as many services as possible (Exchange, SQL, lots of network infrastructure services)...did an NT Backup, blew away that data RAID volume, created a new one, restored the data volume from that NT backup, rebooted the server a couple of times to let the dust settle..and she ran like a champ for another year or two until she was replaced by a new SBS11 server.