Clients may fail to connect to the server after entering a password

Workstations can fail to connect to the FirePoint server when Windows 2000 / XP permissions do not allow users access to FirePoint folders and files.  But even if your Windows permissions are correctly set there may still be intermittent connection problems on isolated PC's using FirePoint 6 and FirePoint 6.5.  These isolated problems should now be resolved with the release of FirePoint 7.  Here's the complete story.

Initial Checklist

Default Printer - Each FirePoint client workstation as well as the server PC should have at least one installed print driver.  A default printer driver should be selected under Start/Control Panels/Printers.

No third-party server backup - Never allow FirePoint server to be backed-up by a third party backup system, including tape back-up.  Outside backup software can corrupt FirePoint and make it unstable until it's upgraded.

Shortcuts - Make sure shortcut icons have simple names.  Avoid space characters in shortcut titles.  Shortcuts should always start the application in the application folder.  Right-click and select "Properties" to determine where the shortcut starts the application.

.res / .rex - If you are using FirePoint Server 6.06 or 6.56 delete the Fire_PS.res and Fire_PS.rex located at C:\Windows\ACI or C:\WinNT\ACI.  These files contain forms downloaded from the server.  These files can sometimes get corrupted.  Both files will automatically regenerate when the client workstation checks back into FirePoint.  The ACI folder has been eliminated in FirePoint 2003.

mem.opt - Delete any mem.opt file located at C:\Windows\ACI or C:\WinNT\ACI.  If you find an mem.opt file then delete the 4DNCMEM.dll file in the "Network" folder (inside the ACI folder) as well.  These files are only used to run 4D Client and 4D Server on the same PC.  The ACI folder has been eliminated in FirePoint 2003.

Required Windows Permissions

If you are using FirePoint Server 6.06 or 6.56 all FirePoint users must have "Full Privileges", expressly granted within C:\Windows\ACI or C:\WinNT\ACI.  Those privileges must extend to all subfolders located in the ACI folder.  The ACI folder has been eliminated in FirePoint 2003.

If FirePoint works well with an Administrator's Windows 2000 / XP log-on, but fails to work with other Windows 2000 / XP log-ons, check for permissions issues.  Remember users must be able to read and write to the Client executable folder as well as to the FirePoint application folder on the server.

It is possible for a particular user's profile to become corrupt.  If you experience problems with FirePoint only under one Windows 2000 / XP logon, then you should consider replacing the user's Windows profile.

FirePoint 7 Changes

FirePoint 7 has eliminated many old "plug-ins" which were used to augment FirePoint programming.  Client log-on problems may have occurred because of subtle incompatibilities between these older plug-ins and newer Windows operating systems.

Also, FirePoint 7 uses a new strategy for starting FirePoint's Command Window.  In beta testing, FirePoint 7 has eliminated intermittent FirePoint log-on problems in all upgraded installations.