Running Freezerworks using Citrix? Keep these in mind:
- Limit the number of clients to 15-20 per physical server. This is not per virtual machine, but physical hardware.
- There is a problem with clipboard sharing. If you notice that rdpclip.exe is using up 99% of resource kill it using the task manager. If it is a repeat issue the administrator can disable it in the terminal services settings.
- A default printer should be set explicitly. Don’t rely on Citrix to dynamically set one.
There cannot be any spaces in the entire path in which Freezerworks Server is installed.
Yes. Contact Dataworks Customer Support for more information.
Freezerworks Basic and Freezerworks Unlimited Server broadcast from Port 19813. This port must be open in firewalls so that users may connect via the Freezerworks Client software.
Freezerworks Unlimited Version 5.0.01 and later also uses ports 19812 and 19814.
Yes, a desktop computer can be used as a server. However, it must be used strictly as a server, and not as a workstation, as that will very likely slow down program access unacceptably.
Ensure that TCP/IP is installed on both the client and server machines. Versions of Freezerworks later than 5.4x and 2.x in FUL do not support IPX/SPX.
Verify that Freezerworks Server is installed and loaded only once on the server.
Generally, client/server connection problems do not occur when the systems are on the same subnet. However, to be certain, the server’s IP address may be added directly to the Connection to 4D Server settings on the client. Select the Custom tab and enter a name and the server’s TCP/IP address, and then click OK. Connect to the server by double clicking the new server name, or highlighting it and clicking OK.
Ping the server by typing the command “ping IP address” at the DOS command prompt, where “IP address” is the server’s IP address. If the ping is not successful, contact your IT support staff for assistance. If you are using Mac OS, and you are communicating with your server via AppleTalk, check whether both machines can see any network devices (file servers and printers). If you can see these devices from both the client and the server, try deleting the 4D folder inside your SystemPreferences folder on the client.
If the client and the server are not on the same subnet, then the server must have a static IP address. This address must be entered directly on the client workstations by following the directions above. If entering the server’s IP address does not solve the problem, it also might be necessary to enter Freezerworks Server’s port number. The port number is 19813. Add the port number by placing a comma and the port number, without any spaces, after the IP address (e.g., NN.NNN.NNN.NNN,19813).
Occasionally, resource files get corrupted. Locate the files “Freezerworks*.res”, and “Freezerworks*.rex” on the client’s system. On Windows clients, they are stored in the Windows system folder (e.g., Winnt4DFreezerworksUL2). On Macintosh clients, they are stored in the System folder (e.g, SystemPreferences4DFreezerworks*). Delete all RES and REX files, and then try connecting to Freezerworks again. For more information, see Error -10001. The connection to the database has been disrupted
Freezerworks 2017 server must be installed on Windows, but Freezerworks clients can be installed on either Windows or Macintosh. A client workstation just needs to be able to “see” the server using a network protocol.
This indicates a network connection problem. Verify that Freezerworks Server is running and connected to the correct Freezerworks database. If Freezerworks Server is running, check the network cable and connections on the client workstation.
Check with the network administrator to see if any changes have been made to the network that can disrupt access to the server. Sometimes, when new firewall software is installed, permissions may not be set properly to allow access to the server by the client in question.
Occasionally resource files get corrupted. Locate files “Freezerworks.res”, and “Freezerworks.rex” or “FreezerworksUL.res” and “FreezerworksUL.rex” on the client’s system. They are stored in the Windows system folder (e.g., Winnt4DFreezerworks or Winnt4DFreezerworksUL). Delete all RES and REX files. Then try connecting to Freezerworks again.
You can set the service to log on as a specific user, or as the Local System account. If you choose to log on as the Local System account, you also will have the option to “Allow service to interact with desktop”. With this option checked, the Freezerworks Server program will be visible on the server, and you will be able to configure backups, see which users are logged into Freezerworks, etc.
Note that if you don’t check the option “Allow service to interact with desktop”, Freezerworks Server will be running in the background. You will need to stop the service and open Freezerworks Server as an application if you need to configure any Freezerworks options (backup, cache settings, etc.)
- Verify that the path name containing the Freezerworks Server application has no spaces in it. Replace any spaces with an underscore “_” if necessary.
- If you decide to start the service logged on as a specific user, note the Account Login Name and Password used to log into the server PC. If you log on as a specific user, Freezerworks Server will be running in the background. You will need to stop the service and open Freezerworks Server as an application if you need to configure any Freezerworks options (backup, cache settings, etc.)
- Verify there is a default printer assigned to the Account used to log into the server PC. It is not necessary to have a printer attached to the server; Freezerworks Server only requires a printer in the Printers folder.
- Start the Freezerworks Server application.
- Select File-Register as Service. If this option is greyed out, close the server application, then right click on the server icon and select “Run as Administrator.” When the server application opens the option should now be active.
- Select File-Quit.
- Select Control Panel-Administrative Tools-Services from the Windows Start menu.
- Right-click 4D Server: Freezerworks* and select Properties. Switch to the Log On tab.
- To run the service as a specific user, click the radio button for “This Account.” Enter the Account User Name and Password used to log onto the server PC. Click OK to exit the service properties. Warning: Be sure to define a valid Windows account in the “Log On As” area. In addition, this user account must have access to a printer; otherwise an error message will be displayed.
- To run the service as the Local System account, Click the radio button for “Local System account”. You can check the “Allow service to interact with desktop” box. This will allow the Freezerworks Server to be visible on the screen, so you can configure backups, see which users are logged on, etc.
- Click OK to exit the service properties. Note that if you don’t check the option “Allow service to interact with desktop”, Freezerworks Server will be running in the background. You will need to stop the service and open Freezerworks Server as an application if you need to configure any Freezerworks options (backup, cache settings, etc.)
- Right-click 4D Server: Freezerworks and select Start.
If Freezerworks Server starts without error, exit and return to the Services dialog. You may then change 4D Server: Freezerworks’ Properties to Startup type: Automatic.
If an error displays indicating that there is no default printer set, stop the service. Go to Settings-Printers, and confirm that at least one printer exists. If there are no printers, add a local printer. It is not necessary to have a printer attached to the server; Freezerworks Server just needs to see a printer in the Printers folder. After adding a printer, return to step 9 above and Start the service.
You cannot change the service registration status of Freezerworks Server from within Freezerworks Server if the application has been launched as a service when Windows was started. In this case, the three menu items are disabled. To stop the service, use the Windows Services Control Panel.
Warning: The full pathname for your database structure file (Freezerworks.4dc) cannot exceed 250 characters.
Freezerworks Server and Client may cause spikes in, or a constant elevation of, CPU Usage. In Freezerworks Server, go to Edit – Preferences and highlight Application-Client/Server. In the Client/Server Communication section, remove the checkmark in the “Register Clients at Startup For Execute On Client” box. Quit Freezerworks Server, and then restart Freezerworks Server. CPU Usage should idle at <10%. Upon Freezerworks Client connection, usage may rise as high as 50-60% during intense processing routines (e.g., Import Samples and Searches).
(Windows and MacOS9) For versions earlier than Freezerworks Unlimited 3.1 and Freezerworks Basic 6.0: If Client/Server performance seems slow, check the application memory setting on the server. Select Edit-Preferences in the Freezerworks Server window. Click the Application icon on the left. Confirm the Application Main Memory is set to at least 4 blocks of 32768 kb. Increase the number of blocks to dedicate more RAM to the Freezerworks Server application.
Another idea to improve performance is to increase the Cache Size. See the section Database Cache Memory in the System Administrors Guide.
Poor performance using Windows Server 2000, 2003:
Windows Server 2000 and 2003 can be configured for use as a file server, which means it will try to allocate as much memory as possible to the file system cache.
Since 4D has its own cache that it manages for itself, you can end up with “dueling caches” which can cause very slow performance, especially after doing things like a full system backup. During the backup (and depending on the backup software you use), Windows may be caching every file as it gets read, which will force 4D’s cache into virtual memory. You’ll have to restart 4D Server or perhaps even reboot the box to get its cache out of the swap file and regain good performance from 4D Server.
So the solution is to tell Windows not to aggressively cache the file system. Here’s how to do it in Windows Server 2003:
- Right click on My Computer and select Properties.
- Click on the Advanced tab
- In the Performance panel, click Settings
- In the Performance Options dialog, click to the Advanced tab
- In the Memory Usage panel, change System Cache to Programs (or Applications).
- And as long as you’re in this dialog, note the Processor Scheduling panel directly above the Memory Usage panel. If you’re running 4D Server as a service, mark the option to favor Background Services. If you’re not running 4D as a service, mark the option to favor Programs (or Applications).