Problem
I changed the system locale using ScoAdmin International Manager,
or by editing /etc/default/lang, and now the calendar server does
not start. It returns a "fatal error" message whenever the system
is brought up to multiuser mode:Error Incorrect SCO isam runtime system installed : 3
I tried to follow the documented workaround in the Graphical Utilities section in Chapter 4 of the SCO OpenServer Features and Limitations, but this workaround doesn't work. It returns "ISERRNO=117" when I try to rebuild the calendar server index file using "isverify".
Cause
This error message is caused by this corrupt or missing file :-
/usr/lib/isam/locks (Should have 644 root root)and should be fixed by "isverify -I" Solution
Do not follow the workaround instructions in the OpenServer Features and Limitations. Instead, take these steps:
1. Log in as root.2. Using your preferred text editor, edit the calendar server startup file /etc/rc2.d/P95calserver and add the following lines at line 20, just after the commented lines which begin with #.
Note: Make sure the quotes are typed exactly as shown:
LANG=`grep IQM_LANGUAGE /usr/adm/ISL/iqm_file \
| awk 'BEGIN { FS="\"" }{ print $2 }'`
export LANGThis change will enable the calendar server to be started using the locale which was set at installation time, regardless of what the system locale may be set to, and without having to rebuild the calendar server index file /usr/lib/sco/oadb/caldata.
3. Bring up the system in multiuser mode.
NOTE: If you see error messages such as:cronsched: No response from server errno = 2, t_errno = 0
appearing in root's mail then it is recommended to:
a) Follow the steps above orb) Configure the Calendaring options for each user by:Some users have found that this message is caused if they have an
incomplete scosh calendar configuration. You can check this by
running (for the affected user - root in this case):scosh -> Application -> Calendar -> Options -> Configure
Have "Invitation and Cancellation Mail?" set to No and "Daily and Weekly Schedules?" set to Off, if you don't use this scosh utility.
This will be dependent on the "Holiday" file being updated and MMDF being configured.
c) Another possible cause of this message is that the calserver
"calendar" daemon is not running on the system, on my system:# ps -ef | grep cal
root 467 1 0 Mar-01 ? 00:00:00 /usr/lib/scosh/calserver
root 469 467 0 Mar-01 ? 00:00:00 /usr/lib/scosh/calserver
root 471 1 0 Mar-01 ? 00:00:00 /usr/lib/scosh/caldaemon
root 4226 4177 4 11:29:22 ttyp1 00:00:00 grep calIf they are not running then you can try manually running:
"/etc/rc2.d/P95calserver start" and see if this starts them with no error messages.
d) If the calendar service is not required then add the following
to "/etc/rc2.d/P95calserver" and using your favorite editor
add "exit 0" to the top of the file so it never starts at boot
time. Also, remove the references to "calserver" in the cron:0 0 * * 1-5 scosh cronsched -r
0 0 * * 1 scosh cronsched -wrNOTE: Alternatively, if you do not wish to run Calendar Server then simply
rename P95calserver to p95calserver (lower case) in /etc/rc2.d See also
If you are running OpenServer 5.0.4 or 5.0.5, you may need to refer to TA105800, "My shell scripts using awk give unexpected results in SCO OpenServer 5.0.4."