|Message||The system does not support the command requested.|
This appears to be a raw Win32 error. More information may be available in error 0x80070077.
This is a Blue Screen of Death stop code. More information is available in the Knowledge Base article Bug Check 0x77: KERNEL_STACK_INPAGE_ERROR.
This code indicates success, rather than an error. This may not be the correct interpretation of this code, or possibly the program is handling errors incorrectly.
|Description||The default facility code.|
|Error Code||119 (0x0077)|
I think the better question is. LET'S PRETEND the hard drive is going to die.
Do you have a backup?
If the answer is "No" then you should be scrambling to make a backup regardless.
As for your other questions... you didn't say enough about your error to really narrow it down but please take a look at this link:
Noticed that you updated your question with some more information.
Hard drives are SO CHEAP right now that I would STRONGLY recommend buying one and backing up your system. The backup that the boss has probably isn't as current as you'd like.
I can't say for sure if your hard drive is dying or not. Normally I'd recommend you give something like SpinRite (http://www.grc.com/sr/spinrite.htm) a try but that's about the cost of a new hard drive and it sounds to me like money is a big issue with you (or your boss)? That being said... your best CHEAP solution would be to buy another hard drive and then use some free cloning software to clone the drive.
Once you clone the drive, boot up off the CLONE and keep your original as the backup.
See if the problems persist or end from there.
If we're wrong and the HDD is NOT the problem then at least you still have a current backup so you really haven't lost anything other than a little bit of time.
You shouldn't have to "weep" to your boss/employer. If he/she can't see the value in backing the data up then at least do your best to WARN THEM of the potential consequences.
After that its their decision (and not your fault) if something goes wrong.
I'm going to make an assumption and guess that you're running Windows Server 2003. I'll appropriately retag your question as such.
Since you are unsure of what the cause of the error is, that's what we need to find out. This is my suggestion: Run chkdisk on the drive, and run memtest86+ if possible (as in, you have a few hours you can schedule for downtime)
When you say this is the corporate server, what exactly does it run? It is just a file server, or does it also host Active Directory, DHCP, DNS, DFS, anything like that? Are there any other applications that are absolutely reliant on this server? If so, you might want to consider a few things. First is getting that server out of where it is, and putting it somewhere that is 1.) climate controlled (aka in a room with a dedicated air conditioner), and 2.) secure from other employees. This will prevent a few things. First, it will make sure that no one that is unauthorized to touch it can do so. Second, it will greatly increase the life of the hardware by ensuring that it stays at appropriate temperatures. Remember, computers make heat, and that heat needs to go somewhere. If it's in a closet, that is going to get very very warm in there, and warm temperatures for computers are a Bad Thing. If you want an idea of how bad it is to have a server in rooms without air conditioning, read this article, and weep.
Also, I'm going to agree with KWPINC. Not having a backup is asking for something bad to happen. Tell your boss you need backup. If he says it's not necessary, compare the cost of a backup service (whether it is done in-house and carried offsite, or done by a managed service) to the approximate $2000 minimum for DriveSavers crack open one of your drives, and not even be able to guarantee that everything will come back.
Also, if you could, can you give us a description of the hardware your "corporate server" is running? Software would be nice as well.
Ok, based on what you've told me, I'm going to make some suggestions.
First: Get RAID in there ASAP. At least RAID 1 so if a disk fails (which seems likely given your current setup) you aren't up shit's creek. And believe me, if your disk fails, and you don't have a backup, you ARE going to be up shit's creek. Many Dell systems support RAID (I have two machines in my office that have it, a Precision 380 and an Optiplex 755), so other than being cheap as hell, there's no real excuse for not doing so.
Second: Work on getting a PowerEdge or comparable server in the building, and getting things migrated over to that. You do this one of two ways. First thing you could do is just image the old server to the new one, but this is unlikely to work because of drivers and such. The proper way to bring it up would be (and this is very much so simplified) to buy the new server, join it to the domain, set it up as a BDC, mirror the file-shares over, eventually set deny permissions on the old server for file shares, then promote the new server to PDC. I'm not sure about IIS or Exchange as I don't deal with them as much as I would like to.
Here is a Microsoft KB reference to start with,
"Directory Services cannot start" error message when you start your Windows-based or SBS-based domain controller.
Have not looked deeply in your other questions, and, i do not see a reference here suggesting you have done a Microsoft KB lookup.
You receive a "lsass.exe-system error: Security Accounts Manager initialization failed" error message and event ID 1168 is logged when you restart a Windows Server 2003 domain controller
In my opinion you should change this:
On server side, set
[SERVER] section to
0. This might disable mouse and keyboard input.
On client side, in section
[MENU] you have to try different values for the key
I have never experienced that particular error before, but I dont think its panic time. Is the Event Viewer available in restore mode? If so check it out, maybe it will give you some idea where to start.
If not, I have used the ERD Commander boot disk many times on our Win2000 AD Server. It will allow you to boot from the ERD CD and 'attach' a Windows installation.
Once booted, you have a windows-like desktop and can do many helpful tasks, such as view event viewer, browse the drives, anything really.
'This issue can occur if the path to the NTDS folder that holds theActive Directory database files and log files does not exist or the NTFS permissions on this folder and database files are too restrictive, and Active Directory cannot start. See Q258007 and Q295932 for more details. Also check Event id 26 from source Program Popup.'
In your case finding the Solution would be needed lots of surfing through sites and Search for the Description of Error codes and find solution for it or You can simply
Analyze crash reports. you’ll receive a certification report that contains additional files that you can use to identify what happened. Depending on the type of error that occurred, you’ll receive either A
crash dump file or An
ErrorInfo file. To examine these files, Dev centre recommend that you use either Microsoft
Visual Studio or the Windows Debugger Tools. Have Look over here Analyzing crash reports and Improving apps with Quality reports. Hope this help you out.
You might have a driver error, a heat error or a failed component (motherboard, power supply, memory, hard drive). It's impossible to tell from the information we see here.
You really ought to bring in some outside help. It may be necessary for this problem and will be necessary to properly backup your data. Once you get through this problem, an IT consultant will likely be able to improve what you're doing in half a day. You boss really needs to compare this to the cost of losing all the company's data.
Also, once this problem is fixed, take that machine out of the closet and stick it under someone's desk. Sure, that's a bad idea from a security perspective, but a good idea from a "stuff not overheating and breaking" perspective.
Looks like lots of advice so far an few answers so:
Is this going to haunt my nights or can I fix it? If yes, how?
No this will be an albatross around your neck for the simple reason that you have no backups. Even if you didn't have the error you should have an email (printed out) on hand for when it does die and something vital is lost. Then you can point to it and say "see- I asked for backups and was told we couldn't afford them/ don't need them"
Is this urgent enough for me to tell my boss to buy whatever I need to ensure the system is backed up efficiently ASAP?
If the $100 or so for a 1TB HD in order to do backups in case of a failure wasn't important before I'd venture a guess to say it won;t be important now. I'd ask but I wouldn't hold out much hope from your description
Is the Hard Drive going to die soon, and if so, will I have to cope with it like the death of my beloved cat?
Everything dies eventually. this is a likely indicator but it's impossible to tell from your description whether its the hard drive, the controller or something else.
Would it be possible that it is caused by write errors on the disk?
Maybe, but it's possible its a read error- and inpage error means that it couldn't read back a page from the disk, It's probably unlikely that it wrote the page out badly but read it ok.
Thread 4: 0 libSystem.B.dylib 0x00001f8e memcpy + 718 1 TestRaspLayer 0x00007718 _inline_memcpy_chk (_string.h:58) 2 TestRaspLayer 0x00007678 -[SERIALPort processRxBuffer] (SERIALPort.m:243)
is where the app crashes, the problem could be from method processRXBuffer in SERIALPort class.
Double check you code and you'll find where the problem is.
I had a very similar error on a winXP machine with a dying drive. There were bad blocks randomly appearing here and there, destroying important system files... What did I do? I used SpinRite to recover the bad blocks, then I booted from SystemRescue CD to restore the missing dll from another machine.
Then I changed the hard drive for a better one :)
User contributions licensed under CC BY-SA 3.0