Back

EDUADMIN FREQUENTLY ASKED QUESTIONS (NETWORKING)

After installing the latest Release files on the server, some of the Workstations fail to request synchronization (SlipStream)!

The 'netpath' setting in the eduadm file on the workstation is invalid.

After installing the latest Release files on the server, some of the Workstations get a file access error - Invalid Record Declaration (47) - when trying to access a file!

The workstation reporting the error has not been upgraded. It does not have the latest version of the program. Another workstation has converted some of the data files and the workstation reporting the error is unable to recognise some of the data files.

When an EduAdmin Module is launched, it returns a UPG error!

EduAdmin cannot see the data directory. Ensure that (a) the user who has logged into the workstation has permissions on the data server, (b) the data directory is shared and (c) the path setting in EduAdmin is valid.

When launching an EduAdmin Module on a workstation, the error "File (EduAdm) Could Not Be Opened Error: File Not Found (2)" is returned!

The is the basic dos error number 2 which means precisely what it says, namely, that a required EduAdmin file cannot be found in the data directory that the eduadm path file in the program directory is pointing to. The solution is to check that the eduadm path file in the program directory is pointing to a valid data directory. If the path setting is correct and you still get the error then run the system install and place all these files into the data directory.

File Corruption

Network problems generally trace to:

  • Network file damage with redirector caching in Windows 95. The incorrect version of the network redirector (vredir.vxd) which caches data locally for files it accesses on a Microsoft network when the file size does not change or if the last modified time does not change within a two-second period the redirector reads file data from the locally stored cache rather than from the file on the server. This issue has apparently been resolved in Windows 98.
  • Having the write behind cache on the workstation enabled.
  • Having the opportunistic file locking set to on (NT server).
  • Poorly written virus checking software.
  • Bad hardware (flaky network card, bad hub or switch).

Remedies in order of precedence:

  • Download and install the vrdupd.exe patch file from the Microsoft support page (Windows 95 only).
  • Disable the write behind cache on all Windows (9X and NT) workstations.
  • Check oplocks=no on the NT server.
  • Switch the virus software to ignore EduAdmin data files.
  • Replace defective hardware.

For more information see Write-Behind Caching.