ALWAYS check the HOMEDIR setting for all NETWORK problems - Even if that is not what you THINK the problem is. This IS the problem MOST OF THE TIME and it is quick and easy to check.
Run OOPSNET and check the HOMEDIR. Make sure you are using a valid drive.
Problem:
Having Numerous network crashes.
Things to check:
1. Access rights to exe, ovl, err, and ilf files.
2. Showing right OOPS! network directory.
3. SHARE loaded on all machines.
4. DON'T run smartdrv and the network cache program.
Using both will cause corruption. Best performance
from the network cache program.
5. Use NOEMS on EMM driver.
6. Load high as many drivers, including network drivers
as you can.
7. Make sure people are exiting correctly!
Netware Lite info:
Each machine on the network can be defined as a client, server or both a client/server. Server should only be used if the hardware resources of that machine are truly going to be shared by others on the network. Otherwise, the 44k server.exe is loaded into memory for no good reason.
In startnet.bat files are loaded in the following sequence:
share (can be loaded high)
lsl (can be loaded high)
network interface card driver (can be loaded high)
ipx odi a (lh)
server (lh)
client (lh)
nlcachex (lh)
It is recommended that you start by loading SERVER, Client and nlcachex high first. The server fluctuates in size so make sure that is gets loaded first. Afterwards you can experiment with loading the IPX, NIC driver, LSL and share high.
The files= parameter that is set for the server mcahine must be large enough to accomodate all files opens from all workstations that access files on that server. So if there are 4 workstations, including the server, and OOPS! opens a maximum of 40 files from each workstation then set the CONFIG.SYS on the server equal to 160.
Avoid mapping a drive on the server to itself; that is, if the server machine is to be used as a workstation to access OOPS, use a SUBST statement instead of a MAP statement. If not the server uses twice the resources acutally used to get the job done, ex. 1 file opened is counted as 2 files opened.
Important: set the client tasks parameter equal to 15 times the number of workstations. This can be set via the NET utility under the Supervise network and then server configuration options. In this example with 4 workstations it should be set to 15*4=60.
Make sure the Share loads before SERVER.EXE and use the /L:200 /F:4096 parameters.
Novell Netware setup.
TO SPEED UP ACCESS TO OOPS! on a network:
1. Create on every workstation a directory called
OOPSLOC
2. Move the *.exe, *.ilf, *.ovl, *.err files from the
OOPS! network directory to the local OOPSLOC directory
3. Erase the files from the OOPS! network directory
4. In the network OOPS.BAT file:
A. Add a new line prior to the OOPSRUN command, put in:
SET KPATH=C:\OOPSLOC
B. Change the OOPSRUN command to:
C:\OOPSLOC\OOPSRUN.EXE OOPSLIB -GM
5. Modify everyones autoexec.bat file to include in the PATH
statement C:\OOPSLOC
Users must have RWCEMFA - Read, Write, Create, Erase, Modify, File Search and Access Control. Lack of Access Control rights in the directory when a compress is attempted will cause the renaming of the temporary file to fail. Use the filer utility to assign the trustee rights to individual network users. The NET.CFG or SHELL.CFG must have EOJ=OFF as the last line, so that OOPS! can do the file locking, not Netware.
Problem:
You get messages that you are not connected to the server
from the workstation machines,
Solution:
Check wires and boards for integrity as this is a network
problem.
Problem:
During clean-up you receive an error message: "Inoperable Command for
Shared Table"
Solution:
NETSYS variable in pmcntrl.mst file was set to "False."
Problem:
When trying to complete WOs you get a message that you are
out of disk space, but chkdsk shows that you still have space.
Solution:
On the network, you probably are not allocated enough disk space
under your user account. You do not have the disk space
available, but you should be able to change your allocation.
Problem:
You cannot run reports from one workstation, but the
others are working fine. You get "CANNOT OPEN FILE" messages.
Solution:
Check files in CONFIG.SYS.
Problem:
You are getting "Max # of Users" message and can't get into OOPS!.
Solution:
Run OOPSNET to reset.
Problem:
When installing KnowledgeMan 3.0 LAN applications on Novell 3.11
KnowledgeMan may lock up unexpectedly. This is not
KnowledgeMan's fault, it is a problem with the default
configuration of Novell 3.11.
Explanation:
Novell 3.11 will try to detect when a file has been left open
that should have been closed. KMAN uses memory image files to
swap parts of memory to disk and back. These files are normally
left open by KMAN. Periodically, Novell will try to close one of
KMAN's memory image files, causing KMAN to crash.
Solution:
To fix the problem, you must modify the boot disk on each Novell
workstation using KMAN. The file that needs to be mofified is
called SHELL.CFG. You need to add the line:
to this file. This will turn Novell's End-Of-Job detection OFF, and KMAN can work as smoothly as ever.
Problem:
You are having trouble accessing SCRF1.IND from a second
workstation when another indivdual is in Active Work Orders.
Solution:
You have an insufficient allocation of file handles.
Problem:
You get "Cannot open File" messages on workstation, but not on
server.
Solution:
Bump up files setting in CONFIG.SYS on workstation.
Problem:
You are getting one of the following Error messages when accessing work orders:
file not found: pmcntrl.mst
not an accessible table name: pmcntrl
undefined name: netsys
logical value expected: false
Run clean up
Solution:
The NETSYS field in the PMCNTRL file is set to "False." Setting it to "True"
should clear up these errors.
Problem:
After upgrading, you are getting a sharing violation error.
Solution:
Make sure all appropriate files are set to read-only, *.exe,
*.err, *.ilf, *.ovl. (reboot the network)
Problem:
After loading Lantastic OOPS! will no longer run.
Solution:
Set files in CONFIG.SYS to 40.
Problem:
Lantastic version 4.0 running OOPS! 3.0. OOPS! security
turned on. Getting errors opening files in shared mode. One
user can access active WOs but when second user tries the USE
fails.
Solution:
SHARE command must be set up to allow more than the default
number of files (20) set up for file locking. Problem was a FILES=
parameter that was in the "Server Startup Parameter" list under
NET_MGR. If you set it to zero so that it will look to the
CONFIG.SYS file make sure that the CONFIG.SYS has a value of 500.
Problem:
DOS 5.0 on Netware 386 3.11. OOPS! 3.0
Problem moving WOs to history.
Solution:
Index operation against a DB file fails with open error on the
index file itself. #PREFIX was set to " ". With no home
directory, all renames failed. Set it to F.
Problem:
Can't get two users on OOPS! at once.
Solution:
Make certain your "Program Files" were not read-only. Set attrib for +R
Problem:
The history file kept losing the EOF pointer.
Solution:
The network directory may be set to restrict the size of
files. When size is exceeded the network acts as though the disk is
full and will not write to the file.
Problem:
One user on the network cannot open a file.
Solution:
Specific user
wasn't mapped correctly.
Problem:
Lantastic network started running reports slower.
Solution:
When you
reinstall the network run lancache instead of smartdrive.
Problem:
Getting an error message that OOPS! can't open a file.
Solution:
Someone may have reset the network drive. This will cause it to point to the
wrong directory on the network.
Problem:
Get a sharing violation EVM001 on krun01.ovl or
krun02.ovl.
Solution:
The network may be dropping the connections. This
problem occurred on a machine running Windows. The Error message wasn't
coming up on that machine, but another one.
The network card memory address was set to 300 which "is the
kiss of death" on a network. Windows and the network card wanted
the same area. Windows stomped on the network area, causing it
to lose connections.
Problem:
Work Orders showing up in active after they have been closed out;
When this problem occurred the user tried to log off the network and was told files were open in OOPS!; the user went back into OOPS! and out, but got the same message. He then logged out anyway. When he tried to go back in, he got MAX# message and ran NET. When he went into WOs, he discovered the old work orders.
Solution:
Checked the path in NET and discovered that it was
taking him onto the local machine OOPS! and leaving you there.
They use the hard disk for backups so they were seeing old versions of the file.
It was necessary to fix the path in NET.BAT.
Problem:
You are running a Novell network and can't copy OOPS! data files even
with all access rights.
Solution:
This may have caused the forecast to fail if you have
duplicate data files on the network. Novell will search for
the data files starting at the root and working up. If the duplicates are found
first in a directory that you don't have rights to, it will fail.
Word to the Wise:
On NT Workstations, users can have a 'profile' or a 'login'. The user must have admin rights to their OOPS! folder for OOPS! to work correctly. If the user does not have admin rights, clean-up will fail as well as any other function where files are rewritten.
Problem:
You have gotten a Network OVL or KMAN error indicating a sharing violation on KRUN.
Solution:
This happened to one customer - when the network was changed from token ring to ethernet, the problem went away. As a bonus, OOPS! started running much faster.
Problem: OOPS! is running slow at startup
This happened with one user. The NET USE command in the Printer Setup file to select a network printer was pointing to an incorrect address; the network was trying to resolve the error which caused the time delay.
Solution:
To check to see if this is your problem, print a report with all of
the printers and their net use command. Then issue the net use command
at a DOS prompt and see if it fails. If it does, check with your network
administrator and have them verify the network address.
To create the report:
DESIGN YOUR OWN REPORTS AND SCREENS
REPORT NAME: PRINTERS DATE LAST USED: 03-01-11 FANCY (F) OR Q&D
(Q)? Q
BASE TABLE FOR THIS REPORT (F9 TO CHANGE) PRTCFG FILE NAME
PRTCFG.MST
ARE THE REPORTS:
ON FORMS? (LABELS, ENVELOPES, ETC.) (Y/N) N
IF 'Y': NUMBER OF LINES @ 6 per INCH? 60
PAUSE BETWEEN PAGES OR SCREENS (Y/N)? N
REPORT TITLE Printers and their network commands_______________
FOR Q&D REPORTS ONLY:
What fields do you want to display? (separate by ,)
(F1-Lookup,F2-Help,F8-Clear)
PRTNAME,NETCMD
FOR ALL REPORTS:
What are the special conditions?
(F1-Lookup,F2-Help,F8-Clear)
netcmd ne " "
What is the sorting order?
(F1-Lookup,F2-Help,F8-Clear)
What is the grouping (sub-totaling)?
(F1-Lookup,F2-Help,F8-Clear)
Special Instructions? (Use only with OOPS! Tech Support Assistance)