Troubleshoot General Issues

Tip: You can check the version of Loftware Enterprise SP and obtain information about its components, the Loftware Application Server, and your Loftware Enterprise SP license (including the integrations allowed) by clicking Help Help > About.

Symptom Resolution

A Security service not available message is displayed.

This message indicates that you are unable to connect to the database used by Loftware Enterprise SP. This may be because you do not have the necessary permissions, because the server is offline, or because your network connection has failed.

Error #2032 is displayed on the sign in page for Loftware Enterprise SP or a GC overhead limit exceeded error message is displayed elsewhere in Loftware Enterprise SP.

These error messages indicate that a problem has caused all available memory or processor resources to be consumed. Contact Loftware Technical Support for assistance.

Time values entered in hours, minutes, or seconds do not produce the intended effect.

See Time Values in Loftware Enterprise SP.

Data appearing on the printed label was not what was expected.

See Troubleshoot Label Data Sources.

Labels are not printed in the expected layout.

See Troubleshoot Layouts.

Users cannot see, open, or select a label template, folder, user, or other object.

See Troubleshoot Access Control (Permissions).

Users cannot print using a label template or process.

See Troubleshoot Access Control (Permissions).

Users cannot sign in to Loftware Enterprise SP.

In a Loftware Enterprise SP environment with distributed services, all Loftware Application Servers that are online must be accessible to each client computer. For example, a firewall should not be blocking a client computer's network access to any Loftware Application Server.

While users are active, the Loftware Enterprise SP session expires and users are signed out.

Active users may be suddenly signed out for the following reasons:

  • An administrator has manually signed out users. For more information, contact your administrator or see Managing User Sessions.
  • If you are using an Amazon Web Services (AWS) HTTPS load balancer, make sure you configure the "idle timeout" setting in the load balancer to be 120 seconds or longer.