Network Installation

Network Installation

Previous Top Next

-----------------------------------------------------------------------

KwikSaleSTM Applications & Networks

-----------------------------------------------------------------------

FILE NAME ON DISK IS : NETREADME.TXT

How KwikSaleSTM Applications Network Installation Works:

The KwikSaleSTM Applications network installation process may place the KwikSaleSTM Applications data files, executables (EXE and DLLs), and help files in a shared network folder. KwikSaleSTM Applications users execute the program from the network which enables the data to be shared among multiple KwikSaleSTM Applications users.

Network Installation Notes:

1. The workstation must have a drive letter mapped to the directory:

KwikSaleSTM Applications requires that the workstation have a drive letter mapped to the directory which contains the KwikSaleSTM Applications data.

Note: The drive letter may be assigned to a parent directory -- the only requirement is that KwikSaleSTM Applications on the user's machine points to the data using a drive letter.

(e.g. "K:\apps\SA1 KwikSaleSTM Applications" is acceptable, but \\Server1\\apps\SA1\ KwikSaleSTM Applications" is not).

2. KwikSaleSTM Applications users must have FULL rights:

KwikSaleSTM Applications users must have FULL rights (Including the creation of files and sub-directories) to the shared directory.3. Choice of Installation:

KwikSaleSTM Applications installation program may offer the installer a choice of a stand-alone network client or network file server installation.

4. The network installation must be completed FIRST:

The network installation must be completed BEFORE users can install the network client option. Otherwise the client install will not be able to create proper shortcuts.

5. Installing a local version of KwikSaleSTM Applications:

If a local version of KwikSaleSTM Applications has been installed followed by a subsequent network client install, the users menu system and window's KwikSaleSTM Applications shortcuts will be updated to reflect the shared database location. Thus they will have to be manually adjusted including the new "Target Path" and "Start in:" folder setting for each shortcut.

6. KwikSaleSTM Applications Uninstall:

Uninstall only works for standalone installations. This prevents a network client user from inadvertently erasing the database.

7. Caching Issues:

There are several important issues involving caching and shared databases discussed below. Most of these are related to problems found with Microsoft's Windows 95 and NT 4.0 network technology. You must make the changes described below to protect your database from corruption.

A "Client" is a PC computer or workstation that accesses files on a shared "File Server". Please consult your network administrator about these changes as well as making backups before making any file server changes.

7.1 Windows 95 Clients:

Microsoft has discovered problems in the Windows95 environment in which the Windows 95 redirector and system registry settings because caching affects database corruption in applications that share files on Windows 95 and NT network servers.

To ensure data integrity, we strongly recommend that the fix for the Virtual Network Redirector of Windows 95 be applied (even if your user has Windows 95b from a new system). For convenience, the fix may be available in the directory where the KwikSaleSTM Applications executables are installed. The fix (Vrdrupd.exe) should be run on every Windows 95 client machine connecting to any KwikSaleSTM Applications shared database.

You may also obtain the same fix from Microsoft Corporation (see article ID Q174371 on the Microsoft Support web site www.microsoft.com ). As stated earlier, the fix should be run even if you have Windows95b (OSR2) - when asked to replace DLLs, you should confirm the request and replace them.

7.2 Windows NT Clients:

Microsoft has discovered problems in the Windows NT 4.0 environment in which the Windows NT client can cause database corruption in applications that share files on NT servers.

To ensure data integrity, we strongly recommend that the latest service pak for NT (currently at level service-pak 4) be applied (Note: Even if your users have Windows NT from a new system they might not have the latest service-pak).

You may also obtain the same fix from Microsoft Corporation at their support web site and see article ID Q174371 on the Microsoft support web site www.micorsoft.com .

In addition Opportunistic locks on an NT workstation should be disabled.

The following registry entries are used to enable or disable OpLocks for the Windows NT Workstation. These registry keys may not exist by default. To access the registry run REGEDT32.EXE from the File menu, choose Run in Program Manager or File Manager.

WARNING: Using Registry Editor incorrectly can cause serious, system-wide problems that may require you to reinstall Windows NT to correct them. KwikSystemSTM Associates cannot guarantee that any problems resulting from the use of Microsoft's Registry Editor can besolved. Use this tool at your own risk.

System Registry Workstation Service Entries location:

\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters

Turn off Opportunistic Locking by changing the following value to 0.

UseOpportunisticLocking REG_DWORD 0 or 1 Value: 0 (true)

Only if you are importing data locally, must you be sure your workstation's virtual memory setting for minimum page file size is set to at least 100 megabytes and maximum of 200. As your database grows these requirements may need adjustment. This can be affected through the NT workstation's file "System Properties" "Performance" settings.

7.3 Windows NT Server:

KwikSaleSTM Applications do not support versions of Windows NT server earlier than 4.0.

Microsoft has reported problems in the Windows NT 4.0 environment in which the Windows NT server in combination with incorrect registry setting can cause database corruption in applications that share files on NT servers.

To ensure data integrity, we strongly recommend that the latest Service-pak for NT (currently at level server Pak 4) be applied (even if you have Windows NT server 4.0 from a new system).

It is critical that you verify that your server has the three settings described below. The first setting listed below already existing in default setting on NT 4.0 server. The second two must be added.

The paragraph below is a description of Opportunistic Locking and RFCB Caching on Windows NT Servers:

Windows NT, by default, caches file handles to increase performance of some Windows applications. This caching causes problems with database applications that use Standard File and Record Locking. In addition, Opportunistic Locking (oplock), which allows each client to cache its own file close requests rather than allowing the application to close its own file handles can also create problems.

To disable RFCB Caching and Opportunistic Locking, modifications you will need to be made to the registry on the Windows NT Server as follows:

The following registry entries are used to enable or disable oplocks for Windows NT Workstation or Server. These registry keys may not exist by default. To access the registry run REGEDT32.EXE from the File menu, choose Run in Program Manager or File Manager.

WARNING: Using Registry Editor incorrectly can cause serious, system-wide problems that may require you to reinstall Windows NT to correct them. Isogon cannot guarantee that any problems resulting from the use of Microsoft's Registry Editor can be solved. Use this tool at your own risk.

System Registry Workstation Server Service Entries Location:

\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters

EnableOplocks REG_DWORD 0 or 1 Value: 0 (False)

Specifies whether the server allows clients to use oplocks on files. Oplocks are a significant performance enhancement, but have the potential to cause lost cached data on some networks, particularly wide-area networks.

EnableOpLockForceClose REG_DWORD 0 or 1 Value: 1 (True)

CachedOpenLimit REG_DWORD 0 or 1 Value: 1 (True)

7.4 Importing Files on File Servers

You can import Using KwikSaleSTM Applications on an NT file server. Your imports of Distiller data will be affected by file server load any backups that are in progress or schedules maintenance and the fact that someone has to log in to the server to start KwikSaleSTM Applications.

RAM should be at least 64 megabytes, preferable higher especially for KwikSaleSTM Applications databases supporting Distiller data from more than 30 systems.

You must be sure your servers virtual memory setting for minimum page file size to at least 200 megabytes and maximum to 250. As your database grows these requirements may need adjustment. This can be affected through the servers file "System Properties" "Performance" settings.

8. Mixed Netware 3.1 and 4.1 File Servers:

In some situations using of shared databases in mixed Netware 3.1 and 4.1 network environments has been know to cause database corruption. Installing the latest version of the Netware Client from Novell will help in most situations.

9. Novell 4.11 can close file handles after 30 minutes

Novell 4.11 by default closes file handles not in used after 30 minutes. This can interrupt the KwikSaleSTM Applications processing during non-active modes. You can go to www.novell.com and search for the document called "watchdog" for instructions on how to change these setting.

10. Faulty Network cable connections and Interface cards:

Make sure the cable connections are proper and secure. This is the most common hardware problem in network installations. Testing equipment is available for the purpose of checking cable continuity and signal integrity. In extremely rare cases, database corruption on shared databases has been shown to be caused by faulty or noisy network cards. This situation can be extremely difficult to diagnose. Experience has shown that using the process of elimination by taking network cards off-line one at a time to locate the offending card on the network is effective.

11. Windows 98 Clients:

At release time no known problems have been encountered using the Windows 98 operating system acting as a client.

12. This document's purpose:

This document is supplied for the purpose of advising users of KwikSaleSTM Applications of known problems associated with operating KwikSaleSTM Applications in a network environment. Since operating systems and applications are constantly being enhanced and improved, you are advised to first believe that KwikSaleSTM Applications are not at fault for data integrity problems. If database integrity problems do arise, please be advised that our applications do not have any known problems when, being used in a stand-alone system and to check out your network system and it's associated hardware first.

End Of KwikSaleSTM Applications Network Advisories