Hello all,
I've recently run into an error I don't think I've seen in over 15 years: SYS1045.
Some background:- This is on a system running eCS v1.2R
- System has been running for over three years and (until this issue) only taken offline for the occasional cleaning. It's manage (between cleanings) 1 year, 11 months 2 days of continuous uptime... until recently
- There have been no hardware changes, and no software changes (until this problem presented itself)
- System is running: Web/2, FTP (Pete Moylan's), MySQL v5, NISTIME (for time sync), and wGET (to report status every few minutes)
The machine (at reboot, during normal operation, and after the error occurs), has only about 180MB of RAM in use.
Recently, every few weeks, everything that requires the commandline (including the commandline itself) will stop working, and no new sessions dependent on the commandline can be started. Attempting to start any cmdline will instead display:
SYS1045: The application program is not compatible with the version of the operating system being used.Yes, that's correct... OS/2's very own CMD.EXE is no longer compatible with itself/the OS.
The full help message is kinda weird (HELP SYS1045):
EXPLANATION: The program requires a different version of the operating system.
ACTION: Use OS/2 Warp and restart the system or install the proper version of the application program on the system. Then retry the command.Once restarted, everything works fine again - for about 3-5 weeks.
So... I'm baffled. I haven't seen this message since trying to run some very old OS/2 apps on a version of OS/2 that's significantly older.
Related notes:- Closing all open programs does not alleviate the problem (as it does in "out of resource" issues)
- One can open various PM apps after this error has occurred. One simply cannot open/start anything that uses the cmdline (including the cmdline itself)
- Restarting the system always resolves this issue.
- ALL of the above listed apps have been running in the same fashion and on the same version for the better part of almost 4 years.
- Since the error started, we've upgraded FTPd, MySQL and Web/2... didnt help.
Any insight would be greatly appreciated,
Robert
Robert,
You have looked at the hardware and checked that all cards are fully seated and memory with clean connectors? I ask because the one time I encountered that problem a load of crud had been forced over the first memory stick by a rather large CPU cooling fan. Once that was cleaned up and a plastic deflector installed the problem vanished never to reappear for the last 6 years.
ivan
Quote from: ivan on 2010.10.31, 22:02:56
Robert,
You have looked at the hardware and checked that all cards are fully seated and memory with clean connectors? I ask because the one time I encountered that problem a load of crud had been forced over the first memory stick by a rather large CPU cooling fan. Once that was cleaned up and a plastic deflector installed the problem vanished never to reappear for the last 6 years.
ivan
Hi Ivan,
We haven't done a thorough cleaning in the last 6 months, and I hadn't thought of that simply because for 3-5 weeks at a time of heavy database use, there have been absolutely no other errors; and I would have thought at least one SYS3175 or something similar for memory related stuff. Whatever's happening is solely causing this one issue - and doesnt affect running any other app (which considering everything I run starts from or runs via the command processor, is a big issue of course).
I'm heading up there again this coming week (just at the customer's last night to "fix" this again, so I probably have at least 3 weeks before it happens again), and I'll shut the box down and pull it apart...
...a bit of dust would be a lot easier to deal with than having to do a reinstall.
Best,
Rob
Hi Robert
I've seen the SYS1045 error happen when a jfs formatted drive needed a full chkdsk (not the "log check" which occurs at every boot).
Regards
Pete
Quote from: Pete on 2010.11.01, 17:15:08
Hi Robert
I've seen the SYS1045 error happen when a jfs formatted drive needed a full chkdsk (not the "log check" which occurs at every boot).
Regards
Pete
No JFS on the system at all...
I've got another system running mostly the same software (the only difference being it's been running LDGW instead of Web/2 for the last 3 of 5 years) and it's actually a combination of HPFS386 and JFS... had occasional JFS issues with it in the past, but never this error either.
Best,
Rob
It may happend that this is HDD error related issue, You may try to replace old cmd.exe and dlls that are related from anoter OS/2 that has no such problems (You may backup original ones before replacing `em). Or from backup, if it is available. Look does exist anything in NOWHERE directory on root drive.
This is a long shot, usually if this is problem, system does not work good for 3 weeks. I was have similar problem, OS/2 works good some time, then pop up weird errors, fixing, again work good for some time... solved with replacing HDD with new one.
If You can afford, try immediately with new drive.