0

LogicNets Installation: Troubleshooting On-Premise Installations

  • updated 1 yr ago

Description

In the event the LogicNets application is not working correctly after an on-premise installation, please read through the list of troubleshooting tips below. If your system still exhibits operational issues, please raise a ticket in our Support Portal or contact your LogicNets representative for further assistance.

Troubleshooting Tips

The following tips may help you identify common installation issues and how to fix them.

1. IIS Logs
If you have set up LogicNets and are using an IIS webserver it may be configured incorrectly for LogicNets. Review the IIS log files for any error codes. Take corrective action yourself or include the logs in your request to LogicNets Support.

2. File Upload Problems
Problems with the File Upload feature in LogicNets, including importing projects in the Designer or the Package Installer upload, are typically identified by a File Too Large error message. IIS has several parameters that can constrain the File Upload process. If the IIS default values do not provide sufficient bandwidth, then we suggest increasing the maximum values for the following IIS settings:
 

 


3. Error 404 - Page Not Found
If users receive a browser message that says Error 404 - Page Not Found, you may have entered the URL incorrectly in IIS. In general, the login URL for login is https://<yourdomain>/<company>. The long version of the above "friendly" URL is https://<yourdomain>/<company>/logicnets.lns?verb=start&code=logon. One common mistake during IIS setup is including "www" in the URL: https://www.

4. System Busy Message
When LogicNets displays the system busy message in a popup window with a black screen, it means that the system is too sluggish to run the LogicNets engine successfully. This could be because of one or more factors, including the following:

  • The connection through the internet/intranet has insufficient capacity.
  • The server on which the LogicNets Engine is running has insufficient resources, like CPU or RAM.
  • The number of concurrent users is higher than expected for the system resources and performance levels required.
    This is a common issue when clients go from design/testing and smaller user base to PRODUCTION roll out when the user base is typically expanded, or when launching larger projects with larger data sets typical of production use.
  • A Designer user has modelled a continuous loop in a logicnet path.
  • A Designer user has turned on the debug mode.

Determine the number of users active on the system and what activities are taking place. Refer to the Installation articles in this Support Center for system requirements. If a Designer user has modeled an infinite loop the IIS webserver generally has a timeout setting of 1-2 minutes that will reset the and kill the loop.


5. Error 500
If you try to log in to LogicNets and receive an Error 500 browser message this is most frequently the result of incorrect IIS configuration settings.

  • Check the path to the logicnets.exe file.
  • Verify that the correct sections of IIS are unlocked.
  • Verify that Visual Studio C 2013 redistributable has been installed.
Reply Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
Like Follow
  • 1 yr agoLast active
  • 31Views
  • 1 Following

Home