Recommended Configuration for the Revelation Windows 2000 Service (NT Service) Advanced Revelation and OpenInsight Environments (General)
Created at 27 APR 2000 04:55PM
Server:
1. REVPARAM file: The Revparam file should be placed (after user creation) in every directory on the server containing linear hash files. If you do not want the Windows 2000 (formerly called NT Service) to control certain directories (backups, etc.) then simply do not include the Revparam file in those directories or switch the flag to 0 (see below). When using the Revparam file to work with the Windows 2000 Service, it need only contain the following: ServerOnly=1
2. Make sure the Revelation Windows 2000 Service (listed as Linear Hash) has been started and is automatic on the server. This can be checked from the server s Services dialog box (Control Panel→Services) or from the directory on the server containing the Revelation Windows 2000 Service, or using lhsrvc.exe (the linear hash service executable) by typing: lhsrvc status from the working directory s command line.
3. Make sure that the System User has been added to any and all directories/files for which the Revelation Windows 2000 Service will be utilized. This is typically the OpenInsight or Advanced Revelation directory on the server (or wherever the oinsight.exe or arev.exe is). This is the operating system user and can be added to this folder. Make sure that this user has FULL rights and the replace permissions of subdirectories and replace permissions on existing files are checked while adding the SYSTEM user account.
Client:
1. Try to run as FEW protocols as possible on workstations that will be utilizing the Revelation NT Service via OpenInsight or Advanced Revelation. The Windows 2000 Service uses named pipes, which can be commuted via NetBEUI, TCP/IP, or IPX/SPX (Microsoft s IPX/SPX) protocols. Speed of the NT service works fastest in the following order NetBEUI > TCP/IP > IPX/SPX. Multiple protocols will impact performance with each additional and/or unnecessary protocol stacked. Banyan Vines protocol has proven to cause FS1019 errors in many cases and is not recommended for use with the Windows 2000 Linear Hash Service.
2. Currently (as of 03/29/2000), there is an issue with running the Revelation Windows 2000 service (which utilizes the All Networks Driver) on Windows NT workstations with Service Pack 6 and the server with Service Pack 5+. (See this Knowledge Base article for complete details). This issue does not exist with Windows NT Server Service Pack 6 running the NT service and Win2000 Professional workstations (see our Support Matrix for the latest supported configurations).