Network Information (version 5) .........................321 - Promas ...

peachbottomyazooΔίκτυα και Επικοινωνίες

27 Οκτ 2013 (πριν από 3 χρόνια και 8 μήνες)

105 εμφανίσεις

HOW TO
PROMAS NETWORK SETUP
7 Pages Follow
Please disregard any other network instructions you may have received. This is the latest informa-
tion available to CMS. These instructions are for version 5 only.
Please read through all of the following pages.
If your network has been set up following these instructions and you are still having problems,
please have the network administrator or other network person fax Network Tech Support at:
703-255-9172 with specific information about the problem you are having, any network prob-
lems you may have encountered and any error messages you have received.
Thanks,
Network Technical Support
Network Registration
This information is for those who have just registered their program for the network version.
Registered onto the Server
If the registration was done at the server, or if the path on the logon screen at the workstation was pointing
to the server, simply follow the instructions on the rest of these pages.
Registered onto a Workstation
If the registration was done at a workstation and the path on the logon screen was pointing to the local drive
rather than the server, the registration files must be copied from the workstation to the server where
they can be accessed by the other workstations. The registration files can be found in the RPROMAS
folder on the machine you registered on. Copy those files to the RPROMAS folder on the server.
Then proceed to follow the instructions in the rest of this document.
PROMAS Landlord Software Center support @ promas.com Sales 888-591-5179
311D Maple Avenue West sales@promas.com Support 703-255-1400
Vienna, V A 22180 website: promas.com Support 800-397-1499
Fax on Demand: 703-255-5164 FAX 703-255-9172
5/2002 Network - 1 #321PROMAS NETWORK SETUP - Version 5
OVERVIEW
Assumptions:
• The network is set up and operational.
• Each workstation has full access to the server where the PROMAS database will reside.
• PROMAS has been installed on all workstations.
1. READ THIS FAX IN ITS ENTIRETY
2. Remove any IPX\SPX compatible protocols from the network components in each computer’s control panel. (See
the section titled “Microsoft Network Issues” for more details.)
3. At the server (if used as a workstation)
From the Start button open the Promas program group and choose BDE.
In the left hand option box highlight the driver name Paradox.
On the right the third field down is “Net Dir”, click the box to the right of it. Type C:\ in the white space.
The third tab at the bottom of this window is System. Click it.
The second field down in the Parameters group on the right is Local Share. Scroll down and choose True.
Go to the file menu at the top left and choose save.
Then close the window.
4. At each workstation.
From the Start button open the Promas program group and choose BDE.
In the left hand option box highlight the driver name Paradox.
On the right the third field down is “Net Dir”. Type in the server drive designator, e.g. F:\ or click the box to the
right of it.
It turns white and a button with three dots come up in the right corner of the white space.
Click on the three dots to get a browse screen.
At the bottom right where it says Drives scroll down and choose the server drive.
In the box above labeled Folders double click the top folder.
If a file named pdoxusrs.net shows up in the big box on the left, highlight pdoxusrs.net and click OK. If it
does not, type in the server drive designator, e.g. F:\, in the Net Dir field.
The third tab at the bottom of this window is System. Click it.
The second field down in the Parameters group on the right is Local Share. Scroll down and choose True.
Go to the File menu at the top left and choose save.
Then close the window.
5. Point the working directory to the server.
At the PROMAS Logon screen click the path above the Database field. That will bring up the Select Working
Directory screen.
Select the server drive from the Drive box.
Select the folder containing the PROMAS data folder. That path, i.e. F:\RPROMAS, must display in the box below
the word Directories.
Click Save.
6. Logon to PROMAS and run the network utilities test (File, Network Utilities)
Select your database from the drop-down list, enter your User Name and Password and click OK.
Go to Help, About and review the directory settings (see page 6).
Go to File, Network Utilities and run the test (see page 6).
PROMAS Landlord Software Center support @ promas.com Sales 888-591-5179
311D Maple Avenue West sales@promas.com Support 703-255-1400
Vienna, V A 22180 website: promas.com Support 800-397-1499
Fax on Demand: 703-255-5164 FAX 703-255-9172
5/2002 Network - 2 #321NETWORK
IMPORTANT FOR NETWORK USERS
Using your data on a network requires that the file server and every workstation be set up correctly. Failure to
follow these instructions may result in data corruption that may not be recoverable except by restoring from a
backup. If you experience ANY problems related to using your files on a network, especially “Index Out of
Date” and “Key Violation” errors, contact technical support for information on how to proceed. You should not
use your data after a power outage, “Index out of Date” or “Key Violation” error, or any other file related
error until you have successfully rebuilt all your indices, reference files, and general ledger using the database
utilities.
IT IS NOT NORMAL TO GET FILE ERROR MESSAGES, COMPUTER LOCKUPS, OR GPFs USING
PROMAS ON A PROPERLY FUNCTIONING NETWORK. IF YOU ARE EXPERIENCING THESE
PROBLEMS, YOU COULD HAVE A NETWORK PROBLEM THAT MUST BE RESOLVED TO PRO-
TECT YOUR DATA.
IN THE EVENT OF A POWER OUTAGE OR COMPUTER LOCKUP, FOLLOW THE INSTRUCTIONS
IN THE TROUBLESHOOTING SECTION FOR RECOVERING FROM A POWER FAILURE.
COMPATIBILITY ISSUES
PROMAS is not recommended for use on Lantastic networks.
Due to bugs with Microsoft’s IPX/SPX compatible protocol, PROMAS should not be used on any network
running this protocol or on a stand alone machine connected to such a network. This may mean that PROMAS
should not be used on networks that use both Novell and Microsoft servers or that use Jet Direct printers unless
changes are made to the protocols being used. There does not appear to be a problem using Novell’s IPX/SPX
protocol. Based on user reported experiences and feedback from several network consultants, we do not rec-
ommend using PROMAS on any network running any version of Microsoft’s IPX/SPX compatible protocols.
BACKUPS AND VIRUS SCANS
Do not use backup programs or virus scanners on PROMAS data files while users are logged on to
PROMAS. These programs do not respect the file locking rules used by the database files and may cause
unpredictable behavior or cause record updates to fail. Schedule your backups and virus scans after hours or
suspend use of the PROMAS program while performing these functions.
PROMAS Landlord Software Center support @ promas.com Sales 888-591-5179
311D Maple Avenue West sales@promas.com Support 703-255-1400
Vienna, V A 22180 website: promas.com Support 800-397-1499
Fax on Demand: 703-255-5164 FAX 703-255-9172
5/2002 Network - 3 #321MICROSOFT NETWORK ISSUES
This section deals with known bugs in the Windows operating system. These issues must be addressed on every
computer in your office to insure that the network will not corrupt your data. PROMAS involves heavy trans-
action processing and requires that the network work correctly in high traffic situations.
Windows 95 Redirector Bug - may be introduced to Windows 98
Some versions of Windows 95 have a serious bug with its virtual redirector (VREDIR.VXD) that will cause data
corruption on a network. This bug may also be introduced to a Windows 98 machine by loading some third party software.
Even if only one workstation on your network has this bug, it can still cause corruption of the server’s files. Use the Net
Check program described below to test your computers for this problem. The updated version of this driver is 4.00.1116.
If your driver is a version before 4.00.1116, you can find a link to the update by searching www.microsoft.com for article
Q174371. Note that you must search the “Knowledge Base”, not the site in general. Just type “Q174371” (without the
quotes) as the word to search for. Select article Q174371 from the matches and there will be a link in that article to
download the Vrdrupd.exe file that will fix the bug. DO NOT ATTEMPT TO COPY THE REDIRECTOR FROM AN-
OTHER MACHINE; USE THE MICROSOFT UPDATE PROCEDURE.
Windows 95 File Locking Bug
Windows 95 workstations can have problems obtaining file locks from a Windows NT server. This bug is described in
Microsoft article Q160807. If you get “Access Denied” error messages and your workstation has full access rights to the
server, this is the likely cause of the error. Microsoft does have some workarounds for this problem that are listed in
article Q160807, but there is no fully tested patch for Windows 95; their recommendation is to use Windows 98.
Windows 95 and 98 Caching Problems with NT Server
Windows 95 and 98 workstations that are connected to an NT server must have registry changes made to correct
caching problems. Windows 95 and 98 do not correctly recognize when their cached information has become invalid when
they are connected to an NT server. This change must be made on all workstations or you risk corrupting data on the
server. This is not an issue if the server is running Windows 95 or Windows 98. The Net Check program described below
can be used to make the required registry changes.
Windows 95, 98, and NT Problems with IPX/SPX Compatible Protocol
The IPX/SPX Compatible protocol is not reliable under certain circumstances (see Microsoft articles Q171351 and
Q151677). To see the protocols used, from the Start button select “Settings” and then “Control Panel”. Double click the
“Network” icon. In Windows 95 and 98, the protocols are listed with the loaded drivers. In Windows NT the protocols are
on a separate page labeled “Protocols”. If the IPX/SPX compatible protocol is present, contact your network technician
for information on how to remove it.
NET CHECK DIAGNOSTIC PROGRAM
There is a program called NCHECK.EXE (Net Check) that will check the registry settings and look for a bad redirector
on Windows servers and workstations. Version 5.0.E and above installs the Net Check program in the BINS folder. Each
time PROMAS is loaded the program will execute and report any errors. If PROMAS is not installed on the server, copy
NCHECK.EXE to the server and run it there.
When the main screen comes up, click the Test Registry Settings button. The message window will indicate whether
the settings on that machine are correct or not for running PROMAS. If any of the settings are incorrect, Net Check can
be used to make the necessary corrections to the registry. You should get approval from your network administrator
before making any changes to the registry.
PROMAS Landlord Software Center support @ promas.com Sales 888-591-5179
311D Maple Avenue West sales@promas.com Support 703-255-1400
Vienna, V A 22180 website: promas.com Support 800-397-1499
Fax on Demand: 703-255-5164 FAX 703-255-9172
5/2002 Network - 4 #321INSTALLATION ON A NETWORK
1. Read the setup instructions in full.
2. Follow the BDE setup instructions for all computers.
3. Follow the PROMAS setup instructions for each computer.
4. Run the Net Check program on each computer to test for potential setup problems.
5. Run the Network Utilities in PROMAS.
BDE SETUP ON SERVER AND WORKSTATIONS
1. Run the BDE Configuration Utility (C:\IDAPI\BDECFG.EXE).
2. Choose Paradox in the Driver Name list.
3. Set NET DIR to the root directory of the server drive. UNC path names are not allowed. Both the workstation and
the server must point to the same physical network directory and the path name must be letter for letter the same
with the exception of the drive letter. If you do not want to provide access to the root directory of the server, you may
create a directory specifically for network locking and point the NET DIR there. DO NOT POINT THE NET DIR
to the PROMAS data files. See below for BDE NET DIR Examples.
4. Click on the System tab.
5. Set LOCAL SHARE to TRUE.
6. Save the changes.
BDE NET DIR Examples (Do not type in the quotes “”)
THE FOLLOWING EXAMPLES ARE CORRECT:
1. Server NET DIR = “C:\”, Client NET DIR = “F:\”
2. Server NET DIR = “D:\”, Client NET DIR = “H:\”
3. Server NET DIR = “C:\LOCKS”, Client NET DIR = “F:\LOCKS”. In this case, “C:\LOCKS” is a directory
specifically created for BDE network locking.
THE FOLLOWING EXAMPLES ARE INCORRECT:
1. Server NET DIR = “C:\RPROMAS”, Client NET DIR = “F:\”. This is wrong even if “F:\” is mapped to
“C:\RPROMAS”. The names must match letter for letter with the exception of the drive letter.
2. Server NET DIR = “C:\”, Client NET DIR = “\\SERVER\”. UNC path names are not allowed.
BDE NET DIR Most Common Setup
This is the situation most commonly found on a network. The PROMAS files are kept in a directory on the file server.
This directory is “C:\RPROMAS” on that machine (APROMAS if you are using the association version). Other ma-
chines on the network refer to the “C” drive of this machine as “F”. The following would be the NET DIR settings:
1. On the server, the NETDIR should be set to “C:\” (do not type in the quotes).
2. On each workstation, the NETDIR should be set to “F:\”.
Some network administrators do not like to give access to the root directory of the server. In this case a new directory
should be created called “C:\LOCKS” on the fileserver. (DO NOT USE C:\RPROMAS OR ANY OF ITS
SUBDIRECTORIES AS THE NET DIR). In this case we recommend that the workstations still map a drive letter to the
root directory of the server. The settings in this case would be:
1. On the server, the NETDIR should be set to “C:\LOCKS” (do not type in the quotes).
2. On each workstation, the NETDIR should be set to “F:\LOCKS”.
WINDOWS 95/98/NT
1. Follow the instructions for BDE Setup outlined above.
2. Run the Net Check program.
3. Check for the IPX/SPX protocol. See the section titled “Microsoft Network Issues” for more details.
PROMAS Landlord Software Center support @ promas.com Sales 888-591-5179
311D Maple Avenue West sales@promas.com Support 703-255-1400
Vienna, V A 22180 website: promas.com Support 800-397-1499
Fax on Demand: 703-255-5164 F AX 703-255-9172
5/2002 Network - 5 #321Setting the Working Directory
From the logon screen at each workstation, point the working directory to the server. At the PROMAS Logon
screen click the path above the Database field. That will bring up the Select Working Directory screen. Select the server
drive from the Drive box. Select the folder containing the PROMAS data folder. That path, i.e. F:\RPROMAS, must
display in the box below the word Directories. Click Save.
If you cannot locate the network drive from the selection form, use Windows Explorer or the File Manager to
determine if you have a connection to the network drive. If you do not, please contact your network technician for help in
properly setting up your workstation to recognize the file server’s drive.
Checking Directory Settings
Go to Help, About. The settings should be as follows:
Working Directory - F:\RPROMAS where F is the network server drive. It points to the root folder containing the
registration files and the database folder(s).
Data Directory - F:\RPROMAS\DATA where "DATA" refers to the folder contains the active database.
Local Directory - C:\RPROMAS\TEMP - if other than this call tech support.
Network Directory - F:\ where F is the network server drive. All workstation must point to the same location.
Network Utilities
The network utilities test writes to and reads from the Server. If the Quick Test checkbox is marked, one hundred
records are written to the server drive. If unmarked, 2,000 records are written. Upon completion an information box will
display the results.
If the test fails, a network card, hub or cabling is a prime suspect. If the test passes, it means that no errors were
detected during the test. Run the network utilities regularly if you are experiencing what you suspect to be network errors.
Run the network utilities test
· At each workstation, sign on to PROMAS and go to File, Network Utilities.
· Mark the Stand Alone Test radio button and then click the Begin Workstation Test button.
To test all workstations simultaneously
· At the first workstation mark the First Workstation radio
· At the other workstations (except the last) mark the Additional Workstation radio button
· At the last workstation mark the Final Workstation radio button, click the Begin Workstation Test button.
If the test fails, contact your network administrator.
WHAT SHOULD BE BACKED UP
To protect your data, you must backup on a regular basis. This is especially important as you start using the system
because there is usually a lot of one time data entry that you would not want to repeat.
If you are using PROMAS Landmaster, you should be backing up the files in your working directory (usually
C:\RPROMAS), and your data directory (usually C:\RPROMAS\DATA). If you are using multiple databases, you need
to back up all of the data directories you use.
If you are using PROMAS Association, you should be backing up the files in your working directory (usually
C:\APROMAS), the common directory (usually C:\APROMAS\COMMON) and your data directory (usually
C:\APROMAS\DATA). If you are using multiple databases, you need to back up all of the data directories you use.
If you would like information on our recommended backup schedule, please call our Fax on Demand at 703-255-5164
and get the “Recommended Backup Method” document (#230).
PROMAS Landlord Software Center support @ promas.com Sales 888-591-5179
311D Maple Avenue West sales@promas.com Support 703-255-1400
Vienna, V A 22180 website: promas.com Support 800-397-1499
Fax on Demand: 703-255-5164 FAX 703-255-9172
5/2002 Network - 6 #321TROUBLESHOOTING
If you experience problems that require troubleshooting, please contact technical support. Make sure that you
have the most current information that is available.
Problem: Intermittent Network Problems
Make sure that your Microsoft server (95, 98, or NT) is not left running 24 hours a day, 7 days a week. Microsoft
operating systems are not stable enough to run without rebooting from time to time. It is highly recommended that you shut
down your server at least once a week. If people need nighttime access, you should shut down the server and reboot after
performing your daily backup.
Recovering from a Power Failure or Workstation Crash
It is not normal for workstations to lock up or reboot themselves when operating on a network. If this is a frequent
problem for you, please contact technical support and ask for assistance with a network problem.
To recover from a crash or power failure:
1. All users must log off of PROMAS.
2. Rebuild the Indices, Reference Files, and General Ledger from <<File, Database Utilities>> to confirm that
your data has not been damaged and repair any damaged indices. If you have a large database, you may want to
consult with technical support on how to turn off the “Local Share” option in the BDE to significantly speed up the
rebuild.
Problem: Index Out of Date, Key Violation, or BLOB Corrupt Errors
1. Verify that no workstation is using the IPX/SPX compatible protocol. See the section titled “Microsoft Network
Issues” for more details.
2. Verify that every Windows 95/98/NT workstation has a good redirector. See the section titled “Microsoft Network
Issues” for more details. The Net Check program described previously can be used to quickly test for a bad
redirector.
3. Make sure the necessary registry changes have been made on every workstation. See the section titled “Microsoft
Network Issues” for more details. The Net Check program can be used to quickly test to see that the correct
registry entries have been made.
4. If you corrected any of the problems mentioned in steps 1-3, rebuild all the indices, reference files, and general
ledger to fix the indices and make sure your data was not corrupted. If your workstations were all correctly set up,
proceed to step 5.
5. Another possible cause of data corruption is a bad network card or cable connection. If problems persist after all the
setup instructions have been followed, hardware problems are usually the cause. Some users have reported network
card problems using 10/100 cards that are set to autodetect. You can have your network or computer technician try
jumpering these cards to the speed to be used on the network. If the problem seems related to a particular worksta-
tion, you can try replacing the network card on that workstation; if the problem occurs at every workstation (after
being tested one at a time alone with the server) you can try replacing the network card on the server. If you cannot
locate the problem, contact technical support and indicate that you need assistance with a network problem.
6. If you cannot resolve the problem, you should stop using the database on a network to avoid corrupting the data. If you
must continue to work with the errors, make frequent backups and keep several copies of backups until the problem
is resolved.
PROMAS Landlord Software Center support @ promas.com Sales 888-591-5179
311D Maple Avenue West sales@promas.com Support 703-255-1400
Vienna, V A 22180 website: promas.com Support 800-397-1499
Fax on Demand: 703-255-5164 FAX 703-255-9172
5/2002 Network - 7 #321Problem: Multiple Net Files in Use Error
You did not correctly set up the BDE. Review the BDE Setup section and examples and verify that all your workstations
have been correctly set up. If you need further assistance, contact technical support and indicate that you need assistance
with a network problem.
Problem: Network Initialization Failed Error
1. Verify that the workstation is connected to the network drive by using Windows Explorer to see if the network drive
is visible.
2. Check to make sure that your workstation has read and write access to the directories specified in the error
message. A quick way to test for access rights is to use the Windows Notepad (usually in <<Start, Programs,
Accessories>>) or a word processor to save a file in the directory in question. If the word processor or Notepad
cannot save the file, you do not have access rights to that directory. In this case you need to contact your network
administrator to make sure each workstation has the necessary access rights.
3. Fax-on-Demand document #265 contains information on how to determine if you have lost your network drive map-
ping and need to reestablish it.
Problem: Another User Has Exclusive Control to the Database
1. This is a correct message if another user is performing database utilities. When database utilities are being run, no
other users are allowed access to the system.
2. If you receive this message after a workstation has locked up it usually means that the server has not released the
locks held by that workstation. If you wait (approximately 10 minutes) the server should release the locks. If it
doesn't, try #3 below.
3. Try rebooting the file server. MAKE SURE YOU NOTIFY YOUR NETWORK ADMINISTRATOR BEFORE
DOING THIS.
Problem: SPOOL32 Errors
This is a known problem with the Windows operating system. If you experience SPOOL32 errors, please search for the
word “SPOOL32” in the Microsoft Knowledge Base available at www. microsoft.com. There are several articles about
problems with SPOOL32.
Problem: Occasional or Frequent Lockups
1. Follow the instructions for recovering from a power failure at the start of this troubleshooting section.
2. If you experience occasional or frequent lockups and are using a screen saver or a virus detection program, you
should try disabling one or both of these programs. Some virus detection programs are known to have bugs that cause
them to lock the system when the screen saver activates.
3. On rare occasions lockups, general protection faults, and other problems have been traced to bad video cards or
drivers. Make sure you have current drivers for your video cards.
4. Bad memory or a bad motherboard may also cause lockups.
Problem: Access Denied Error After Successful Logon
If you experience this problem from a Windows 95 workstation connected to an NT server, see the section titled
“Microsoft Network Issues” for details on the “Windows 95 File Locking Bug”. Otherwise, please contact technical
support and indicate that you need assistance with a network problem.
PROMAS Landlord Software Center support @ promas.com Sales 888-591-5179
311D Maple Avenue West sales@promas.com Support 703-255-1400
Vienna, V A 22180 website: promas.com Support 800-397-1499
Fax on Demand: 703-255-5164 FAX 703-255-9172
5/2002 Network - 8 #321